When comparing MEGA vs Amazon S3 , the Slant community recommends MEGA for most people. In the question“What are the best cloud backup services?” MEGA is ranked 4th while Amazon S3 is ranked 31st. The most important reason people chose MEGA is:
Linux, Windows and Mac.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cross platform
Linux, Windows and Mac.
Pro Client-side encryption
All files uploaded to Mega are first encrypted on the users side. To access files a decryption key must be supplied. For ease of use, the decryption key can be appended to the URL you share.
Pro 50GB free
50 GB trial for new accounts after registering for a month, then 15 GB. There's also three upgrade plans, starting at 500GB and $110/yr. 15GB may not seem much, but Dropbox only offers 2GB for the free plan. This is better than Google Drive because Google Drive storage is shared with all the Google services you are using.
Pro Functional web interface
Pro Easy to use
Just drag and drop files in the browser window, then create a link for sharing. You will need an account to create a link. To streamline the process for new users you can start uploading as soon as you access the website and create an account while it's uploading.
Pro Respects personal privacy
They will never look through your files unless they ask for permission.
Pro Open source client
Pro Free for small sites
The free tier will cover most personal home pages.
Pro Easily scalable
There's no cap in storage or traffic. Cost is based on usage.
Pro Super cheap with a year's worth of free service
S3 storage costs $0.03 per GB and gets cheaper the more is stored, PUT, COPY, POST, or LIST requests are $0.005 per 1,000 requests and GET and all other requests are $0.004 per 10,000 requests. And with some restrictions is available for free for a year.
Pro Fast setup
You can provision a S3 bucket, upload files, setup the DNS, and go live in under 10 minutes.
Pro Fast
S3 is fast even without a CDN.
Pro Easy to setup with CDN
Simple to set up with Amazon's CloudFont CDN.
Pro Supports custom root domains
To set up a custom domain, Amazon Route 53 has to be configured as the DNS provider with the domain registrar, two buckets have to be created and configured with the name the same as the domain - one including, one excluding www. A more in-depth explanation can be found here.
Pro No security risks
There's no server to manage, so no security issues to patch or keep watch.
Cons
Con Slow syncs
Servers are slow, and the new app is terrible.
Con Credit card needed
Amazon will try to retrieve the money every month after one year trial. If you have no money you will be banned.
Con Setting up automatic public permissions is confusing
By default, S3 sets uploaded files to private. You can configure your S3 bucket to auto-apply public permissions by copying and pasting a template. But the template might be intimidating to some users.
Con Confusing web interface
Amazon S3's web interface is quite confusing, especially for first-time users, but there are many tutorials online that help beginners to set up a static site on S3.
Con No SFTP support
Amazon S3 does not have SFTP support, instead the S3 web interface has to be used.