Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

For fargate: It seems like there is a <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_timeout|2 minute stop timeout>, is this accurate? So if you have a task that runs for longer than 2 minutes it is killed? How does that work?

That has AFAIK nothing to do with task runs but just for task definitions with multiple containers and how long they wait for the startup. I am not familiar with that option but there is nothing killed automatically by Fargate. Using it too here

Hi <@UTMGMTB28>, I'm not super familiar with Fargate, but I think <@U016C6EMJ6P>'s correct. It looks like `stopTimeout` is used as a backup in the event the container doesn't exit as expected. If you do see issues with this, absolutely let us know and we can take a look.

I am considering implementing a cloud run version because that's the GCP analog, but it is limited to 15 minute runtimes. I saw the thing about fargate and was having a hard time believing that was reality

Yeah, I was a bit surprised when I read that as well! The docs are a bit confusing, but I think it's sort of an "in case of emergency, break glass" configuration.