Amazon Aurora MySQL now supports multi-source replication and delayed replication
- Announced
- Tags
- amazon-aurora
- Severity
- info, set by
reef/rss-rule-v1 - Source
- https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-aurora-mysql-multisourcerep-delayedrep/
<p>Starting today, Amazon Aurora MySQL supports two new replication capabilities: multi-source replication and delayed replication. Multi-source replication lets a single Aurora MySQL cluster replicate from multiple source databases at the same time, making it easier to consolidate data from separate MySQL databases. This enables critical use-cases, such as merging shards or aggregating data from separate databases (e.g. regional or departmental instances) into a central location for operational workflows, such as reporting and backups. To learn more, please refer to the <a href="https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source.html" target="_blank" rel="noopener noreferrer">MySQL multi-source replication documentation</a>.<br> <br> Delayed replication lets you configure a binlog replica to intentionally lag behind its source by a set period of time, giving you a simple safeguard against human error and logical data corruption. If a harmful change is made on the source, you can recover quickly by stopping replication to the replica before the change is applied and promoting it, without performing a full database restore. A delayed replica also provides a convenient fallback during upgrades and a way to inspect an earlier state of your data. To learn more, please refer to the <a href="https://dev.mysql.com/doc/refman/8.4/en/replication-delayed.html" target="_blank" rel="noopener noreferrer">MySQL delayed replication documentation</a>.<br> <br> Together, these capabilities give you greater flexibility and stronger data protection when replicating into Aurora MySQL. Multi-source replication and Delayed replication are supported on Aurora MySQL version 8.4.8 and higher, in all <a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.RegionsAndAvailabilityZones.html#Aurora.Overview.Availability.MySQL" target="_blank" rel="noopener noreferrer">AWS Regions</a> where Aurora MySQL is available. For additional information on Aurora MySQL disaster recovery, see the <a href="https://docs.aws.amazon.com/solutions/disaster-recovery-using-amazon-aurora/" target="_blank" rel="noopener noreferrer">guidance from our solutions library</a>. To learn more, please refer to <a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.84Updates.html" target="_blank" rel="noopener noreferrer">Aurora MySQL 8.4</a> release notes.<br> <br> <a href="https://aws.amazon.com/rds/aurora/" target="_blank" rel="noopener noreferrer">Amazon Aurora</a> is designed for high performance and availability at global scale with full MySQL compatibility. It provides scale-to-zero serverless compute, Aurora Global Database for multi-Region resilience, Aurora I/O-Optimized for improved price performance on I/O-intensive workloads, and built-in security and continuous backups. To get started, take a look at Aurora’s <a href="https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html" target="_blank" rel="noopener noreferrer">getting started page</a>. </p>
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.