This took me way too long to figure out, so I hope this post will save you some time.
If you’re the kind of cool cat who uses a static site generator like Jekyll for your site you’re probably also the kind of cool person who wants to put your static site on Amazon’s S3 so you don’t have to worry about a traffic spike taking your site down or your site getting hacked.
But if you’re like me you also want the site to use the apex domain, a.k.a. root domain, a.k.a. naked domain, that is, the site itself like thecoredump.org instead of www.thecoredump.org.
Cough hipster cough.
Amazon, not being idiots, have solved this problem with their Route 53 DNS service. But what if you don’t want to use Route 53?
It looks grim, since Route 53 have figured out what is essentially a hack of the DNS system and one that’s mostly of use to them. Why would anybody else support this?
From a technical standpoint the issue is that the domain name system expects the naked domain, or if you want to use the technical term, the apex domain (which sounds like a pretty cool band name) to be set up to resolve to an IP address but Amazon’s S3 (and Heroku) does its own domain name resolution so there is no IP address to resolve to.
But more and more domain name hosts are figuring out how to replicate this feat, and the one I recommend is Cloudflare. If you put your domain behind Cloudflare (which I’ve been doing for years for the Content Delivery Network functionality and the hack protection they provide), they support what they call CNAME flattening, which means they support naked domains for things like Amazon S3 and Heroku. Which is awesome. And free.
Incidentally, as I said, I’ve used Cloudflare for years and am continually amazed that their base level service is free. Seriously? A free CDN? That’s very cool but kind of nutty.
So why not just use Route 53? This goes into a much bigger post about Amazon Web Services. A lot of companies are building their businesses on top of AWS and are very happy with it, but the thing with AWS is that it’s incredibly flexible and that flexibility inevitably leads to complexity. AWS has a massive learning curve.
S3 is sort of an outlier in the AWS eco system in that it’s very straightforward: You create a bucket, you put files in the bucket, people can see the files. Boom. Simple. The rest of the AWS system is very much not so simple, including Route 53.
Route 53 lets you do all kinds of very cool things with the DNS system, but if all you want to do is put up a simple static site for your business you’ll get a headache real quick.
Cloudflare keeps it simple.
It’s so great you can put your static site on S3 and have an apex domain point to it and not have to worry about any kind of server maintenance and upkeep. It’s very future.
Nic reports his experiences so far with voice computing from Amazon and Google and is a bit mystified at the reaction to Apple’s HomePod.
After a few weeks of using iPhone X I’m ready to join the congratulatory choir.
Nic is interested in smart homes. His contractor let him know how the wealthy are already using them.
Apple’s neglect of the pro market is causing a lot of gnashing of teeth in Apple-nerd circles, but it’s true to Apple’s vision.
There is unrest in the Mac community about Apple’s commitment to the platform. Some are turning their eyes to building a Hackintosh to get the kind of computer Apple doesn’t provide. Here’s what it’s like to run a Hackintosh.
Car nerds are dealing with some cognitive dissonance as car technology changes.
The Oasis is Amazon’s best e-ink reader to date, but it’s not good enough for the price.
Nic buys an Amazon Echo and is indubitably happy with the fantasy star ship in his head.
The problem isn’t ads. The problem is being stalked like an animal across the internet.
The DS416j is a nice NAS for light home use. Just don’t expect raw power.
The Core Dump is moving to GitHub Pages. This is a good thing, most likely.
Thoughts on Apple Watch after half a year of daily usage.
Predictably, the Paris attacks brought the anti-encryption crowd back out of the woodwork. They're at best being willfully disingenuous.
Things to consider when planning to build a site on a compressed time table.
Nic provides some basic not-too-paranoid tips for securing your digital life.
Installing Jekyll on an EC2 Amazon Linux AMI is easy. Here are the steps.
After wearing the watch for over a month, Nic has thoughts on its future. Spoiler: Depends on how you define success.
Turns out “it's just a big iPhone” is a stroke of genius.
Some technical terms still confuse people who should know better, like journalists.
How to host a static site on Amazon S3 with an apex domain without using Amazon’s Route 53.
People fear change, so new technology is used as as a faster version of the old. This makes technologists sad.
Nic loves his Pebble and looks forward to the Apple Watch, but realizes he’s in the minority.
Nic loves books, but he loves their content more.
Nic is worried about the fragile state of our technology and thinks you should be as well.
Nic tries to understand the WATCH. It doesn't go well.
Nic thinks home integration could be Apple’s next major category. Read on to find out why.
Nic is frustrated with his Kindle and would love to see Apple make an e-ink reader.
The iPhone was announced Jan. 9, 2007. It now occupies a huge chunk of Nic’s life.
Nic is very impressed with the speed of the iPhone 5S and iPad Air.
Nic buys a Nexus 7 to test the Android waters.
Nic outlines some of the risks of ceding comments on news stories to Facebook.
Nic is bemused by the sturm und drang surrounding the iOS-ification of Mac OS X.
Web publishing used to require heavy-duty nerditry, but no longer.
Nic is creating an e-book. He shares what he’s learned so far.