If you want WordPress hosting on Lightsail without hand-rolling Nginx, PHP-FPM, and Let’s Encrypt yourself, Amazon’s fully managed WordPress blueprint is the fastest path to a production site. Where our EC2 setup guide walks through building the server by hand, Lightsail bundles compute, storage, and a guided setup wizard into one predictable monthly plan — you’re online in about 15 minutes.
Lightsail lists two blueprint providers for WordPress: Lightsail and Bitnami. As of May 19, 2026, the Bitnami-packaged blueprint stopped receiving updates, and AWS retires it for new instances on November 19, 2026. Existing Bitnami instances keep running fine, but for anything new, pick the Lightsail blueprint provider. It’s actively maintained, has IMDSv2 enforced by default, and comes with the guided setup wizard this tutorial uses — no more digging through SSH for a bitnami_application_password file.
Entry-level Lightsail Linux plans start at $3.50/month for an IPv6-only instance, or $5/month if you want a public IPv4 address — both bundle compute, SSD storage, and a data transfer allowance into one flat price. For a low-traffic blog, the $5 or $7/month tier is plenty to start, and you can resize later by spinning up a new instance from a snapshot rather than migrating everything by hand.
Once the instance shows a Running state, grab the public IPv4 address from the instance page and paste it into a browser. You’ll see WordPress’s default test post — confirmation the server is up before you touch DNS or SSL.
This is the part that used to mean manually attaching a static IP, editing DNS records, then SSH-ing in to run bncert-tool. Now it’s one wizard.
On the instance page, open the Connect tab and choose Set up your website, then work through:
Setup can take up to 15 minutes — don’t stop or modify the instance while it runs. Two things worth double-checking beforehand:
# Confirm your domain resolves to the static IP you just created
dig +short yourdomain.com
Let’s Encrypt certificates issued through this wizard renew automatically every 60–90 days — no cron job or certbot maintenance required.
WordPress generates a random admin password on first boot, and Lightsail hands it to you through CloudShell rather than a file over SSH:
Log in, then head straight to Users → Profile and set a password of your own. The default one lives in a system-generated location you don’t want to rely on long-term.

© 2026 Stackstroke. All rights reserved.