AWS whitepapers documentation change
Summary
Changed 'Elastic Load Balancing' abbreviation to 'ELB' in parentheses for consistency
Security assessment
Change only modifies abbreviation usage without altering security context or DDoS mitigation guidance
Diff
diff --git a/whitepapers/latest/security-at-the-edge/ddos-mitigation.md b/whitepapers/latest/security-at-the-edge/ddos-mitigation.md index 97295038c..849722df8 100644 --- a//whitepapers/latest/security-at-the-edge/ddos-mitigation.md +++ b//whitepapers/latest/security-at-the-edge/ddos-mitigation.md @@ -13 +13 @@ AWS services include basic DDoS protection as a standard feature. All AWS custom -This protection is always on, but is preconfigured, static, and provides no reporting or analytics. Mitigations are configured with pre-assigned limits based on the service that is being targeted. For example, if your [Elastic Load Balancing](https://aws.amazon.com/elasticloadbalancing/) (ELB) is targeted by an infrastructure layer DDoS attack, a mitigation that is configured based on ELB service limits to ensure the resource remains operational is placed. This mitigation is effective at blocking many known vectors of attack, and protecting the underlying resource. The nuance is that the limits of your application may differ from the limits of the ELB, resulting in the resource remaining operational, but your application still being impacted. +This protection is always on, but is preconfigured, static, and provides no reporting or analytics. Mitigations are configured with pre-assigned limits based on the service that is being targeted. For example, if your [ELB](https://aws.amazon.com/elasticloadbalancing/) (ELB) is targeted by an infrastructure layer DDoS attack, a mitigation that is configured based on ELB service limits to ensure the resource remains operational is placed. This mitigation is effective at blocking many known vectors of attack, and protecting the underlying resource. The nuance is that the limits of your application may differ from the limits of the ELB, resulting in the resource remaining operational, but your application still being impacted.