AWS AWSEC2 documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in two instances discussing VPC creation
Security assessment
Terminology update without technical changes. The IAM permission requirements remain identical, and no security implications are introduced.
Diff
diff --git a/AWSEC2/latest/UserGuide/win-fast-launch-troubleshoot.md b/AWSEC2/latest/UserGuide/win-fast-launch-troubleshoot.md index 177566045..a0e07720d 100644 --- a//AWSEC2/latest/UserGuide/win-fast-launch-troubleshoot.md +++ b//AWSEC2/latest/UserGuide/win-fast-launch-troubleshoot.md @@ -32 +32 @@ To configure EC2 Fast Launch for an AMI, you must create the AMI using **Sysprep -If you don't use a launch template to specify an existing VPC, and don't have a default VPC defined for your account, the service automatically creates an AWS CloudFormation stack that includes a VPC and other resources, as described in [EC2 Fast Launch prerequisites](./win-start-fast-launch-prereqs.html). +If you don't use a launch template to specify an existing VPC, and don't have a default VPC defined for your account, the service automatically creates an CloudFormation stack that includes a VPC and other resources, as described in [EC2 Fast Launch prerequisites](./win-start-fast-launch-prereqs.html). @@ -66 +66 @@ If you have an urgent quota request, or if your quota increase request is denied -When you enable EC2 Fast Launch for the first time without specifying a Launch Template, EC2 Fast Launch creates a service-owned AWS CloudFormation stack with service default resources. However, the CloudFormation templates will fail to deploy if your IAM principal (role or user) lacks the necessary permissions. +When you enable EC2 Fast Launch for the first time without specifying a Launch Template, EC2 Fast Launch creates a service-owned CloudFormation stack with service default resources. However, the CloudFormation templates will fail to deploy if your IAM principal (role or user) lacks the necessary permissions.