Running your Compose application to an existing cluster
Previously, we managed to run a Compose application on ECS by using an ECS Docker context. By deploying the application, a new infrastructure was provisioned through CloudFormation and an entire new ECS cluster was created for the application.
If we take our time and check the CloudFormation file, we can see that various AWS components have been created:
- A VPC and its subnets
- A CloudWatch log group
- Security groups
- A load balancer
- CloudMap for service discovery
- An ECS cluster
- ECS tasks
By default, CloudFormation will use the default VPC and subnets that already exist in our AWS account. The load balancer, security groups, and CloudMap, which assist with service discovery, will have to be created, as well as the ECS cluster and the ECS tasks. Those applications will be deployed to AWS Fargate.
It is obvious that these resources are provisioned and we have no control over their settings...
