AWS toolkit-for-vscode documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in multiple sections including service permissions, stack deletion instructions, and UI references
Security assessment
Consistency update in service naming without security implications. No evidence of security vulnerabilities, security features, or changes to security guidance in the modifications.
Diff
diff --git a/toolkit-for-vscode/latest/userguide/sam-get-started.md b/toolkit-for-vscode/latest/userguide/sam-get-started.md index a897131a8..9c9d9553e 100644 --- a//toolkit-for-vscode/latest/userguide/sam-get-started.md +++ b//toolkit-for-vscode/latest/userguide/sam-get-started.md @@ -9 +9 @@ PrerequisitesIAM permissions for serverless applicationsCreating a new serverles -The following sections describe how to get started creating an AWS Serverless Application from the AWS Toolkit for Visual Studio Code, using AWS Serverless Application Model (AWS SAM) and AWS CloudFormation stacks. +The following sections describe how to get started creating an AWS Serverless Application from the AWS Toolkit for Visual Studio Code, using AWS Serverless Application Model (AWS SAM) and CloudFormation stacks. @@ -32 +32 @@ The following operations may require you to exit or restart VS Code before the c -In the Toolkit for VS Code you must have a credentials profile that contains the AWS Identity and Access Management (IAM) permissions necessary to deploy and run serverless applications. You must have appropriate read/write access to the following services: AWS CloudFormation, IAM, Lambda, Amazon API Gateway, Amazon Simple Storage Service (Amazon S3), and Amazon Elastic Container Registry (Amazon ECR). +In the Toolkit for VS Code you must have a credentials profile that contains the AWS Identity and Access Management (IAM) permissions necessary to deploy and run serverless applications. You must have appropriate read/write access to the following services: CloudFormation, IAM, Lambda, Amazon API Gateway, Amazon Simple Storage Service (Amazon S3), and Amazon Elastic Container Registry (Amazon ECR). @@ -239 +239 @@ When the deployment is complete, you see your application listed in the **AWS Ex -Deleting a serverless application involves deleting the AWS CloudFormation stack that you previously deployed to the AWS Cloud. Note that this procedure does not delete your application directory from your local host. +Deleting a serverless application involves deleting the CloudFormation stack that you previously deployed to the AWS Cloud. Note that this procedure does not delete your application directory from your local host. @@ -243 +243 @@ Deleting a serverless application involves deleting the AWS CloudFormation stack - 2. In the **AWS Toolkit Explorer** window, expand the Region containing the deployed application that you want to delete, and then expand **AWS CloudFormation**. + 2. In the **AWS Toolkit Explorer** window, expand the Region containing the deployed application that you want to delete, and then expand **CloudFormation**. @@ -245 +245 @@ Deleting a serverless application involves deleting the AWS CloudFormation stack - 3. Open the context (right-click) menu for the name of the AWS CloudFormation stack that corresponds to the serverless application that you want to delete, and then choose **Delete AWS CloudFormation Stack**. + 3. Open the context (right-click) menu for the name of the CloudFormation stack that corresponds to the serverless application that you want to delete, and then choose **Delete CloudFormation Stack**. @@ -252 +252 @@ Deleting a serverless application involves deleting the AWS CloudFormation stack -If the stack deletion succeeds, the Toolkit for VS Code removes the stack name from the AWS CloudFormation list in **AWS Explorer**. +If the stack deletion succeeds, the Toolkit for VS Code removes the stack name from the CloudFormation list in **AWS Explorer**.