Geographic and Regional Compliance
You'll learn how to design cloud architectures that respect where data must physically reside and which laws apply based on geographic boundaries.
Why Geography Matters in Compliance
Even in the "borderless" cloud, physical location matters. Many regulations mandate that certain types of data must stay within specific countries, regions, or economic zones. For example, GDPR restricts transferring EU citizen data outside the EEA without adequate safeguards, while Russia's Federal Law 242 requires Russian citizen data to be stored on servers physically located in Russia.
Think of it like handling cash in different countries—you must follow local currency and banking laws wherever the money physically exists, even if your company operates globally.
Data Residency Requirements
Data residency defines where data must be stored geographically. This isn't just about compliance certifications (which you inherit from your cloud provider); it's about physical server location. You must:
- Choose cloud regions within required geographic boundaries
- Verify your provider's actual datacenter locations (not just region names)
- Prevent data from being replicated, backed up, or cached outside allowed areas
Architecting for Geographic Constraints
When designing systems under geographic compliance:
- Region selection: Deploy resources only in compliant regions
- Data classification: Tag and separate data by residency requirements
- Cross-region controls: Block replication, snapshots, or backups to non-compliant regions
- Service verification: Some cloud services process data globally—confirm each service's data flow
- Disaster recovery: Ensure backups and failover regions also meet residency rules
If you need German healthcare data to stay in Germany, you'd deploy to eu-central-1 (Frankfurt), encrypt using KMS keys in that region, disable automated cross-region backups, and document that your DR site is also EU-based.
Key Takeaway: Geographic compliance requires deliberate architecture choices—selecting specific cloud regions, controlling data movement, and ensuring every component (storage, backups, processing) respects physical location requirements mandated by law.