Class CfnService

The AWS::ECS::Service resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

Inheritance

object

CfnElement

CfnRefElement

CfnResource

CfnService

Implements

IInspectable

ITaggable

Inherited Members

CfnResource.IsCfnResource(object)

CfnResource.AddDeletionOverride(string)

CfnResource.AddDependency(CfnResource)

CfnResource.AddDependsOn(CfnResource)

CfnResource.AddMetadata(string, object)

CfnResource.AddOverride(string, object)

CfnResource.AddPropertyDeletionOverride(string)

CfnResource.AddPropertyOverride(string, object)

CfnResource.ApplyRemovalPolicy(RemovalPolicy?, IRemovalPolicyOptions)

CfnResource.GetAtt(string, ResolutionTypeHint?)

CfnResource.GetMetadata(string)

CfnResource.ObtainDependencies()

CfnResource.ObtainResourceDependencies()

CfnResource.RemoveDependency(CfnResource)

CfnResource.ReplaceDependency(CfnResource, CfnResource)

CfnResource.ShouldSynthesize()

CfnResource.ToString()

CfnResource.ValidateProperties(object)

CfnResource.CfnOptions

CfnResource.CfnResourceType

CfnResource.UpdatedProperites

CfnResource.UpdatedProperties

CfnRefElement.Ref

CfnElement.IsCfnElement(object)

CfnElement.OverrideLogicalId(string)

CfnElement.CreationStack

CfnElement.LogicalId

CfnElement.Stack

Namespace: Amazon.CDK.AWS.ECS

Assembly: Amazon.CDK.Lib.dll

Syntax (csharp)

public class CfnService : CfnResource, IInspectable, ITaggable

Syntax (vb)

Public Class CfnService Inherits CfnResource Implements IInspectable, ITaggable

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

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:

Invalid request provided: When switching from launch type to capacity provider strategy on an existing service, or making a change to a capacity provider strategy on a service that is already using one, you must force a new deployment. (Service: Ecs, Status Code: 400, Request ID: xxx) (SDK Attempt Count: 1)" (RequestToken: xxx HandlerErrorCode: InvalidRequest)

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.

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Examples

// The code below shows an example of how to instantiate this type.
             // The values are placeholders you should change.
             using Amazon.CDK.AWS.ECS;

             var cfnService = new CfnService(this, "MyCfnService", new CfnServiceProps {
                 AvailabilityZoneRebalancing = "availabilityZoneRebalancing",
                 CapacityProviderStrategy = new [] { new CapacityProviderStrategyItemProperty {
                     Base = 123,
                     CapacityProvider = "capacityProvider",
                     Weight = 123
                 } },
                 Cluster = "cluster",
                 DeploymentConfiguration = new DeploymentConfigurationProperty {
                     Alarms = new DeploymentAlarmsProperty {
                         AlarmNames = new [] { "alarmNames" },
                         Enable = false,
                         Rollback = false
                     },
                     BakeTimeInMinutes = 123,
                     DeploymentCircuitBreaker = new DeploymentCircuitBreakerProperty {
                         Enable = false,
                         Rollback = false
                     },
                     LifecycleHooks = new [] { new DeploymentLifecycleHookProperty {
                         HookTargetArn = "hookTargetArn",
                         LifecycleStages = new [] { "lifecycleStages" },
                         RoleArn = "roleArn"
                     } },
                     MaximumPercent = 123,
                     MinimumHealthyPercent = 123,
                     Strategy = "strategy"
                 },
                 DeploymentController = new DeploymentControllerProperty {
                     Type = "type"
                 },
                 DesiredCount = 123,
                 EnableEcsManagedTags = false,
                 EnableExecuteCommand = false,
                 ForceNewDeployment = new ForceNewDeploymentProperty {
                     EnableForceNewDeployment = false,

                     // the properties below are optional
                     ForceNewDeploymentNonce = "forceNewDeploymentNonce"
                 },
                 HealthCheckGracePeriodSeconds = 123,
                 LaunchType = "launchType",
                 LoadBalancers = new [] { new LoadBalancerProperty {
                     AdvancedConfiguration = new AdvancedConfigurationProperty {
                         AlternateTargetGroupArn = "alternateTargetGroupArn",

                         // the properties below are optional
                         ProductionListenerRule = "productionListenerRule",
                         RoleArn = "roleArn",
                         TestListenerRule = "testListenerRule"
                     },
                     ContainerName = "containerName",
                     ContainerPort = 123,
                     LoadBalancerName = "loadBalancerName",
                     TargetGroupArn = "targetGroupArn"
                 } },
                 NetworkConfiguration = new NetworkConfigurationProperty {
                     AwsvpcConfiguration = new AwsVpcConfigurationProperty {
                         AssignPublicIp = "assignPublicIp",
                         SecurityGroups = new [] { "securityGroups" },
                         Subnets = new [] { "subnets" }
                     }
                 },
                 PlacementConstraints = new [] { new PlacementConstraintProperty {
                     Type = "type",

                     // the properties below are optional
                     Expression = "expression"
                 } },
                 PlacementStrategies = new [] { new PlacementStrategyProperty {
                     Type = "type",

                     // the properties below are optional
                     Field = "field"
                 } },
                 PlatformVersion = "platformVersion",
                 PropagateTags = "propagateTags",
                 Role = "role",
                 SchedulingStrategy = "schedulingStrategy",
                 ServiceConnectConfiguration = new ServiceConnectConfigurationProperty {
                     Enabled = false,

                     // the properties below are optional
                     LogConfiguration = new LogConfigurationProperty {
                         LogDriver = "logDriver",
                         Options = new Dictionary<string, string> {
                             { "optionsKey", "options" }
                         },
                         SecretOptions = new [] { new SecretProperty {
                             Name = "name",
                             ValueFrom = "valueFrom"
                         } }
                     },
                     Namespace = "namespace",
                     Services = new [] { new ServiceConnectServiceProperty {
                         PortName = "portName",

                         // the properties below are optional
                         ClientAliases = new [] { new ServiceConnectClientAliasProperty {
                             Port = 123,

                             // the properties below are optional
                             DnsName = "dnsName",
                             TestTrafficRules = new ServiceConnectTestTrafficRulesProperty {
                                 Header = new ServiceConnectTestTrafficRulesHeaderProperty {
                                     Name = "name",

                                     // the properties below are optional
                                     Value = new ServiceConnectTestTrafficRulesHeaderValueProperty {
                                         Exact = "exact"
                                     }
                                 }
                             }
                         } },
                         DiscoveryName = "discoveryName",
                         IngressPortOverride = 123,
                         Timeout = new TimeoutConfigurationProperty {
                             IdleTimeoutSeconds = 123,
                             PerRequestTimeoutSeconds = 123
                         },
                         Tls = new ServiceConnectTlsConfigurationProperty {
                             IssuerCertificateAuthority = new ServiceConnectTlsCertificateAuthorityProperty {
                                 AwsPcaAuthorityArn = "awsPcaAuthorityArn"
                             },

                             // the properties below are optional
                             KmsKey = "kmsKey",
                             RoleArn = "roleArn"
                         }
                     } }
                 },
                 ServiceName = "serviceName",
                 ServiceRegistries = new [] { new ServiceRegistryProperty {
                     ContainerName = "containerName",
                     ContainerPort = 123,
                     Port = 123,
                     RegistryArn = "registryArn"
                 } },
                 Tags = new [] { new CfnTag {
                     Key = "key",
                     Value = "value"
                 } },
                 TaskDefinition = "taskDefinition",
                 VolumeConfigurations = new [] { new ServiceVolumeConfigurationProperty {
                     Name = "name",

                     // the properties below are optional
                     ManagedEbsVolume = new ServiceManagedEBSVolumeConfigurationProperty {
                         RoleArn = "roleArn",

                         // the properties below are optional
                         Encrypted = false,
                         FilesystemType = "filesystemType",
                         Iops = 123,
                         KmsKeyId = "kmsKeyId",
                         SizeInGiB = 123,
                         SnapshotId = "snapshotId",
                         TagSpecifications = new [] { new EBSTagSpecificationProperty {
                             ResourceType = "resourceType",

                             // the properties below are optional
                             PropagateTags = "propagateTags",
                             Tags = new [] { new CfnTag {
                                 Key = "key",
                                 Value = "value"
                             } }
                         } },
                         Throughput = 123,
                         VolumeInitializationRate = 123,
                         VolumeType = "volumeType"
                     }
                 } },
                 VpcLatticeConfigurations = new [] { new VpcLatticeConfigurationProperty {
                     PortName = "portName",
                     RoleArn = "roleArn",
                     TargetGroupArn = "targetGroupArn"
                 } }
             });

Synopsis

Constructors

CfnService(Construct, string, ICfnServiceProps?)

The AWS::ECS::Service resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

Properties

AttrName	The name of the Amazon ECS service, such as `sample-webapp` .
AttrServiceArn	The ARN that identifies the service.
AvailabilityZoneRebalancing	Indicates whether to use Availability Zone rebalancing for the service.
CFN_RESOURCE_TYPE_NAME	The CloudFormation resource type name for this resource class.
CapacityProviderStrategy	The capacity provider strategy to use for the service.
CfnProperties	The `AWS::ECS::Service` resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.
Cluster	The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on.
DeploymentConfiguration	Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
DeploymentController	The deployment controller to use for the service.
DesiredCount	The number of instantiations of the specified task definition to place and keep running in your service.
EnableEcsManagedTags	Specifies whether to turn on Amazon ECS managed tags for the tasks within the service.
EnableExecuteCommand	Determines whether the execute command functionality is turned on for the service.
ForceNewDeployment	Determines whether to force a new deployment of the service.
HealthCheckGracePeriodSeconds	The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.
LaunchType	The launch type on which to run your service.
LoadBalancers	A list of load balancer objects to associate with the service.
NetworkConfiguration	The network configuration for the service.
PlacementConstraints	An array of placement constraint objects to use for tasks in your service.
PlacementStrategies	The placement strategy objects to use for tasks in your service.
PlatformVersion	The platform version that your tasks in the service are running on.
PropagateTags	Specifies whether to propagate the tags from the task definition to the task.
Role	The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf.
SchedulingStrategy	The scheduling strategy to use for the service.
ServiceConnectConfiguration	The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.
ServiceName	The name of your service.
ServiceRegistries	The details of the service discovery registry to associate with this service.
Tags	Tag Manager which manages the tags for this resource.
TagsRaw	The metadata that you apply to the service to help you categorize and organize them.
TaskDefinition	The `family` and `revision` ( `family:revision` ) or full ARN of the task definition to run in your service.
VolumeConfigurations	The configuration for a volume specified in the task definition as a volume that is configured at launch time.
VpcLatticeConfigurations	The VPC Lattice configuration for the service being created.

Methods

Inspect(TreeInspector)	Examines the CloudFormation resource and discloses attributes.
RenderProperties(IDictionary<string, object>)	The `AWS::ECS::Service` resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

Constructors

CfnService(Construct, string, ICfnServiceProps?)

The AWS::ECS::Service resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

public CfnService(Construct scope, string id, ICfnServiceProps? props = null)

Parameters

scope Construct: Scope in which this resource is defined.
id string: Construct identifier for this resource (unique in its scope).
props ICfnServiceProps: Resource properties.

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Properties

AttrName

The name of the Amazon ECS service, such as sample-webapp .

public virtual string AttrName { get; }

Property Value

string

Remarks

CloudformationAttribute: Name

AttrServiceArn

The ARN that identifies the service.

public virtual string AttrServiceArn { get; }

Property Value

string

Remarks

For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide .

CloudformationAttribute: ServiceArn

AvailabilityZoneRebalancing

Indicates whether to use Availability Zone rebalancing for the service.

public virtual string? AvailabilityZoneRebalancing { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

CFN_RESOURCE_TYPE_NAME

The CloudFormation resource type name for this resource class.

public static string CFN_RESOURCE_TYPE_NAME { get; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

CapacityProviderStrategy

The capacity provider strategy to use for the service.

public virtual object? CapacityProviderStrategy { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

CfnProperties

The AWS::ECS::Service resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

protected override IDictionary<string, object> CfnProperties { get; }

Property Value

IDictionary<string, object>

Overrides

CfnResource.CfnProperties

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Cluster

The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on.

public virtual string? Cluster { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

DeploymentConfiguration

Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.

public virtual object? DeploymentConfiguration { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

DeploymentController

The deployment controller to use for the service.

public virtual object? DeploymentController { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

DesiredCount

The number of instantiations of the specified task definition to place and keep running in your service.

public virtual double? DesiredCount { get; set; }

Property Value

double?

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

EnableEcsManagedTags

Specifies whether to turn on Amazon ECS managed tags for the tasks within the service.

public virtual object? EnableEcsManagedTags { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

EnableExecuteCommand

Determines whether the execute command functionality is turned on for the service.

public virtual object? EnableExecuteCommand { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

ForceNewDeployment

Determines whether to force a new deployment of the service.

public virtual object? ForceNewDeployment { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

HealthCheckGracePeriodSeconds

The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started.

public virtual double? HealthCheckGracePeriodSeconds { get; set; }

Property Value

double?

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

LaunchType

The launch type on which to run your service.

public virtual string? LaunchType { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

LoadBalancers

A list of load balancer objects to associate with the service.

public virtual object? LoadBalancers { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

NetworkConfiguration

The network configuration for the service.

public virtual object? NetworkConfiguration { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

PlacementConstraints

An array of placement constraint objects to use for tasks in your service.

public virtual object? PlacementConstraints { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

PlacementStrategies

The placement strategy objects to use for tasks in your service.

public virtual object? PlacementStrategies { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

PlatformVersion

The platform version that your tasks in the service are running on.

public virtual string? PlatformVersion { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

PropagateTags

Specifies whether to propagate the tags from the task definition to the task.

public virtual string? PropagateTags { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Role

The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf.

public virtual string? Role { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

SchedulingStrategy

The scheduling strategy to use for the service.

public virtual string? SchedulingStrategy { get; set; }

Property Value

string

Remarks

For more information, see Services .

ServiceConnectConfiguration

The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

public virtual object? ServiceConnectConfiguration { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

ServiceName

The name of your service.

public virtual string? ServiceName { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

ServiceRegistries

The details of the service discovery registry to associate with this service.

public virtual object? ServiceRegistries { get; set; }

Property Value

object

Remarks

For more information, see Service discovery .

TagsRaw

The metadata that you apply to the service to help you categorize and organize them.

public virtual ICfnTag[]? TagsRaw { get; set; }

Property Value

ICfnTag[]

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

TaskDefinition

The family and revision ( family:revision ) or full ARN of the task definition to run in your service.

public virtual string? TaskDefinition { get; set; }

Property Value

string

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

VolumeConfigurations

The configuration for a volume specified in the task definition as a volume that is configured at launch time.

public virtual object? VolumeConfigurations { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

VpcLatticeConfigurations

The VPC Lattice configuration for the service being created.

public virtual object? VpcLatticeConfigurations { get; set; }

Property Value

object

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Methods

Inspect(TreeInspector)

Examines the CloudFormation resource and discloses attributes.

public virtual void Inspect(TreeInspector inspector)

Parameters

inspector TreeInspector: tree inspector to collect and process attributes.

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

RenderProperties(IDictionary<string, object>)

The AWS::ECS::Service resource creates an Amazon Elastic Container Service (Amazon ECS) service that runs and maintains the requested number of tasks and associated load balancers.

protected override IDictionary<string, object> RenderProperties(IDictionary<string, object> props)

Remarks

The stack update fails if you change any properties that require replacement and at least one Amazon ECS Service Connect <code>ServiceConnectConfiguration</code> property is configured. This is because AWS CloudFormation creates the replacement service first, but each <code>ServiceConnectService</code> must have a name that is unique in the namespace. > Starting April 15, 2023, AWS ; will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS , or Amazon EC2 . However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service. > 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 <code>CapacityProviderStrategy</code> parameter with the standard practice. For more information, see <a href="https://docs.aws.amazon.com/about-aws/whats-new/2025/05/amazon-ecs-capacity-provider-configuration-ecs/">Amazon ECS adds support for updating capacity provider configuration for ECS services</a> . Previously Amazon ECS ignored the <code>CapacityProviderStrategy</code> property if it was set to an empty list for example, <code>[]</code> 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 ( <code>[]</code> ) for the <code>CapacityProviderStrategy</code> property in your AWS CloudFormation template, Amazon ECS will remove any capacity providers associated with the service, as follows:

No launch type to fall back to for empty capacity provider strategy. Your service was not created with a launch type.

Recommended Actions

If you are currently using CapacityProviderStrategy: [] in your AWS CloudFormation templates, you should take one of the following actions:

If you are experiencing active production issues related to this change, contact AWS Support or your Technical Account Manager.

See: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html

CloudformationResource: AWS::ECS::Service

ExampleMetadata: fixture=_generated

Implements

IInspectable

ITaggable