Skip to content
Discussion options

You must be logged in to vote

We've determined that AWS is applying an artificial ECS resource limit to newer accounts - and it appears to be set to 2 vCPU and 4GB of RAM. There are further clues pointing to this limit in this thread.

This is lower than what we tend to specify for the Elastic Deploy Runner - especially so that it can handle larger module deployments and the more resource intensive run-all command, which explains the error message.

This means that if you recently had a ref arch deployed that uses Fargate for the ECS Deploy Runner and are encountering this error, you have two main workarounds available right now:

  • Change your memory requests in your ECS Deploy Runner terragrunt.hcl configs to 4096 down …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zackproser
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
1 participant