Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Netlify vs Amazon S3 , the Slant community recommends Netlify for most people. In the question“What are the best website hosting providers?” Netlify is ranked 3rd while Amazon S3 is ranked 11th.
Specs
Question Ranking
Pros
Pro Netlify CDN
Pro Free one-click SSL
Pro Continuous deployment
Pro Custom domains
Pro Versioning and rollbacks
Pro Free tier
Netlify's PRO Plan now Free for Open-Source Projects
Pro Webhooks and integrations
Pro Redirect, rewrite and proxy rules
Pro Full featured CLI
Pro Custom HTTP headers
Pro Support simple forms
Pro Post processing
The post processing doesn't really work. It's a good idea, though!
Pro Functions
Can deploy aws functions without an aws account.
Pro Multiple environment support
Pro Atomic deploys
Pro RESTful API
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 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.
