Difference between revisions of "Amazon ECS events"
Jump to navigation
Jump to search
(→Logs) |
|||
Line 16: | Line 16: | ||
* <code>[[has reached a steady state]]</code> | * <code>[[has reached a steady state]]</code> | ||
* [[has begun draining connections on]] | * [[has begun draining connections on]] | ||
− | * [[Deployment completed.]] | + | * <code>[[Deployment completed.]]</code> |
* <code>Message: Successfully set desired count to 1. Change successfully [[fulfilled]] by ecs. Cause: monitor alarm your-service in state ALARM triggered policy your-service</code> | * <code>Message: Successfully set desired count to 1. Change successfully [[fulfilled]] by ecs. Cause: monitor alarm your-service in state ALARM triggered policy your-service</code> | ||
Revision as of 11:15, 20 July 2023
{ "source": [ "aws.ecs" ], "detail-type": [ "ECS Task State Change" ] }
Contents
Logs
has reached a steady state
- has begun draining connections on
Deployment completed.
Message: Successfully set desired count to 1. Change successfully fulfilled by ecs. Cause: monitor alarm your-service in state ALARM triggered policy your-service
ECS task errors
Error: error creating MyECSServiceName service
is unable to consistently start tasks successfully
Essential container in task exited
Resourceinitializationerror: unable to pull secrets or registry auth
exec format error
Is already using a port required by your task.
Related
See also
- Amazon ECS events:
SERVICE_STEADY_STATE
- 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, AWS ECS Rolling deployments
Advertising: