AWS r53recovery documentation change
Summary
Updated terminology from 'Auto Scaling groups' to 'Amazon EC2 Auto Scaling groups' for clarity and service name consistency
Security assessment
Change only clarifies service naming conventions without introducing security-related content or addressing vulnerabilities
Diff
diff --git a/r53recovery/latest/dg/introduction-components-readiness.md b/r53recovery/latest/dg/introduction-components-readiness.md index ec91e7aec..9ca8d3b56 100644 --- a//r53recovery/latest/dg/introduction-components-readiness.md +++ b//r53recovery/latest/dg/introduction-components-readiness.md @@ -46 +46 @@ Readiness rules are audits that ARC performs against a set of resources in a res -A readiness check monitors a resource set in your application, such as a set of Amazon Aurora instances, that ARC is auditing recovery readiness for. Readiness checks can include auditing, for example, capacity configurations, AWS quotas, or routing policies. For example, if you want to audit readiness for your Amazon EC2 Auto Scaling groups across two Availability Zones, you can create a readiness check for a resource set with two resource ARNs, one for each Auto Scaling group. Then, to make sure that each group is scaled equally, ARC continually monitors the instance types and the counts in the two groups. +A readiness check monitors a resource set in your application, such as a set of Amazon Aurora instances, that ARC is auditing recovery readiness for. Readiness checks can include auditing, for example, capacity configurations, AWS quotas, or routing policies. For example, if you want to audit readiness for your Amazon EC2 Amazon EC2 Auto Scaling groups across two Availability Zones, you can create a readiness check for a resource set with two resource ARNs, one for each Amazon EC2 Auto Scaling group. Then, to make sure that each group is scaled equally, ARC continually monitors the instance types and the counts in the two groups.