AWS elasticloadbalancing documentation change
Summary
Removed all references to Amazon Application Recovery Controller (ARC) integration, including zonal shift features and administrative overrides. Updated sections on IP address pool management and load balancer attributes.
Security assessment
The changes remove documentation about disaster recovery capabilities (zonal shifts) but provide no evidence of addressing a security vulnerability. While availability impacts reliability, there is no direct indication of patching exploits or mitigating attacks. The content removal appears to be a service integration deprecation rather than a security fix.
Diff
diff --git a/elasticloadbalancing/latest/application/load-balancer-integrations.md b/elasticloadbalancing/latest/application/load-balancer-integrations.md index b1c864509..d37de0061 100644 --- a//elasticloadbalancing/latest/application/load-balancer-integrations.md +++ b//elasticloadbalancing/latest/application/load-balancer-integrations.md @@ -5 +5 @@ -Amazon Application Recovery Controller (ARC)Amazon CloudFront + AWS WAFAWS Global AcceleratorAWS ConfigAWS WAF +Amazon CloudFront + AWS WAFAWS Global AcceleratorAWS ConfigAWS WAF @@ -13,2 +12,0 @@ You can optimize your Application Load Balancer architecture by integrating with - * Amazon Application Recovery Controller (ARC) - @@ -26,61 +23,0 @@ You can optimize your Application Load Balancer architecture by integrating with -## Amazon Application Recovery Controller (ARC) - -Amazon Application Recovery Controller (ARC) helps you prepare for and accomplish faster recovery operations for applications running on AWS. Zonal shift and zonal autoshift are features of Amazon Application Recovery Controller (ARC). - -With zonal shift, you can shift traffic away from an impaired Availability Zone with a single action. This way, you can continue operating from other healthy Availability Zones in an AWS Region. - -With zonal autoshift, you authorize AWS to shift away resource traffic for an application from an Availability Zone during events, on your behalf, to help reduce time to recovery. AWS starts an autoshift when internal monitoring indicates that there is an Availability Zone impairment that could potentially impact customers. When AWS starts an autoshift, application traffic to resources that you've configured for zonal autoshift starts shifting away from the Availability Zone. - -When you start a zonal shift, your load balancer stops sending new traffic for the resource to the affected Availability Zone. ARC creates the zonal shift immediately. However, it can take a short time for existing, in-progress connections in the Availability Zone to complete, depending on client behavior and connection reuse. Depending on your DNS settings and other factors, existing connections can complete in just a few minutes, or might take longer. For more information, see [Limit the time that clients stay connected to your endpoints](https://docs.aws.amazon.com/r53recovery/latest/dg/route53-arc-best-practices.zonal-shifts.html#arc-zonal-shift.existing-connections) in the _Amazon Application Recovery Controller (ARC) Developer Guide_. - -To use zonal shift features on Application Load Balancers, you must have the **ARC zonal shift integration** attribute set to **Enabled**. - -Before you enable the Amazon Application Recovery Controller (ARC) integration and start utilizing zonal shift, review the following: - - * You can start a zonal shift for a specific load balancer only for a single Availability Zone. You can't start a zonal shift for multiple Availability Zones. - - * AWS proactively removes zonal load balancer IP addresses from DNS when multiple infrastructure issues impact services. Always check current Availability Zone capacity before you start a zonal shift. If your load balancers have cross-zone load balancing turned off and you use a zonal shift to remove a zonal load balancer IP address, the Availability Zone affected by the zonal shift also loses target capacity. - - - - -For more information, see [Best practices for zonal shifts in ARC](https://docs.aws.amazon.com/r53recovery/latest/dg/route53-arc-best-practices.zonal-shifts.html) in the _Amazon Application Recovery Controller (ARC) Developer Guide_. - -### Cross-zone enabled Application Load Balancers - -When a zonal shift is started on an Application Load Balancer with cross-zone load balancing enabled, all traffic to targets is blocked in the availability zone being impacted, and zonal IP addresses are removed from DNS. - -###### Benefits: - - * Quicker recovery from availability zone failures. - - * The ability to move traffic to a healthy availability zone if failures are detected in an availability zone. - - * You can test application integrity by simulating and identifying failures to prevent unplanned downtime. - - - - -#### Zonal shift administrative override - -Targets that belong to a Application Load Balancer will include a new status `AdministrativeOverride`, which is independent from the `TargetHealth` state. - -When a zonal shift is started for a Application Load Balancer, all targets within the zone being shifted away from are considered administratively overridden. The Application Load Balancer will stop routing new traffic to the administratively overridden targets, however existing connections remain intact until they are organically closed. - -The possible `AdministrativeOverride` states are: - -**unknown** - - -State cannot be propagated due to an internal error - -**no_override** - - -No override is currently active on target - -**zonal_shift_active** - - -Zonal shift is active in target Availability Zone - @@ -138 +75 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Update the IPAM IP address pools +Monitor reservation @@ -140 +77 @@ Update the IPAM IP address pools -Edit load balancer attributes +Listeners and rules