3 ms·

Note also that the Docker integration into Fargate was released at the same time, see https://aws.amazon.com/blogs/containers/aws-docker-collaborate-simplify-de

Note also that the Docker integration into Fargate was released at the same time, see https://aws.amazon.com/blogs/containers/aws-docker-collaborate-simplify-developer-experience/ https://aws.amazon.com/blogs/containers/aws-docker-collabora... and https://www.docker.com/blog/from-docker-straight-to-aws/ https://www.docker.com/blog/from-docker-straight-to-aws/ - this provides a simpler way of using Fargate, especially if you are already using Docker Compose. You can output cloudformation from this as well, but you don't have to understand the internals of ECS to use it. This is in beta and would love more feedback (here https://github.com/docker/ecs-plugin); https://github.com/docker/ecs-plugin); I worked on this at Docker with Amazon.

gavinray 6y ago
My goodness, Docker Compose file to production stack?! My dreams have come true. The arguments for k8s I have is that the local and production setups are identical. It's a PITA to run k8s locally, but the alternative is that you use Docker Compose local, and then deploy to k8s, which means two sets of configs. And that's terrible. Or, you use Docker Compose locally, and fragment all of the containers into individual ECS/Fargate services which you write the deploy pipeline for individually. These were your best options, for one glaring reason: You can't use a docker-compose.yaml in production. (I know, I know, Kompose, but it doesn't always work quite right and you now have a k8s cluster). Really excited to try this out, thanks for the work on it!