Looks very similar to my project <a href="https://github.com/kkuchta/scarr" rel="nofollow">https://github.com/kkuchta/scarr</a> from a while back. It even uses the same acronym (I assume that's just a coincidence, since we both just picked a cool-sounding english-language word using the initials from S3, Cloudfront, ACM, and ACM.<p>At a glance:
- Mine handles domain registration + ACM verification automatically
- This one wisely uses clioudformation instead of api calls
- This one does apex->ww redirects, whereas mine uses the apex and has no redirect<p>Seems pretty cool!
GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify.<p>[0] <a href="https://pages.github.com/" rel="nofollow">https://pages.github.com/</a>
Am I the only one who still hosts my own static sites on a plain old virtual machine?<p>It's pretty simple to configure nginx for static sites, and by doing it yourself you reduce vendor lockin to just about nil.<p>Even if S3 is massively cheaper, $5/month for a tiny VM seems like a small price to pay for being vendor-abstract.<p>I suppose S3 is way less likely to suffer a meaningful outage than my little VM, but how many 9s do my personal websites actually need?
Nice project.<p>As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays.
I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet.<p>Edit: Thanks for these replies.
We use a combination of Netlify + Webflow + Hugo for our website (www.facetdev.com). With that we get a global CDN and our website will never go down.<p>Netlify has been awesome and it made it stupid easy to combine our www site on Webflow with a hugo static blog in a subfolder (/blog). This might be my favorite web publishing workflow ever.<p>If you haven't tried Netlify yet, definitely give it a look.
I wrote a tutorial for how to do all this setup manually, if you prefer: <a href="https://www.davidbaumgold.com/tutorials/host-static-site-aws-s3-cloudfront/" rel="nofollow">https://www.davidbaumgold.com/tutorials/host-static-site-aws...</a><p>Sometimes it’s nice to understand how all the pieces fit together, instead of using an automated system!
How much does this cost? I put in some more effort to setup my HAProxy and nginx containers on a Vultr node, but I get LetsEncrypt for free, so I'm just paying for a Vultr node (or DO droplet) and the price of the domain name:<p><a href="https://github.com/sumdog/bee2" rel="nofollow">https://github.com/sumdog/bee2</a>
I have a two-line Makefile that with one target that sync's my website with an S3 bucket. Deploys are instant. The rest is handled by Cloudflare an AWS. The sheer number of moving parts in this system is outrageous for a static website. A fun project for sure, though.
Bundling service config and launch makes the whole process easier, for sure. There's also more than one way to configure this depending on what your needs are, so it'd be cool to have a few different versions of SCAR.<p>I started with a setup similar to your diagram and tweaked it when I realized S3 didn't serve index.html when the URL was just the parent "directory", i.e. example.com/foo/ doesn't resolve to s3://example.com/foo/index.html. To get this working I had to write a bit of JS in a Lambda function and deploy it at the edge of my CloudFront distribution to do some URL rewriting.<p>Given that's the behavior most people expect, might be worth considering?
Recently moved some static sites from S3 to AWS Amplify Console. Super easy setup and even easier maintenance with the Git-based workflow: <a href="https://aws.amazon.com/amplify/console/" rel="nofollow">https://aws.amazon.com/amplify/console/</a>
Anyone have an a average monthly fee for using these as hosting solution? last time i ran the numbers using all that services go from 5 to 10 USD per month and was better to use amazon lightsail (3.5 per month) or other cheaper alternatives at lowendbox
For anyone looking for a hosted solution, <a href="https://surge.sh/" rel="nofollow">https://surge.sh/</a> is super nice and simple without any of the complexity of managing the stack yourself. Deploying uses one simple command, and you get hosting and custom domains for free, though I believe SSL is paid for custom domains. (I'm not affiliated with Surge at all, just a happy user.)
Same feature set - plus a few extras like Basic Auth support, custom headers, preventing direct access to the underlying S3 bucket - implemented as a reusable Terraform module: <a href="https://github.com/futurice/terraform-utils/tree/master/aws_static_site" rel="nofollow">https://github.com/futurice/terraform-utils/tree/master/aws_...</a>
great job! I wish more projects have 1-click deploy to Heroku, aws, gcp or azure. This is a good habit more people should get into.<p>Running this project on aws can give a cloud beginner an interesting way to expose them to many concepts. Now I just have to figure out what static website I want to run in this!<p>Please do the same for running your own scalable wordpress install!
TL;DR this is an AWS stack with <i>10 AWS services</i> required to build/deploy a static site with HTTPS/CDN<p>I will be staying with netlify
You've only taken care of the surface-level complexity with AWS. Want to do something more like add a header to the response? Well then, create a lambda, deploy it to the edge, and pay per page view. This is something Firebase is much more elegant at - the initial deploy, and then evolution and addition of features geared to static site deployment.
Try out <a href="https://freepage.io" rel="nofollow">https://freepage.io</a> is much easier to use than github pages. You don't even have to create an account, verify email and all that nonsense to use it. And it has social media built in to get your page out there in to the world.
This is highly complex for no reason.
GitHubPages, Netify provide you with easy to use custom static page hosting.<p>Your abstraction is nice, but the learning curve for someone is incredibly high for such a setup.
This seems like a nightmare to setup and maintain for a new comer. Netlify lets us setup things in a whiff. This is a nice project but not for anyone below intermediate.
How to host static website with HTTPS, a global CDN and custom domains for free:<p>1. Setup public repo with Hugo project<p>2. Add Travis CI integration with GH Pages<p>3. Use CloudFlare for free SSL + other goodies<p>Why would anyone need this?