I have an EC2 instance running on AWS and I need to upload some project files. I’ve downloaded FileZilla, but I’m confused about how to use my .pem key file to authenticate the connection. Every time I try to connect using the public IP, the connection times out or gives a "Permission Denied" error. What are the specific steps to configure the Site Manager in FileZilla for SFTP, and do I need to convert my private key or change any security group settings on the AWS console first?
3 answers
To connect via SFTP, open FileZilla and go to Edit > Settings > Connection > SFTP to add your .pem key file. Then, in Site Manager, create a new site, set the Protocol to SFTP, and enter your EC2 Public DNS as the host. For the Logon Type, select Key File. The most critical part is the username: for Amazon Linux, it’s usually ec2-user, for Ubuntu, it's ubuntu. Also, ensure your AWS Security Group has Port 22 open for your IP address. FileZilla handles the key exchange automatically once the key is added to the settings, allowing you to browse your server directories just like a local folder.
I followed those steps, but I'm getting an error saying the "key file is insecure" or has too many permissions. Does FileZilla require me to change the permissions on my .pem file locally before it will accept it for an SFTP connection?
Don't forget to check your "Inbound Rules" in the AWS Console. If Port 22 isn't open for your specific IP, FileZilla will just time out repeatedly regardless of your key settings.
I agree with Rebecca. I spent two hours debugging my key only to realize my home IP had changed and I hadn't updated the Security Group. It's the most common "gotcha" in EC2 file management!
Steven, that usually happens on Linux or Mac. You need to run chmod 400 yourkey.pem in your terminal to restrict access. However, on Windows, FileZilla sometimes asks to convert the .pem to a .ppk format. If it prompts you to convert, say yes; it uses an internal version of PuTTYgen to make the key compatible. Once the key is converted and restricted, the "insecure" error should vanish, and you'll be able to view the /var/www or home directories immediately.