Access to custom TCP Rule in AWS EC2 [closed]

问题

Closed. This question needs debugging details. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 3 years ago.

Improve this question

I had created a custom TCP rule in aws EC2 server. And the inbound and the outbound rules for the rule is anywhere mean anyone can access the port.

But the port is not enabled. I was getting a problem like port is closed whenever I tried to check it using "yougetsignal".

Whereas being able yo access the common port 22. The problem is facing is only with the custom TCP rule I created.

What might be the problem?

回答1:

Please check two thing:

1. Your Network ACL's (VPC) - see if your traffic rules are ok
2. If you got no problems in number 1, check the following link:

Ephemeral Ports

If you are using a custom VPC, you may need to add a ACL rule (ephemeral ports): ephemeral port rule

来源：https://stackoverflow.com/questions/44254360/access-to-custom-tcp-rule-in-aws-ec2