Did you know that you can navigate the posts by swiping left and right?
I’ve recently came across an architecture which contained several microservices being contacted by AWS API Gateway. All of them were served behind an external alb on Amazon AWS. The problem here was that a lot of these microservices were mainly used for backed calls, there was no need for them to be exposed to the world.
The backend microservices were moved behind an internal ALB. This made sure that they could not be accessed from the world. The only way to access them is if you are in the VPC which they are deployed in.
Amazon API Gateway is deployed outside the VPC.
frontend http-in bind :80 acl user_agent hdr_sub(User-Agent) -i AmazonAPIGateway_[APIID] block if !user_agent default_backend web-app-cluster backend web-app-cluster balance leastconn option httpclose cookie JSESSIONID prefix server node1 [ALB_IP_1]:80 check server node2 [ALB_IP_2]:80 check server node3 [ALB_IP_3]:80 check
In the end, the architecture looks like this:
An API request will roughly look like this: