Pain Point

Data Residency

The legal and regulatory requirement that data must be stored and processed within specific geographic boundaries, impacting how S3 buckets, replication policies, and compute resources are deployed across regions.

5 connections 3 resources

Summary

What it is

The legal and regulatory requirement that data must be stored and processed within specific geographic boundaries, impacting how S3 buckets, replication policies, and compute resources are deployed across regions.

Where it fits

Data residency constraints shape the physical architecture of S3-based systems. They determine which AWS regions can host buckets, whether cross-region replication is permitted, and how multi-region lakehouse designs must partition data to comply with jurisdiction-specific regulations.

Misconceptions / Traps
  • S3 region selection is not just a latency optimization — it is a legal decision. Storing EU personal data in a US region may violate GDPR regardless of technical access controls.
  • S3 Cross-Region Replication (CRR) can inadvertently copy data to a non-compliant region. Replication rules must be audited against data residency requirements.
  • Data residency applies to backups, logs, and metadata too. Storing CloudTrail logs or Glue Catalog metadata in a different region than the data itself may violate residency requirements.
Key Connections
  • scoped_to S3, Object Storage — geographic constraints on S3 storage
  • enables Sovereign Storage — data residency drives sovereign storage adoption
  • constrains Active-Active Multi-Site Object Replication — replication must respect residency boundaries
  • enables Compliance-Aware Architectures — residency is a core compliance requirement

Definition

What it is

The regulatory requirement that data must be stored and processed within a specific geographic jurisdiction, constraining where S3 buckets can be located and how data can be replicated.

Connections 5

Outbound 3
Inbound 2

Resources 3