- Newest
- Most votes
- Most comments
AWS have documented this here: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Procedural.Exporting.NonRDSRepl.html, however, this isn't really for continuous use, only to export from RDS for MySQL to an external non RDS Database.
If you would like to do this on an ongoing basis to external MySQL databases from an RDS MySQL instance - then consider looking at the AWS Data Migration Service.
Hi,
You should use RDS read replicas for what you what to achieve: https://aws.amazon.com/rds/features/read-replicas/
It's designed to allow multiple copies of your database to be distributed on different RDS instances.
Best,
Didier
Question is about using multiple non-RDS read replicas (hosts running MySQL on WIndows) with RDS being the master. Multiple RDS read replicas are available when they are all RDS.
You can use mysql multi source replication.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-multi-source-replication.html
The question is about replicating with RDS as the source, not multiple sources too RDS.
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
My replication needs to be connected 24/7 to sync the changes whenever they are new changes. Using AWS DMS to run a task 24/7 isn't go to be a cost unsustainable cost? If so, mabe my option is to sync myself with a listener script, right?