AWS cdk documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The changes are purely terminological, removing redundant 'AWS' prefixes from CloudFormation references. No security implications or security-related content modifications are present.
Diff
diff --git a/cdk/v1/guide/apps.md b/cdk/v1/guide/apps.md index b635c1845..338e907f8 100644 --- a//cdk/v1/guide/apps.md +++ b//cdk/v1/guide/apps.md @@ -76 +76 @@ C# -However, this code has only _declared_ a stack. For the stack to actually be synthesized into a AWS CloudFormation template and deployed, it needs to be instantiated. And, like all CDK constructs, it must be instantiated in some context. The `App` is that context. +However, this code has only _declared_ a stack. For the stack to actually be synthesized into a CloudFormation template and deployed, it needs to be instantiated. And, like all CDK constructs, it must be instantiated in some context. The `App` is that context. @@ -80 +80 @@ However, this code has only _declared_ a stack. For the stack to actually be syn -To define the previous stack within the scope of an application, use the [App](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.App.html) construct. The following example app instantiates a `MyFirstStack` and produces the AWS CloudFormation template that the stack defined. +To define the previous stack within the scope of an application, use the [App](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.App.html) construct. The following example app instantiates a `MyFirstStack` and produces the CloudFormation template that the stack defined. @@ -150 +150 @@ All constructs that have implemented the `validate` method can validate themselv -This is the final stage of the execution of your AWS CDK app. It's triggered by a call to `app.synth()`, and it traverses the construct tree and invokes the `synthesize` method on all constructs. Constructs that implement `synthesize` can participate in synthesis and emit deployment artifacts to the resulting cloud assembly. These artifacts include AWS CloudFormation templates, AWS Lambda application bundles, file and Docker image assets, and other deployment artifacts. Cloud assemblies describes the output of this phase. In most cases, you won't need to implement the `synthesize` method +This is the final stage of the execution of your AWS CDK app. It's triggered by a call to `app.synth()`, and it traverses the construct tree and invokes the `synthesize` method on all constructs. Constructs that implement `synthesize` can participate in synthesis and emit deployment artifacts to the resulting cloud assembly. These artifacts include CloudFormation templates, AWS Lambda application bundles, file and Docker image assets, and other deployment artifacts. Cloud assemblies describes the output of this phase. In most cases, you won't need to implement the `synthesize` method @@ -155 +155 @@ This is the final stage of the execution of your AWS CDK app. It's triggered by -In this phase, the AWS CDK Toolkit takes the deployment artifacts cloud assembly produced by the synthesis phase and deploys it to an AWS environment. It uploads assets to Amazon S3 and Amazon ECR, or wherever they need to go, and then starts an AWS CloudFormation deployment to deploy the application and create the resources. +In this phase, the AWS CDK Toolkit takes the deployment artifacts cloud assembly produced by the synthesis phase and deploys it to an AWS environment. It uploads assets to Amazon S3 and Amazon ECR, or wherever they need to go, and then starts an CloudFormation deployment to deploy the application and create the resources. @@ -157 +157 @@ In this phase, the AWS CDK Toolkit takes the deployment artifacts cloud assembly -By the time the AWS CloudFormation deployment phase (step 5) starts, your AWS CDK app has already finished and exited. This has the following implications: +By the time the CloudFormation deployment phase (step 5) starts, your AWS CDK app has already finished and exited. This has the following implications: @@ -159 +159 @@ By the time the AWS CloudFormation deployment phase (step 5) starts, your AWS CD - * The AWS CDK app can't respond to events that happen during deployment, such as a resource being created or the whole deployment finishing. To run code during the deployment phase, you must inject it into the AWS CloudFormation template as a [custom resource](./cfn-layer.html#cfn-layer-custom). For more information about adding a custom resource to your app, see the [AWS CloudFormation module](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_cloudformation-readme.html), or the [custom-resource](https://github.com/aws-samples/aws-cdk-examples/tree/CDKv1/typescript/custom-resource/) example. + * The AWS CDK app can't respond to events that happen during deployment, such as a resource being created or the whole deployment finishing. To run code during the deployment phase, you must inject it into the CloudFormation template as a [custom resource](./cfn-layer.html#cfn-layer-custom). For more information about adding a custom resource to your app, see the [CloudFormation module](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_cloudformation-readme.html), or the [custom-resource](https://github.com/aws-samples/aws-cdk-examples/tree/CDKv1/typescript/custom-resource/) example. @@ -168 +168 @@ By the time the AWS CloudFormation deployment phase (step 5) starts, your AWS CD -The call to `app.synth()` is what tells the AWS CDK to synthesize a cloud assembly from an app. Typically you don't interact directly with cloud assemblies. They are files that include everything needed to deploy your app to a cloud environment. For example, it includes an AWS CloudFormation template for each stack in your app, and a copy of any file assets or Docker images that you reference in your app. +The call to `app.synth()` is what tells the AWS CDK to synthesize a cloud assembly from an app. Typically you don't interact directly with cloud assemblies. They are files that include everything needed to deploy your app to a cloud environment. For example, it includes an CloudFormation template for each stack in your app, and a copy of any file assets or Docker images that you reference in your app.