3 Answers
- Newest
- Most votes
- Most comments
5
Please check at the following:
- Verify Security Group Rules – Ensure inbound and outbound rules allow traffic on the required TCP ports.
- Check Network ACLs – Confirm that your Network Access Control Lists (ACLs) aren't blocking traffic.
- Inspect Route Table Settings – If this EIP is associated with an AWS instance, verify that the route table correctly directs traffic.
- Review AWS Service Health – AWS occasionally experiences regional outages. You can check the AWS Service Health Dashboard for any reported issues.
- Run Connectivity Tests – Use telnet 15.223.143.32 <port> or nc -zv 15.223.143.32 <port> to test port accessibility.
- Check for Port Exhaustion – If the instance is running Windows, port exhaustion could be a factor.
1
What do you mean by you cannot access 15.223.143.32. I can easily ping this IP and it returns a response.
0
You should enable some logs like CloudWatch or Flow logs on VPC. since IP is pingable, then try to verify if the port you are trying to access the IP with is open.
Views expressed are my own and not those of my employer.
answered 7 months ago
Relevant content
- asked 6 years ago
- AWS OFFICIALUpdated 2 years ago
