Difference between revisions of "Aws ecs update-service"
Jump to navigation
Jump to search
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{lowercase}} | {{lowercase}} | ||
| − | |||
| − | + | <code>[[aws ecs]] update-service</code> [https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-service.html ref] | |
| + | ::<code>[[--foce-new-deployment]]</code> can be used to trigger a new [[deployment]] with no [[service definition]] changes | ||
| + | ::<code>[[--desired-count]]</code> | ||
| − | [[Restart]] ECS service: | + | == Examples == |
| − | + | * [[Restart]] ECS service: | |
| − | ::<code>[[-- | + | <code>[[aws ecs]] update-service --cluster your_cluster_name --service [[your_service-name]] [[--force-new-deployment]]</code> |
| + | |||
| + | * Stop service: | ||
| + | ::<code>[[aws ecs]] update-service --cluster your_cluster_name --service [[your_service-name]] [[--desired-count]] 0</code> | ||
| + | * Stop all services: | ||
| + | {{stop all services from a cluster}} | ||
* <code>[[--task-definition]]</code> | * <code>[[--task-definition]]</code> | ||
Latest revision as of 09:46, 27 April 2023
--foce-new-deploymentcan be used to trigger a new deployment with no service definition changes--desired-count
Contents
Examples[edit]
- Restart ECS service:
aws ecs update-service --cluster your_cluster_name --service your_service-name --force-new-deployment
- Stop service:
aws ecs update-service --cluster your_cluster_name --service your_service-name --desired-count 0
- Stop all services:
for SERVICES in $(aws ecs list-services --cluster your-cluster | grep YOUR-TEXT | grep . | cut -d":" -f6- | cut -d'"' -f1 | cut -d"/" -f3); do aws ecs update-service --cluster your-cluster --service $SERVICES --desired-count 0; done
Synopsis[edit]
update-service [--cluster <value>] --service <value> [--desired-count <value>] [--task-definition <value>] [--capacity-provider-strategy <value>] [--deployment-configuration <value>] [--network-configuration <value>] [--placement-constraints <value>] [--placement-strategy <value>] [--platform-version <value>] [--force-new-deployment | --no-force-new-deployment] [--health-check-grace-period-seconds <value>] [--enable-execute-command | --disable-execute-command] [--enable-ecs-managed-tags | --no-enable-ecs-managed-tags] [--load-balancers <value>] [--propagate-tags <value>] [--service-registries <value>] [--cli-input-json <value>] [--generate-cli-skeleton <value>]
Errors[edit]
An error occurred (InvalidParameterException) when calling the UpdateService operation: Identifier is for 0123456789. Your accountId is ***
Related[edit]
kubectl applyhelm upgradeaws ecs update-cluster-settings- AWS update
aws ecs list-servicesaws ecs create-service
See also[edit]
- AWS ECS:
aws ecs [ create-cluster | create-service | update-service | list-clusters | list-services | describe-cluster | describe-services | describe-tasks | put-account-setting | execute-command | run-task ] - Amazon ECS, Service, Tasks (Task overview), capacity providers, Cluster Auto Scaling (CAS),
aws ecs, ecs-cli, ~/.ecs/config, AWS Copilot, AWS Fargate, AWS CloudWatch Container Insights,/etc/ecs/ecs.config, Security group (SG), container agent, task definition, Amazon ECS events, best practices, Amazon ECS Exec Checker, Amazon ECS Agent, Service Connect,AWSServiceRoleForECS, Terraform ECS
Advertising:
