The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

<https://docs.dagster.io/_apidocs/libraries/dagster-aws#ecs>
In the documentation for the dagster_aws.ecs.EcsRunLauncher, I expected a ECS pool id, and saw "container name".
Is this the container pool ID?

But in the deployment config I see cluster name
<https://docs.dagster.io/dagster-cloud/deployment/agents/amazon-ecs/configuration-reference#per-deployment-configuration>

So I assume that the earlier config is not for the elastic load? (Perhaps for the orchestrator itself?)

You might find this overview of the ECS integration helpful: <https://docs.dagster.io/deployment/guides/aws#deploying-in-ecs> - the EcsRunLauncher launches an ECS task for each run. The majority of our ECS users use fargate which handles the autoscaling for you, but we do have support for running in ECS on EC2 as well. I don't think we have a specific field for the ECS pool ID currently, but it may be possible to configure it using some of the options on that page