If I modify the port from 22 to 2222 in the secure instance connect feature with the correct configuration...?

Question

I am currently using the Secure Instance Connect feature. I've configured two security groups: one for the endpoint and another for the private instance. The feature's limitations specify allowing only port 22 and 3389, so I enabled port 22 in the endpoint security group for the instance security group ID. When port 22 is enabled in the instance security group, I can successfully connect to the instance. However, if I allow any other port, the instance becomes inaccessible. To address this, I also configured SSH settings using the path 'vi /etc/ssh/sshd_config' and restarted the SSH service. Despite these efforts, I'm still unable to connect to the instance. Could you confirm whether my approach is correct, or if there is an alternative solution available?

Riku_Kobayashi · Accepted Answer

Hello.

As I answered in the previous question, if you change the SSH listening port, you will no longer be able to SSH with EC2 Instance Connect Endpoint.  
Please do not change ports other than port 22 or 3389 as they are not allowed.  
https://repost.aws/ja/questions/QUNbtjF5hBS8mriY19UuQJ1A/if-i-use-port-2222-instead-of-port-22-ssh-for-the-secure-endpoint-connection-feature-on-the-instance

If you want to change the SSH port number, you will need to connect using Systems Manager's Session Manager, etc.  
https://aws.amazon.com/jp/blogs/mt/use-port-forwarding-in-aws-systems-manager-session-manager-to-connect-to-remote-hosts/

If I modify the port from 22 to 2222 in the secure instance connect feature with the correct configuration...?

Add your answer

Relevant content