Easy ReviewDOP-C02
Security and Compliance17

Shield

Use automatic DDoS protection or configure Advanced resource protection, response support and health-based engagement.

Shield basics

AWS Shield protects applications from distributed denial of serviceAn attack uses many systems to flood a target and prevent legitimate access. (DDoS) attacks.

How it works

  1. Every AWS customer gets automatic protection against common network attacks.
  2. Shield Advanced adds managed protection for chosen resources, for a fee.

Exam cues

  • If the question says DDoS, think AWS Shield; extra protection and support means Shield Advanced.

Remember

  • Standard protection: automatic, no extra cost.
  • Shield Advanced: paid.

Trap: Shield stops DDoS floods; AWS WAF filters web requests such as SQL injection.

From the AWS docs (3)
  • AWS gives automatic protection against common DDoS attacks such as UDP reflection and SYN floods at no extra cost.
  • AWS Shield Advanced is a paid managed service that adds DDoS protection for internet-facing applications.
  • Serving traffic through Amazon CloudFront and Amazon Route 53, which run in edge locations, is an AWS best practice for DDoS resilience because attacks are absorbed at the edge.

Standard and Advanced protection

AWS Shield helps keep applications available during a distributed denial of serviceAn attack uses many systems to flood a target and prevent legitimate access. (DDoS) attack, where many systems flood a target with traffic. Standard protection is automatic. Advanced adds explicitly configured protection for supported resources.

How it works

  1. Shield Standard protects against common network and transport attacks. These target network capacity or connections at layers 3 and 4. Web request floods target the application at layer 7The application layer handles requests such as web queries that can be flooded during an attack..
  2. Subscribe to Advanced and select resources to protect, or apply a Firewall Manager policy. A subscription alone does not enroll resources.
  3. For application protection, use a WAF web access control listA web ACL groups rules that inspect web requests and determine their treatment. (web ACL), which is a collection of request filtering rules. Automatic application layer mitigationA mitigation is a measure that reduces the impact of attack traffic on an application. can count or block attack requests.
  4. Use Advanced reports and CloudWatch metrics to examine events. Protection groups let Shield consider several protected resources together.
Resource Advanced protection target
CloudFront, Route 53, Global Accelerator Distribution, hosted zone, standard accelerator
Application or Classic Load Balancer Load balancer
EC2 instance or Network Load Balancer Associated Elastic IP, a public IP address allocated to your account

Exam cues

  • If the question says common network floods with no additional subscription, think Shield Standard, because its protection is automatic.
  • If the question says automatic WAF changes during a web request flood, think Advanced automatic application layer mitigation, because it manages attack-specific WAF protections.
  • If the question says DDoS-related scaling charges, think Advanced cost protection eligibility, because credits depend on protection and required controls being in place before the attack.

Remember

  • Layers 3 and 4 cover network and transport attacks; layer 7 covers application requests.
  • Advanced protects selected resources, including EC2 and NLB resources through Elastic IPs.
  • For applicable ALB and CloudFront cost protection, configure a WAF rate-based rule in Block mode before an attack.
  • Submit eligible credit requests within 15 days after the attack billing month. Credits apply only to Shield Advanced usage.
  • Shield Advanced: each account subscribes; one fee covers a consolidated billing family, billed to the payer account.

Trap: Subscribing during an attack does not make previously unprotected resources eligible for cost protection.

From the AWS docs (15)
  • A distributed denial of service (DDoS) attack floods a target with traffic from multiple systems and can deny access to legitimate users.
  • Shield Standard automatically protects AWS customers from common network and transport layer DDoS attacks at no additional charge.
  • Network and transport attacks target layers 3 and 4; application layer attacks target layer 7, such as web request floods.
  • Shield Advanced requires a subscription and explicit resource protection, either directly or through a Firewall Manager Shield Advanced policy.
  • Shield Advanced supports CloudFront distributions, Route 53 hosted zones and Global Accelerator standard accelerators.
  • Shield Advanced supports Application and Classic Load Balancers, plus Elastic IP addresses and the EC2 instances or Network Load Balancers associated with them.
  • Shield Advanced uses AWS WAF web ACLs, rules and rule groups for application layer protection.
  • Shield Advanced automatic application layer mitigation can count or block attack requests and manage custom WAF protections.
  • Shield Advanced exposes attack metrics and reports through its console, API and CloudWatch.
  • Protection groups combine protected resources for group-level detection and mitigation; a resource can belong to multiple groups.
  • Shield Advanced cost protection is a service credit process for eligible attack-related charges; resources must have been protected before the attack.
  • For applicable CloudFront and ALB resources, cost protection requires a WAF web ACL with a rate-based rule in Block mode before the attack.
  • Credit requests must be submitted within 15 days after the attack billing month; awarded credits apply only to Shield Advanced usage.
  • Serving traffic through Amazon CloudFront and Amazon Route 53, which run in edge locations, is an AWS best practice for DDoS resilience because attacks are absorbed at the edge.
  • Shield Advanced is subscribed per account; for accounts in an AWS Organizations organization, subscriptions are billed to the payer account, and one subscription fee covers all subscribed accounts in the consolidated billing family.

Response team and proactive engagement

The Shield Response Team (SRT) provides specialist help during DDoSAn attack uses many systems to flood a target and prevent legitimate access. events for Shield Advanced customers. Proactive engagement lets the SRT contact your operations team when a Shield-detected event affects application health.

How it works

  1. Subscribe to Shield Advanced and Business Support or Enterprise Support to use SRT services.
  2. Associate a Route 53 health checkA health check reports whether a resource meets configured availability criteria. with an eligible protected resource. A health check tests whether the resource meets your availability criteria.
  3. Enable proactive engagement and supply contacts. Use WAF v2 for any web ACLA web ACL groups rules that inspect web requests and determine their treatment. associated with the resource.
  4. During a Shield Advanced detected event, the SRT uses the health check state to assess impact and follows your contact guidance.
  5. The SRT can analyze WAF logs and, with your approval during engagement, change filtering rules. It can also create custom network mitigationsA mitigation is a measure that reduces the impact of attack traffic on an application..

Exam cues

  • If the question says experts must call operations during a DDoS event affecting health, think proactive engagement, because Shield combines its event detection with the associated health check.
  • If the question says Advanced is subscribed but SRT access is unavailable, think support plan requirements, because Business or Enterprise Support is also required.
  • If the question says only an Anti-DDoS managed rule group detected an event, think separate metric or event notifications, because that detection alone cannot trigger proactive engagement.

Remember

  • Provide between one and ten contacts.
  • Proactive engagement supports Elastic IPs, standard Global Accelerator accelerators, CloudFront distributions and ALBs for the documented event types.
  • Health-based detection excludes Route 53 hosted zones.
  • Any associated WAF web ACL must use WAF v2.

Trap: An unhealthy health check alone is not a Shield-detected DDoS event. Proactive engagement evaluates health during an event detected by Shield Advanced.

Health-based proactive engagement
12Route 53 checkShield eventSRT contacts team
  1. Health informs impact

  2. Contact guidance

From the AWS docs (11)
  • The Shield Response Team (SRT) consists of engineers who assist Shield Advanced customers with DDoS event response.
  • SRT services require Business Support or Enterprise Support in addition to Shield Advanced.
  • The SRT can analyze WAF logs and, with customer approval during engagement, change a web ACL to block identified attacks.
  • The SRT can develop custom infrastructure attack mitigations and recommend architecture changes.
  • A Route 53 health check reports whether a resource meets configured health criteria and can inform Shield Advanced detection.
  • Shield Advanced health-based detection is available for resource types other than Route 53 hosted zones.
  • Proactive engagement uses an associated Route 53 health check to assess impact during an event detected by Shield Advanced and contact the customer.
  • Proactive engagement covers network and transport events on Elastic IPs and standard Global Accelerator accelerators, and web floods on CloudFront and ALBs.
  • Proactive engagement requires at least one contact and supports up to ten contacts.
  • For proactively protected resources associated with a WAF web ACL, the ACL must use WAF v2.
  • Events detected only by the Anti-DDoS managed rule group do not trigger SRT proactive engagement; use its events and metrics for notification.

Flashcards

tap to flip
Answer

·

All 17 cards as a list

Does an application on AWS get DDoS protection without paying for anything extra?

Yes. Common DDoS attacks are covered automatically at no extra cost; Shield Advanced adds more for a fee.

Which AWS service protects against DDoS attacks?

AWS Shield: the standard protection is automatic, and Shield Advanced is the paid tier.

A company wants to improve DDoS resilience by absorbing attack traffic at AWS edge locations. Which services should it use?

Amazon CloudFront and Amazon Route 53. Serving traffic through these edge services helps absorb attacks at the edge.

How do AWS Shield Standard and Shield Advanced differ?

Standard provides automatic protection from common network and transport DDoS attacks at no extra charge. Advanced requires a subscription and explicit protection of supported resources.

Which resources can AWS Shield Advanced protect?

CloudFront distributions, Route 53 hosted zones, standard Global Accelerator accelerators, Application and Classic Load Balancers, and Elastic IPs. Protect EC2 instances and Network Load Balancers through their Elastic IPs.

A company subscribes to AWS Shield Advanced but never selects its ALB. Does the subscription protect that ALB automatically?

No. Explicitly protect the ALB, or use a Firewall Manager Shield Advanced policy.

A protected web application needs AWS Shield Advanced to create WAF protections during a request flood. Which feature fits?

Automatic application layer DDoS mitigation. Configure it to count or block attack requests through WAF.

A web application faces a flood of HTTP requests. How does AWS Shield Advanced integrate with AWS WAF to protect it?

Shield Advanced uses WAF web ACLs and rules for application layer protection. Automatic mitigation can count or block attack requests.

What do AWS Shield Advanced protection groups do?

Group protected resources for detection and mitigation across the group. A resource can belong to more than one protection group.

Besides AWS Shield, which two edge services help a web application absorb DDoS attacks?

Amazon CloudFront and Amazon Route 53, which run in edge locations.

An organization subscribes ten of its AWS accounts to AWS Shield Advanced. Does it pay ten subscription fees?

No. One subscription fee covers the subscribed accounts in its consolidated billing family, billed to the payer account. Each account still subscribes.

What must a team configure for AWS Shield Advanced proactive engagement?

Business or Enterprise Support, an associated Route 53 health check, proactive engagement enabled, and at least one contact. Any associated WAF web ACL must use WAF v2.

A Shield Advanced protected ALB has an unhealthy Route 53 health check during a Shield-detected web flood. How can the SRT contact operations automatically?

Enable proactive engagement and maintain contact details. The SRT uses the associated health check to assess the event impact.

A team needs expert help analyzing AWS WAF logs during a DDoS attack. What can the AWS Shield Response Team do?

Analyze WAF logs and, with customer approval, change the web ACL to block identified attacks.

A company has AWS Shield Advanced but lacks Business or Enterprise Support. Can it use SRT services?

No. SRT services require one of those support plans in addition to Shield Advanced.

Can the AWS Shield Response Team change a WAF web ACL while assisting with an attack?

Yes, with customer approval during engagement. The SRT can analyze WAF logs and apply rules to block identified attack traffic.

How can AWS Shield Advanced use application health to support DDoS response?

Associate a Route 53 health check. Shield Advanced can use it to inform detection and assess impact for proactive engagement.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!