3 個答案
- 最新
- 最多得票
- 最多評論
0
For internet user to access VPC based opensearch we did the following
- created alb in public subnet
- create r53 cname mapping with alb
- Create target group with IP based
- using event bridge (createNetworkInterface & DeleteNetworkInterface) & lambda(python) we were able to query the ENI's and update the IP's in Target group.
With the above approach internet users able to access the vpc based opensearch
已回答 1 年前
0
Can you elaborate your solution here? were you able to automate this approach? specifically the Listeners and rules that need to be setup, what health checks need to setup in TG?
已回答 7 個月前
相關內容
- 已提問 1 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
no as per compliance it has to be inside vpc. but some users via internet they need access to kibana dashboard. the internet users wont use vpn's.
What about using a Systems Manager Session Manager proxy to access EC2 as a stepping stone?
https://repost.aws/knowledge-center/systems-manager-ssh-vpc-resources
Using this configuration, you can access OpenSearch in the VPC from the EC2 on the trestle.