2 Answers
- Newest
- Most votes
- Most comments
1
I've seen the same issue too - I found this discussion which suggests it's a console bug only and the workaround is to use CLI. https://www.reddit.com/r/aws/comments/qcbgfr/option_to_create_aurora_read_replica_of_rds/
1
This could be a good use case for DMS with continuous replication:
- use DMS for ongoing replication
- move read endpoints to Aurora
- move write endpoints to Aurora
https://docs.aws.amazon.com/dms/latest/sbs/chap-manageddatabases.mysql2rds.replication.html
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 4 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago