Amazon Lightsail is retiring its Bitnami blueprints

On November 19, 2026, Amazon Lightsail retires its Bitnami-based WordPress, WordPress Multisite, LAMP, Nginx and Node.js blueprints; the remaining Bitnami blueprints follow on May 19, 2027. If you run a Lightsail instance from one of these, here's what's changing — and the honest set of options.

The deadlines

What retires, and when

Date	What changes
May 19, 2026	Lightsail stopped shipping newer versions of the Bitnami blueprints
November 19, 2026	Bitnami blueprints for WordPress, WordPress Multisite, LAMP, Nginx, and Node.js are deprecated — no longer selectable for new instances
May 19, 2027	The remaining Bitnami blueprints (Joomla, Magento, MEAN, Drupal, GitLab, Redmine, Ghost, Django, PrestaShop) are deprecated

Existing instances keep running after each date, and you can still create new instances from an existing snapshot of a Bitnami-blueprint instance at any time. What you lose is the blueprint itself in the create-instance picker — and since May 19, 2026 those blueprints receive no newer versions, so patching is entirely on you. Any rebuild, scale-out or new environment that depends on picking a retired blueprint is the event that bites; snapshot what you may need to rebuild and plan the move before the date.

Sources: AWS — Blueprints packaged by Bitnami (FAQ) · AWS — Migrating from Bitnami blueprints to Lightsail blueprints. Last reviewed November 10, 2026.

Your options

Three honest paths

Option 1

AWS's own replacement

For the popular stacks — WordPress, WordPress Multisite, LAMP, Nginx, Node.js — AWS publishes its own Lightsail-packaged replacement blueprints, and recommends them for new instances. If you just need a basic instance of one of these, that may be all you need. We won't pretend otherwise.

Option 2

A hardened image in your own account

If you want a hardened, CIS-aligned, regularly rebuilt image — or you're graduating off Lightsail to a full cloud account with per-hour marketplace billing — our hardened nginx image maps to the retiring Nginx blueprint, and the broader catalog covers the databases and services you might run alongside it.

Option 3

Apps without a free successor

Running something in the May 2027 wave — GitLab, Drupal, Ghost, Redmine, Django and friends? Those get no Lightsail-packaged replacement. Our catalog spans databases, messaging, analytics, security and web platforms — browse it.

Questions we get

Frequently asked

Will my existing Lightsail instance stop working on November 19, 2026?

No. AWS states that existing instances created from Bitnami blueprints keep running without disruption after the deprecation dates. What changes is that the deprecated blueprint can no longer be selected when creating a new instance in the Lightsail console or API.

Can I still create a new instance from a Bitnami blueprint after the date?

Not from the blueprint picker. You can, however, create new instances from existing snapshots of a Bitnami-blueprint instance at any time, including after the deprecation date, so take a snapshot of anything you may need to rebuild.

Do I have to migrate?

AWS says no, as long as you keep patching the operating system and application yourself. Since May 19, 2026 Lightsail no longer ships newer versions of the Bitnami blueprints, so every security update on those instances is your job.

What does AWS recommend for new instances?

Blueprints packaged by Lightsail, which exist for WordPress, WordPress Multisite, LAMP, Nginx and Node.js. Applications in the May 19, 2027 wave (Joomla, Magento, MEAN, Drupal, GitLab, Redmine, Ghost, Django, PrestaShop) have no Lightsail-packaged successor.

When is a hardened marketplace image the better fit?

When you are moving off Lightsail to a full AWS, Azure, Google Cloud or Oracle Cloud account anyway, when you want a maintained image rebuilt against current advisories rather than a frozen blueprint, or when you run an application that gets no free successor. For a simple WordPress or LAMP site, AWS's free Lightsail blueprint is likely the right call.

Why teams pick the marketplace-native route

Hardened and maintained, not a frozen blueprint — a monthly rebuild cadence against current advisories, with out-of-band rebuilds for critical ones.
Your own account, your identity, networking and governance — the image deploys into your subscription or account, not ours.
Pay-as-you-go through your cloud's marketplace — stop the instance, stop paying; see how buying works.

Migration hub How buying works

For a simple WordPress or LAMP site, AWS's free replacement blueprint is likely the right call — we're not the answer for every Lightsail workload. We're the marketplace-native alternative for teams that want hardened, maintained images deployed in their own account. Amazon Lightsail, AWS and Bitnami are trademarks of their respective owners, used for identification only; no affiliation or endorsement is implied.