If you don’t, then Google up some other article explaining what to do.
Starting point: you already know how to connect to your EC2 server via SSH using your private key. FileZilla (on Mac OS X) and EC2 using private keys For the benefit of other Mac OS X users, here is the Mac-ified version of what to do. It worked! It’s written from a Window-centric standpoint. It describes how to use FileZilla to connect to EC2 using private keys. I re-gave-up. But then one day I randomly came across this post which links to this post. But I could not figure out how to use a private key. It worked immediately for a server with a username and password. Later someone let me know that FileZilla can indeed use SCP despite the above issue. It would be nice if the FileZilla folks would update that rejected feature request to indicate that the feature was indeed added at a later time. Eventually I realized that this is not true. Please add Secure Copy Protocol (SCP) support – Ticket #4147 (closed Feature request: rejected) First, FileZilla completely rejected the idea of adding the ability to transfer files via SCP. But I could not get FileZilla to do an scp copy when the connection had to use a private key to connect. It saves me all of the FTP shenanigans I was going through before. Eventually I learned the correct way to do it in one step: scp -i ~/my_private_key /Users/mdahlman/temp/messages.json FileZilla and EC2 using private keys
But it’s a lot more painful than it ought to be. Then I would FTP the file down to that instance. I would upload files via FTP from my machine to an FTP server somewhere. I nearly always connect like this: ssh -i ~/my_private_key SCP and EC2 using private keysĪt first I didn’t have a simple way to upload files from my laptop to my EC2 instance. We always use private keys to login rather than passwords. We often use RightScale on top of EC2 to manage things.