AWS wellarchitected documentation change
Summary
Updated 'Auto Scaling groups (ASG)' to 'Amazon EC2 Auto Scaling groups (ASG)' in the service quota example.
Security assessment
Terminology refinement without security impact. The example still illustrates the same reliability risk (service disruption from quota limits) but with updated service naming. No security vulnerabilities addressed.
Diff
diff --git a/wellarchitected/2025-02-25/framework/rel_manage_service_limits_aware_quotas_and_constraints.md b/wellarchitected/2025-02-25/framework/rel_manage_service_limits_aware_quotas_and_constraints.md index 1b6cd6a6b..ad09bcdb0 100644 --- a//wellarchitected/2025-02-25/framework/rel_manage_service_limits_aware_quotas_and_constraints.md +++ b//wellarchitected/2025-02-25/framework/rel_manage_service_limits_aware_quotas_and_constraints.md @@ -50 +50 @@ Some service limits, like rate limits on throttled APIs are set within the Amazo -Service quotas can be Region specific or can also be global in nature. Using an AWS service that reaches its quota will not act as expected in normal usage and may cause service disruption or degradation. For example, a service quota limits the number of DL Amazon EC2 instances used in a Region. That limit may be reached during a traffic scaling event using Auto Scaling groups (ASG). +Service quotas can be Region specific or can also be global in nature. Using an AWS service that reaches its quota will not act as expected in normal usage and may cause service disruption or degradation. For example, a service quota limits the number of DL Amazon EC2 instances used in a Region. That limit may be reached during a traffic scaling event using Amazon EC2 Auto Scaling groups (ASG).