#Kill syncmate service update

The service scheduler uses the minimum healthy percent and maximum percent parameters (in the service's deployment configuration) to determine the deployment strategy.

If you have updated the Docker image of your application, you can create a new task definition with that image and deploy it to your service. You can add to or subtract from the number of instantiations of a task definition in a service by specifying the cluster that the service is running in and a new desiredCount parameter.

If the launch type, load balancer, network configuration, platform version, or task definition need to be updated, create a new task set For more information, see CreateTaskSet.

#Kill syncmate service update

įor services using an external deployment controller, you can update only the desired count, task placement constraints and strategies, health check grace period, enable ECS managed tags option, and propagate tags option, using this API. For more information, see CreateDeployment in the CodeDeploy API Reference. If the network configuration, platform version, task definition, or load balancer need to be updated, create a new CodeDeploy deployment. When you update any of these parameters, Amazon ECS starts new tasks with the new configuration.įor services using the blue/green ( CODE_DEPLOY ) deployment controller, only the desired count, deployment configuration, health check grace period, task placement constraints and strategies, enable ECS managed tags option, and propagate tags can be updated using this API.

These Beta Terms apply to your participation in this preview.įor services using the rolling update ( ECS ) you can update the desired count, deployment configuration, network configuration, load balancers, service registries, enable ECS managed tags option, propagate tags option, task placement constraints and strategies, and task definition. Updating the task placement strategies and constraints on an Amazon ECS service remains in preview and is a Beta Service as defined by and subject to the Beta Service Participation Service Terms located at ('Beta Terms').