Amazon Web Services SOA-C02 Online Access

To optimize the routing of requests to the application for users in different geographic locations, use Amazon Route 53's latency-based routing:

Latency Routing Policy: Modify the Route 53 DNS settings for app.anycompany.com by changing the routing policy to latency. This policy routes user requests to the server that has the lowest latency relative to the user's location.

Configure Latency Records: Create latency records for each ALB—one for the ALB in us-west-2 and another for the new ALB in ap-southeast-2. Route 53 will automatically direct traffic to the endpoint that provides the lowest latency connection to the user.

Seamless User Experience: By using latency routing, the URL remains the same (app.anycompany.com), but the backend service location varies based on which endpoint is likely to respond the fastest. This setup provides a seamless experience for users, reducing latency without requiring any changes to how they access the application.

This method leverages Route 53's advanced DNS capabilities to ensure optimal performance and user experience by dynamically routing traffic based on geographic latency considerations.

To identify who is creating the Elastic IP addresses, the following steps should be taken:

Enable CloudTrail Logging:

Ensure AWS CloudTrail is enabled to log all API activities in your AWS account.

If you're using AWS Organizations, check the service control policies for any statements that explicitly deny Amazon S3 access. In particular, check the service control policies for statements denying the s3:PutBucketPolicy action.

If EC2 instances in one region (eu-central-1) need to access a database in another (us-east-1), and the database must remain only in us-east-1, the most operationally efficient solution is a VPC peering connection.

From the VPC Peering documentation:

Inter-Region VPC peering enables routing of traffic between VPCs in different AWS Regions using private IP addresses, without VPN or additional hardware.

Also:

You must manually update security group rules to allow traffic from the peered VPC.

So:

Create the VPC peering

Add the private IP range of the remote EC2 instances to the inbound rules of the database’s security group