AWS wellarchitected documentation change
Summary
Updated 'Auto Scaling groups' to 'Amazon EC2 Auto Scaling groups' for service name specificity.
Security assessment
Change clarifies the exact AWS service name but doesn't address security aspects. Service quota management discussion remains unchanged.
Diff
diff --git a/wellarchitected/2024-06-27/framework/rel_manage_service_limits_aware_quotas_and_constraints.md b/wellarchitected/2024-06-27/framework/rel_manage_service_limits_aware_quotas_and_constraints.md index 47bbdb29a..7b6a85cda 100644 --- a//wellarchitected/2024-06-27/framework/rel_manage_service_limits_aware_quotas_and_constraints.md +++ b//wellarchitected/2024-06-27/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).