2 回答
- 最新
- 投票最多
- 评论最多
1
For people who encountered this error, I believe this is an error in Management Console. Before they fix this, you can create a read replica for a RDS instance in EC2 Classic properly with AWS command line.
Example Command:
aws rds create-db-instance-read-replica --profile xxxx --db-instance-identifier xxx --source-db-instance-identifier xxx --db-instance-class db.m3.medium --storage-type standard --no-multi-az --publicly-accessible --no-auto-minor-version-upgrade
Command Reference:
已回答 2 年前
0
The VpcId is the identity of the VPC to create the replica within. It is possible that the engine version you are using is not supported in EC2 Classic. See the documentation for determining this. You may have to move your RDS to a VPC.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceNotinaVPC.html
已回答 2 年前
相关内容
- 已提问 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
Hi, thanks for the help. This RDS instance (m3.large, MySQL 5.6.34) is already inside EC2 Classic so I believe it is supported . Since EC2 classic is still in support, this feels like a RDS issue to me. Do you have any suggestion what I can do next ?
Have you tried using the CLI/API?