A company hosts a dynamic web application on Amazon EC2 instances behind Application Load Balancers (ALBs) in the us-west-2 and eu-west-1 Regions. The application is accessed by users globally. The company wants to improve application performance by minimizing transit path latency, packet loss, and jitter. Additionally, they must implement stateless network filtering to block a list of known malicious IP ranges at the subnet boundary before the traffic reaches the ALBs.
Which two options should the solutions architect choose to meet these requirements?
- Deploy AWS Global Accelerator and register the ALBs in both Regions as endpoints.Answer
- Configure Network ACLs on the subnets where the ALBs are deployed with deny rules for the malicious IP ranges.Answer
- CCreate Amazon Route 53 records with latency-based routing policies that point directly to the ALB in each Region.
- DAdd inbound rules to the ALB security groups to explicitly deny traffic from the malicious IP ranges.
- EEstablish a single AWS Site-to-Site VPN connection from the users' networks to the VPCs to route the application traffic.
Answer
Deploying AWS Global Accelerator to route traffic over the AWS backbone network and configuring Network ACLs on the ALB subnets to statelessly block malicious IP ranges.
The combination of deploying AWS Global Accelerator and configuring Network ACLs meets all constraints. AWS Global Accelerator improves application performance for global users by routing traffic over the optimized AWS global backbone, which minimizes latency, jitter, and packet loss. Network ACLs provide stateless network filtering at the subnet boundary, allowing the solutions architect to create deny rules to block the specified malicious IP ranges before the traffic reaches the Application Load Balancers.
Step-by-Step Solution
Key Concept
Combining AWS Global Accelerator for optimized global routing with Network ACLs for stateless edge subnet security filtering.