AWS elasticbeanstalk documentation change
Summary
Updated 'ELB load balancer' to 'Elastic Load Balancing load balancer' in permissions description
Security assessment
The change standardizes service naming without altering security semantics. No new security information is added, and there's no evidence of vulnerability remediation. Permission requirements remain identical.
Diff
diff --git a/elasticbeanstalk/latest/dg/concepts-roles-user.md b/elasticbeanstalk/latest/dg/concepts-roles-user.md index 91745086a..6c167384b 100644 --- a//elasticbeanstalk/latest/dg/concepts-roles-user.md +++ b//elasticbeanstalk/latest/dg/concepts-roles-user.md @@ -9 +9 @@ Create IAM users for each user who uses Elastic Beanstalk to avoid using your ro -Elastic Beanstalk requires permissions not only for its own API actions, but also for several other AWS services. Elastic Beanstalk uses user permissions to launch resources in an environment. These resources include EC2 instances, an ELB load balancer, and an Auto Scaling group. Elastic Beanstalk also uses user permissions to save logs and templates to Amazon Simple Storage Service (Amazon S3), send notifications to Amazon SNS, assign instance profiles, and publish metrics to CloudWatch. Elastic Beanstalk requires CloudFormation permissions to orchestrate resource deployments and updates. It also requires Amazon RDS permissions to create databases when needed, and Amazon SQS permissions to create queues for worker environments. +Elastic Beanstalk requires permissions not only for its own API actions, but also for several other AWS services. Elastic Beanstalk uses user permissions to launch resources in an environment. These resources include EC2 instances, an Elastic Load Balancing load balancer, and an Auto Scaling group. Elastic Beanstalk also uses user permissions to save logs and templates to Amazon Simple Storage Service (Amazon S3), send notifications to Amazon SNS, assign instance profiles, and publish metrics to CloudWatch. Elastic Beanstalk requires CloudFormation permissions to orchestrate resource deployments and updates. It also requires Amazon RDS permissions to create databases when needed, and Amazon SQS permissions to create queues for worker environments.