Amazon RDS, Amazon Aurora, AWS RDS Weekly — 2026-03, Week 10
Editor’s Note
This week’s coverage centers on cross-cloud database migration workflows, unconventional approaches to testing against production data, and physical security incidents that underscore infrastructure dependencies beyond the control plane. AWS published detailed guidance for migrating Cloud SQL for MySQL to Aurora and RDS, while the community explored database proxy architectures and bidirectional infrastructure-as-code models.
Top Stories
Cross-Cloud MySQL Migration via AWS DMS
AWS has released official documentation covering the migration of Cloud SQL for MySQL 8 and later versions to Amazon Aurora MySQL-Compatible and Amazon RDS for MySQL using AWS Database Migration Service over Site-to-Site VPN. The guidance addresses environment preparation and cross-cloud connectivity configuration, targeting practitioners moving workloads from Google Cloud to AWS. Separately, community discussions highlight the longer-term challenge of maintaining synchronized data across services, observing that optimizing for immediate performance at the expense of modularity introduces synchronization debt as schemas evolve over time. Read more
Database Proxy for Testing Against Production Data
The Mori project introduces a proxy architecture that allows developers to test code changes against live production data by routing read queries to production while directing writes to a local shadow database. The implementation classifies queries at the AST level, generates collision-free primary keys, and implements four independent safety layers to prevent accidental production writes. This approach addresses the operational risk of testing against current production state without requiring data snapshots or synthetic datasets. The project is available on GitHub
Bidirectional Infrastructure-as-Code Synchronization
Autoschematic introduces a push-pull state model for infrastructure management that enables automatic import of existing resources and bidirectional synchronization to resolve configuration drift. Unlike traditional declarative infrastructure-as-code tools that enforce one-way state, this model targets environments where configuration drift is common, such as Snowflake deployments where manual changes frequently occur outside the provisioning workflow. The architecture treats infrastructure state as a mutable entity requiring active reconciliation rather than enforcement. More details
Releases
AWS Database Migration Service now supports migration from Cloud SQL for MySQL 8 and later to Amazon Aurora MySQL-Compatible and Amazon RDS for MySQL 8 and later over AWS Site-to-Site VPN. Guidance available
Security and Compliance
Amazon Web Services reported impacts to data centers in the Middle East region due to physical objects, with restoration timelines estimated at a minimum of one day according to Business Insider reporting. Separately, Rest of World reports that Iranian drone strikes targeted Amazon data center sites, raising questions about physical security requirements for cloud infrastructure facilities in geopolitically sensitive regions. Further coverage
Worth Reading
https://aws.amazon.com/blogs/database/from-bottlenecks-to-breakthroughs-dutchies-database-migration-journey/
Case study documenting a database migration addressing performance bottlenecks.
https://aws.amazon.com/blogs/database/automating-amazon-rds-backup-and-maintenance-windows-for-daylight-saving-time-shifts/
Guidance for automating RDS backup and maintenance window adjustments during daylight saving transitions.
https://github.com/psrth/mori
Database proxy enabling safe testing against production data with write isolation.