Skip to content

PATTERN Cited by 1 source

Data boundary recovery

Shape

Keep backup data and the recovery data plane at an approved in-country location, typically an on-premises site with AWS Outposts, while using a different parent AWS Region for service-control-plane operations. Replication can use AWS DataSync for S3 data or database-native MySQL binlog/PostgreSQL logical replication. (Source: sources/2026-08-13-aws-recovery-strategies-to-meet-data-residency-requirements)

Why the control-plane distinction matters

Outposts-hosted EC2, RDS, and S3 data-plane resources serve local-network access, but their provisioning/configuration operations depend on the selected parent Region. Choosing a parent different from the primary avoids a shared control-plane failure; maintaining highly available parent-Region connectivity avoids treating Outposts as a disconnected platform.

Preconditions

  • Residency policy permits an out-of-country parent control plane while requiring local data placement.
  • The selected Outposts service subset supports the workload.
  • Replication lag meets the recovery budget.
  • Recovery tests simulate primary-Region loss while proving that the parent control plane can launch/reconfigure the local environment.

Trade-offs

The pattern preserves physical data locality and a familiar AWS resource model, but adds on-premises facility, capacity, replication, and connectivity operations. It does not provide strict local operational autonomy.

Seen in

Last updated · 622 distilled / 1,953 read