desiredCount, Amazon ECS spawns another instantiation of the task in the specified cluster. To update an existing service, see UpdateService.
You can optionally specify a deployment configuration for your service. During a deployment
(which is triggered by changing the task definition of a service with an UpdateService
operation), the service scheduler uses the
maximumPercent parameters to determine the deployment strategy.
minimumHealthyPercent is below 100%, the scheduler can ignore
desiredCount temporarily during a deployment. For example, if your
service has a
desiredCount of four tasks, a
of 50% allows the scheduler to stop two existing tasks before starting two new tasks.
Tasks for services that do not use a load balancer are considered healthy if
they are in the
RUNNING state; tasks for services that do use
a load balancer are considered healthy if they are in the
and the container instance it is hosted on is reported as healthy by the load balancer.
The default value for
minimumHealthyPercent is 50% in the console and
100% for the AWS CLI, the AWS SDKs, and the APIs.
maximumPercent parameter represents an upper limit on the number
of running tasks during a deployment, which enables you to define the deployment batch
size. For example, if your service has a
desiredCount of four tasks,
maximumPercent value of 200% starts four new tasks before stopping
the four older tasks (provided that the cluster resources required to do this are
available). The default value for
maximumPercent is 200%.
When the service scheduler launches new tasks, it attempts to balance them across the Availability Zones in your cluster with the following logic:
Determine which of the container instances in your cluster can support your service's task definition (for example, they have the required CPU, memory, ports, and container instance attributes).
Sort the valid container instances by the fewest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.
Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.
Version: (assembly version)
public class CreateServiceRequest : AmazonECSRequest IRequestEvents
The CreateServiceRequest type exposes the following members
Gets and sets the property ClientToken.
Unique, case-sensitive identifier you provide to ensure the idempotency of the request. Up to 32 ASCII characters are allowed.
Gets and sets the property Cluster.
The short name or full Amazon Resource Name (ARN) of the cluster on which to run your service. If you do not specify a cluster, the default cluster is assumed.
Gets and sets the property DeploymentConfiguration.
Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
Gets and sets the property DesiredCount.
The number of instantiations of the specified task definition to place and keep running on your cluster.
Gets and sets the property LoadBalancers.
A list of load balancer objects, containing the load balancer name, the container name (as it appears in a container definition), and the container port to access from the load balancer.
Gets and sets the property Role.
The name or full Amazon Resource Name (ARN) of the IAM role that allows your Amazon ECS container agent to make calls to your load balancer on your behalf. This parameter is only required if you are using a load balancer with your service.
Gets and sets the property ServiceName.
The name of your service. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a region or across multiple regions.
Gets and sets the property TaskDefinition.
Supported in: 4.5, 4.0, 3.5
.NET for Windows Store apps:
Supported in: Windows 8