Question

Difficulty: HardEdge and DDoS Protection

A digital publishing company hosts a subscription-based platform on AWS. The static frontend is stored in an Amazon S3 bucket, and the dynamic subscription API runs on Amazon EC2 instances behind an Application Load Balancer (ALB). During a high-profile release, the platform suffers from a Layer 7 HTTP flood attack targeting the login API endpoint, causing database connection exhaustion. Concurrently, the infrastructure experiences a Layer 4 SYN flood attack that threatens to saturate the internet bandwidth. The company needs to block the application-layer attack, mitigate infrastructure-layer attacks at the network edge, and secure financial protection against EC2 auto-scaling charges incurred during DDoS attacks. Which combination of actions will meet these requirements with the least operational overhead?

  1. A
    Deploy an Amazon CloudFront distribution in front of the S3 bucket and the ALB. Enable AWS Shield Standard on the distribution, and configure AWS WAF on the ALB with custom rate-limiting rules to block the Layer 7 flood and claim automatic credit refunds for resource scaling.
  2. B
    Configure stateless Network Access Control Lists (NACLs) at the VPC boundary to drop traffic from the attacking IP addresses. Enable AWS Shield Advanced on the backend EC2 instances to mitigate the Layer 7 HTTP flood and provide scaling cost protection.
  3. Deploy an Amazon CloudFront distribution in front of the S3 bucket and the ALB. Enable AWS Shield Advanced on the CloudFront distribution and associate an AWS WAF web ACL with a rate-based rule targeting the login endpoint.Answer
  4. D
    Associate an AWS WAF web ACL directly with the ALB to mitigate the Layer 7 attack. Rely on AWS Shield Standard at the ALB to automatically block the Layer 4 SYN flood, and configure AWS Budgets to automatically shut down EC2 instances to prevent scaling charges.

Answer

Deploy an Amazon CloudFront distribution in front of the S3 bucket and the ALB. Enable AWS Shield Advanced on the CloudFront distribution and associate an AWS WAF web ACL with a rate-based rule targeting the login endpoint.
Deploying Amazon CloudFront in front of the S3 bucket and ALB places the entry point of the application at the AWS edge locations, providing a resilient outer layer. Associating an AWS WAF web ACL with a rate-based rule on the CloudFront distribution allows the system to identify and drop Layer 7 HTTP flood attacks targeting the login API endpoint before they reach the origin infrastructure. Furthermore, enabling AWS Shield Advanced on the CloudFront distribution provides dedicated Layer 3 and Layer 4 mitigation, access to the AWS Shield Response Team (SRT), and cost protection to cover scaling charges incurred due to auto-scaling during a DDoS attack.

Step-by-Step Solution

1
Determine the optimal location to place the entry point for DDoS mitigation.
Deploy Amazon CloudFront in front of both the S3 bucket and the Application Load Balancer.
Placing CloudFront at the edge locations ensures that malicious traffic is absorbed and filtered at the AWS network edge before reaching the origin servers.
2
Address the Layer 7 HTTP flood targeting the login endpoint.
Create an AWS WAF web ACL with a rate-based rule matching the login URI and associate it with the CloudFront distribution.
AWS WAF rate-based rules automatically track request rates from client IP addresses and temporarily block IPs exceeding the threshold, neutralizing the Layer 7 flood before it exhausts backend database connections.
3
Apply infrastructure protection and scaling charge safeguards.
Enable AWS Shield Advanced on the CloudFront distribution.
AWS Shield Advanced mitigates Layer 3/4 network and transport layer attacks (such as SYN floods) and provides financial protection to refund auto-scaling costs caused by DDoS-related traffic spikes.

Key Concept

Using Amazon CloudFront combined with AWS WAF and AWS Shield Advanced provides comprehensive edge-based Layer 3/4 and Layer 7 protection, along with financial safeguards against scaling charges.
Estimated Time:2m 30s
Rate this question