Difference between revisions of "Amazon ECS events"
Jump to navigation
Jump to search
(→Logs) |
|||
| Line 14: | Line 14: | ||
== Logs == | == Logs == | ||
| + | * [[SERVICE_STEADY_STATE]] | ||
* <code>[[has reached a steady state]]</code> | * <code>[[has reached a steady state]]</code> | ||
* <code>[[has begun draining connections on]]</code> | * <code>[[has begun draining connections on]]</code> | ||
Revision as of 13:00, 15 August 2023
{
"source": [
"aws.ecs"
],
"detail-type": [
"ECS Task State Change"
]
}
Contents
Logs
- SERVICE_STEADY_STATE
has reached a steady statehas begun draining connections onDeployment 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 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:
