3.3.1.12. Data Sovereignty and Data Residency Controls
3.3.1.12. Data Sovereignty and Data Residency Controls
💡 First Principle: Residency is about where data is stored and processed; sovereignty is about whose rules apply and who can control or access the data and the operations around it. A design can meet one and fail the other.
Residency controls (location):
- Pick Regions deliberately. AWS does not move customer content out of the Regions you choose, but features you enable can: S3 Cross-Region Replication, DynamoDB global tables, Aurora global databases, AWS Backup copy rules, KMS multi-Region key replicas. Keep each of them pointed at approved Regions; for in-country disaster recovery use two Regions in the same country (for example
ca-central-1andca-west-1in Canada). - Region deny: an SCP that denies requests where
aws:RequestedRegionis outside the approved list must exempt global services (IAM, Organizations, Route 53, CloudFront, Support and others) withNotAction, or administrators lose those services. The Control Tower Region deny control (landing zone or OU level) ships with those exemptions. SCPs do not apply to the management account. - Control Tower data residency controls (elective, per OU) close paths that Region deny cannot see because the call is made in an allowed Region: disallow cross-Region networking (VPC peering, Transit Gateway peering, CloudFront distributions, Global Accelerator; it also blocks same-Region peering), disallow VPN connections and disallow internet access for customer-managed VPCs.
- Keys: use the condition key
kms:ReplicaRegionin key policies and SCPs to limit wherekms:ReplicateKeymay create multi-Region replicas. - No Region in the country: AWS Outposts (with S3 on Outposts) or Local Zones keep data processing in-country. Outposts EBS snapshots go to the parent Region by default; create EBS local snapshots (stored in S3 on Outposts, schedulable with Data Lifecycle Manager) and enforce them with IAM policies.
- Detect drift: Config rules or conformance packs and Security Hub CSPM controls flag resources that break the rules.
Sovereignty controls (control and access):
- Key control: customer managed KMS keys with key policies you own and audit in CloudTrail; a CloudHSM custom key store for single-tenant HSMs; a KMS external key store when keys must stay in your own HSMs outside AWS, so revoking the proxy's access makes the data unreadable in AWS.
- Operator access: the AWS Nitro System is designed with no mechanism for AWS operators to access customer data in EC2 instance memory or storage.
- Operational sovereignty: the AWS European Sovereign Cloud (generally available January 2026; first Region in Brandenburg, Germany) is physically and logically separate from other Regions as its own partition. It is operated by EU-resident personnel, and its metadata (IAM, billing) stays in the EU. Choose it when rules require EU-only operation and control, not just EU storage.
| Requirement wording | Likely answer |
|---|---|
| "Data must be stored and processed only in country X" | Region selection, Region deny, replication limits, in-country DR Region |
| "We, not the provider, must control decryption" | Customer managed keys; XKS for keys outside AWS |
| "Operated only by EU-resident staff, separate from global infrastructure" | AWS European Sovereign Cloud |
| "No Region in the country" | Outposts / Local Zones with local snapshots |
⚠️ Exam Trap: CloudFront geographic restrictions control which viewers can fetch content; they say nothing about where data is stored. Encryption is not residency either: an encrypted snapshot in a foreign Region still left the country.