I m testing out the ECS workpool worker and deployments I m

Question

I m testing out the ECS workpool worker and deployments I m curious is there a convenient way to inject secrets from either secrets manager or parameter store I m trying to not use blocks because I d rather not store my AWS credentials in prefect cloud Ideally there would be a job variables option that would allow me to set secrets in the container definition

Jake Kaplan · Answer

hey I believe you can do this from the advanced tab on the work pool

Jake Kaplan · Answer

you can add whatever parameters you d like to `containerDefinitions` and they ll get passed to `registerTaskDefinition`

Jake Kaplan · Answer

the ones shown are just the common ones we surface

Mark McDonald · Answer

ok let me play around with that Thanks Jake

Mark McDonald · Answer

< Jake Kaplan> following up on this I ve gotten it to work by manually editing the Advance tab using the UI However ideally this would be something that could be configured via deployments in prefect yaml Is that currently possible It doesn t seem like it is I tried adding the containerDefinitions to the `job variables` but it does not get added to the task definition The reason this is important for my use case is that I have different teams at my company using Prefect Each team has different needs for networking secrets volumes etc Ideally at a flow level I could be able to control these settings By hard coding it into the Advance tab the task definition becomes very static

Mark McDonald · Answer

Ideally we d like to be able to set the following items per flow deployment using job variables ephemeralStorage secrets in containerDefinitions subnets security groups awsvpcConfiguration I see that <https github com PrefectHQ prefect aws issues 298|this issue> covers my third point I could look at making a PR to add these things Is Prefect open to having these configurations added to the base template

Jake Kaplan · Answer

Hey All of that should be possible already <https docs prefect io 2 11 3 concepts work pools base job template> While you can hard code things into the work pool template like you ve done you re right that it will be the same for every deployment Under the advanced section you can add temptable job variables which are then able to be set on every deployment differently You ll also need to add the temptable value into the job configuration like ` my extra variable job variable ` You can also edit the base template to include values that the ECS API accepts even if they re not already in the base template

Mark McDonald · Answer

this worked it s amazing thank you