Suggesting ECS Compose-X for AWS ECS#14
Merged
dannysteenman merged 1 commit intotowardsthecloud:mainfrom Dec 9, 2021
Merged
Conversation
dannysteenman
approved these changes
Dec 9, 2021
dannysteenman
added a commit
that referenced
this pull request
Mar 19, 2026
* feat(sdk): generalize aws terraform resource parsing * fix(sdk): address pr review follow-ups
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Suggesting ECS Compose-X in the AWS ECS toolbox.
Aimed for all levels of engineers (from new users to AWS advanced users), this allows to create CFN templates from docker-compose files, with extension fields that expand way beyond the docker+aws plugin, deals with enforcing least privileges access (although custom IAM is possible), security groups ingress, auto-tuning, side-cars, volumes, logging, advanced features, AWS AppMesh integration, etc.
We (work) use it everyday for production and dev environment workloads, which are identical thanks to the consistent definitions of the services via a well-known (compose) definitions format and AWS CFN definitions support for resources.
Thank you for your consideration.