# DDoS Mitigation

DDoS mitigation combines traffic filtering, distributed capacity, and resilient architecture to keep services available during distributed denial-of-service attacks.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/ddos-mitigation

> Distributed denial-of-service attacks use many sources to exhaust network bandwidth, connection capacity, or application resources. Mitigation matches defenses to the threatened layer, rejects malicious traffic before it reaches constrained resources, and preserves access for legitimate users.

Practice exams covering DDoS Mitigation: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of DDoS Mitigation

Effective DDoS mitigation combines layer-appropriate edge defenses, protected origins, controlled resource consumption, and tested operational response.

1. **Threat-specific defense selection**: Identify whether an attack threatens bandwidth, protocol state, or application processing. Select upstream network mitigation for floods and HTTP-aware controls for application request abuse rather than assuming one filter addresses every layer.
2. **Distributed edge absorption**: Use distributed ingress, managed DNS, and caching to reduce the concentration of traffic on regional resources. Filter attacks before they reach links or systems whose capacity cannot expand quickly.
3. **Origin bypass prevention**: Ensure that attackers cannot reach the application through an unprotected public endpoint. Use private connectivity where supported or combine origin network restrictions with verification of the intended edge distribution.
4. **Selective application controls**: Apply rate limits, request validation, and suitable challenges to expensive or abused endpoints. Tune aggregation keys and thresholds to avoid penalizing shared-IP users or legitimate automation.
5. **Bounded resource consumption**: Combine caching and scaling with concurrency limits, timeouts, and load shedding. Protect downstream dependencies and recognize that accepting more requests can increase both outages and costs.
6. **Measured incident response**: Baseline normal behavior and correlate edge traffic with application health before changing controls. Maintain response procedures, escalation contacts, and visibility into false positives, protection coverage, and financial exposure.

## Cloud services for DDoS Mitigation

Use Route 53 for resilient DNS and select an ingress service that fits the application protocol. For web applications, CloudFront reduces origin traffic through caching, while AWS WAF filters abusive HTTP requests. For TCP or UDP applications, Global Accelerator supplies distributed network ingress without HTTP-specific inspection. Shield provides network and transport-layer DDoS protection, with Advanced capabilities available for eligible protected resources. These services complement rather than replace origin restrictions, resilient application capacity, and monitoring. Verify protection enrollment, inspect traffic that still reaches the origin, and tune application controls against legitimate usage patterns.

- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: Shield Standard automatically provides baseline protection against common network and transport-layer DDoS attacks. Shield Advanced adds enhanced capabilities for eligible resources enrolled in protection, including response assistance and DDoS-related cost protection subject to applicable conditions.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: AWS WAF inspects HTTP and HTTPS requests at supported integration points and applies rules such as rate-based controls, request matching, and challenges. It helps mitigate application-layer floods but is not a substitute for upstream volumetric protection.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFront distributes HTTP and HTTPS ingress across edge locations and caches eligible responses to reduce origin load. Combining it with AWS WAF and origin access restrictions makes the edge an effective enforcement point rather than a path attackers can bypass.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Route 53 provides distributed authoritative DNS infrastructure with built-in DDoS defenses. It helps keep DNS resolution available, but DNS resilience alone does not protect an application's public endpoints.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: Global Accelerator provides static anycast entry points for TCP and UDP applications and routes traffic over the AWS global network to healthy endpoints. It benefits from Shield Standard protection and supports Shield Advanced protection, but does not provide HTTP request inspection or content caching.

## DDoS Mitigation exam questions

Real practice exam questions on DDoS Mitigation, with the correct answer and its explanation.

### Question 1 (SAA-C03)

**Question:**

A company runs a public ticket-sales application behind an Application Load Balancer (ALB). The ALB is protected by AWS Shield Advanced and has an associated AWS WAF web ACL. During ticket releases, legitimate request volumes increase sharply. Recent application-layer DDoS attacks have used changing source IP addresses, making manually maintained IP block lists ineffective.

The company wants a managed solution that identifies application-layer DDoS attacks, automatically deploys attack-specific blocking rules, and removes those rules when the attacks end. The operations team must not need to create rules for each attack.

Which solution meets these requirements?

**Correct answer:** Enable Shield Advanced automatic application-layer DDoS mitigation for the ALB and configure its rule action to Block.

**Explanation:** Shield Advanced automatic application-layer DDoS mitigation uses AWS WAF to deploy rules tailored to detected attacks. In Block mode, these rules mitigate matching attack traffic. Shield Advanced manages the rules throughout the attack lifecycle and removes attack-specific rules when they are no longer needed.

### Question 2 (SCS-C03)

**Question:**

A company delivers a public HTTPS application through Amazon CloudFront. The origin accepts application traffic only from this distribution. Before a major product launch, a security engineer reviews two anticipated attacks:

• UDP reflection and TCP SYN floods directed at the distribution's public endpoints.
• Distributed HTTPS floods against POST /availability/check. These requests contain valid application data but trigger expensive origin processing. Each attacking IP address is expected to send more than 1,000 requests per minute. Legitimate traffic, including users behind shared NAT addresses, does not exceed 100 requests per minute per viewer IP address to this endpoint.

The company needs upstream mitigation of common network-layer attacks and an application-layer control that reduces abusive requests before they reach the origin. Other application endpoints must not contribute to the request-rate calculation. The company does not require DDoS cost protection or specialist response-team access.

Which strategy meets these requirements with the LEAST operational overhead?

**Correct answer:** Use the distribution's included network-layer protection. Associate an AWS WAF web ACL with the distribution and configure a blocking rate-based rule aggregated by viewer IP address, with a 1-minute evaluation window and a limit of 300 requests. Scope the rule to POST requests to exactly /availability/check.

**Explanation:** CloudFront benefits from AWS Shield Standard protection against common network- and transport-layer DDoS attacks. The scoped AWS WAF rate-based rule addresses the separate application-layer threat by counting requests per viewer IP only for the expensive endpoint. Its approximate threshold is above the stated legitimate rate and below the anticipated attacking rate. No additional subscription or custom mitigation automation is needed.

### Question 3 (DOP-C02)

**Question:**

A company operates a public TCP service behind an internet-facing Network Load Balancer (NLB). The service uses a proprietary binary protocol and cannot be moved to an HTTP-based endpoint. The NLB spans three Availability Zones and has one explicitly allocated Elastic IP address in each zone. Application instances have only private IP addresses.

During recent attacks, rapidly changing sources generated SYN floods and high-volume traffic against the service. The company requires enhanced resource-specific DDoS detection, upstream mitigation, and access to AWS DDoS response specialists. Application connectivity must remain unchanged.

A DevOps engineer must integrate protection enrollment into the infrastructure deployment pipeline so that every address through which clients reach the NLB is covered, including addresses added during future Availability Zone expansion.

Which solution meets these requirements?

**Correct answer:** Subscribe to AWS Shield Advanced. After each NLB deployment or update, reconcile its Elastic IP allocation IDs with Shield Advanced protections and create a protection for each unprotected Elastic IP address.

**Explanation:** Shield Advanced supports protecting an NLB through its associated Elastic IP addresses. Registering every NLB Elastic IP provides enhanced detection and mitigation for the public network entry points, along with access to the Shield Response Team. Reconciling the allocation IDs during deployment also covers addresses introduced by Availability Zone expansion without changing the service protocol or connectivity.

## Practice DDoS Mitigation in a full exam

Questions on DDoS Mitigation in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 4 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 2 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is DDoS Mitigation

DDoS mitigation protects availability when many sources simultaneously send traffic intended to overwhelm a service. The constrained resource might be an internet connection, a connection-tracking table, a web server, or a database behind an apparently inexpensive API request. Successful mitigation is not simply blocking high traffic volumes: it requires distinguishing attack traffic from legitimate demand and keeping critical business functions usable.

Choose edge defenses according to the anticipated attack. Volumetric attacks, including reflection and amplification attacks, attempt to saturate bandwidth and require upstream filtering or a sufficiently distributed provider edge. Protocol attacks, such as SYN floods, target connection establishment and network state. Application-layer attacks use HTTP requests that can resemble legitimate activity but exhaust expensive operations such as searching, authentication, or report generation. A web application firewall can inspect HTTP requests, but it does not replace network-layer DDoS protection.

Cloud architectures typically place managed edge infrastructure in front of regional application resources. A content delivery network distributes incoming requests and serves cacheable responses without contacting the origin. Managed authoritative DNS reduces dependence on a small, self-managed DNS deployment. For non-HTTP applications, a distributed network entry point can provide an appropriate protected path without relying on HTTP-specific controls. Multi-zone application capacity improves resilience, but it cannot compensate for an unprotected upstream bottleneck.

For example, an online store can cache product images and public catalog pages at the edge while applying application-layer rate controls to login and search endpoints. Requests to checkout may require separate thresholds because legitimate customers have different usage patterns there. Request aggregation can use IP addresses or other supported attributes, but IP-only limits can penalize users behind shared NAT gateways, while a widely distributed botnet may remain below each individual IP threshold. Challenge mechanisms must also account for API clients that cannot execute browser challenges.

Prevent attackers from bypassing the protected entry point. Where supported, use private origins; otherwise restrict origin network access and verify that requests arrive through the intended distribution. Merely changing the public DNS record to point at a CDN does not protect an origin that remains directly reachable. Security groups and network ACLs reduce exposure, but rules close to the application cannot recover bandwidth already saturated farther upstream.

In AWS scenarios, distinguish automatic network and transport-layer protection from configurable HTTP filtering and enhanced incident-response capabilities. AWS Shield Standard provides baseline protection automatically, while Shield Advanced adds capabilities for eligible protected resources, including enhanced detection, response assistance, and conditional DDoS-related cost protection. AWS WAF supplies application-layer controls. Do not assume that purchasing enhanced protection automatically enrolls every resource, configures application-specific rules, or eliminates all attack-related charges.

Capacity and operational controls remain essential. Autoscaling can absorb some demand, but scaling alone can increase costs or move the bottleneck to a database. Use caching, bounded concurrency, timeouts, and load shedding to limit work per request. Monitor request rates, error rates, latency, cache hit ratios, and backend saturation together. During an incident, inspect edge logs and mitigation metrics, check for origin bypass, and tune rules cautiously to avoid blocking legitimate traffic. Maintain an escalation runbook and conduct testing only within provider policies and authorization requirements.

## Learn DDoS Mitigation in lessons

3 short lessons on DDoS Mitigation in 3 certification courses.

- SAA-C03: DDoS Mitigation: matching defenses to attack layers (Premium), https://app.blowstack.com/lessons/ddos-mitigation-matching-defenses-to-attack-layers-saa-c03
- SCS-C03: DDoS Mitigation: matching edge defenses to attack layers (Premium), https://app.blowstack.com/lessons/ddos-mitigation-matching-edge-defenses-to-attack-layers-scs-c03
- DOP-C02: DDoS Mitigation: Automated layered ingress defenses (Premium), https://app.blowstack.com/lessons/ddos-mitigation-automated-layered-ingress-defenses-dop-c02
