AWS cdk documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' throughout the document
Security assessment
The changes are purely branding/terminology updates (removing redundant 'AWS' prefix from CloudFormation references). No security vulnerabilities, mitigations, or security features are mentioned or implied in the changes.
Diff
diff --git a/cdk/v1/guide/identifiers.md b/cdk/v1/guide/identifiers.md index 198e68d69..dbe0f9a51 100644 --- a//cdk/v1/guide/identifiers.md +++ b//cdk/v1/guide/identifiers.md @@ -182 +182 @@ C# -Since AWS CloudFormation requires that all logical IDs in a template are unique, the AWS CDK must be able to generate a unique identifier for each construct in an application. Resources have paths that are globally unique (the names of all scopes from the stack to a specific resource) so the AWS CDK generates the necessary unique identifiers by concatenating the elements of the path and adding an 8-digit hash. (The hash is necessary to distinguish distinct paths, such as `A/B/C` and `A/BC`, that would result in the same AWS CloudFormation identifier, since AWS CloudFormation identifiers are alphanumeric and cannot contain slashes or other separator characters.) The AWS CDK calls this string the _unique ID_ of the construct. +Since CloudFormation requires that all logical IDs in a template are unique, the AWS CDK must be able to generate a unique identifier for each construct in an application. Resources have paths that are globally unique (the names of all scopes from the stack to a specific resource) so the AWS CDK generates the necessary unique identifiers by concatenating the elements of the path and adding an 8-digit hash. (The hash is necessary to distinguish distinct paths, such as `A/B/C` and `A/BC`, that would result in the same CloudFormation identifier, since CloudFormation identifiers are alphanumeric and cannot contain slashes or other separator characters.) The AWS CDK calls this string the _unique ID_ of the construct. @@ -216 +216 @@ C# -The _address_ is another kind of unique identifier that uniquely distinguishes CDK resources. Derived from the SHA-1 hash of the path, it is not human-readable, but its constant, relatively short length (always 42 hexadecimal characters) makes it useful in situations where the "traditional" unique ID might be too long. Some constructs may use the address in the synthesized AWS CloudFormation template instead of the unique ID. Again, your app generally should not need to know about its constructs' addresses, but you can retrieve a construct's address as follows. +The _address_ is another kind of unique identifier that uniquely distinguishes CDK resources. Derived from the SHA-1 hash of the path, it is not human-readable, but its constant, relatively short length (always 42 hexadecimal characters) makes it useful in situations where the "traditional" unique ID might be too long. Some constructs may use the address in the synthesized CloudFormation template instead of the unique ID. Again, your app generally should not need to know about its constructs' addresses, but you can retrieve a construct's address as follows. @@ -250 +250 @@ C# -Unique IDs serve as the _logical identifiers_ , which are sometimes called _logical names_ , of resources in the generated AWS CloudFormation templates for those constructs that represent AWS resources. +Unique IDs serve as the _logical identifiers_ , which are sometimes called _logical names_ , of resources in the generated CloudFormation templates for those constructs that represent AWS resources. @@ -252 +252 @@ Unique IDs serve as the _logical identifiers_ , which are sometimes called _logi -For example, the Amazon S3 bucket in the previous example that is created within `Stack2` results in an `AWS::S3::Bucket` resource with the logical ID `Stack2MyBucket4DD88B4F` in the resulting AWS CloudFormation template. +For example, the Amazon S3 bucket in the previous example that is created within `Stack2` results in an `AWS::S3::Bucket` resource with the logical ID `Stack2MyBucket4DD88B4F` in the resulting CloudFormation template. @@ -256 +256 @@ For example, the Amazon S3 bucket in the previous example that is created within -Avoid changing the logical ID of a resource after it has been created. Since AWS CloudFormation identifies resources by their logical ID, if you change the logical ID of a resource, AWS CloudFormation creates a new resource with the new logical ID, then deletes the existing one. Depending on the type of resource, this may cause service interruption or data loss, or both. +Avoid changing the logical ID of a resource after it has been created. Since CloudFormation identifies resources by their logical ID, if you change the logical ID of a resource, CloudFormation creates a new resource with the new logical ID, then deletes the existing one. Depending on the type of resource, this may cause service interruption or data loss, or both.