AWS Security ChangesHomeSearch

AWS AWSCloudFormation documentation change

Service: AWSCloudFormation · 2025-07-18 · Documentation low

File: AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentconfiguration.md

Summary

Added BakeTimeInMinutes, LifecycleHooks, and Strategy properties for ECS deployment configurations

Security assessment

These changes add new deployment configuration options but don't directly address security vulnerabilities. The blue/green strategy improves deployment safety but isn't explicitly a security feature.

Diff

diff --git a/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentconfiguration.md b/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentconfiguration.md
index 823e0d673..68fc4ae1a 100644
--- a//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentconfiguration.md
+++ b//AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-deploymentconfiguration.md
@@ -19,0 +20 @@ To declare this entity in your AWS CloudFormation template, use the following sy
+      "BakeTimeInMinutes" : Integer,
@@ -20,0 +22 @@ To declare this entity in your AWS CloudFormation template, use the following sy
+      "LifecycleHooks" : [ [DeploymentLifecycleHook](./aws-properties-ecs-service-deploymentlifecyclehook.html), ... ],
@@ -22 +24,2 @@ To declare this entity in your AWS CloudFormation template, use the following sy
-      "MinimumHealthyPercent" : Integer
+      "MinimumHealthyPercent" : Integer,
+      "Strategy" : String
@@ -30,0 +34 @@ To declare this entity in your AWS CloudFormation template, use the following sy
+      BakeTimeInMinutes: Integer
@@ -32,0 +37,2 @@ To declare this entity in your AWS CloudFormation template, use the following sy
+      LifecycleHooks: 
+        - [DeploymentLifecycleHook](./aws-properties-ecs-service-deploymentlifecyclehook.html)
@@ -34,0 +41 @@ To declare this entity in your AWS CloudFormation template, use the following sy
+      Strategy: String
@@ -49,0 +57,26 @@ _Required_ : No
+`BakeTimeInMinutes`
+    
+
+The duration when both blue and green service revisions are running simultaneously after the production traffic has shifted.
+
+The following rules apply when you don't specify a value:
+
+  * For rolling deployments, the value is set to 3 hours (180 minutes).
+
+  * When you use an external deployment controller (`EXTERNAL`), or the CodeDeploy blue/green deployment controller (`CODE_DEPLOY`), the value is set to 3 hours (180 minutes).
+
+  * For all other cases, the value is set to 36 hours (2160 minutes).
+
+
+
+
+_Required_ : No
+
+ _Type_ : Integer
+
+ _Minimum_ : `0`
+
+ _Maximum_ : `1440`
+
+ _Update requires_ : [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
+
@@ -64,0 +98,11 @@ _Required_ : No
+`LifecycleHooks`
+    
+
+An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle.
+
+_Required_ : No
+
+ _Type_ : Array of [DeploymentLifecycleHook](./aws-properties-ecs-service-deploymentlifecyclehook.html)
+
+ _Update requires_ : [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)
+
@@ -129,0 +174,20 @@ _Required_ : No
+
+`Strategy`
+    
+
+The deployment strategy for the service. Choose from these valid values:
+
+  * `ROLLING` \- When you create a service which uses the rolling update (`ROLLING`) deployment strategy, the Amazon ECS service scheduler replaces the currently running tasks with new tasks. The number of tasks that Amazon ECS adds or removes from the service during a rolling update is controlled by the service deployment configuration.
+
+  * `BLUE_GREEN` \- A blue/green deployment strategy (`BLUE_GREEN`) is a release methodology that reduces downtime and risk by running two identical production environments called blue and green. With Amazon ECS blue/green deployments, you can validate new service revisions before directing production traffic to them. This approach provides a safer way to deploy changes with the ability to quickly roll back if needed.
+
+
+
+
+_Required_ : No
+
+ _Type_ : String
+
+ _Allowed values_ : `ROLLING | BLUE_GREEN`
+
+ _Update requires_ : [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)