AWS AmazonRDS documentation change
Summary
Clarified synchronization requirements during Aurora Global Database switchover by specifying that only the target secondary cluster (not all secondary clusters) must be synchronized with the primary before switchover.
Security assessment
The change corrects documentation about synchronization scope during disaster recovery procedures but does not address a security vulnerability or introduce security-related content. It improves accuracy of operational steps without direct security implications.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.md b/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.md index 8d76e984a..b3328c6c5 100644 --- a//AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.md +++ b//AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.md @@ -79 +79 @@ You can perform managed cross-Region switchovers with Aurora Global Database onl -During a switchover, Aurora makes the cluster in your chosen secondary Region be your primary cluster. The switchover mechanism maintains your global database's existing replication topology: it still has the same number of Aurora clusters in the same Regions. Before Aurora starts the switchover process, it waits for all secondary Region clusters to be fully synchronized with the primary Region cluster. Then, the DB cluster in the primary Region becomes read-only. The chosen secondary cluster promotes one of its read-only nodes to full writer status, which allows that secondary cluster to assume the role of primary cluster. Because all secondary clusters were synchronized with the primary at the beginning of the process, the new primary continues operations for the Aurora global database without losing any data. Your database is unavailable for a short time while the primary and selected secondary clusters are assuming their new roles. +During a switchover, Aurora makes the cluster in your chosen secondary Region be your primary cluster. The switchover mechanism maintains your global database's existing replication topology: it still has the same number of Aurora clusters in the same Regions. Before Aurora starts the switchover process, it waits for the target secondary Region clusters to be fully synchronized with the primary Region cluster. Then, the DB cluster in the primary Region becomes read-only. The chosen secondary cluster promotes one of its read-only nodes to full writer status, which allows that secondary cluster to assume the role of primary cluster. Because the target secondary cluster was synchronized with the primary at the beginning of the process, the new primary continues operations for the Aurora global database without losing any data. Your database is unavailable for a short time while the primary and selected secondary clusters are assuming their new roles.