1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello Uladzimir,
Take a look and see if any of these options suit your needs.
Potential Solutions:
- Private Endpoint: If your primary use-case involves accessing the RDS instance from within the same VPC, consider switching the "Publicly accessible" setting to "No". This will ensure that only private IPs are associated with the RDS instance and its listener endpoint.
- Route 53 Resolver: Set up a custom DNS resolver using Amazon Route 53 Resolver. You can create a rule that forces resolution of the listener endpoint's domain name to its private IP.
Alternative Solution (not recommended):
- Hosts File: As a workaround, though not recommended for production systems, you can manually map the listener endpoint to the private IP in the /etc/hosts (or equivalent) file on your EC2 instance. This will force the EC2 instance to resolve the endpoint to the specified IP. However, if the IP ever changes, you will need to manually update it.
con risposta 8 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Any update?