Configure WordPress with a Lightsail content delivery network
This blueprint packaged by Bitnami is being deprecated
Blueprints packaged by Bitnami will no longer receive updates after May 19, 2026. Starting November 19, 2026, you will no longer be able to create new instances with this blueprint. When creating new instances, we recommend using the equivalent Lightsail blueprint if available. Existing instances using blueprints packaged by Bitnami will continue to run without any disruption. Learn more
If you have an existing instance that uses a blueprint packaged by Bitnami and want to migrate to a Lightsail-packaged blueprint, see Migrate to Lightsail blueprints.
This tutorial applies to instances that use WordPress packaged by Bitnami only
If your instance uses the WordPress blueprint packaged by Lightsail, see WordPress instead.
In this guide, we show you how to configure your WordPress instance to work with an Amazon Lightsail distribution.
All Lightsail distributions have HTTPS enabled by default for their default domain (for
example, 123456abcdef.cloudfront.net). The configuration of your distribution
determines whether the connection between your distribution and your instance is
encrypted.
-
Your WordPress website uses HTTP only – If your website uses HTTP only as the origin of your distribution, and it is not configured to use HTTPS, you can configure your distribution to terminate SSL/TLS and forward all content requests to your instance using an unencrypted connection.
-
Your WordPress website uses HTTPS – If your website uses HTTPS as the origin of your distribution, you can configure your distribution to forward all content requests to your instance using an encrypted connection. This configuration is known as end-to-end encryption.
Step 1: Complete the prerequisites
Before you get started, make sure your WordPress instance is in a running state. For more information, see Start, stop, or restart your instance.
Step 2: Create the distribution
Complete the following steps to configure a Lightsail distribution for your WordPress instance. For more information, see Create a Lightsail content delivery network distribution.
To create a distribution for your WordPress instance
-
In the left navigation pane, choose Networking.
-
Choose Create distribution.
-
For Choose your origin, choose the Region where you're running your WordPress instance and then choose your WordPress instance. We automatically use the static IP address that you attached to the instance.
-
For Caching behavior, choose Best for WordPress.
-
(Optional) To configure end-to-end encryption, change the origin protocol policy to HTTPS only. For more information, see Origin protocol policy. This requires your WordPress instance to serve HTTPS. For instructions, see Enable HTTPS on your WordPress instance.
-
Configure the remaining options and then choose Create distribution.
-
On the Custom domains tab, choose Create certificate. Enter a unique name for the certificate, enter the names of your domain and subdomains, and then choose Create certificate.
-
Choose Attach certificate.
-
For Update DNS records, choose I understand.
Step 3: Update DNS records
Complete the following steps to update the DNS records for your Lightsail DNS zone.
To update the DNS records for your distribution
-
In the left navigation pane, choose Domains & DNS.
-
Under the DNS zones section of the page, choose the domain name to which you want to add the record that will direct traffic for your domain to your distribution.
-
Choose the DNS records tab. Then, choose Add record.
-
Complete one of the following steps depending on the type of domain that you want to point to your distribution:
-
Choose an address (A) record to point an apex domain (e.g.,
example.com) to your distribution.If an A record for the apex of your domain is already present in your DNS zone, then you will need to edit that existing record instead of adding another A record.
-
Choose a canonical name (CNAME) to point a sub domain, such as
website.example.com, to your distribution.
-
-
If you're adding an A record, then in the Resolves to text box choose the name of your distribution. If you're adding a CNAME record, then in the Maps to text box enter the default domain name of your distribution.
Note
When you add an A record to your DNS zone, and choose the name of your distribution, you are in fact adding an alias record, which is different than an address record. Lightsail makes it easy for you to add alias records without the additional steps that are typically required at other DNS hosting providers.
-
Choose the save icon to save the record to your DNS zone.
Repeat these steps to add additional DNS records for domains on your certificate that you are using with your distribution. Allow time for changes to propagate through the Internet's DNS. After a few minutes, you should see if your domain is pointing to your distribution. You should also test your distribution. For more information, see the following Test your distribution.
Step 4: Allow static content to be cached by the distribution
Complete the following procedure to edit the wp-config.php file in your
WordPress instance so that it works with your distribution.
Note
We recommend that you create a snapshot of your WordPress instance before getting started with this procedure. The snapshot can be used as a backup from which you can create another instance in case something goes wrong. For more information, see Create a snapshot of your Linux or Unix instance.
-
Sign in to the Lightsail console
. -
In the left navigation pane, choose the browser-based SSH client icon that is displayed next to your WordPress instance.
-
After you're connected to your instance, enter the following command to create a backup of the
wp-config.phpfile. If something goes wrong, you can restore the file using the backup.sudo cp /opt/bitnami/wordpress/wp-config.php /opt/bitnami/wordpress/wp-config.php.backup -
Enter the following command to open the
wp-config.phpfile using Vim.sudo vim /opt/bitnami/wordpress/wp-config.php -
Press
Ito enter insert mode in Vim. -
Delete the following lines of code in the file.
define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/'); define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/'); -
Add one of the following lines of code to the file depending on the version of WordPress that you're using:
-
If you're using version 3.3 or lower, add the following lines of code where you previously deleted the code.
define('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] . '/'); define('WP_HOME', 'https://' . $_SERVER['HTTP_HOST'] . '/'); if (isset($_SERVER['HTTP_CLOUDFRONT_FORWARDED_PROTO']) && $_SERVER['HTTP_CLOUDFRONT_FORWARDED_PROTO'] === 'https') { $_SERVER['HTTPS'] = 'on'; } -
If you're using version 3.3.1-5 or higher, add the following lines of code where you previously deleted the code.
define('WP_SITEURL', 'http://DOMAIN/'); define('WP_HOME', 'http://DOMAIN/'); if (isset($_SERVER['HTTP_CLOUDFRONT_FORWARDED_PROTO']) && $_SERVER['HTTP_CLOUDFRONT_FORWARDED_PROTO'] === 'https') { $_SERVER['HTTPS'] = 'on'; }
-
-
Press the Esc key to exit insert mode in Vim, then type
:wq!and press Enter to save your edits (write) and quit Vim. -
Enter the following command to restart the Apache service on your instance.
sudo /opt/bitnami/ctlscript.sh restart apache -
Wait a few moments for your the Apache service to restart, then test that your distribution is caching your content. For more information, see Test your Amazon Lightsail distribution.
-
If something went wrong, re-connect to your instance using the browser-based SSH client. Run the following command to restore the
wp-config.phpfile using the backup you created earlier in this guide.sudo cp /opt/bitnami/wordpress/wp-config.php.backup /opt/bitnami/wordpress/wp-config.phpAfter you restore the file, enter the following command to restart the Apache service:
sudo /opt/bitnami/ctlscript.sh restart apache
Additional information about distributions
Here are some articles to help you manage distributions in Lightsail: