Geography and compliance — region, residency, and the regulatory boundaries

Geography and compliance drive hard cluster boundaries. Regional clusters serve users with low latency; data residency requires data to stay in specific regions; sovereignty requires dedicated infrastructure. This lesson walks the regulatory mapping, the operational trade-offs, and the operational discipline.

Geography for latency

flowchart LR
    A[User in EU] --> B[EU cluster]
    C[User in US] --> D[US cluster]
    E[User in APAC] --> F[APAC cluster]

For global users, a single-region cluster produces high latency. Regional clusters place workloads closer to users:

• EU users → EU cluster (low latency for EU traffic).
• US users → US cluster.
• APAC users → APAC cluster.

Global load balancing (Route 53, Cloudflare, Cloud DNS) routes users to the nearest cluster.

The trade-off:

• Latency reduction. Users see <50ms response times from a regional cluster.
• Operational cost. Each region has its own control plane (3 nodes minimum for HA).
• Data replication. State shared across regions requires cross-region replication (expensive, high-latency).

Data residency

flowchart LR
    A[User in EU] --> B["EU cluster, EU database"]
    C[User in US] --> D["US cluster, US database"]
    E[EU user data] --> B
    F[US user data] --> D

Data residency requires that user data stay in the region where it was collected. GDPR (EU), LGPD (Brazil), PIPL (China) all have residency requirements.

The cluster boundary:

• EU users’ data stays in the EU cluster and the EU database.
• US users’ data stays in the US cluster and the US database.
• Cross-region data access is restricted or forbidden by the regulation.

The implementation:

• Regional databases with regional-only access.
• Cluster boundaries aligned with database boundaries.
• Network policies preventing cross-region data flows.

Sovereignty

flowchart LR
    A[Government workload] --> B[Dedicated sovereign cluster]
    C[Sovereign cloud region] --> B
    D[Compliance audit] --> B

Sovereignty requirements (FedRAMP High, classified workloads, sovereign clouds) require dedicated infrastructure:

• FedRAMP High. US government workloads requiring dedicated infrastructure in specific regions.
• Classified workloads. Dedicated air-gapped infrastructure.
• Sovereign clouds. Clouds operated by a country’s nationals within the country’s borders (AWS GovCloud, Azure Government, Google Sovereign Cloud).

The cluster boundary:

• Dedicated cluster with dedicated credentials.
• Dedicated network with no public internet access.
• Dedicated monitoring with no external log shipping.

The regulatory mapping

Each regulation has specific requirements. The discipline is to map the regulation to the cluster boundary explicitly, and to audit the alignment regularly.

The operational trade-offs

flowchart LR
    A["Regional / sovereign cluster"] --> B[Compliance achieved]
    A --> C["Operational cost: high"]
    A --> D["Cross-region replication: complex"]
    A --> E["Latency to data: lower for users in region"]

The trade-offs:

• Compliance achieved. The cluster boundary satisfies the regulatory requirement.
• Operational cost. Each region adds a control plane (3+ nodes). Three regions triples the control-plane cost.
• Cross-region replication. State shared across regions requires replication, which is expensive and adds latency.
• Latency. Users in the region see low latency; users in other regions see higher latency.

The operational failure modes

Geography and compliance boundaries fail for predictable reasons:

• Cross-region data flow. A workload in the EU cluster reads data from the US database. The residency requirement is violated.
• Sovereign cluster on public internet. A classified workload is exposed to the public internet through a misconfigured ingress. The classification is violated.
• Backup in wrong region. A backup of the EU database is stored in the US region. The residency requirement is violated.
• Monitoring data leaves the region. Logs and metrics are shipped to a SaaS monitoring platform in another region. The residency requirement is violated.

Quiz

Production discipline

Geography and compliance in production rest on five non-negotiable elements:

• Map regulations to cluster boundaries. Each regulation has a specific requirement; the cluster boundary must satisfy it.
• Audit data flows for residency. Verify that no data crosses regulatory boundaries. Backups, monitoring, logs are all in scope.
• Sovereign clusters on dedicated infrastructure. FedRAMP, classified workloads, sovereign clouds require dedicated infrastructure.
• Network policies enforce regional isolation. A misconfigured NetworkPolicy allowing cross-region traffic is a compliance violation.
• Document the residency architecture. The architecture diagram must show the regional boundaries, the data flows, and the compliance enforcement.

Geography and compliance are non-negotiable. The discipline is to align the cluster boundaries with the regulatory boundaries and to audit the alignment regularly.