This article outlines a secure, scalable pattern for transferring a single tenant's data between isolated Amazon Aurora MySQL clusters in separate AWS accounts. By utilizing Amazon S3 as an intermediary touchpoint and implementing a table-level parallel export/import strategy, the approach avoids direct VPC networking requirements and enables resilient, retriable data migrations.
Key points
Avoid direct network paths between production and non-production accounts by using Amazon S3 as a secure, regional staging area.
Improve operational reliability by replacing monolithic dump-and-load jobs with granular, per-table parallel exports and imports.
Use Aurora database cloning to perform isolated data extraction without impacting the primary production instance's performance.
Implement cross-account staging bucket access via IAM and encryption policies to maintain security while moving sensitive tenant data.