AWS autoscaling documentation change
Summary
Updated terminology from 'Auto Scaling' to 'Amazon EC2 Auto Scaling' throughout the document for consistency
Security assessment
The changes are purely terminological updates to use the full service name ('Amazon EC2 Auto Scaling') instead of the abbreviated form. No security vulnerabilities, configurations, or features were added/modified. The security-related content about subnet considerations (e.g., public vs private subnets, SSH access, Session Manager usage) remains substantively unchanged.
Diff
diff --git a/autoscaling/ec2/userguide/asg-in-vpc.md b/autoscaling/ec2/userguide/asg-in-vpc.md index c589bbeef..c19bf68df 100644 --- a//autoscaling/ec2/userguide/asg-in-vpc.md +++ b//autoscaling/ec2/userguide/asg-in-vpc.md @@ -7 +7 @@ Default VPCNondefault VPCConsiderations when choosing VPC subnetsIP addressing i -# Provide network connectivity for your Auto Scaling instances using Amazon VPC +# Provide network connectivity for your Amazon EC2 Auto Scaling instances using Amazon VPC @@ -9 +9 @@ Default VPCNondefault VPCConsiderations when choosing VPC subnetsIP addressing i -Amazon Virtual Private Cloud (Amazon VPC) is a service that lets you launch AWS resources such as Auto Scaling groups in a logically isolated virtual network that you define. +Amazon Virtual Private Cloud (Amazon VPC) is a service that lets you launch AWS resources such as Amazon EC2 Auto Scaling groups in a logically isolated virtual network that you define. @@ -11 +11 @@ Amazon Virtual Private Cloud (Amazon VPC) is a service that lets you launch AWS -A subnet in Amazon VPC is a subdivision within an Availability Zone defined by a segment of the IP address range of the VPC. Using subnets, you can group your instances based on your security and operational needs. A subnet resides entirely within the Availability Zone it was created in. You launch Auto Scaling instances within the subnets. +A subnet in Amazon VPC is a subdivision within an Availability Zone defined by a segment of the IP address range of the VPC. Using subnets, you can group your instances based on your security and operational needs. A subnet resides entirely within the Availability Zone it was created in. You launch Amazon EC2 Auto Scaling instances within the subnets. @@ -38 +38 @@ To enable communication between the internet and the instances in your subnets, -If you created your AWS account after December 4, 2013 or you are creating your Auto Scaling group in a new AWS Region, we create a default VPC for you. Your default VPC comes with a default subnet in each Availability Zone. If you have a default VPC, your Auto Scaling group is created in the default VPC by default. +If you created your AWS account after December 4, 2013 or you are creating your Amazon EC2 Auto Scaling group in a new AWS Region, we create a default VPC for you. Your default VPC comes with a default subnet in each Availability Zone. If you have a default VPC, your Amazon EC2 Auto Scaling group is created in the default VPC by default. @@ -56 +56 @@ A VPC spans all Availability Zones in its AWS Region. When you add subnets to yo -Note the following considerations when choosing VPC subnets for your Auto Scaling group: +Note the following considerations when choosing VPC subnets for your Amazon EC2 Auto Scaling group: @@ -58 +58 @@ Note the following considerations when choosing VPC subnets for your Auto Scalin - * If you're attaching an Elastic Load Balancing load balancer to your Auto Scaling group, the instances can be launched into either public or private subnets. However, the load balancer must be created in public subnets to support DNS resolution. + * If you're attaching an ELB load balancer to your Amazon EC2 Auto Scaling group, the instances can be launched into either public or private subnets. However, the load balancer must be created in public subnets to support DNS resolution. @@ -60 +60 @@ Note the following considerations when choosing VPC subnets for your Auto Scalin - * If you're accessing your Auto Scaling instances directly through SSH, the instances can be launched into public subnets only. + * If you're accessing your Amazon EC2 Auto Scaling instances directly through SSH, the instances can be launched into public subnets only. @@ -62 +62 @@ Note the following considerations when choosing VPC subnets for your Auto Scalin - * If you're accessing no-ingress Auto Scaling instances using AWS Systems Manager Session Manager, the instances can be launched into either public or private subnets. + * If you're accessing no-ingress Amazon EC2 Auto Scaling instances using AWS Systems Manager Session Manager, the instances can be launched into either public or private subnets. @@ -64 +64 @@ Note the following considerations when choosing VPC subnets for your Auto Scalin - * If you're using private subnets, you can allow the Auto Scaling instances to access the internet by using a public NAT gateway. + * If you're using private subnets, you can allow the Amazon EC2 Auto Scaling instances to access the internet by using a public NAT gateway. @@ -73 +73 @@ Note the following considerations when choosing VPC subnets for your Auto Scalin -When you launch your Auto Scaling instances in a VPC, your instances are automatically assigned a private IP address from the CIDR range of the subnet in which the instance is launched. This enables your instances to communicate with other instances in the VPC. +When you launch your Amazon EC2 Auto Scaling instances in a VPC, your instances are automatically assigned a private IP address from the CIDR range of the subnet in which the instance is launched. This enables your instances to communicate with other instances in the VPC. @@ -81 +81 @@ For information on specifying CIDR ranges for your VPC or subnet, see the [Amazo -Amazon EC2 Auto Scaling can automatically assign additional private IP addresses on instance launch when you use a launch template that specifies additional network interfaces. Each network interface is assigned a single private IP address from the CIDR range of the subnet in which the instance is launched. In this case, the system can no longer auto-assign a public IPv4 address to the primary network interface. You will not be able to connect to your instances over a public IPv4 address unless you associate available Elastic IP addresses to the Auto Scaling instances. +Amazon EC2 Auto Scaling can automatically assign additional private IP addresses on instance launch when you use a launch template that specifies additional network interfaces. Each network interface is assigned a single private IP address from the CIDR range of the subnet in which the instance is launched. In this case, the system can no longer auto-assign a public IPv4 address to the primary network interface. You will not be able to connect to your instances over a public IPv4 address unless you associate available Elastic IP addresses to the Amazon EC2 Auto Scaling instances. @@ -87 +87 @@ Each instance in your VPC has a default network interface (the primary network i -When launching an instance using a launch template, you can specify additional network interfaces. However, launching an Auto Scaling instance with multiple network interfaces automatically creates each interface in the same subnet as the instance. This is because Amazon EC2 Auto Scaling ignores the subnets defined in the launch template in favor of what is specified in the Auto Scaling group. For more information, see [Creating a launch template for an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html). +When launching an instance using a launch template, you can specify additional network interfaces. However, launching an Amazon EC2 Auto Scaling instance with multiple network interfaces automatically creates each interface in the same subnet as the instance. This is because Amazon EC2 Auto Scaling ignores the subnets defined in the launch template in favor of what is specified in the Amazon EC2 Auto Scaling group. For more information, see [Creating a launch template for an Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html). @@ -101 +101 @@ For more information, see the [AWS Outposts User Guide](https://docs.aws.amazon. -For an example of how to deploy an Auto Scaling group that serves traffic from an Application Load Balancer within an Outpost, see the following blog post [Configuring an Application Load Balancer on AWS Outposts](https://aws.amazon.com/blogs/networking-and-content-delivery/configuring-an-application-load-balancer-on-aws-outposts/). +For an example of how to deploy an Amazon EC2 Auto Scaling group that serves traffic from an Application Load Balancer within an Outpost, see the following blog post [Configuring an Application Load Balancer on AWS Outposts](https://aws.amazon.com/blogs/networking-and-content-delivery/configuring-an-application-load-balancer-on-aws-outposts/).