3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta un anno fa
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?
con risposta 3 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
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.