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

Hi :wave:
A quick one.
When using the new ECS push work pool, how would define custom CPU and memory size for a task?

```- name: migrate_users_to_no_steps_buckets
  entrypoint: jobs/migrate_users_to_no_steps_buckets/migrate_users_to_no_steps_buckets.py:migrate_users_to_no_steps_buckets
  work_pool:
    name: main
  job_variables:
    cpu: 4096
    memory: 8192```

CleanShot 2023-10-13 at 11.48.42@2x.jpg

```  - name: default
    version: '{{ commit-hash.stdout }}'
    tags:
      - my-tag
    schedule:
      cron: 0 3 * * *
      timezone: UTC
    entrypoint: dir/to_flow.py:myflow
    work_pool:
      &lt;&lt;: *es_ecs_work_pool
      job_variables:
        &lt;&lt;: *ecs_work_pool_overrides
        family: this__default
        cpu: 2048
        memory: 16384```

<@U024LD633LK> Is the “&lt;&lt;: *ecs_work_pool_overrides” mandatory?

in the sample you posted, is the indentation there exactly how it looks in your `prefect.yaml`? `job_variables` should be part of the `work_pool` like so:
```  work_pool:
    name: main
    job_variables:
      cpu: 4096
      memory: 8192```

<@U03U4BQ9G6A> no, that's just a variable override I'm yaml if you want to type stuff less

<@U024LD633LK> <@U05TQMN8RUP> Thanks! works now.