Seq running in AWS ECS - "Termination signal received"

[richard-stafflink]

The Seq container (AWS ECS) reported receiving a "Termination signal".
We received 503/504 errors from Seq running in AWS ECS around that time.
Is there anything we can do to reduce the likelihood of this happening again?
And what would be the cause(s)?

These are the logs:

CPU/Memory (4 weeks):

1. Same thing happened on the 6th March
2. Terminated today (3rd April)

CPU/Memory (12 hours):

System settings:

Retention rules:

[nblumhardt]

Hi @richard-stafflink,

We don't have any specifics on how to configure ECS for this, but a custom AWS maintenance window should help narrow down the time of day that container recycling is performed. It'd be great to hear whether you're able to use this.

Hope this helps,
Nick

[richard-stafflink]

Hi @nblumhardt,

We haven't configured any container restarts or maintenance windows, so I'm not sure how the termination signal came about.

[nblumhardt]

Hi @richard-stafflink; AWS itself performs restarts when rebalancing load across hosts, or when the host the container is on requires maintenance.

[richard-stafflink]

That makes sense, thank you.
https://repost.aws/knowledge-center/ecs-task-stopped

[richard-stafflink]

Restart occurred due to ECS event: https://repost.aws/knowledge-center/ecs-task-stopped