- Newest
- Most votes
- Most comments
I was able to get the parameter group changed and verified using the AWS RDS CLI tool. Once the change was made via the CLI, the UI still DID NOT reflect the changes.
I am going to sum this up to a UI/Javascript bug in the AWS console.
How to do it via CLI:
aws rds modify-db-cluster --db-cluster-identifier {your-cluster-id} --db-cluster-parameter-group-name {your-cluster-parameter-group-id} --apply-immediately
Then restart cluster (also something I cannot do in the UI)
aws rds reboot-db-cluster --db-cluster-identifier {your-cluster-id}
Guides:
CLI tool install: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html#getting-started-install-instructions
CLI tool configuration: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-quickstart.html
There is a parameter group option for the DB instances (writer/reader nodes), which is different from the DB cluster parameter group. If you select one of your DB instances, and choose Modify, you can see the two parameter group options. Here is an example for an Aurora DB instance:
If you want to change the parameter group for the DB instances (writer/reader nodes), then you must update the second field DB parameter group
.
If you've created an RDS DB cluster/instances and initially just used the default parameter groups, you can see the two different types of parameter groups automatically created (DB cluster parameter group
and Parameter groups
which is for DB instances).
See below example for aurora-mysql8.0 default parameter groups:
More information about RDS parameter groups can be found here: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html
Relevant content
- asked 5 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
There is no "Modify" option when dealing with RDS Multi-AZ MySQL Cluster DB instances (non-aurora). What you provided may work for an Aurora DB instance, but does not work for the new mysql (non-aurora) cluster nodes.
Example screenshot: https://docs.aws.amazon.com/images/AmazonRDS/latest/UserGuide/images/multi-az-db-cluster-instance-actions-console-postgresql.png