@Marvin How do I change the ephemeral storage on an ECS Task in a worker deployment?

To change the ephemeral storage on an ECS Task in a worker deployment, you need to modify the ECS task definition used by Prefect to set up the worker. Unfortunately, the direct documentation specific to modifying the ephemeral storage was not found, but you can follow the general steps to achieve this through customization of the ECS task. Here are the general steps: 1. Create/Update the ECS Task Definition: You need to specify the

ephemeralStorage

parameter in your ECS task definition. This would require editing the JSON configuration for the ECS task. An example ECS task definition snippet:

json
   {
     "family": "my-task-family",
     "cpu": "256",
     "memory": "512",
     "ephemeralStorage": {
       "sizeInGiB": 100
     },
     "containerDefinitions": [
       {
         "name": "my-container",
         "image": "my-image",
         ...
       }
     ],
     ...
   }

2. Deploy the Task Definition with Prefect: Using Prefect, ensure you load and apply the modified task definition. Example command in your deployment script:

python
   from prefect.deployments import Deployment
   from prefect.infrastructure.ecs import ECSTask

   ecs_task = ECSTask.load("ecs-task-block-name")  # Your defined ECS Task Block Name
   ecs_task.task_definition['ephemeralStorage'] = {"sizeInGiB": 100}

   deployment = Deployment.build_from_flow(
       flow=flow,
       name="my-flow",
       infrastructure=ecs_task,
       ...
   )
   deployment.apply()

Refer to the Prefect AWS ECS Guide for details on configuring ECS tasks and other ECS related configurations. For reference about others experiencing issues and solutions around Prefect and ECS, you might find this GitHub issue insightful: - Prefect stops downloading Flow code from GitHub in AWS ECS If you have further questions or run into issues, searching or posting on the Prefect GitHub repository might also provide additional help.