Building a Free Website (LEMP on AWS) | Part 1 – The Plan

I have a website! And not just any website. One with my name on it. One where I totally unnecessarily configured every square inch of it. One that is totally overkill for what it’s actually being used for. But it uses entirely free infrastructure, thanks to the magic of AWS free tier infrastructure. Will it be free forever? No. But I currently save $9-10/month on hosting costs, and learned a bunch of cool new skills in the process.

In this series, I’m going to cover how to set up your own “free” website on AWS. We’ll get a site set up exactly as this one is. runs using LEMP infrastructure (Linux, NGINX, MySQL, PHP) on EC2, s3, and RDS, using CloudFront for its CDN and Wordpress for its CMS.

Part 2 | Part 3 | Part 4 | Part 5 | Epilogue

Getting Started

To build a similar site, you will need the following:

  • AWS Account (sign up for free at
  • A domain
    • I purchased mine from Google Domains, but AWS also resells domains (which will allow you to save yourself a little bit of time editing nameservers). If you want a vanity domain (.blog, .tv, .fm, etc.) you may have to check a few different registrars to figure out who sells those domains.
  • SSH client
    • I use PuTTY but anything will work.
  • FTP client
  • Patience
    • In my experience, it is a rare tutorial that works flawlessly end-to-end first go. And even when they do, it is far too easy to accidentally misread or skip a step, and then be very confused. Networking is also just...frustrating sometimes, so be patient and you will get there. I believe in you.

Once you’ve got all your tools, it’s time to dive in.

System Overview

General infrastructure diagram

This is what we’re building. It looks fairly messy (and the stack isn’t exactly correct) but it’s actually not too bad. Here’s what’s happening:

  • Route 53
    • DNS management. Tells the internet where to go when someone types in "" into their browser bar.
  • EC2
    • A computer. This one happens to be running Ubuntu, which is a Linux operating system. You can get them to run Windows too. AWS never turns them off and they have zillions of them to choose from, including the t2.micro instance I am using for this site. We're using it as a server, which will serve our website to the internet. Since it hosts our website, it is our web host.
  • RDS
    • Relational Database Service. Runs the database that makes the Wordpress CMS work. We're using MySQL (the "M" in LEMP).
  • S3
    • Folders of files. S3 is basically the same as the file explorer on your computer, with folder hierarchies and sorting. We're passing off all the images and media to be stored in a separate system for two reasons: 1) the EC2 instance we're using doesn't exactly have a massive amount of storage, and 2) using S3 means we can use a CDN, resulting in super fast image load speeds and less work for the EC2 instance to do.
  • CloudFront
    • A content delivery network (CDN). CDN's are networks of servers that cache websites and images around the world, so that users in Tokyo only need to connect to a computer in Seoul to get your cat GIFs, instead of connecting to Chicago.

That’s the macro-level stuff on AWS. All of it is either free-tier eligible or just free forever (Route 53). You can get by without S3 and CloudFront in this assembly, but they’re not hard to get going. There are also a couple of pieces of software running on our EC2 instance:

    • NGNIX is one of a couple popular web server technologies available out there. Perhaps slightly less common for a basic website than Apache server, I just happen to be more familiar with it due to some work I did using the video streaming plugin NGINX-RTMP so it's my default server of choice.
  • Wordpress
    • Our content management system (CMS). Far and away the most popular choice of CMS for websites great and small. Wordpress makes it easy to create or modify custom themes, build new web pages, start a blog, the works.
  • Certbot (not pictured)
    • Free, auto-renewing SSL certificates. SSL is the "S" at the end of HTTPS, and makes that little padlock appear in your address bar on any site properly maintained. There is literally no reason in this day and age to not have an HTTPS connection when browsing the web.
  • TiddlyWiki (& NodeJS)
    • Not relevant for this series, but it's a cool piece of software that does well as a wiki or personal notes system. I included it in the diagram to show an example of how port forwarding works and also to give it a plug because I really like it. Check it out at

There are also a bunch of default software packages that come preinstalled on Ubuntu, Again, all of these things are free and open source, so no need to bust out the credit card.

The Road Ahead

Part 2 of this series covers setting up an EC2 instance and connecting to it. Part 3 will cover installing NGINX, and configuring your DNS to serve your domain to your web host. Part 4 will cover setting up WordPress, and launching your website. Part 5 will cover the finishing flourishes: setting up the CDN and s3 offload.

As someone who does not have a formal background in computer science, I intend to keep the tutorial focused on the core contents and the logic behind each step. I always prefer to understand the “why” when I am doing things so that I have a solid grasp of the core concepts and can then leap off to explore the next thing in the future.

« Previous
Next »

Grahame Watt