Setting up This Blog with AWS

Abstract

This post talks about how this blog was set up with Amazon AWS. Specifically, how S3 was sued to host the blog, Route 53 for the setting up the domain, and CloudFront for providing https.

1. S3 as Website Storage

Amazon Simple Storage Service (S3) is an Amazon Web Service that offers object storage through API or simple web interface. It relies on the scalable infrastructure that all AWS benefit from. In this case, a specific S3 bucket was created and this HTML blog was uploaded to it. The blog is based on Bootstrap that lets anyone create their own web page in just a few minutes and with basic HTML and JavaScript knowledge. It is open-source, responsive and supports mobile devices. While S3 does not provide support for dynamic websites - websites that e.g., use PHP - but this is not required in this specific blog.

2. Route 53 to get the Domain

Next, AWS Route 53 was used to get the respective domain name. Route 53 is the scalable Domain Name Service (DNS) and is used to redirect incoming web requests from the URL: yetanotherdatablog.com to the S3 bucket. I chose and registered a .com domain for $12 per year which I find totally acceptable.

3. CloudFront to enable https

Last, it was my goal to ensure a proper https connection for all users. To do so, I use CloudFront - a service that is traditionally as a content delivery network - to enable https support for this blog. While CloudFront offers servers in all major geographical regions, I chose to go with the cheapest option (only U.S., Canada, and Europe) because latency is not the most important issue when opening a website.

4. Combine all these 3 Services

In a last step, I used Route 53 to point to the CloudFront distribution, which then redirects the website user to the S3 bucket.

AWS Flow Chart