OSS deployed on ECS is creating spikes in AWS Config

[dagsir[bot]]

I have Dagster deployed on AWS ECS by following the <https://docs.dagster.io/deployment/guides/aws|Deploying Dagster to Amazon Web Services> guide, but I have a cost problem.
I am running schedules that trigger around 800 runs, where each creates a separate ECS task, which leads to a spike in the AWS Config.
Is there a resolution on how to bring the amount of created configurations down?

---

The question was originally asked in Dagster Slack.

[ammerzon]

Here is the corresponding screenshot from the AWS Cost Center