AWS r53recovery documentation change
Summary
Removed 'About zonal autoshift' section and restructured content about practice runs, traffic validation, and configuration options. Added emphasis on verifying application operation through on-demand practice runs.
Security assessment
Changes focus on operational best practices and documentation restructuring. No mention of security vulnerabilities, patches, or explicit security controls. The content updates relate to validation procedures and configuration options rather than security features or mitigations.
Diff
diff --git a/r53recovery/latest/dg/arc-zonal-autoshift.md b/r53recovery/latest/dg/arc-zonal-autoshift.md index 803498992..ca7f13bc0 100644 --- a//r53recovery/latest/dg/arc-zonal-autoshift.md +++ b//r53recovery/latest/dg/arc-zonal-autoshift.md @@ -5,2 +4,0 @@ -About zonal autoshift - @@ -23 +21 @@ If you plan to enable zonal autoshift or configure practice runs, after you pre- -To ensure your tests with zonal shift are effective, it's important to validate that traffic drains as expected from the AZ you shift away from. For example, both Application Load Balancers and Network Load Balancers provide per AZ metrics in Amazon CloudWatch that you can use to monitor this. Depending on how long a service and clients reuse connections, traffic might continue to the AZ that you have shifted away from for longer than you expect. To learn more, see [Limit the time that clients stay connected to your endpoints](./arc-zonal-autoshift.considerations.html#ZAConsiderationsCurrentConnections). +After you enable zonal autoshift, we recommend that you verify, by starting and evaluating an on-demand practice run zonal shift, that your application can continue operating normally with traffic shifted away from an Availability Zone. Then, the regular practice runs that ARC performs help you to confirm, on an ongoing basis, that you have enough capacity for an autoshift. @@ -25 +23 @@ To ensure your tests with zonal shift are effective, it's important to validate -After you verify, by starting and evaluating a zonal shift, that your application can continue operating normally with traffic shifted away from an Availability Zone, the regular practice runs that ARC performs help you to confirm, on an ongoing basis, that you have enough capacity for an autoshift. +To ensure that your tests with zonal shift are effective, it's important to validate that traffic drains as expected from the AZ you shift away from. For example, both Application Load Balancers and Network Load Balancers provide per AZ metrics in Amazon CloudWatch that you can use to monitor this. Depending on how long a service and clients reuse connections, traffic might continue to the AZ that you have shifted away from for longer than you expect. To learn more, see [Limit the time that clients stay connected to your endpoints](./arc-zonal-autoshift.considerations.html#ZAConsiderationsCurrentConnections). @@ -27 +25 @@ After you verify, by starting and evaluating a zonal shift, that your applicatio -In addition to enabling zonal autoshift for a supported resource in the ARC console, you have the option to instead enable zonal autoshift for a specific load balancer in the Amazon EC2 console. To learn more about enabling zonal autoshift with Elastic Load Balancing, see [Zonal shift](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/zonal-shift.html) in the Elastic Load Balancing User Guide. +You can enable zonal autoshift, for a supported resource, in the ARC console. Or, in the Amazon EC2 console, you have the option to enable zonal autoshift for a specific load balancer resource. To learn more about enabling zonal autoshift with Elastic Load Balancing, see [Zonal shift](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/zonal-shift.html) in the Elastic Load Balancing User Guide. @@ -33,16 +30,0 @@ You can configure Amazon EventBridge notifications to alert you about autoshifts -## About zonal autoshift - -Zonal autoshift is a capability where AWS shifts application resource traffic away from an Availability Zone, on your behalf. AWS starts an autoshift when internal telemetry indicates that there is an Availability Zone impairment that could potentially impact customers. The internal telemetry incorporates metrics from several sources, including the AWS network, and the Amazon EC2 and Elastic Load Balancing services. - -You must manually enable zonal autoshift for supported AWS resources. - -When you deploy and run AWS applications on load balancers in multiple (typically three) AZs in a Region, and you pre-scale to support static stability, AWS can quickly recover customer applications in an AZ by shifting traffic away with an autoshift. By shifting away resource traffic to other AZs in the Region, AWS can reduce the duration and severity of potential impact caused by power outages, hardware or software issues in an AZ, or other impairments. - -ARC's supported resources provide integrations that mark the specified AZ as unhealthy, which results in a traffic shifting away from the impaired AZ. - -When you enable zonal autoshift for a resource, you must also configure a practice run for the resource. AWS performs practice runs about weekly, for 30 minutes, to help you make sure that you have enough capacity to run your application without one of the Availability Zones in the Region. - -As with zonal shift, there are a few specific scenarios where zonal autoshift does not shift traffic away from the AZ. For example, if the load balancer target groups in the AZs don't have any instances, or if all of the instances are unhealthy, then the load balancer is in a fail open state and you can't shift away one of the AZs. - -To learn more about zonal autoshift, see [Zonal autoshift in ARC](./arc-zonal-autoshift.html). -