大网数据广告活动
服务器运维问答

How do I access an internal ELB from a peered VPC?

· 52CE 我爱测

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 …

问题原文

原帖链接 · Lars S · CC BY-SA 4.0

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?

已采纳解答

原帖链接 · kenlukas · CC BY-SA 4.0

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

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-08-21)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。