AWS Frontend Service Design – How to Guide

amazon-albamazon-web-services

In AWS, we deployed a backend service – API in the internal ALB. For frontend(Web UI), it call the API and also needs to be accessed from internal enterprise network. It should be bind to Route53.

We are using VPN in our enterprise. We use DirectConnect to connect AWS VPC. So we can use private IP to access internal ALB resource in AWS.

Now we want to bind the original internal ALB's DNS name to Route 53 with a domain. Is it possible to do if use the use the internal ALB only?

Maybe the current internal ALB can't realize the purpose. So we will add a second ALB – internet facing. Use it to bind the Route53.

If set both 2 kinds of ALB for it, deploy with ECS, how to do the blue/green deployment for 2 kinds of different target security groups?

Best Answer

My initial suggestion is to:

  • Create a new public facing ALB
  • Route enterprise traffic over DirectConnect using a public VIF to the ALB
  • Use the existing target group
  • Use standard green / blue techniques

There may be better ways to do this, I'd have to give it a bit of thought. Others might have better ideas.

Related Topic