tomcart90

This is causing major problems for us at the moment. It feels like this behaviour regressed at some point.

I've had a bit of a look at this today and wonder if the cause here is that the provisioning call [here](https://github.com/jenkinsci/amazon-ecs-plugin/blob/90793694c31e698156993e0bca730444448afe4c/src/main/java/com/cloudbees/jenkins/plugins/amazonecs/ECSProvisioningStrategy.java#L65) doesn't take into account the `maxAgents` value, it...

I've raised https://github.com/jenkinsci/amazon-ecs-plugin/pull/284 to address this.

I'm experiencing the same problem trying to use AWS's CodeArtifact which only supports v3.

@trispad, we could really do with making us of those one, let me know if there's anything I can do to help get this over the line, it looks like...

I also hit this issue today on Windows. An initial `plan-all` worked, but then once the terragrunt cache had been populated further `plan-all` actions failed with the same error that...

@mikeboers, I had the same issue yesterday. The following changes were needed to get Flask-Images working for me on Windows: https://github.com/tomcart90/Flask-Images/commit/50863882431ab55439bdd2f410f2f99343b22da3

In light of the [AppMesh discontinuation](https://aws.amazon.com/blogs/containers/migrating-from-aws-app-mesh-to-amazon-ecs-service-connect/) we're looking at Service Connect as a replacement, the lack of mTLS support is currently our only blocker. Looking forward to this one being...

Having done a bunch more testing I'm seeing this error under other circumstances, I'll continue testing and will hopefully report back some more concrete repro steps. Edit: ok - I've...

@yhakbar, any `--all` plan involving both `--source-update` and a `--json-out-dir` seems to hit the issue on my end.