AWS cloud9 documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The changes are purely branding/terminology updates (removing 'AWS' prefix from CloudFormation references). No security-related content was added, removed, or modified. The existing security context about no-ingress EC2 instances and Session Manager permissions remains unchanged.
Diff
diff --git a/cloud9/latest/user-guide/ec2-ssm.md b/cloud9/latest/user-guide/ec2-ssm.md index 8ced4f694..46b6e622e 100644 --- a//cloud9/latest/user-guide/ec2-ssm.md +++ b//cloud9/latest/user-guide/ec2-ssm.md @@ -5 +5 @@ -Benefits of using Systems Manager for EC2 environmentsManaging Systems Manager permissionsGiving users access to instances managed by Session ManagerUsing AWS CloudFormation to create no-ingress EC2 environmentsConfiguring VPC endpoints for Amazon S3 to download dependenciesConfiguring VPC endpoints for private connectivity +Benefits of using Systems Manager for EC2 environmentsManaging Systems Manager permissionsGiving users access to instances managed by Session ManagerUsing CloudFormation to create no-ingress EC2 environmentsConfiguring VPC endpoints for Amazon S3 to download dependenciesConfiguring VPC endpoints for private connectivity @@ -11 +11 @@ AWS Cloud9 is no longer available to new customers. Existing customers of AWS Cl -A "no-ingress EC2 instance" that's created for an EC2 environment enables AWS Cloud9 to connect to its Amazon EC2 instance without the need to open any inbound ports on that instance. You can select the no-ingress option when creating an EC2 environment using the console, the command line interface, or a AWS CloudFormation stack. For more information about how to create an environment using the console or command line interface, see [Step 1: Create an environment](./tutorials-basic.html#tutorial-create-environment). +A "no-ingress EC2 instance" that's created for an EC2 environment enables AWS Cloud9 to connect to its Amazon EC2 instance without the need to open any inbound ports on that instance. You can select the no-ingress option when creating an EC2 environment using the console, the command line interface, or a CloudFormation stack. For more information about how to create an environment using the console or command line interface, see [Step 1: Create an environment](./tutorials-basic.html#tutorial-create-environment). @@ -176 +176 @@ The following managed policies also include these policy statements: `AWSCloud9A -## Using AWS CloudFormation to create no-ingress EC2 environments +## Using CloudFormation to create no-ingress EC2 environments @@ -178 +178 @@ The following managed policies also include these policy statements: `AWSCloud9A -When using an [AWS CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) to define a no-ingress Amazon EC2 development environment, do the following before creating the stack: +When using an [CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) to define a no-ingress Amazon EC2 development environment, do the following before creating the stack: @@ -180 +180 @@ When using an [AWS CloudFormation template](https://docs.aws.amazon.com/AWSCloud - 1. Create the `AWSCloud9SSMAccessRole` service role and `AWSCloud9SSMInstanceProfile` instance profile. For more information, see Creating service role and instance profile with an AWS CloudFormation template. + 1. Create the `AWSCloud9SSMAccessRole` service role and `AWSCloud9SSMInstanceProfile` instance profile. For more information, see Creating service role and instance profile with an CloudFormation template. @@ -182 +182 @@ When using an [AWS CloudFormation template](https://docs.aws.amazon.com/AWSCloud - 2. Update the policy for the IAM entity calling AWS CloudFormation. This way, the entity can start a Session Manager session that connects to the EC2 instance. For more information, see Adding Systems Manager permissions to an IAM policy. + 2. Update the policy for the IAM entity calling CloudFormation. This way, the entity can start a Session Manager session that connects to the EC2 instance. For more information, see Adding Systems Manager permissions to an IAM policy. @@ -187 +187 @@ When using an [AWS CloudFormation template](https://docs.aws.amazon.com/AWSCloud -### Creating service role and instance profile with an AWS CloudFormation template +### Creating service role and instance profile with an CloudFormation template @@ -195 +195 @@ If you previously created `AWSCloud9SSMAccessRole` and `AWSCloud9SSMInstanceProf -Suppose that you attempt to create an AWS CloudFormation stack for a no-ingress EC2 environment but you didn't first create the required service role and instance profile. Then, the stack isn't created and the following error message is displayed: +Suppose that you attempt to create an CloudFormation stack for a no-ingress EC2 environment but you didn't first create the required service role and instance profile. Then, the stack isn't created and the following error message is displayed: @@ -199 +199 @@ Suppose that you attempt to create an AWS CloudFormation stack for a no-ingress -When creating a no-ingress EC2 environment for the first time using AWS CloudFormation, you can define the `AWSCloud9SSMAccessRole` and `AWSCloud9SSMInstanceProfile` as IAM resources in the template. +When creating a no-ingress EC2 environment for the first time using CloudFormation, you can define the `AWSCloud9SSMAccessRole` and `AWSCloud9SSMInstanceProfile` as IAM resources in the template. @@ -237 +237 @@ This excerpt from a sample template shows how to define these resources. The `As -After defining a service role and instance profile in the [AWS CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html), ensure that the IAM entity creating the stack has permission to start a Session Manager session. A session is a connection made to the EC2 instance using Session Manager. +After defining a service role and instance profile in the [CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html), ensure that the IAM entity creating the stack has permission to start a Session Manager session. A session is a connection made to the EC2 instance using Session Manager. @@ -243 +243 @@ If you don't add permissions to start a Session Manager session before creating -Add the following permissions to the policy for the IAM entity by calling AWS CloudFormation. +Add the following permissions to the policy for the IAM entity by calling CloudFormation.