Deploy an app having Frontend in Angular and Backend in Java on Fargate ECS.

Hello, To migrate from on-prem running containers, to go to Fargate, I'd humbly recommend to use ECS Compose-X which will deal with (almost ?) everything for you. If you haven't defined your services in docker-compose files yet, I'd highly recommend to do so, which will allow you to then run ecs-compose-x up [...]. This will generate all the CFN templates that you need to deploy to AWS to run on ECS, defaulting with using Fargate instead of EC2.

If you already have a VPC or an ECS cluster, that's fine too, it can discover such resources and just use them to deploy the services onto.

I would imagine you already have created IAM policies for your services locally to work if you needed these, so just make sure to set these policies in x-iam.Policies and they will be applied to your service task role.

Now networking wise, to allow your frontend to find your backend, you can define x-route53 and/or (not mutually exclusive) to create DNS records pointing at your services. For ingress, I would imagine you need a load-balancer, which is what x-elbv2 will do for you: it will create the load-balancer, the listeners, the routing rules and link everything to your services. It will also respect the least privileges access and open security groups between the load-balancer and your services accordingly.

There are examples in the labs which I hope would be useful or in the main docs Examples or How do I ?

Hope this helps your transition to running on ECS!

Hi AWS, this is the current architecture diagram

Ques: If an external system(kind of contact us form hosted somewhere outside not on-premise) is needed to connect to the ALB in Aws to reach the Java fargate ecs —-what are the things to consider and open and consider also the vpc endpoint?

Also I need expertise in order to optimize this workflow diagram following the concept of Well Architected Framework (WAF).

Thanks