1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hello,
By API Gateway I guess you mean within your application, not using AWS API Gateway, right?
If you can put your services into a docker-compose file, which helps with local testing and configuration, ECS Compose-X will deal with setting everything up for you: it will create IaC templates (CloudFormation) to deploy everything to AWS (with something as simple as ecs-compose-x up
. It will create your ECS Cluster, VPC, the ECS resources, IAM roles, etc. for you. You can also have it deal with other things such as DNS, ELB etc.
Alternatively, you can try Copilot too, but that does not use the docker-compose syntax.
Hope this helps,
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
Yea correct. In Nestjs i have 2 "apps" in my monorepo. One api-gateway & products. All my calls go through my api-gateway and using rabbitMq messages it calls the proper microservice (in this case only products). I have a docker-compose file in my project and then Dockerfile in each app. When i do docker-compose up its runs perfectly no issues.
If this ecs-compose-x up deploys this then perfect ill take a look!