- Newest
- Most votes
- Most comments
Hi,
This is an known issue identified by our internal team and investigation is on going.
I personally have tested that option to create aurora read replica works for below versions through console.
RDS PostgreSQL 12.5 RDS PostgreSQL 9.6.21
For RDS PostgreSQL 12.7, no option presents from the console.
Workaround is to use CLI command:
Use below to create a cluster:
aws rds create-db-cluster --db-cluster-identifier Aurora-cluster --engine aurora-postgresql --db-subnet-group-name <subnet-group-name-here> --replication-source-identifier <source-RDS-instance-arn> --region us-east-1 --engine-version 12.7
Use below to add instances to the cluster via the CLI command:
aws rds create-db-instance --db-instance-identifier <instance-identifier> --db-instance-class <instance-class> --engine aurora-postgresql --db-cluster-identifier <db-cluster-identifier> --region us-east-1
Hope CLI command can help you workaround the issue.
Relevant content
- asked 3 years ago
- Accepted Answer
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
I'm experiencing the same problem from RDS console. and would prefer not to have to resort to CLI in future. is there an ETA on this fix?
I'm experiencing the same problem on 13.4 - I've managed to migrate my Test and Staging databases but not the production one. Any idea when this might be fixed?
Looks like AWS does not care about this issue and no one is going to fix it. What a shame!