Skip to content

Fix hardcoded security group ID and suggested improvement for SSL mode handling for RDS #2

@malbaugh

Description

@malbaugh

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions