Difference between revisions of "Amazon ECS events"
Jump to navigation
Jump to search
(→Logs) |
|||
| Line 17: | Line 17: | ||
* [[has begun draining connections on]] | * [[has begun draining connections on]] | ||
* [[Deployment completed.]] | * [[Deployment completed.]] | ||
| + | * <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> | ||
== [[ECS task errors]] == | == [[ECS task errors]] == | ||
Revision as of 11:13, 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 serviceis unable to consistently start tasks successfullyEssential container in task exitedResourceinitializationerror: unable to pull secrets or registry authexec format errorIs already using a port required by your task.
Related
See also
- 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:
