1

I have two AWS VPCs in the same region. VPC A has an internal ELB that routes to my application. VPC B has resources that need access to this application. The VPCs are peered, with routing tables having routes that point to each others' main CIDR block.

Currently, I can access the ELB from instances in the same VPC A, but not yet from those in VPC B.

How do I set up DNS and routing so that the resources in VPC B can resolve and access this ELB?

Improve this question
1

1 Answer 1

Reset to default
1

You could directly use the DNS name of the internal load balancer.

The nodes of an internal load balancer have only private IP addresses. The DNS name of an internal load balancer is publicly resolvable to the private IP addresses of the nodes. Therefore, internal load balancers can only route requests from clients with access to the VPC for the load balancer.

You could also create a CNAME record in Route53 (or other DNS service) if you'd like to name it something different.

If the routes are correct for your VPC peer, your application (VPC B) will be able to resolve and reach the application in VPC A.

Make sure you add entries in the Internal Load Balancers Security Group(s) to allow traffic from VPC B

References

Internal Load Balancers
VPC Peering Security Groups

Improve this answer
2
  • The application in VPC B is currently able to resolve but somehow can't connect to the ELB. I feel like I have done all of these things, but I will go back to verify each one. Thanks!
    – Lars S
    Aug 22, 2019 at 7:36
  • It turned out one of the route tables I edited to allow traffic between the two VPCs was not attached to the correct subnet - a rookie mistake I guess. Thanks for the help!
    – Lars S
    Aug 26, 2019 at 16:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .