Usually I would think ftps, but for one I'm having several troubles configuring it, and for two I'm wondering if there's a better way to transfer files in and out.
It's a basic web server that we decided to go with AWS for the load balancing and all amazing stuff we heard about how it can properly manage heavy loads. All we want here is a simple way to access the files within /var/www/html
like FTP usually is (and later on add access to mysql).
I've set it up using the amazing CloudFormation and the default WordPress template because we will have a blog (I've already managed to move the blog from root to /blog
) and a database. That was simple enough. So we're running a weird Amazon RedHat 4.4 with no iptables
. I believe vsftpd is already working just fine (after configuring it, also fairly simple). But then, not even using the pasv tactics and opening the ports through AWS EC2's Security Group could I penetrate amazon's "firewall".
Right now I know I can transfer files using SSH and manually move & sudo
permissions later on, since I can't and should not login as a root. But a more automated and simple way would be highly preferred.
How should we be accessing those files anyway? If it's HTTPS then it shall be, but then why?
If FTPS is the right way, can you please point a direction or a tutorial?
If by any chance it's using S3, all that would be new to me... So I'd also appreciate any pointers!
Thanks in advance.
I would not use ftp(s) to transfer files, maybe its a personal thing but I think ftp is outdated, a pain to manage and setup.
Just use scp and manage your user/group permissions so you can write to that web folder. Or use something like svn to manage your files and better yet your revisions. A simple svn up is all you would need to do.
Since depending on your architecture, you will need to duplicate your htdocs folders across nodes if your actually planing on doing load balancing.
I would assume ssh would be the way to go here. ssh is pretty much the standard. Set your ownership to something like www:www, then scp or sftp with the client of your choice.