- Newest
- Most votes
- Most comments
It seems RDS console issue with the version which is no longer able to launch new Aurora MySQL cluster(e.g. Aurora MySQL version1). Please try with AWS CLI to add new Reader instance
aws rds create-db-instance --db-instance-identifier READER_INSTANCE_IDENTIFIER --db-cluster-identifier DB_CLUSTER_IDENTIFIER --engine aurora --db-instance-class DB_INSTANCE_TYPE --region YOUR_REGION
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/rds/create-db-instance.html
Yes, I was able to add a reader via the CLI. So I agree, it appears to be a console issue.
No I was not able to reproduce on the console. You must have run into some sort of boundary condition which cannot be debugged without looking at logs or without having a clearly reproducible set of steps. I agree, the Aurora service team should fix an issue. The only thing I was trying to point out is I am not aware of a mechanism other than through support to bring the issue to the attention of the service team. Will try to find out internally.
OK. Yutaka informed me that this issue is reproducible only with older versions of MySQL and is a known issue and a ticket has been opened internally for it. Thanks Yutaka.
In which region is this? I could not reproduce the issue in us-west-2 region. You will need to open a Support case so Customer Support can take a look at what the issue is.
This is in us-east-1. I'm not on a paid support plan so I can't open a ticket. The javascript error is getting thrown by js running as part of the RDS console. Presumably that's something the RDS team would be interested in knowing about and fixing regardless of whether I happen to be paying extra for support or not.
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
FWIW I also see similar javascript errors and an empty DB instance class select menu, when just selecting an existing aurora mysql instance and clicking the modify button. I was able to create a reader instance from the CLI. So this seem to be an issue with the RDS console itself and not the underlying aurora functionality.