AWS elasticbeanstalk documentation change
Summary
Clarified security group requirements and added AWS CLI reference
Security assessment
Improves documentation about security group configuration requirements, which helps users implement proper security controls. No specific vulnerability addressed.
Diff
diff --git a/elasticbeanstalk/latest/dg/using-features.managing.ec2.instances.sg.md b/elasticbeanstalk/latest/dg/using-features.managing.ec2.instances.sg.md index 996afdbeb..0e7140a5f 100644 --- a//elasticbeanstalk/latest/dg/using-features.managing.ec2.instances.sg.md +++ b//elasticbeanstalk/latest/dg/using-features.managing.ec2.instances.sg.md @@ -23 +23 @@ If you disable the default EC2 security group for a load balanced environment, E - * At least one security group security group must be assigned to the load balancer. + * At least one security group must be assigned to the load balancer using the `SecurityGroups` option of the [aws:elbv2:loadbalancer](./command-options-general.html#command-options-general-elbv2) or [aws:elb:loadbalancer](./command-options-general.html#command-options-general-elbloadbalancer), depending on whether it's an application load balancer or classic load balancer, respectively. For AWS CLI examples see [Configuring with the AWS CLI](./using-features.managing.ec2.aws-cli.html). @@ -25 +25 @@ If you disable the default EC2 security group for a load balanced environment, E - * Inbound traffic rules must exist that allow your EC2 instances to receive traffic from the load balancer. Both your EC2 security groups and your load balancer security groups must reference these inbound rules. + * Inbound traffic rules must exist that allow your EC2 instances to receive traffic from the load balancer. Both your EC2 security groups and your load balancer security groups must reference these inbound rules. For more information, see the Inbound rules for traffic section that follows.