aws / aws/containers-roadmap

[ECS] Notification or Event When Container Actually Killed Or Ends

Open
#324 2 comments 5 reactions 0 assignees View on GitHub
ECS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

Today, our containers have some grace period until our current process in the docker will be done its businesses and then the process is gonna exit.

However, we want to track the time between the ECS task had stopped in the ECS (that means it sent SIGTERM or SIGINT to the docker container) until it actually terminated or killed.

We would very happy if a notification/event can be sent when the docker container is actually killed in the instance. ECS Stop Task action doesn't fit our goals because the ECS says it stopped before it actually is.

Thanks

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or entry points are identified. Start by clarifying the ECS task and Docker container lifecycle around SIGTERM/SIGINT, and compare the requested signal with the existing ECS Stop Task action. Done would mean defining a notification or event that occurs when the container actually terminates or is killed, rather than when ECS marks the task stopped.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.