Fix hardcoded security group ID and suggested improvement for SSL mode handling for RDS
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, postgresql, shell
- Domain
- cloud, databases, documentation
Research direction
Locate the migration script's SECURITY_GROUP_ID definition and the documentation describing the --tls flag. Trace how replication-instance creation receives the security group, then review the RDS SSL guidance. Done means the script no longer depends on the author's account-specific ID, users can supply one if needed, and the documentation accurately explains TLS for RDS.
Written by the indexing model from the issue text.
Description
Issue
While running the migration script, I encountered the following error:
An error occurred (InvalidParameterValueException) when calling the CreateReplicationInstance operation: The provided security group identifier or name is invalid. Please verify and provide a valid security group identifier or name.
After some investigation, I found that the script includes a hardcoded SECURITY_GROUP_ID, which is specific to the original author’s AWS environment. This ID will not exist in other users’ accounts and causes the script to fail unless updated manually.
Suggested fix
- Remove the hardcoded
SECURITY_GROUP_ID, or - Allow users to optionally pass in their own security group ID.
- In my testing, omitting the security group entirely worked fine.
Thanks for your work on this project!
P.S. in the docs, you note that users migrating from Neon must use the --tls flag. This is likely true for all RDS users as well. Alternatively, they could set the parameter rds.force_ssl to 0.
- Dominant language
- Shell
- Stars
- 32
- Forks
- 9
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from planetscale/migration-scripts
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
planetscale/migration-scripts#26 · 1 comment ·
All issues in planetscale/migration-scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·