AWS codecatalyst documentation change
Summary
Updated documentation to use 'CloudFormation' instead of 'AWS CloudFormation' throughout the text for consistency
Security assessment
The changes are purely branding/naming convention updates (removing 'AWS' prefix from CloudFormation references). No security-related content was added, modified, or referenced. No security vulnerabilities, permissions, or configurations were discussed.
Diff
diff --git a/codecatalyst/latest/userguide/deploy-tut-lambda.md b/codecatalyst/latest/userguide/deploy-tut-lambda.md index 4125f6fe5..78433714a 100644 --- a//codecatalyst/latest/userguide/deploy-tut-lambda.md +++ b//codecatalyst/latest/userguide/deploy-tut-lambda.md @@ -13 +13 @@ In this tutorial, you learn how to build, test, and deploy a serverless applicat -The application in this tutorial is a simple web application that outputs a 'Hello World' message. It consists of an AWS Lambda function and an Amazon API Gateway, and you build it using the [AWS Serverless Application Model (AWS SAM)](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html), which is an extension of [AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). +The application in this tutorial is a simple web application that outputs a 'Hello World' message. It consists of an AWS Lambda function and an Amazon API Gateway, and you build it using the [AWS Serverless Application Model (AWS SAM)](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html), which is an extension of [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). @@ -96 +96 @@ In this step, you create the following AWS IAM roles: - * **Deploy role** – Grants the CodeCatalyst **Deploy AWS CloudFormation stack** action permission to access your AWS account and CloudFormation service where you’ll deploy your serverless application. The **Deploy AWS CloudFormation stack** action is part of your workflow. + * **Deploy role** – Grants the CodeCatalyst **Deploy CloudFormation stack** action permission to access your AWS account and CloudFormation service where you’ll deploy your serverless application. The **Deploy CloudFormation stack** action is part of your workflow. @@ -503 +503 @@ You have now added a file called `package.json` to the root of the repository. -The `sam-template.yml` file contains the instructions for deploying the Lambda function and API Gateway and configuring them together. It follows the [AWS Serverless Application Model template specification](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-specification.html), which extends the AWS CloudFormation template specification. +The `sam-template.yml` file contains the instructions for deploying the Lambda function and API Gateway and configuring them together. It follows the [AWS Serverless Application Model template specification](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-specification.html), which extends the CloudFormation template specification. @@ -505 +505 @@ The `sam-template.yml` file contains the instructions for deploying the Lambda f -You use an AWS SAM template in this tutorial instead of a regular AWS CloudFormation template because AWS SAM offers a helpful [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html) resource type. This type performs much behind-the-scenes configuration that you normally have to write out to use the basic CloudFormation syntax. For example, the `AWS::Serverless::Function` creates a Lambda function, Lambda execution role, and event source mappings that start the function. You have to code all of this if you want to write it using basic CloudFormation. +You use an AWS SAM template in this tutorial instead of a regular CloudFormation template because AWS SAM offers a helpful [AWS::Serverless::Function](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html) resource type. This type performs much behind-the-scenes configuration that you normally have to write out to use the basic CloudFormation syntax. For example, the `AWS::Serverless::Function` creates a Lambda function, Lambda execution role, and event source mappings that start the function. You have to code all of this if you want to write it using basic CloudFormation. @@ -507 +507 @@ You use an AWS SAM template in this tutorial instead of a regular AWS CloudForma -Although this tutorial uses a pre-written template, you can generate one as part of your workflow using a build action. For more information, see [Deploying an AWS CloudFormation stack](./deploy-action-cfn.html). +Although this tutorial uses a pre-written template, you can generate one as part of your workflow using a build action. For more information, see [Deploying an CloudFormation stack](./deploy-action-cfn.html). @@ -835 +835 @@ In the preceding code, replace: - * Both instances of `us-west-2` with the Region where your Amazon S3 bucket resides (first instance) and where your stack will be deployed (second instance). These Regions can be different. This tutorial assumes that both Regions are set to `us-west-2`. For details about Regions supported by Amazon S3 and AWS CloudFormation, see [Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html) in the _AWS General Reference_. + * Both instances of `us-west-2` with the Region where your Amazon S3 bucket resides (first instance) and where your stack will be deployed (second instance). These Regions can be different. This tutorial assumes that both Regions are set to `us-west-2`. For details about Regions supported by Amazon S3 and CloudFormation, see [Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/aws-service-information.html) in the _AWS General Reference_. @@ -847 +847 @@ If you decided not to create build, deploy, and stack roles, replace `codecataly -For information about the properties in the code shown previously, see the ['Deploy AWS CloudFormation stack' action YAML](./deploy-action-ref-cfn.html). +For information about the properties in the code shown previously, see the ['Deploy CloudFormation stack' action YAML](./deploy-action-ref-cfn.html). @@ -896 +896 @@ For more information about viewing run details, see [Viewing workflow run status - * If the workflow run failed on the **DeployCloudFormationStack** action, choose the deploy action, and then choose the **Summary** tab. Scroll to the **CloudFormation events** section to view the detailed error message. If a rollback occurred, delete the `codecatalyst-cfn-stack` stack through the AWS CloudFormation console in AWS before re-running the workflow. + * If the workflow run failed on the **DeployCloudFormationStack** action, choose the deploy action, and then choose the **Summary** tab. Scroll to the **CloudFormation events** section to view the detailed error message. If a rollback occurred, delete the `codecatalyst-cfn-stack` stack through the CloudFormation console in AWS before re-running the workflow. @@ -1020 +1020 @@ Clean up the files and services used in this tutorial to avoid being charged for - 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/). @@ -1055 +1055 @@ Deleting the stack removes all tutorial resources from the API Gateway and Lambd -In this tutorial, you learned how to deploy a serverless application as a CloudFormation stack using a CodeCatalyst workflow and a **Deploy AWS CloudFormation stack** action. +In this tutorial, you learned how to deploy a serverless application as a CloudFormation stack using a CodeCatalyst workflow and a **Deploy CloudFormation stack** action. @@ -1065 +1065 @@ Deploying a CloudFormation stack -Adding the 'Deploy AWS CloudFormation stack' action +Adding the 'Deploy CloudFormation stack' action