- Newest
- Most votes
- Most comments
Hello.
As far as I know, you can't have a read replica as a source database.
About two years ago, I had a failed attempt to use an Aurora MySQL read replica as a source database with DMS.
https://repost.aws/knowledge-center/dms-binary-logging-aurora-mysql
To use change data capture (CDC) with a full-load and CDC or CDC-only AWS DMS task, turn on binary logging on the source DB writer instance. Use the writer instance because read replicas don't support CDC operations. For more information, see Limitations on using a MySQL database as a source for AWS DMS.
The same conversation is taking place in the following thread:
https://repost.aws/ja/questions/QUtMkQjrd5QIej-tpyjh0hhw/you-cant-use-aurora-my-sql-replicas-as-a-source-for-aws-dms-unless-your-dms-migration-task-mode-is-migrate-existing-data-full-load-only
Aurora supports reader nodes. These are read only instances that are connected to the same Aurora storage volume as the writer node. Other RDS engines such as mysql and postgres support read replicas which are distinct instances that replicate from binary logs or wal logs from their source instance. RDS read replicas could be configured as the source of DMS but an Aurora reader node cannot.
