AWS AWSCloudFormation documentation change
Summary
Updated linear deployment documentation with detailed step calculation logic and corrected deployment type references
Security assessment
The changes clarify deployment timeout validations and calculation methods without addressing security vulnerabilities or introducing security features. Focuses on operational reliability rather than security.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md b/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md index 8c77cad94..a1dcaaa90 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-linearconfiguration.md @@ -11 +11 @@ Configuration for a linear deployment strategy that shifts production traffic in -The following validation applies only to Linear deployments created throughAWS CloudFormation.AWS CloudFormation operations time out after 36 hours. Canary 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 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: @@ -15 +15,10 @@ The following validation applies only to Linear deployments created throughAWS C -Where: Number of deployment steps = 1 ÷ StepPercent +Where the number of deployment steps is calculated as follows: + + * **If`StepPercent` evenly divides by 100**: The number of deployment steps equals `(100 ÷ StepPercent) - 1` + + * **Otherwise** : The number of deployment steps equals the floor of `100 ÷ StepPercent`. For example, if `StepPercent` is 11, the number of deployment steps is 9 (not 9.1). + + + + +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%.