Menu
I'm working on a project where one of the tasks is to provide AWS ELB services for instances in a remote VPC. The AWS ELB is located in VPC A and the instances are located in VPC B. My initial response- No, because the ELB is a load balancer, not a router. Documentation and working with the AWS ELB indicate that load balancing to subnets/instances in a remote VPC is not supported or can be configured.
I'm checking to see if anyone tried this scenario to any form of success.
Many thanks for any response or feedback.
834
An ELB can only attach instances that are reachable by it. When you place an ELB in a VPC it's constrained there. VPC's are independent and can have overlapping subnet ranges.
A: No. For each associated subnet a Network Load Balancer is in, the Network Load Balancer can only support a single public/internet facing IP address.
With the API or CLI, cross-zone load balancing is disabled by default. With the AWS Management Console, the option to enable cross-zone load balancing is selected by default. After you create a Classic Load Balancer, you can enable or disable cross-zone load balancing at any time.
An ELB can only attach instances that are reachable by it.
When you place an ELB in a VPC it's constrained there. VPC's are independent and can have overlapping subnet ranges.
Ie if your ELB is in VPC A with 10.0.0.0/8 and you had another VPC B with 10.0.0.0/8 there's no way it could differentiate that route. It would be dangerous to cross that boundary and send data say to 10.0.0.8 if there was an instance in both VPC's with that IP. It has no route that can figure that out. If you want to send data from VPC to VPC you'd need a VPC peering connection and routes that handle that. Then you'd send to a proxy in VPC A that sends it to either an ELB or the instance in VPC B
96
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
