When comparing Surge vs Amazon S3 , the Slant community recommends Amazon S3 for most people. In the question“What are the best website hosting providers?” Amazon S3 is ranked 11th while Surge is ranked 15th. The most important reason people chose Amazon S3 is:
The free tier will cover most personal home pages.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free Tier
Unlimited projects, deployments, and collaborators in free tier which also includes basic SSL. Pro options for those who need it cost $13/month (or all you can eat top tier at $30/mo) which gives you auto-provisioning SSL certificates on custom domains.
Pro Automatic Clean URLS
/page resolves /page.html
Pro Custom 404.html files
Catch-all 200.html files.
Pro Six Keystrokes to publish site
Type surge and hit enter in your project directory to deploy.
Pro pushState support for single page apps
Great for front ends like React and Vue.
Pro Automatic Gziping
Auto gzips and sends gziped files.
Pro Supports Jekyll and Grunt and other CIs
Pro Far-future expire headers
Pro Support on Slack
Live Chat Support.
Pro ent (intelligently) about trailing slashes (“/”)
Pro Fully featured CLI tool
Provides a CLI tool to easily deploy using terminal with surge
command.
Pro Atomic Deploys
Deployments are fast, instant, and atomic - with zero chance of collisions.
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 Does not support .pdf by default
Does not support .pdf. To get PDF support you have to add a credit card by running surge card
(though no charges apply).
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.