AWS AWSEC2 documentation change
Summary
Updated terminology for Directory Service and corrected references to Amazon EC2 Auto Scaling
Security assessment
Changes involve minor terminology updates (removing 'AWS' prefix from Directory Service) and fixing redundant phrasing in Auto Scaling references. No security implications identified as these are editorial improvements without security context.
Diff
diff --git a/AWSEC2/latest/UserGuide/ec2-instance-launch-parameters.md b/AWSEC2/latest/UserGuide/ec2-instance-launch-parameters.md index 99f23b60d..9f7c2c85d 100644 --- a//AWSEC2/latest/UserGuide/ec2-instance-launch-parameters.md +++ b//AWSEC2/latest/UserGuide/ec2-instance-launch-parameters.md @@ -270 +270 @@ For **Advanced details** , expand the section to view the fields and specify any - * (Launch instance wizard only) **Domain join directory** : Select the AWS Directory Service directory (domain) to which your instance is joined to after launch. If you select a domain, you must select an IAM role with the required permissions. For more information about domain joining, see [Seamlessly join an Amazon EC2 Linux instance to your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/seamlessly_join_linux_instance.html) (Linux instances) and [Seamlessly join an Amazon EC2 Windows instance to your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/launching_instance.html) (Windows instances). + * (Launch instance wizard only) **Domain join directory** : Select the Directory Service directory (domain) to which your instance is joined to after launch. If you select a domain, you must select an IAM role with the required permissions. For more information about domain joining, see [Seamlessly join an Amazon EC2 Linux instance to your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/seamlessly_join_linux_instance.html) (Linux instances) and [Seamlessly join an Amazon EC2 Windows instance to your AWS Managed Microsoft AD directory](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/launching_instance.html) (Windows instances). @@ -339 +339 @@ To ensure faster instance launches, break up large requests into smaller batches - * (Optional) If you specify more than one instance, to help ensure that you maintain the correct number of instances to handle demand on your application, you can choose **consider EC2 Auto Scaling** to create a launch template and an Auto Scaling group. Auto Scaling scales the number of instances in the group according to your specifications. For more information, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/). + * (Optional) If you specify more than one instance, to help ensure that you maintain the correct number of instances to handle demand on your application, you can choose **consider EC2 Amazon EC2 Auto Scaling** to create a launch template and an Amazon EC2 Auto Scaling group. Amazon EC2 Auto Scaling scales the number of instances in the group according to your specifications. For more information, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/). @@ -343 +343 @@ To ensure faster instance launches, break up large requests into smaller batches -If Amazon EC2 Auto Scaling marks an instance that is in an Auto Scaling group as unhealthy, the instance is automatically scheduled for replacement where it is terminated and another is launched, and you lose your data on the original instance. An instance is marked as unhealthy if you stop or reboot the instance, or if another event marks the instance as unhealthy. For more information, see [Health checks for instances in an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-health-checks.html) in the _Amazon EC2 Auto Scaling User Guide_. +If Amazon EC2 Amazon EC2 Auto Scaling marks an instance that is in an Amazon EC2 Auto Scaling group as unhealthy, the instance is automatically scheduled for replacement where it is terminated and another is launched, and you lose your data on the original instance. An instance is marked as unhealthy if you stop or reboot the instance, or if another event marks the instance as unhealthy. For more information, see [Health checks for instances in an Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-health-checks.html) in the _Amazon EC2 Auto Scaling User Guide_.