AWS elasticbeanstalk documentation change
Summary
Updated terminology from 'Auto Scaling group' to 'Amazon EC2 Auto Scaling group' in error messages and examples
Security assessment
This is a branding/terminology update without any security implications. The changes improve clarity but do not address security vulnerabilities or document security features.
Diff
diff --git a/elasticbeanstalk/latest/dg/health-enhanced-status.md b/elasticbeanstalk/latest/dg/health-enhanced-status.md index 20174d56c..00052fa5a 100644 --- a//elasticbeanstalk/latest/dg/health-enhanced-status.md +++ b//elasticbeanstalk/latest/dg/health-enhanced-status.md @@ -57 +57 @@ _Example:_ environment is in the process of scaling up to 5 instances. -_Message (environment):_ 4 active instances is below Auto Scaling group minimum size 5. +_Message (environment):_ 4 active instances is below Amazon EC2 Auto Scaling group minimum size 5. @@ -106 +106 @@ _Example:_ Elastic Beanstalk can't access the environment's [service role](./iam -_Example:_ The [Auto Scaling group](./using-features.managing.as.html) that Elastic Beanstalk created for the environment has been deleted. +_Example:_ The [Amazon EC2 Auto Scaling group](./using-features.managing.as.html) that Elastic Beanstalk created for the environment has been deleted. @@ -108 +108 @@ _Example:_ The [Auto Scaling group](./using-features.managing.as.html) that Elas -_Message:_ Environment health has transitioned from **OK** to **Severe**. There are no instances. Auto Scaling group desired capacity is set to 1. +_Message:_ Environment health has transitioned from **OK** to **Severe**. There are no instances. Amazon EC2 Auto Scaling group desired capacity is set to 1.