How to host WordPress in AWS Lightsail

Cover Image for How to host WordPress in AWS Lightsail

How to host WordPress in AWS Lightsail

How-to written and screenshots taken on 2020 March 418 min read


When I started the previous version of my blog site ( WordPress blog), I didn't knew how to host WordPress myself. So I took a subscription to a webhosting service at TransIP. They not only offered hosting, but also a one button WordPress installation. This is not something special, but a great way for people to get started.

Although the speed and the price were good, something was missing. I didn't need it, but I wanted more control. With more control I mean setting up advanced caching (Redis and Nginx) and installing the latest MySQL version (8.0).

That meant getting my own VPS. As I already researched and implemented this for jodiBooks, it was a logical choice to also use AWS for my blog. And as I couldn't find a proper guide I created this "How to host WordPress in AWS Lightsail" tutorial. One that is not based on the standard Bitnami image.

AWS Lightsail

As far as I know AWS has two services that are suitable for hosting WordPress: EC2 and Lightsail. EC2 is the advanced option which comes with a lot of additional options. For a simple blog Lightsail is good enough, much simpler and cheaper.

Looking at pricing comparing Lightsail with a hosting solution is fairer as it isn't a full VPS. It doesn't have dedicated vCPU cores and network connections are shared. It does include data traffic and dns management. If you choose to use an EC2 instance, bare in mind that it needs to be extended with a Route 53 hosted zone ($0,50 per month) and you pay for data transfer.

In this guide I'll show you how to setup WordPress on a Lightsail instance. I will do that in 3 parts. The first 2 are essential, the last one optional but recommended.

  1. Prepare AWS
  2. Install LEMP stack
  3. Backups
Webhosting TransIP--€ 5.99
VPS TransIP11 GB€ 10.00
AWS Lightsail 1GB1 (10%)1 GB$ 5.00
AWS EC2 t3a.micro2 (10%)1 GB$ 8.31

*Pricing as of 21 September 2020

Prepare AWS

1. Setup AWS account

Before we can start with Lightsail, we have to get an account. You don't need to be a business to register with AWS, but you do need a credit card. When you successfully registered the account, you have to secure it.

Using the root account needs to be avoided and instead a daily admin account should be made. I have described how to do that here: Hosting ASP.NET apps on AWS part 4.

2. Setup Lightsail instance

  1. Now that we have our account and have logged in with our admin user, we can go to the Lightsail dashboard. Here we click on the Create instance button. I already had an instance running, but otherwise the dashboard would show a big Create button.

    aws lightsail dashboard with the "create instance" button hightlighted

  2. After clicking that button select the region closest to you or your intended visitors to make the latency of your website as low as possible. For me that is Frankfurt. Optionally you can also select the availability zone, but for a single instance that doesn't matter.

    a visual list (flags, with country, state or city) of all the available regions

  3. Next we can select the OS (platform), Linux/Unix, and the OS type, Ubuntu 18.04. If you want an easy installation and your application is listed, you can also select Apps + OS. This will use a Bitnami image with everything preinstalled en configured.

    Visual selection of the OS (Linux or Windows) and the Linux version (Ubuntu 18.04)

  4. Scrolling down further, we can select some optional items. For now we leave all of these settings on the default values.

    Further down, we can also select the instance size. WordPress will run fine on all of them. Our intended setup uses a little more memory, so we need at least the second (1 GB) option.

    Set optional launch script, keys and snapshots. Choose instance size.

  5. As the last step we enter the instance name. I chose joeplaa-server-u01 for my server. It hosts the joeplaa website, it is a web server and is a Ubuntu instance with number 01 (02 for this how-to).

    Set the instance name to joeplaa-server-u02

  6. After we click the Create instance button the instance will be initiated. This can take a few minutes. After that the instance will be accessible through the dashboard as shown in the first picture ('Good afternoon').

3. Setup Route 53

I wanted to move my domain to AWS. This is not necessary. You can also use any other registrar, as long as you can configure your DNS and nameserver settings. In the first part of Hosting ASP.NET apps on AWS part 7 I describe how to register and/or transfer a domain to Route 53. You can stop when you arrive at the "DNS management" heading. We'll do that in Lightsail.

4. Setup Lightsail networking

  1. In the Lightsail dashboard go to the Networking tab. Now click the Create static IP button.

    The networking tab of the Lightsail dashboard. Showing DNS zone and static IP address.

  2. Select the region. Use the same as your instance. I choose Frankfurt.

    Flags showing the available regions for the IP address

  3. Next we select the instance (I can't as all my instances already have a static IP attached). And we give it a name. I named mine joeplaa-static-ip1. Create the IP.

    Attach and name the IP address

  4. With the IP address created and the nameservers of the domain accessible, we now click Create DNS zone.

    Lightsail networking dashboard

  5. Enter the domain, for me that's and click Create DNS zone at the bottom of the page.

    Entered domain name on create DNS zone page

  6. Enter the following records one by one:

TypeSubdomainResolves to
A@<your static ip address>
CNAMEwww<your main domain>
  1. Now scroll down. You'll find a list with the 4 nameservers for your DNS zone. Go to your domain registrar and change their nameservers to the Lightsail ones.

    Censored nameservers for DNS zone

  2. Something I didn't understand at first is that you had to configure these servers with your registrar, in my case Route 53. Once I knew, I still had to find out where and how to configure the nameservers in Route 53. Go to your "Registered domains" in the Route 53 dashboard and open the domain for the DNS zone we are configuring in Lightsail.

    Details for the domain. Edit nameservers and disable DNSSEC

  3. Make sure DNSSEC is disabled. If not click Add or edit name servers and disable it (Route 53 currently doesn't support it). When DNSSEC is disabled you can change the nameservers by clicking Add or edit name servers again.

Install LEMP (Linux, Nginx, MariaDB, PHP) stack

1. Login and update

Now that the instance is running, we can connect to it through SSH. This will all be command line, so no nice GUI.

  1. If you use Windows, download PuTTY and install. On Mac or Linux you can use the terminal.

  2. Follow this excellent guide from the AWS docs to connect to your instance. It would basically be copy-pasting and a waste of time if I redid it here. I just want to add one thing: instead of using the IP address, you can also use your domain if set up correctly.

    Use your domain instead of an IP in PuTTY

  3. Once you're connected start with updating the OS:

    sudo apt update && sudo apt upgrade -y

2. Setup firewall

I'm not a firewall guru. To be honest, I know very little about firewalls, especially how to configure them in Linux. I used the sources below to setup mine.

  1. We start with installing the firewall. In Ubuntu this is UFW, UncomplicatedFireWall.

    sudo apt update
    sudo apt install ufw
  2. Now the first thing we do is configure the default settings. We want to allow all outgoing traffic and deny all incoming traffic.

    sudo ufw default allow outgoing
    sudo ufw default deny incoming
  3. All incoming ports are closed now, but we want to be able to SSH (PuTTY) into the instance. To do that we need to configure that in the firewall. We do that by allowing port 22 to accept traffic. With this setting anyone can enter your server. Don't worry though, we'll fix that in a minute.

    sudo ufw allow ssh
  4. We also want our WordPress page to be accessible. To do that we have to allow traffic on port 80 and 443. There are multiple ways to do that, but we'll take the easy route.

    sudo ufw allow 'Nginx Full'
  5. Lastly we enable the firewall. You will be warned that enabling the firewall may disrupt existing ssh connections. We've opened that port, so we can type y and hit Enter.

    sudo ufw enable
  6. Check the firewall settings with the following command:

    sudo ufw status verbose

    enabled ufw rules

  7. Now go to the Lightsail dashboard, click on your instance and select the Networking tab. Here you'll see another firewall. This is the firewall AWS provides. It sounds like doing the firewall in Linux is double the work and unnecessary, but better be safe and enable both. Again the ports 22, 80 and 443 need to be open. For port 22 we enable the "Restrict to IP address" option and add our home/office address (

    Networking tab of the instance settings.

3. Enable Swap

Preferably you only use the RAM of your instance, because that is the fastest option to store temporary data. As we only have 1 GB, this is quite tight. So the second option would be to create swap space on the local SSD, ephemeral storage in AWS terms. A Lightsail instance however doesn't have that, so we are forced to forgo on best-practices and use the attached network volume.

AWS recommends creating swap space that is "2x the amount of RAM but never less than 32 MB". You can create a new volume (disk) specifically for swap, but I've added it to the main volume.

  1. We will create a 2 GB swap space (64 blocks of 32 MB). In the command line type:

    sudo dd if=/dev/zero of=/swapfile bs=32M count=64
  2. Update the read and write permissions for the swap file:

    sudo chmod 600 /swapfile
  3. Set up a Linux swap area:

    sudo mkswap /swapfile
  4. Make the swap file available for immediate use by adding the swap file to swap space:

    sudo swapon /swapfile
  5. Verify that the procedure was successful:

    sudo swapon -s
  6. Enable the swap file at boot time by editing the /etc/fstab file. Open the file in the editor:

    sudo nano /etc/fstab
  7. Add the following new line at the end of the file (use arrow keys and paste the line with right-mouse button), save the file (ctrl+x), and then exit (y and hit Enter):

    /swapfile swap swap defaults 0 0

    add line to /etc/fstab using nano editor

  8. When starting a new SSH session, Ubuntu will display the amount of used memory, but you can also see it by using top or htop. These can be opened by simply typing top or htop in the terminal.

    memory info at start of session
    Memory usage info when starting an SSH session

    top information
    System information and memory usage as displayed in top. Sort on memory (%MEM): `shift+M`

4. Install Redis, Nginx, PHP, MySQL

For jodiBooks I configured the exact same stack. The only difference is that it was done on an EC2 instance instead of Lightsail. The process however is (almost) exactly the same (I used that guide to install this blog). The only difference is the S3 plugin, which I'll discuss below.

5. Set file and folder permissions

Instead of using the Duplicator plugin, I had to manually copy my files from the old hoster to my Lightsail instance. After I copied the files from my computer to the correct folder on my instance, the Autoptimize plugin gave an error. It couldn't access the cache folder.

This was due to incorrect folder and file credential settings on the instance. If you get an error, working settings are listed in the table below. To achieve this, follow the steps below.

sudo chown ubuntu:ubuntu -R /var/www/<website>
sudo chown www-data:www-data -R /var/www/<website>/wp-content
cd /var/www/<website>
sudo find -type d -exec chmod 755 {} \;
sudo find -type f -exec chmod 644 {} \;
sudo chmod 600 wp-config.php
sudo chmod 444 index.php

Be aware that the opinions on the "correct" folder settings vary. The settings I use are generally not considered safe (enough). But, if I use the safe settings, I cannot upload files through plugins, I can't edit the theme or add plugins.

In the end it's your choice between safety (it's very hard to modify your files) and usability (I don't want to change files manually through the terminal, I prefer the WordPress admin panel). As I make regular backups, I chose usability.


1. Lightsail snapshot

Now that we have a working WordPress website, it'a good idea to make a backup of all the work we did. If anything goes wrong in the future, be it a hack or you yourself (accidentally) screwing something up, you can go back to this state.

When running a virtual machine, or in our case an instance, you can make snapshots. A snapshot is a description of the state of the machine at that given moment. In effect it's an exact copy of all the data on the volume (SSD, hard disk, network drive) of that machine.

In Lightsail snapshots can be made automatically every day (last 7 days are stored), but as you pay for the storage of each snapshot ($0.05 per GB per month), we only make a single snapshot of the current state. You can always make a new one later if you updated software or added a lot of data.

  1. In Lightsail go to your dashboard and click on the instance for which you want to make a snapshot. Do not go to the snapshot tab, as that is only a list of your snapshots.

    The Lightsail dashboard with a visual list of instances. In this case the instance joeplaa-server-u01.

  2. Now go to the Snapshots tab. On this page you'll see a list of snapshots you already made (or were made automatically). I made one on March 2, which was after I finished setting up this site. Click on + Create snapshot to make a new one.

    The snapshot overview page with one manual snapshot and automatic snapshot disabled.

  3. Enter a name for your snapshot. Personally I want to know what instance this snapshot belongs to joeplaa-server-u01, the date 20200503 and why initial setup or OS update or something. I forgot that with my first snapshot though. Press Create.

    Give the new snapshot a name. Something recognizable.

2. Backup to S3 plugin

We could have used snapshots to make backups of our posts, images and WP settings, but it's cheaper to store data in S3. A GB of snapshot storage costs 5 cents per month, where data storage in S3 costs 2.45 cents (Frankfurt).

S3 is known as object storage. I wrote about that in more detail in this post. For now it's enough to know all objects (files) are stored in buckets. Every bucket can be configured to be accessible by certain users that have been given certain credentials (read, write, delete, etc.).

I found a plugin, UpdraftPlus, which makes a backup of the database, plugins, themes, uploads (images) and other files. To do that, we have to create an S3 bucket for these objects and a user with access to this bucket.

  1. Go to the S3 dashboard. It will list all your current buckets.

    The S3 dashboard with two buckets

  2. Click the + Create bucket button and enter the name of your bucket. Let's call this one joeplaa-backup-example. Change the Region to your region if needed. The correct one is probably already selected, in my case EU (Frankfurt).

    Create bucket display. We've entered the bucket name and chosen the region (Frankfurt).

  3. Click Next and select Versioning and Default encryption: AES-256.

    Screen with multiple bucket config options. We only enable Versioning and Encryption.

  4. In the next screen keep the setting: Block all public access and click Next.

    Block public access settings

  5. In the last screen check your settings and click Create bucket. The bucket will be added to the list and we can open it by clicking the name.

  6. To allow the plugin (Updraft) to access this bucket, we have to create an IAM user with a policy that allows that. Go to the IAM dashboard and click Users. In the user screen, we'll click the Add user button.

    User list in AWS IAM dashboard showing 3 users.

  7. Enter the user name and try to use a name that explains who the user is. I often make the mistake of giving users names the future-me has no idea who or what they are. Let's try wp-updraft-backup-restore (please remember future-me). Select Programmatic access.

    Add user page in IAM panel. Added a user name and selected Programmatic access as the Access type

  8. In the next screen click Attach existing policies directly and then click the Create policy button.

    Set user permissions. Select a policy from the list or create one.

  9. A new browser tab or windows will open with a Create policy screen. Click on the JSON tab and paste the policy below.

    "Version": "2012-10-17",
    "Statement": [
    "Sid": "VisualEditor0",
    "Effect": "Allow",
    "Action": [
    "Resource": ""
    "Sid": "VisualEditor1",
    "Effect": "Allow",
    "Action": [
    "Resource": "*"

    Add JSON to describe the policy

  10. Give the policy a name in the last screen. Again choose something you can identify later. I'll take the service S3, the bucket and the user updraft. In the Description I write that down with more words.

    Review policy screen with entered name and description.

  11. After you created the policy, go back to the browser tab with the create user screen. Click the Refresh button and search for the policy you just created and select it.

    Select the policy you just created

  12. Click Next twice and Create user. Now save the credentials somewhere safe.

  13. Open the Updraft plugin settings in WordPress. Plugins can be found in the Settings part of the main menu.

  14. First we can select how often we want backups and how many to keep. For example Daily and 14 (two weeks). Next we can select the storage provider. S3 obviously.

    The Updraft settings screen. Set schedule to daily and retain 14 backups. Also selected Amazon S3 as storage

  15. Almost there. When we scroll down a little, we can enter the user credentials and the bucket name. Below that we can select the parts we want to backup and add any exclusions (e.g. cache folders). Scroll all the way down and press Save Changes.

    Add S3 bucket name and credentials and set folders to backup and exclude

Wrapping up

That's it. Now you have a super fast WordPress site on Lightsail which is regularly backed up to S3. If however your traffic grows and you're running into limitations, just make a snapshot, spin up a bigger instance and deploy your snapshot.

If you're really getting serious traffic, you probably want to look into a separate database instance and multiple Lightsail or EC2 instances coupled with a load balancer. That however is a very different use case.

Thanks for reading and I hope my guide helped you setup your WordPress site. If you have any questions or remarks send me an email or hit me up on one of the social platforms below.