Actions, recommendations, and best practices

AWS will not move data between Regions, meaning that data placed in Frankfurt (or any other AWS Region) will remain within the specified Region, unless the customer organizes cross-region Replication or data movement. If there is no personal data in the AWS Cloud, the customer can work with data in the AWS Cloud as usual (as suggested in Approach 2). Additional data residency considerations can be found in the Data Residency: AWS Policy Perspectives whitepaper.

This requirement is addressed in the following reference architectures:

2.1 Big Data and analytics, and machine learning use cases
2.2 Local IdP for authentication flow and storing user data
2.3 Industrial IoT with AWS IoT Greengrass
2.4 Website scenario with API engine and DBMS in on-premises data center
3.1 Disaster recovery with elastic disaster recovery
3.2 Read-replicas in Amazon RDS from on-premises databases

Warning Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

Approach 2 – no personal data in AWS

REQ2 – Measures to prevent unauthorized or accidental access