Flexible load balancing both internally and over the Internet

We are trying to use elastic load balancing in AWS with auto-scaling so that we can scale and exit as needed.

Our application consists of several small applications, all of them are in the same subnet of the same VPC.

We want to put our ELB between one of our applications and the rest.

The problem is that we want the load balancer to work both internally between different applications using the API, and using the Internet, because our application still has some use that needs to be executed from the outside, and not through the API.

I read this question , but I could not understand exactly how to do this, there are no steps indicated or maybe I did understand it well.

Do we have an ELB that is internal and external?

For recording, I can access this network only through a VPN.

+11
source share
5 answers

It is not possible for an elastic load balancer to have both a public IP address and a private IP address. This one or the other, but not both.

If you want your ELB to have a private IP address, it cannot listen to requests from the Internet.

ELB , EC2 . , :

  • VPC . ELB, IP-.
  • .

3 :

  • ELB EC2, , .
  • 2 ELB ( , ), EC2.
  • ELB EC2 Elastic IP- ( ) IP- ( ).
+22

@MattHouser. , VPC ELB , Public IP Primary private IP. IP- ELB, , .

: IP- , , DNS- ELB. .

POC script , , Route53: https://gist.github.com/darylounet/3c6253c60b7dc52da927b80a0ae8d428

+9

AWS ELB. , @DaryL , 5 , DNS . IP-, ENI IP- ELB.

+1

-, , IP- loadbalancer, Route53 : https://github.com/Bramzor/lambda-sync-private-elb-ips

, ELB . VPC ELB.

+1

, , - ALB, , . ALB , .

Make sure that the network settings (subnets, security groups) of both ALBs are the same, so that both get access to the same cluster instances. Auto-scaling and startup tuning work seamlessly when both ALBs are connected to the same AutoSacling group. This also works with ALBs created from ElasticBeanstalk environments.

0
source

All Articles