AWS AWSCloudFormation documentation change
Summary
Updated branding from 'AWS CloudFormation' to 'CloudFormation' and clarified timeout limitations for linear deployments
Security assessment
Changes are branding/terminology updates and operational timeout clarifications. No security vulnerabilities or security features are mentioned.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md b/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md index a1dcaaa90..4382e3922 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md @@ -5 +5 @@ SyntaxProperties -This is the new _AWS CloudFormation Template Reference Guide_. Please update your bookmarks and links. For help getting started with CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). +This is the new _CloudFormation Template Reference Guide_. Please update your bookmarks and links. For help getting started with CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). @@ -11 +11 @@ Configuration for a linear deployment strategy that shifts production traffic in -The following validation applies only to Linear deployments created through AWS CloudFormation. AWS CloudFormation operations time out after 36 hours. Linear deployments can approach this limit because of their extended duration. This can cause AWS CloudFormation to roll back the deployment. To prevent timeout-related rollbacks, AWS CloudFormation rejects deployments when the calculated deployment time exceeds 33 hours based on your template configuration: +The following validation applies only to Linear deployments created through CloudFormation. CloudFormation operations time out after 36 hours. Linear deployments can approach this limit because of their extended duration. This can cause CloudFormation to roll back the deployment. To prevent timeout-related rollbacks, CloudFormation rejects deployments when the calculated deployment time exceeds 33 hours based on your template configuration: @@ -24 +24 @@ Where the number of deployment steps is calculated as follows: -This calculation reflects that AWS CloudFormation doesn't apply the step bake time after the final traffic shift reaches 100%. For example, with a `StepPercent` of 50%, there are actually two traffic shifts, but only one deployment step is counted for validation purposes because the bake time is applied only after the first 50% shift, not after reaching 100%. +This calculation reflects that CloudFormation doesn't apply the step bake time after the final traffic shift reaches 100%. For example, with a `StepPercent` of 50%, there are actually two traffic shifts, but only one deployment step is counted for validation purposes because the bake time is applied only after the first 50% shift, not after reaching 100%. @@ -30 +30 @@ Additional backend processes (such as task scaling and running lifecycle hooks) -To declare this entity in your AWS CloudFormation template, use the following syntax: +To declare this entity in your CloudFormation template, use the following syntax: