Amir Szekely

> It doesn`t happen all the time right. And for most of the users it`s quite ok how it works even with org runners. > But for some of them...

I do want something like this one day, but I don't think we have all the details figured out yet. For example, when using ECS with a limited ASG, a...

Please do share the code, if you can. I think I may have misunderstood the matching you were doing between jobs and the existing state machine. It might already cover...

> @kichik hope you have seen my invitation - created a private repo for this. I did. Thanks.

The name uses GitHub webhook delivery id to remain unique. https://github.com/CloudSnorkel/cdk-github-runners/blob/06ffc53c8067027748a4447d3f3b248fabb94131/src/webhook-handler.lambda.ts#L167 Do you maybe have the same webhook hooked up more than once somehow?

Can you tell what's the initial failure? It makes sense for the second webhook retry to fail with "the stepfunction alreadyexists message" and return 502. But why would the first...

Nice debugging!

> I use it for multiple orgs so I need the full name... Can you please clarify the need? Do you often have to jump in and debug these that...

This could theoretically work. You can test by overriding the task configuration with something like: ``` const provider = new EcsRunnerProvider(...); const taskDefinitionResource = provider.node.findChild('task').node.defaultChild as ecs.CfnTaskDefinition; taskDefinitionResource.addPropertyOverride('NetworkMode', 'awsvpc'); taskDefinitionResource.addPropertyOverride('ContainerDefinitions.0.Environment',...

The EC2 provider should work fine for your use case, yeah. As for ECS, let's see if it can work first. Would you be able to test with the overrides...