Cloud concept · Updated

Data Residency - Data residency is the geographic location where data is stored and, when applicable requirements specify it, processed.

In short

Data residency connects the physical location of data to legal, contractual, and organizational requirements. Cloud architectures must account for primary databases, replicas, backups, logs, and downstream systems because choosing a deployment Region alone does not establish compliance.

Cloud Concepts Hub →

6 key aspects of Data Residency

Effective data residency requires explicit geographic rules, complete data-flow coverage, enforceable controls, and recovery plans that stay within approved boundaries.

01
Explicit geographic boundaries

Define permitted countries, territories, or Regions for each data classification. Distinguish storage requirements from any additional restrictions on processing, access, or transfers.

02
Complete lifecycle coverage

Include replicas, backups, snapshots, caches, exports, and deletion workflows in the residency design. A compliant primary database does not compensate for an unauthorized copy elsewhere.

03
Residency-aware logging

Map audit, network, host, and application logs from their sources through ingestion, analysis, and archival storage. Check subscription destinations and external security tools because telemetry can contain regulated information.

04
Layered enforcement and evidence

Combine organization policies, deployment checks, configuration monitoring, and audit records. Region restrictions alone do not prove that every service operation or downstream transfer respects the required boundary.

05
Jurisdiction and compliance distinctions

Evaluate physical location separately from applicable law, contractual commitments, and provider compliance scope. Encryption and provider certifications support a compliance program but do not independently satisfy residency requirements.

06
Recovery within approved locations

Choose replication and disaster-recovery destinations that meet the same geographic requirements as production. Where restrictions prevent cross-Region recovery, document the resulting availability and recovery limitations.

Cloud services for Data Residency

Use AWS Organizations to establish regional guardrails, then configure regional storage and logging destinations that match the approved geography. Amazon S3 can hold application objects and audit archives, while CloudWatch Logs supports operational log ingestion and analysis. CloudTrail supplies AWS activity records, with its collection scope and destination evaluated independently. Review replication, subscriptions, exports, and external integrations across these services to identify transfers outside the boundary. AWS Artifact supports compliance assessment with provider reports and agreements, but configuration evidence and documented data flows are still needed to demonstrate that the workload meets its own requirements.

Amazon S3Amazon S3

Regional S3 buckets provide explicit storage destinations for application data, audit logs, and archives. Review replication rules, exports, and downstream consumers to ensure that additional copies remain in approved locations.

AWS CloudTrailAWS CloudTrail

CloudTrail records AWS account activity and can deliver trail logs to a selected S3 bucket. Evaluate collection scope separately from storage location because a multi-Region trail can consolidate events from different Regions into one destination.

AWS OrganizationsAWS Organizations

Service control policies can restrict many operations outside approved Regions across member accounts. Policies using aws:RequestedRegion need careful handling of global services and operations with cross-Region effects; they are not a complete residency guarantee.

AWS ArtifactAWS Artifact

AWS Artifact provides access to AWS compliance reports and certain agreements that support assessment of provider controls. Review the relevant service and geographic scope alongside customer-specific obligations rather than treating a report as proof that a workload satisfies residency requirements.

Data Residency exam questions

Real practice exam questions on Data Residency, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIF-C01

A company is auditing the storage locations of AI training datasets inherited from an acquired business. Policy permits storage only in an approved list of AWS Regions. The datasets are stored in Amazon S3, and some buckets have replication enabled. Other processing and data flows have already been verified. Bucket names and tags identify intended locations, but the company needs evidence of the actual locations of the datasets and their replicas. Which approach provides the required evidence?

Show answerCORRECT ANSWER

Retrieve each source bucket's configured AWS Region, inspect its replication destinations, and verify the Region of every destination bucket against the approved list.

The actual Regions of the source and destination buckets establish where these dataset copies are stored. Inspecting replication destinations ensures that the audit covers replicas rather than only the original datasets.

MLA-C02 (beta)

A healthcare company is migrating a PostgreSQL database that stores patient observations and clinician-provided labels for ML training. The ingestion application uses SQL joins, foreign keys, and transactions that update multiple tables. The company wants a managed database that preserves these capabilities. Compliance requires all database copies and backups to remain in one approved AWS Region. If an Availability Zone fails, the database must recover automatically without losing acknowledged transactions or requiring application-managed failover. Which storage configuration best meets these requirements?

Show answerCORRECT ANSWER

Deploy Amazon RDS for PostgreSQL as a Multi-AZ DB instance deployment in the approved Region. Keep automated backups and any snapshot copies in that Region.

A Multi-AZ DB instance deployment synchronously replicates to a standby in another Availability Zone and provides automatic failover. This protects acknowledged transactions during an Availability Zone failure while preserving PostgreSQL functionality. Keeping database copies and backups in the approved Region satisfies the stated residency requirement.

SAP-C03

A pharmaceutical company stores clinical records in Amazon S3 in eu-central-1. Its research team uses an analytics platform hosted outside the European Union. A contractual requirement prohibits clinical records and patient-level query results from leaving eu-central-1. Only outputs produced by a compliance-approved aggregation process may be transferred to the external platform.

The aggregation process suppresses small cohorts and removes patient-level information. Researchers must be able to submit analysis parameters, but must not be able to modify the process or execute arbitrary code with its permissions. Temporary files and failed-job outputs can contain clinical records. Separate controls already prevent cross-Region replication and unauthorized infrastructure changes.

Which architecture meets these requirements?

Show answerCORRECT ANSWER

Run the approved aggregation process in eu-central-1 through a broker that accepts only validated analysis parameters. Keep source data and intermediate outputs in buckets inaccessible to the external platform. Publish only successfully validated aggregate outputs to a separate release bucket that the external platform can read.

This design places the release boundary after the approved aggregation and validation steps. Researchers cannot replace the processing logic or use its permissions for arbitrary execution. Raw records, temporary files, and failed-job outputs remain inaccessible to the external platform, while only approved aggregates can leave the Region.

Practice Data Residency in a full exam

Questions on Data Residency in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Data Residency

3 min read

Data residency describes where data resides geographically, such as within a country, an economic area, or an approved set of cloud Regions. Requirements can come from legislation, industry rules, customer contracts, or internal policy. Engineers must translate these requirements into explicit boundaries for particular data classes rather than assume that every workload has the same restrictions. For example, a contract might require customer records and associated audit logs to remain within one country while allowing public website assets to be distributed globally.

Residency is related to, but distinct from, data sovereignty and data localization. Sovereignty concerns the laws and jurisdiction applicable to data, while localization generally refers to requirements to keep specified data within a geographic boundary. Physical placement alone does not resolve questions about foreign legal access, remote administration, or international transfers. Privacy laws also do not universally require all personal data to remain in its country of origin; the applicable rules and transfer conditions must be established with legal and compliance teams.

In the cloud, apply residency requirements across the complete data lifecycle. Identify where applications receive and process information, where databases and object stores persist it, and where replicas, snapshots, backups, exports, caches, and analytics outputs go. Select approved Regions and review each service's documented storage and processing behavior. Multiple Availability Zones within a Region can improve availability without introducing cross-Region replication, but their placement must still satisfy the required boundary. Global services, edge caching, support workflows, and third-party integrations need separate assessment.

Logging deserves particular attention because operational telemetry can contain personal information, resource identifiers, request parameters, or application payloads. Identify the required sources, such as cloud API audit events, network flow logs, DNS query logs, operating-system logs, and application logs. Then map each source to its collection Region, ingestion endpoint, storage destination, subscribers, and archive. A workload hosted in an approved Region can still violate a residency policy if its logs are forwarded to a security platform in an unapproved location.

For example, a German-only contractual boundary might require application data, backups, and security logs to use approved resources in the AWS Europe (Frankfurt) Region. A centralized logging account can still be used, provided its storage and processing resources meet that boundary. An AWS CloudTrail multi-Region trail can collect events from multiple Regions into a designated Amazon S3 bucket; its coverage does not mean each event stays in its source Region. Consequently, the log destination and the geographic scope of collection must both be evaluated.

Use preventive controls, deployment validation, and ongoing monitoring together. Organization policies can restrict many operations outside approved Regions, while infrastructure templates can standardize destinations and disable unauthorized replication. In AWS, conditions using aws:RequestedRegion constrain the Region of the requested endpoint, not necessarily every geographic effect of an operation. Global services and cross-Region capabilities require careful exceptions and additional controls. Encryption and access restrictions protect confidentiality but do not change where data resides.

Residency restrictions introduce trade-offs in disaster recovery, service availability, latency, cost, and centralized security analysis. If only one Region is permitted, cross-Region failover may be unavailable unless another location is explicitly approved. Establish recovery objectives that fit the permitted geography, minimize sensitive fields in logs, and validate retention and deletion across copies. Provider compliance reports help assess service controls and their scope, but a provider certification does not automatically make a customer's architecture compliant. The customer remains responsible for selecting appropriate services, configuring data flows, and maintaining evidence that the implemented design meets its requirements.

Learn Data Residency in lessons

12 short lessons on Data Residency in 9 certification courses.

and 6 more lessons

Open the lessons