AWS cloud9 documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout troubleshooting documentation for consistency
Security assessment
Changes are purely branding/terminology updates (shortening AWS CloudFormation to CloudFormation) without altering technical content. No security vulnerabilities, mitigations, or new security features are introduced.
Diff
diff --git a/cloud9/latest/user-guide/troubleshooting.md b/cloud9/latest/user-guide/troubleshooting.md index 93b2035e8..1b0cfbd8f 100644 --- a//cloud9/latest/user-guide/troubleshooting.md +++ b//cloud9/latest/user-guide/troubleshooting.md @@ -254 +254 @@ Suppose that the environment owner and collaborator belong to the same AWS accou -**Possible cause:** AWS CloudFormation might have a problem deleting one or more of the environments. AWS Cloud9 relies on AWS CloudFormation to create and delete environments. +**Possible cause:** AWS CloudFormation might have a problem deleting one or more of the environments. AWS Cloud9 relies on CloudFormation to create and delete environments. @@ -256 +256 @@ Suppose that the environment owner and collaborator belong to the same AWS accou -**Recommended solution:** Try using AWS CloudFormation to delete each of the undeleted environments. +**Recommended solution:** Try using CloudFormation to delete each of the undeleted environments. @@ -258 +258 @@ Suppose that the environment owner and collaborator belong to the same AWS accou - 1. Open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). + 1. Open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/). @@ -262 +262 @@ Suppose that the environment owner and collaborator belong to the same AWS accou - 3. In the list of AWS CloudFormation stacks, select the entry where **Stack name** contains the undeleted environment name and **Status** is **DELETE_FAILED**. For example, if the environment name is `my-demo-environment`, choose the stack that begins with the name **aws-cloud9-my-demo-environment**. (Choose the box or option next to the environment name, not the environment name itself.) + 3. In the list of CloudFormation stacks, select the entry where **Stack name** contains the undeleted environment name and **Status** is **DELETE_FAILED**. For example, if the environment name is `my-demo-environment`, choose the stack that begins with the name **aws-cloud9-my-demo-environment**. (Choose the box or option next to the environment name, not the environment name itself.) @@ -281 +281 @@ Manually deleting a failed stack's resources doesn't remove the stack itself fro -To manually delete these resources, do the following. In the AWS CloudFormation console, choose the failed stack, and then select the **Resources** section. Go to the console in AWS for each resource in this list, and then use that console to delete the resource. +To manually delete these resources, do the following. In the CloudFormation console, choose the failed stack, and then select the **Resources** section. Go to the console in AWS for each resource in this list, and then use that console to delete the resource. @@ -472 +472 @@ For configuration information, see [VPC and subnet sizing](https://docs.aws.amaz -**Possible causes:** AWS License Manager streamlines the management of software vendor licenses across the AWS Cloud. When setting up License Manager, you create license configurations, which are sets of licensing rules based on the terms of your enterprise agreements. These license configurations can be attached to a mechanism, such as an Amazon Machine Image (AMI) or AWS CloudFormation. You can use one of these mechanisms to launch EC2 instances. +**Possible causes:** AWS License Manager streamlines the management of software vendor licenses across the AWS Cloud. When setting up License Manager, you create license configurations, which are sets of licensing rules based on the terms of your enterprise agreements. These license configurations can be attached to a mechanism, such as an Amazon Machine Image (AMI) or CloudFormation. You can use one of these mechanisms to launch EC2 instances. @@ -486 +486 @@ Older versions of **AWSCloud9ServiceRolePolicy** for the AWSServiceRoleForAWSClo -### Error message reporting "Instance profile AWSCloud9SSMInstanceProfile does not exist in account" when creating EC2 environment using AWS CloudFormation +### Error message reporting "Instance profile AWSCloud9SSMInstanceProfile does not exist in account" when creating EC2 environment using CloudFormation @@ -488 +488 @@ Older versions of **AWSCloud9ServiceRolePolicy** for the AWSServiceRoleForAWSClo -**Issue:** When using the [ AWS::Cloud9::EnvironmentEC2](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) AWS CloudFormation resource to create an EC2 environment, users receive an error message that **`Instance profile AWSCloud9SSMInstanceProfile does not exist in account.`** +**Issue:** When using the [ AWS::Cloud9::EnvironmentEC2](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) CloudFormation resource to create an EC2 environment, users receive an error message that **`Instance profile AWSCloud9SSMInstanceProfile does not exist in account.`** @@ -492 +492 @@ Older versions of **AWSCloud9ServiceRolePolicy** for the AWSServiceRoleForAWSClo -If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole` and `AWSCloud9SSMInstanceProfile` are created automatically. But when using AWS CloudFormation or AWS CLI to create your first no-ingress environment, you must create these IAM resources manually. +If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole` and `AWSCloud9SSMInstanceProfile` are created automatically. But when using CloudFormation or AWS CLI to create your first no-ingress environment, you must create these IAM resources manually. @@ -494 +494 @@ If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole -**Recommended solution:** For information about editing your AWS CloudFormation template and updating IAM permissions, see [Using AWS CloudFormation to create no-ingress EC2 environments](./ec2-ssm.html#cfn-role-and-permissions) +**Recommended solution:** For information about editing your CloudFormation template and updating IAM permissions, see [Using CloudFormation to create no-ingress EC2 environments](./ec2-ssm.html#cfn-role-and-permissions) @@ -496 +496 @@ If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole -### Error message reporting "not authorized to `perform: ssm:StartSession` on resource" when creating EC2 environment using AWS CloudFormation +### Error message reporting "not authorized to `perform: ssm:StartSession` on resource" when creating EC2 environment using CloudFormation @@ -498 +498 @@ If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole -**Issue:** When using the [ AWS::Cloud9::EnvironmentEC2](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) AWS CloudFormation resource to create an EC2 environment, users receive an `AccessDeniedException` and are informed that they're "not authorized to perform: `ssm:StartSession` on resource." +**Issue:** When using the [ AWS::Cloud9::EnvironmentEC2](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloud9-environmentec2.html) CloudFormation resource to create an EC2 environment, users receive an `AccessDeniedException` and are informed that they're "not authorized to perform: `ssm:StartSession` on resource." @@ -502 +502 @@ If you create a no-ingress environment with the console, `AWSCloud9SSMAccessRole -**Recommended solution:** For information about editing your AWS CloudFormation template and updating IAM permissions, see [Using AWS CloudFormation to create no-ingress EC2 environments](./ec2-ssm.html#cfn-role-and-permissions). +**Recommended solution:** For information about editing your CloudFormation template and updating IAM permissions, see [Using CloudFormation to create no-ingress EC2 environments](./ec2-ssm.html#cfn-role-and-permissions). @@ -534 +534 @@ If you accept the default VPC settings, the Amazon EC2 instance is launched into -You can confirm that the error is caused by the EC2 instance not being in the default VPC. Use AWS CloudFormation to view the stack event history for the development environment. +You can confirm that the error is caused by the EC2 instance not being in the default VPC. Use CloudFormation to view the stack event history for the development environment. @@ -536 +536 @@ You can confirm that the error is caused by the EC2 instance not being in the de - 1. Open the AWS CloudFormation console. For more information, see [Logging in to the AWS CloudFormation console.](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-login.html) + 1. Open the CloudFormation console. For more information, see [Logging in to the CloudFormation console.](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-login.html) @@ -538 +538 @@ You can confirm that the error is caused by the EC2 instance not being in the de - 2. In the AWS CloudFormation console, choose **Stacks**. + 2. In the CloudFormation console, choose **Stacks**. @@ -676 +676 @@ For more information about this task, see [Create an AWS Cloud9 that uses Amazon -**Possible causes:** AWS License Manager streamlines the management of software vendor licenses across the AWS Cloud. When setting up License Manager, you create license configurations, which are sets of licensing rules based on the terms of your enterprise agreements. These license configurations can be attached to a mechanism, such as an Amazon Machine Image (AMI) or AWS CloudFormation. You can use one of these mechanisms to launch EC2 instances. +**Possible causes:** AWS License Manager streamlines the management of software vendor licenses across the AWS Cloud. When setting up License Manager, you create license configurations, which are sets of licensing rules based on the terms of your enterprise agreements. These license configurations can be attached to a mechanism, such as an Amazon Machine Image (AMI) or CloudFormation. You can use one of these mechanisms to launch EC2 instances.