AWS cdk documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The changes are purely editorial/terminology updates (removing redundant 'AWS' prefix from CloudFormation references). No security-related content was added or modified. The existing example about encrypted S3 buckets remains unchanged.
Diff
diff --git a/cdk/v1/guide/stack-how-to-create-multiple-stacks.md b/cdk/v1/guide/stack-how-to-create-multiple-stacks.md index 7be96a4e5..a0a280558 100644 --- a//cdk/v1/guide/stack-how-to-create-multiple-stacks.md +++ b//cdk/v1/guide/stack-how-to-create-multiple-stacks.md @@ -9 +9 @@ This is the AWS CDK v1 Developer Guide. The older CDK v1 entered maintenance on -Most of the other code examples in the _AWS CDK Developer Guide_ involve only a single stack. However, you can create apps containing any number of stacks. Each stack results in its own AWS CloudFormation template. Stacks are the _unit of deployment:_ each stack in an app can be synthesized and deployed individually using the `cdk deploy` command. +Most of the other code examples in the _AWS CDK Developer Guide_ involve only a single stack. However, you can create apps containing any number of stacks. Each stack results in its own CloudFormation template. Stacks are the _unit of deployment:_ each stack in an app can be synthesized and deployed individually using the `cdk deploy` command. @@ -572 +572 @@ This code uses the new `encryptBucket` (Python: `encrypt_bucket`) property on th -Now you can deploy stacks from the app. First, synthesize a AWS CloudFormation template for `MyEastCdkStack`—the stack in `us-east-1`. This is the stack with the encrypted S3 bucket. +Now you can deploy stacks from the app. First, synthesize a CloudFormation template for `MyEastCdkStack`—the stack in `us-east-1`. This is the stack with the encrypted S3 bucket. @@ -577 +577 @@ Now you can deploy stacks from the app. First, synthesize a AWS CloudFormation t -The output should look similar to the following AWS CloudFormation template (there might be slight differences). +The output should look similar to the following CloudFormation template (there might be slight differences).