Skip to content

PATTERN Cited by 1 source

Strict local autonomy recovery

Shape

Keep both recovery data and the systems that manage its restoration inside the approved national or local boundary. The two forms are self-managed on-premises infrastructure and a recovery environment on another cloud provider; both must operate without depending on the primary AWS Region during recovery. (Source: sources/2026-08-13-aws-recovery-strategies-to-meet-data-residency-requirements)

Requirements

  • Copy self-managed S3 backups to local storage, for example with DataSync.
  • Ensure on-premises encryption/decryption does not require primary-Region availability.
  • Prove backups restore and workloads operate outside AWS.
  • For a second cloud, explicitly decide whether to restore a compatible workload or activate a reduced-function lifeboat.

Trade-offs

This is the strongest locality/autonomy posture, but it owns the most infrastructure, cryptographic, operational, and testing complexity. It is appropriate when legal policy constrains both the data plane and recovery control plane, not merely where ciphertext is stored.

Seen in

Last updated · 622 distilled / 1,953 read