EC2 Instance Endpoint restricts the use of ports other than TCP ports 22 and 3389. How can I still connect to RDS...?
This is Onikai (@fat47) from the Service Reliability Group (SRG) of the Technology Division.
#SRGThe Service Reliability Group primarily provides comprehensive support for the infrastructure surrounding our media services, focusing on improving existing services, launching new ones, and contributing to open-source software (OSS).
This article is located within SRG.DBWGThe DB Working Group is releasing database-related materials that it provides to the entire company.
I hope this is of some help.
EC2 Instance Endpoint restricts the use of ports other than SSH and RDP.Wouldn't it be better to simply change the port used on the RDS side to 3389?In conclusion
EC2 Instance Endpoint restricts the use of ports other than SSH and RDP.
The other day, after reading an article by Classmethod, I tried connecting to RDS using the EC2 Instance Connect Endpoint.
Today, June 28, 2023, this feature was suddenly updated, restricting its use to TCP ports other than 22 and 3389.
When I try to connect, I get the following error message:
I think AWS probably didn't intend for everything to be so easily accessible.
Wouldn't it be better to simply change the port used on the RDS side to 3389?
Come to think of it, I remembered that the port used on the RDS (Aurora) side can be changed.
I thought that changing this might make it work, so I decided to experiment.
You can change the port to 3389 from the Aurora cluster settings.
We will also change the security group settings applied to Aurora and VPC endpoints to port 3389.
Then, we establish a tunnel to port 3389.
We have confirmed that we can connect!
In conclusion
I don't think I'll actually use it, but I tried it out as an experiment.
It would be great if they could update it to include more officially available ports.
SRG is looking for new team members.
If you are interested, please contact us here.