AWS elasticbeanstalk documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' for consistency and clarity. Minor phrasing adjustments in configuration change example.
Security assessment
The changes are purely terminological updates to use the full service name (Amazon EC2 Auto Scaling group) rather than the abbreviated form. No security vulnerabilities, configurations, or practices are mentioned or modified.
Diff
diff --git a/elasticbeanstalk/latest/dg/GettingStarted.md b/elasticbeanstalk/latest/dg/GettingStarted.md index 799915f77..f46d1c440 100644 --- a//elasticbeanstalk/latest/dg/GettingStarted.md +++ b//elasticbeanstalk/latest/dg/GettingStarted.md @@ -375 +375 @@ Some configuration changes are simple and happen quickly. Some changes require d -In this example of a configuration change, you edit your environment's capacity settings. You configure a load-balanced, scalable environment that has between two and four Amazon EC2 instances in its Auto Scaling group, and then you verify that the change occurred. Elastic Beanstalk creates an additional Amazon EC2 instance, adding to the single instance that it created initially. Then, Elastic Beanstalk associates both instances with the environment's load balancer. As a result, your application's responsiveness is improved and its availability is increased. +In this example of a configuration change, you edit your environment's capacity settings. You configure a load-balanced, scalable environment that has between two and four Amazon EC2 instances in its Amazon EC2 Auto Scaling group, and then you verify that the change occurred. Elastic Beanstalk creates an additional Amazon EC2 instance, adding to the single instance that it created initially. Then, Elastic Beanstalk associates both instances with the environment's load balancer. As a result, your application's responsiveness is improved and its availability is increased. @@ -387 +387 @@ In this example of a configuration change, you edit your environment's capacity - 5. Collapse the **Instances** section, so you can more easily see the **Capacity** section. Under **Auto Scaling group** change **Environment type** to **Load balanced**. + 5. Collapse the **Instances** section, so you can more easily see the **Capacity** section. Under **Amazon EC2 Auto Scaling group** change **Environment type** to **Load balanced**. @@ -462 +462 @@ To ensure that you're not charged for any services you aren't using, delete all -You have successfully deployed a sample application to the AWS Cloud, uploaded a new version, modified its configuration to add a second Auto Scaling instance, and cleaned up your AWS resources! +You have successfully deployed a sample application to the AWS Cloud, uploaded a new version, modified its configuration to add a second Amazon EC2 Auto Scaling instance, and cleaned up your AWS resources!