How to access OpenSearch from few different VPCs?

I have an OpenSearch cluster in VPC A, I need applications deployed in VPC B and VPC C to access OpenSearch in VPC A. The problem is that VPC B and VPC C have the same IP range (even the subnets have the same range and I can't change it), so I cannot do a vpc peering or use transit gateway.

A solution would be to put an Nginx proxy in VPC A and then via VPC endpoints allows applications in VPC B and VPC C to access Nginx, but I'd like to avoid to need to support the Nginx proxy.

Any other solution?

主题

网络和内容交付无服务器分析

标签

亚马逊 VPC 亚马逊开放搜索服务 AWS 专用链接

语言

English

Miki

已提问 2 年前943 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

VPC Peering does not allow transitive routing. You can peer VPC B and C to A, this configuration does not allow VPC B to communicate to VPC C. For return traffic from VPC A to VPCs B and C you would need to configure specific routing, even down to the instance if need be. Take a look here for options and examples https://docs.aws.amazon.com/vpc/latest/peering/peering-configurations-partial-access.html

AJ_C

已回答 2 年前

Miki
2 年前
Thanks but that doesn't work in my case as VPC B and C have the same structure (same IP ranges associated to the subnets) and instances are running on ASG so I can't go too specific on the IP routing. And for simplicity I put only VPC B and C, but in reality I have around 30 VPCs that needs to connect to OpenSearch I found a solution on this link https://aws.amazon.com/blogs/networking-and-content-delivery/how-to-solve-private-ip-exhaustion-with-private-nat-solution/ but it's bit expensive to have a HA solution, as each VPC would required at least 2 extra NATs plus Transit Gateway.

How to access OpenSearch from few different VPCs?

相关内容