1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello, from what you indicate I see that you verified the configuration correctly, I add the following:
- I understand that the instance at the operating system level is listening on port 8700, to validate it you could put the following command "netstat -tulpn | grep ':8700'" or you can search it visually with the following command "sudo lsof -i -P -n | grep LISTEN", if you have the service in LISTEN everything is fine, but otherwise check the service.
- In addition to verifying the inbound rules of your instances, from the client instance it validates the outbound rules.
- I understand that at the network level everything is well configured, but you could validate the communication between instances with reachability analyzer at the cloud level (there are other tools from the AWS Network Manager service), Docs: https://docs.aws.amazon. com/vpc/latest/reachability/getting-started.html
- If you are trying to access some DNS name, but you don't have a DNS server, you will have to specify the DNS name locally in the instance's host file.
- Perform connection tests from the client instance, and test the port 8700 connection via telnet, for example, in case of time out problems, rule out DNS problems and networking again.
Greetings.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa