Hello! Is there a way to run ECSTask on a SPOT instance? thank you

You can use

launch_type

in ECSTask to specify

FARGATE_SPOT

(see docs here)

While this is certainly doable, there are some open issues regarding scheduling of work if the spot instances are reclaimed while your work is still processing

thank you It doesn’t work, do you know why?

https://prefecthq.github.io/prefect-aws/ecs/#prefect_aws.ecs.ECSTask.launch_type - it should be

launch_type

instead of

lunch_type

ohhh

all good, if that’s all that’s needed, that’s the easiest answer I can give all day 🙂

it’s work! thank you!

I’ll have to think and get back to you on this one in the morning. Generally RBAC and roles are the way to limit who can see what - if a user has access to the flow and history, they can see what goes in. You can use Prefect secrets which are obscured, but that won’t obscure what ECS reports back

thank you. looking forward to it.

The safest route is to pass secrets from AWS secrets manager into the task definition as env vars. This is what we do with the prefect API key in our recipe: https://github.com/PrefectHQ/prefect-recipes/blob/main/devops/infrastructure-as-code/aws/tf-prefect2-ecs-agent/ecs.tf#L36-L41 (credit to @Emil Christensen)

Hi, I just introduced myself to this community and came across this thread re: ECS and using spot instances with Prefect. Memory Machine automatically manages spot instance reclaims and also has an user defined interval based checkpoint and recovery service that works with any OCI compliant container. This enables any job running on spot to be resumed on a new compute instance vs starting over, and it is fully automated from job submit to job complete. If this sounds like a useful approach I’d love to learn more @Rikimaru Yamaguchi .