AWS AWSCloudFormation documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' and clarified behavior changes for CapacityProviderStrategy property. Added guidance for handling empty lists in CapacityProviderStrategy to avoid deployment errors.
Security assessment
The changes primarily address documentation clarity and behavior updates for CapacityProviderStrategy configuration. While the update impacts deployment behavior, there is no evidence of addressing a security vulnerability or introducing security features. The focus is on preventing configuration errors rather than mitigating security risks.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.md b/AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.md index d23673807..1fe410ce9 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-resource-ecs-service.md @@ -5 +5 @@ SyntaxPropertiesReturn valuesExamples -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). @@ -21 +21 @@ Starting April 15, 2023, AWS; will not onboard new customers to Amazon Elastic I -On June 12, 2025, Amazon ECS launched support for updating capacity provider configuration for Amazon ECS services. With this launch, Amazon ECS also aligned the AWS CloudFormation update behavior for `CapacityProviderStrategy` parameter with the standard practice. For more information, see [Amazon ECS adds support for updating capacity provider configuration for ECS services](https://aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/). Previously Amazon ECS ignored the `CapacityProviderStrategy` property if it was set to an empty list for example, `[]` in AWS CloudFormation, because updating capacity provider configuration was not supported. Now, with support for capacity provider updates, customers can remove capacity providers from a service by passing an empty list. When you specify an empty list (`[]`) for the `CapacityProviderStrategy` property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows: +On June 12, 2025, Amazon ECS launched support for updating capacity provider configuration for Amazon ECS services. With this launch, Amazon ECS also aligned the CloudFormation update behavior for `CapacityProviderStrategy` parameter with the standard practice. For more information, see [Amazon ECS adds support for updating capacity provider configuration for ECS services](https://aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/). Previously Amazon ECS ignored the `CapacityProviderStrategy` property if it was set to an empty list for example, `[]` in CloudFormation, because updating capacity provider configuration was not supported. Now, with support for capacity provider updates, customers can remove capacity providers from a service by passing an empty list. When you specify an empty list (`[]`) for the `CapacityProviderStrategy` property in your CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows: @@ -42 +42 @@ Recommended Actions -If you are currently using `CapacityProviderStrategy: []` in your AWS CloudFormation templates, you should take one of the following actions: +If you are currently using `CapacityProviderStrategy: []` in your CloudFormation templates, you should take one of the following actions: @@ -46 +46 @@ If you are currently using `CapacityProviderStrategy: []` in your AWS CloudForma - * Remove the `CapacityProviderStrategy` property entirely from your AWS CloudFormation template + * Remove the `CapacityProviderStrategy` property entirely from your CloudFormation template @@ -50 +50 @@ If you are currently using `CapacityProviderStrategy: []` in your AWS CloudForma - * If you intend to maintain or update the Capacity Provider Strategy, specify the actual Capacity Provider Strategy for the service in your AWS CloudFormation template. + * If you intend to maintain or update the Capacity Provider Strategy, specify the actual Capacity Provider Strategy for the service in your CloudFormation template. @@ -55 +55 @@ If you are currently using `CapacityProviderStrategy: []` in your AWS CloudForma -If your AWS CloudFormation template had an empty list ([]) for `CapacityProviderStrategy` prior to the aforementioned launch on June 12, and you are using the same template with `CapacityProviderStrategy: []`, you might encounter the following error: +If your CloudFormation template had an empty list ([]) for `CapacityProviderStrategy` prior to the aforementioned launch on June 12, and you are using the same template with `CapacityProviderStrategy: []`, you might encounter the following error: @@ -59 +59 @@ Invalid request provided: When switching from launch type to capacity provider s -Note that AWS CloudFormation automatically initiates a new deployment when it detects a parameter change, but customers cannot choose to force a deployment through AWS CloudFormation. This is an invalid input scenario that requires one of the remediation actions listed above. +Note that CloudFormation automatically initiates a new deployment when it detects a parameter change, but customers cannot choose to force a deployment through CloudFormation. This is an invalid input scenario that requires one of the remediation actions listed above. @@ -65 +65 @@ If you are experiencing active production issues related to this change, contact -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: