even port 20 open in the SG to 0.0.0.0/0 is not changing the behavior. I also created a listener in the LB just in case, but it also change nothing. There is nothing else in the VPC except for the AWS Transfer Family server. There are no EC2 instances. There is no firewall. There is no Direct Connect.
Error: The data connection could not be established: ETIMEDOUT - Connection attempt timed out
Timeout detected. (data connection)
FTP uses two ports, port 21 is the control port and port 20 is used for data transfer.
Make sure that both these ports are open in the security group (and/or NACL) associated with the AWS Transfer server.
And depending on where you're accessing the AWS Transfer server from, ensure that both ports are open all along the way. This could be secuerity group rules relating to an EC2 instance in the same VPC, or firewall rules allowing access along a Direct Connect link to on-prem, or anything else.
Ok, finally fixed it. Apparently I forgot to click register on all the ports >.<
- How do I configure my AWS Transfer Family server to use an Amazon S3 bucket that's in another AWS account?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- How can I fix the error "Unable to locate credentials" when I try to connect to my Amazon S3 bucket using the AWS CLI?AWS OFFICIALUpdated a year ago
- How do I troubleshoot connectivity issues when I use interface VPC endpoints to connect to my Amazon S3 bucket?AWS OFFICIALUpdated 3 months ago
- EXPERTpublished 18 days ago
- EXPERTpublished 3 months ago