- Newest
- Most votes
- Most comments
Hi @FinneyCanHelp, You can very well use App Runner for this usecase, there is no direct way of defining dependencies between services both in ECS or App Runner. But you can use environment variables to specify the downstream/dependent URL's which can get used by the source service to invoke these services.
The team has recently introduced support for private services that allows you to keep the service private and route the traffic within VPC, please refer to these blogs for more details:
Let us know if you have any further questions regarding this. Thanks
Hi, @FinneyCanHelp.
I think you can use App Runner.
First, Elastic Beanstalk is not an option if you want to go serverless.
You can also adopt App Runner with ECS on Fargate.
App Runner is more AWS managed than ECS on Fargate. And it's easy to get started.
This is also mentioned in session CON406.
However, you may face limitations if you want to achieve complex requirements.
App Runner is essentially a public service that runs outside of your VPC.
Therefore, I think that I will make full use of VPC Connector and VPC Endpoint to access private APIs.
I think ECS on Fargate is a good choice if you want to manage flexible orchestrations and microservices, or if you have a lot of traffic and want control over autoscaling and his WAF.
Relevant content
- Accepted Answerasked 2 years ago
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 4 months ago
Thank you for your thorough and thoughtful response. If I have further questions, I will do as you suggest. Thanks so much!