@Marvin - this may be a naive question, but in the ecs work pool configuration, what's the difference between a

task_run_request

and

task_run_definition

In the context of ECS work pool configuration in Prefect, a

task_run_request

and a

task_run_definition

serve different purposes: 1. Task Run Request: This typically involves the parameters or specifications needed to initiate a task run. It is like a command or a request sent to the ECS to start a task based on predefined settings. 2. Task Run Definition: This is more comprehensive and includes the detailed configuration of what the task should execute. It describes the Docker containers to run and the actions to take within these containers. The task definition is a blueprint for the task run, specifying the resources, environment variables, and other configurations necessary for execution. In summary, the

task_run_request

is about initiating a task, while the

task_run_definition

is about defining the task's execution environment and parameters. For more details, you can refer to the Prefect ECS Guide.

@Marvin I am using a custom task definition generated in terraform prior to deployment so I can set custom values such as ephemeral storage. Is it best practice to populate the backend template with the task definition arm and leave the other values as the defaults?