Difference between revisions of "Amazon ECS events"
Jump to navigation
Jump to search
(→Logs) |
|||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
* https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_cwe_events.html | * https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_cwe_events.html | ||
− | + | [[SERVICE_STEADY_STATE]] | |
− | |||
Line 14: | Line 13: | ||
== Logs == | == Logs == | ||
+ | * [[SERVICE_STEADY_STATE]] | ||
* <code>[[has reached a steady state]]</code> | * <code>[[has reached a steady state]]</code> | ||
− | * [[has begun draining connections on]] | + | * <code>[[has begun draining connections on]]</code> |
− | * [[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> | ||
Line 24: | Line 24: | ||
== Related == | == Related == | ||
* [[Amazon EventBridge]] | * [[Amazon EventBridge]] | ||
− | |||
* [[AWS ECS tasks errors]] | * [[AWS ECS tasks errors]] | ||
* [[Force new deployment]] | * [[Force new deployment]] | ||
+ | * [[K8s events]] | ||
== See also == | == See also == | ||
+ | * {{ECS events}} | ||
* {{ECS}} | * {{ECS}} | ||
[[Category:AWS]] | [[Category:AWS]] |
Latest revision as of 13:03, 15 August 2023
SERVICE_STEADY_STATE
{ "source": [ "aws.ecs" ], "detail-type": [ "ECS Task State Change" ] }
Contents
Logs[edit]
- SERVICE_STEADY_STATE
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[edit]
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[edit]
See also[edit]
- 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: