[docs] document valid config options for ECS / Fargate #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been using
dask-cloudprovider
a lot recently to test things and come up with reproducible examples.Through this experience, I learned that ECS / Fargate only allow task definitions to choose from a finite list of CPU and memory settings. This is an AWS limitation and not a
dask-cloudprovider
one, but it took me a bit of investigation to figure that out.This PR proposes adding a link to the valid config values for ECS in the docs, so that when people search the
dask-cloudprovider
docs or Google for this error, they quickly find the answer and the set of valid values.Thanks for your time and consideration.