community-registry-extensions
ecs_composex
community-registry-extensions | ecs_composex | |
---|---|---|
2 | 12 | |
85 | 155 | |
- | 4.5% | |
7.7 | 8.7 | |
4 months ago | 6 days ago | |
Python | Python | |
MIT No Attribution | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
community-registry-extensions
-
Journey of creating a new AWS CloudFormation resource
I created a few myself before, and published these out of my own AWS Accounts. But this time instead of doing this all on my own, I had the opportunity to contribute to the Open Source community driven repository on GitHub. Great place to see what already existed, and have other people actually help and review my code.
-
Managing low-code environments with AWS CloudFormation and Azure Resource Manager
AWS Cloudformation Registry: This community is focused on AWS CloudFormation. The community provides resources and support for users of CloudFormation, including best practices, tutorials, and troubleshooting tips.
ecs_composex
-
Journey of creating a new AWS CloudFormation resource
If you have read my earlier posts or heard me talk with Corey on Screaming in the Cloud, I am the author of a tool called ECS Compose-X. It's designed to support all the docker compose features, and allow for extensions that make it easier to deploy to AWS.
- ecs_composex
-
How to take docker-compose to production?
Now, given you already have a docker-compose file, you could deploy to AWS in just a few minutes (assuming you have an account, and can pull the docker image from somewhere, like AWS ECR) with ECS Compose-X (GH|Docs). You can have a look at the wordpress demo on how to take your docker compose file as an input and let compose-x deal with everything (security, networking etc.) for you.
-
Running parallel builds in codebuild
Hope this might help https://github.com/compose-x/ecs_composex/blob/main/.cicd/buildspec_manifest.yml It does not use build-list but I got everything working in that way.
-
Creating Infrastructure at run time. Any advice?
In case you want to deploy infrastructure with some services running on ECS (planning on adding lambda to that mix though) and other AWS resources, i.e. Dyn tables, RDS etc., you could do something very nice using ECS Compose-X (GH) CFN Macro
-
Problems Communicating Between ECS Tasks
If you happen to have a docker-compose file locally that you used for dev testing, try ECS Compose-X (GH) which will parse that, render CFN templates and allow you to deploy the services in AWS ECS. If you have existing VPC and ECS Cluster, it can do discovery based on tags or just give it the subnets or cluster to use, as-is, it will take care of the rest (networking. IAM etc).
-
AWS Copilot and another 6 ways to easily deploy containers to AWS
docs and source code
-
How to use docker compose for dev "feature branch" environments
So, I created ECS Compose-X (docs) which covers 99% of our use-cases to date. The idea behind it was to allow developers to do exactly what you described: have one docker-compose.yaml file which describes the services, and use override files for each environments.
-
Four ways of writing infrastructure-as-code on AWS
I started using Troposphere when writing Compose-X because at the time CDK did not have Python support and once CDK had python support, the variable names for the resources properties were all changed from the original CFN definition.
-
How do you feel about AWS App Mesh and do you prefer EKS or just ECS with it?
ECS with AppMesh works like a charm. I will find you back my example app to show you, but I have created a project commonly called compose-x which would allow you to declare your services in docker compose format and declare your mesh nodes/routers/services as well and it will automatically create everything necessary for your services and the mesh
What are some alternatives?
spring-petclinic-microservices - Distributed version of Spring Petclinic built with Spring Cloud
cloudformation-resource-providers - automated monorepo of public CloudFormation AWS resource providers
flask-react-aws
aws-iam-generator - Generate Multi-Account IAM users/groups/roles/policies from a simple YAML configuration file and Jinja2 templates.
sst - Build modern full-stack applications on AWS
wordpress-demo - Deploy Wordpress with ECS ComposeX from original docker-compose by Bitnami
troposphere - troposphere - Python library to create AWS CloudFormation descriptions
cfn-secret-provider - A CloudFormation custom resource provider for deploying secrets and keys
troposphere-awscommunity-applicationautoscaling-scheduledaction - Troposphere resource to manage AwsCommunity::ApplicationAutoscaling::ScheduledAction