What must you do to comply with this requirement for a web based profile management application running on EC2?
Run EC2 instances in multiple AWS Availability Zones in single Region and leverage an Elastic Load Balancer with session stickiness to route traffic to the appropriate zone to create their profile
Run EC2 instances in multiple Regions and leverage Route 53’s Latency Based Routing capabilities to route traffic to the appropriate region to create their profile
Run EC2 instances in multiple Regions and leverage a third party data provider to determine if a user needs to be redirect to the appropriate region to create their profile
Run EC2 instances in multiple AWS Availability Zones in a single Region and leverage a third party data provider to determine if a user needs to be redirect to the appropriate zone to create their profile
Explanations:
Running EC2 instances in multiple Availability Zones within a single Region does not ensure compliance with data residency requirements, as data could still leave the EU if the application is not designed to handle data correctly. Additionally, session stickiness does not address data localization.
Running EC2 instances in multiple Regions (one in the EU and one in the US) and using Route 53’s Latency Based Routing allows the application to direct users to the appropriate region based on their location, ensuring that EU data remains in the EU and US data remains in the US, thus complying with the data residency requirements.
Leveraging a third-party data provider for routing based on user location introduces unnecessary complexity and potential latency. Additionally, running EC2 instances in multiple Regions alone does not ensure compliance without properly managing data residency.
While using multiple Availability Zones within a single Region might provide some level of availability, it does not address compliance with data residency as it does not separate data based on geographic location. Using a third-party provider does not resolve the fundamental issue of ensuring data does not leave the required region.
If memory serves me right, the answer is:
Run EC2 instances in multiple Regions and leverage Route 53’s Latency Based Routing capabilities to route traffic to the appropriate region to create their profile