For more than a decade, Bitnami was the default answer to “I need a WordPress on AWS, yesterday”. It packaged half the internet —AMIs, containers and charts— fully configured and ready to boot in two clicks. If you have touched infrastructure in the last ten years, you have almost certainly launched one.
That free catalogue is no longer maintained. After passing into Broadcom’s hands, the images were moved to a legacy repository that receives no updates, and the AMIs were withdrawn from the AWS Marketplace. There is no new version to launch, and nobody to open a ticket with.
The problem is not the day they stop publishing
It is the day after. Your instance still boots exactly as it did yesterday: the same services, the same paths, the same performance. Nothing breaks, and that is precisely the trap. What changes is invisible from the outside.
From that moment on, every CVE published against the base system or the software inside it stays open on your machine. There is no patched image to relaunch, no notice, nobody to answer. The debt piles up quietly until somebody finds it: an audit, a customer asking for a vulnerability inventory, or something worse.
And rebuilding the image by hand is not trivial. A Bitnami AMI is not “the installed package”: it is its own directory tree, boot scripts, services wired together in a specific way and a pile of decisions taken years ago that your application takes for granted.
What we did
We published replacements that we do maintain. The idea is deliberately boring: same architecture, same paths, same services, so that migrating is not a project but an afternoon.
- Regular patching. Every image revision incorporates the security updates of the base system and of the software it ships.
- Security audit. Vulnerability scanning and CIS hardening verification on every published image, with its report.
- Human support. Tickets reach the team that builds the images.
The catalogue grows according to what the migrating teams ask for, and every available AMI is on the replacement map next to the Bitnami stack it replaces.
How to migrate
In most cases it is three steps, without rewriting anything:
- Launch the replacement from the AWS Marketplace, in the same region and with the same instance type you had.
- Migrate your data: restore the dump or mount the data volume. The paths and services match Bitnami’s.
- Move the elastic IP to the new instance. Your customers notice nothing.
If your stack is not on the map yet, write to us. We prioritise new replacements according to what people ask for most, and knowing that someone needs it is exactly what moves the list.
