Skip to content

Bitnami on AWS

A Bitnami alternative for AWS, image by image.

Broadcom pulled Bitnami's AMIs from AWS Marketplace on June 10, 2026, and Bitnami instances stopped getting updates after May 20. Here is the ProvenCloud image that replaces each retired Bitnami stack, and what changes on the server when you move.

01What changed

Your Bitnami server still runs. Its stack is frozen.

The Apache, PHP, database and application builds under /opt/bitnami are Bitnami's own, not Ubuntu or Debian packages, so apt cannot patch them. Since Broadcom stopped shipping updates, they stay at whatever version you launched.

  1. Updates stop

    Existing EC2 and Lightsail instances keep running, but the Bitnami stacks on them receive no updates after this date.

    Source: Broadcom: Important Update: Transitioning Bitnami Offerings on AWS (May 20, 2026)
  2. Bitnami leaves AWS

    Bitnami AMIs, containers and Helm charts are no longer available through AWS Marketplace, Lightsail blueprints or Amazon ECR.

    Source: Broadcom: Important Update: Transitioning Bitnami Offerings on AWS (May 20, 2026)
  3. Upcoming

    First Lightsail blueprints deprecated

    The WordPress, WordPress Multisite, LAMP, Nginx and Node.js blueprints packaged by Bitnami can no longer be picked for new Lightsail instances.

    Source: AWS: Lightsail user guide, Blueprints packaged by Bitnami
  4. Upcoming

    Remaining Lightsail blueprints deprecated

    Joomla, Magento, MEAN, Drupal, GitLab, Redmine, Ghost, Django and PrestaShop follow. Instances you already run, and new ones from your own snapshots, still work.

    Source: AWS: Lightsail user guide, Blueprints packaged by Bitnami

02Replacement map

The ProvenCloud image for each Bitnami one.

One row per Bitnami AMI with a counterpart in our catalog. Versions, clouds and status are read from the catalog itself, so this table changes when the catalog does.

Every image in this table is available now.

Retired Bitnami images on AWS and the ProvenCloud image that replaces each one
Bitnami imageProvenCloud replacement
Elasticsearch Stack (ELK)AMIELK Stack with Elasticsearchv9.5.3 on Ubuntu 24.04 LTSAWS · AzureAvailable
GrafanaAMIGrafana & Prometheus Monitoringv13.2.1 on Ubuntu 24.04 LTSAWS · AzureAvailable
JenkinsAMIJenkins CI/CD Serverv2.568.3 on Ubuntu 24.04 LTSAWS · AzureAvailable
LAMPAMI and Lightsail blueprintLAMP Stack (Apache, MySQL, PHP)Apache 2.4.58 / MySQL 8.0.46 / PHP 8.3.33 on Ubuntu 24.04 LTSAWS · AzureAvailable
LEMPAMILEMP Stack (Nginx, MySQL, PHP)nginx 1.30.4 / MySQL 9.7.2 / PHP 8.5.10 on Ubuntu 24.04 LTSAWS · AzureAvailable
MatomoAMIMatomo Web Analyticsv5.13.0 on Ubuntu 24.04 LTSAWS · AzureAvailable
MauticAMIMautic Marketing Automationv7.2.0 on Ubuntu 24.04 LTSAWS · AzureAvailable
Moodle LMSAMIMoodle LMSv4.5 on Ubuntu 24.04 LTSAWS · AzureAvailable
Neo4jAMINeo4j Community Graph Databasev2026.08.1 on Ubuntu 24.04 LTSAWS · AzureAvailable
NGINX Open SourceAMI and Lightsail blueprintNginx Web Serverv1.30.4 on Ubuntu 24.04 LTSAWS · AzureAvailable
Node.jsAMI and Lightsail blueprintNode.js LTS Production Stackv24.20.0 on Ubuntu 24.04 LTSAWS · AzureAvailable
OdooAMIOdoo ERP and CRM Communityv19.0 on Ubuntu 24.04 LTSAWS · AzureAvailable
PostgreSQLAMIPostgreSQL with pgAdmin 4v18.6 on Ubuntu 24.04 LTSAWS · AzureAvailable
PrestaShopAMI and Lightsail blueprintPrestaShop eCommerce Storev8.2.8 on Ubuntu 22.04 LTSAWS · AzureAvailable
RabbitMQAMIRabbitMQ Message Brokerv4.3.5 on Ubuntu 24.04 LTSAWS · AzureAvailable
RedisAMIRedis with Redis Commanderv8.10.1 on Ubuntu 24.04 LTSAWS · AzureAvailable
RedmineAMI and Lightsail blueprintRedmine Project Managementv7.0.1 on Ubuntu 24.04 LTSAWS · AzureAvailable
Ruby (Ruby on Rails)AMIRuby on Rails Application StackRails 8.1.3.1 / Ruby 3.4.10 on Ubuntu 24.04 LTSAWS · AzureAvailable
SonarQubeAMISonarQube Code Quality Serverv26.9.0 on Ubuntu 24.04 LTSAWS · AzureAvailable
SuiteCRMAMISuiteCRM Open Source CRMv8.10.2 on Ubuntu 24.04 LTSAWS · AzureAvailable
WordPressAMI and Lightsail blueprintWordPress CMSv7.1 on Ubuntu 24.04 LTSAWS · AzureAvailable

No ProvenCloud image yet

  • Django
  • Drupal
  • Ghost
  • GitLab
  • Joomla!
  • Magento
  • MEAN
  • MySQL
  • WordPress Multisite

Running one of these? Requests decide what we build next. Tell us which one.

03What changes when you move

Same applications, a standard Ubuntu layout.

Bitnami put its own build of every component under /opt/bitnami. ProvenCloud images install each component from its official repository or release onto Canonical's Ubuntu image, so systemd, /etc and apt work the way they do on any Ubuntu server.

Bitnami and ProvenCloud server layouts compared
BitnamiProvenCloud
SSH userbitnamiubuntu
Where the stack livesBitnami's own builds of every component under /opt/bitnamiOfficial packages in the standard Ubuntu places: /etc, /var/www/html, /var/lib
Restart a servicesudo /opt/bitnami/ctlscript.sh restart apachesudo systemctl restart apache2
WordPress files/opt/bitnami/wordpress/var/www/html/wordpress
DatabaseMariaDB on most stacks, data in /opt/bitnami/mariadb/dataMySQL or PostgreSQL from official packages, data in /var/lib/mysql or /var/lib/postgresql
First passwordGenerated at first boot, read from /home/bitnami/bitnami_credentialsSet at first boot; on most images it is your EC2 instance ID, and the product page names every login it opens
HTTPSsudo /opt/bitnami/bncert-toolsudo certbot --apache -d your.domain; certbot ships on the WordPress, nginx, Node.js and Jitsi images and is one apt install away on the rest
Patching the stackLaunch a newer Bitnami image and migrate to it. For AWS, no newer image is coming.sudo apt upgrade patches the operating system and the server packages in place

First-boot credentials

Bitnami generated one application password per instance and wrote it to /home/bitnami/bitnami_credentials. ProvenCloud images also set every password on your instance at first boot and ship none in the image. On most of them the starting password is your EC2 instance ID, so there is no log to dig through; a few, such as n8n, have you create the owner account on the first visit instead.

Each product page's getting-started steps name every login and the script in /home/ubuntu/iscripts that changes it. Once you import your data, you sign in to the application with your existing accounts: they come across with the database.

Moving a database

Don't move the data volume. Most Bitnami stacks ran MariaDB, and MySQL cannot open MariaDB's data files; PostgreSQL will not start on a data directory from another major version either. Move the data as a dump.

MariaDB to MySQL, on the Bitnami server and then on the new one:

/opt/bitnami/mariadb/bin/mariadb-dump -h 127.0.0.1 -u root -p \
  --single-transaction --routines --triggers --databases <name> > db.sql

sed -i -e '/enable the sandbox mode/d' \
  -e 's/utf8mb4_uca1400_ai_ci/utf8mb4_0900_ai_ci/g' db.sql
mysql -u root -p < db.sql

The sed line strips the two things recent MariaDB dumps contain that MySQL 8 rejects. PostgreSQL goes across the same way:

/opt/bitnami/postgresql/bin/pg_dumpall -h 127.0.0.1 -U postgres > all.sql

sudo -u postgres psql < all.sql

pg_dumpall carries roles and their passwords across, including the postgres role. To copy plain files such as uploads, attach a snapshot of the old volume to the new instance and copy them off it.

Moving a WordPress site

  1. 1. Snapshot the Bitnami instance. It is your rollback until the new site is live.

  2. 2. Export from the Bitnami server. The first line prints the database name, user and password to use in the second.

    grep DB_ /opt/bitnami/wordpress/wp-config.php
    /opt/bitnami/mariadb/bin/mariadb-dump -h 127.0.0.1 \
      -u <DB_USER> -p <DB_NAME> > wordpress.sql
    sudo tar -czf wp-content.tgz -C /opt/bitnami/wordpress/wp-content .

    Older Bitnami images kept the site in /opt/bitnami/apps/wordpress/htdocs and the client in /opt/bitnami/mysql/bin.

  3. 3. Import on the ProvenCloud server. Copy both files across as ubuntu, then:

    sed -i -e '/enable the sandbox mode/d' \
      -e 's/utf8mb4_uca1400_ai_ci/utf8mb4_0900_ai_ci/g' ~/wordpress.sql
    sudo tar -xzf ~/wp-content.tgz -C /var/www/html/wordpress/wp-content
    sudo chown -R www-data:www-data /var/www/html/wordpress/wp-content
    sudo wp --allow-root --path=/var/www/html/wordpress \
      db import ~/wordpress.sql

    Both sides default to the wp_ table prefix. If you changed yours, set $table_prefix in /var/www/html/wordpress/wp-config.php to match.

  4. 4. Move the domain. Run sudo bash /home/ubuntu/iscripts/wp_url.sh to add your domain and make it the site address, point DNS at the new instance, then add HTTPS with sudo certbot --apache -d your.domain.

Rather not do it yourself?

We move the server and keep your rollback.

Move a Bitnami WordPress, Jenkins, Redis, Moodle or other server to the matching ProvenCloud image, with no data loss.

On your first done-for-you package you pay after delivery, once you have verified the work in your own account.

$299$499founding rate, 5 business days

  • Inventory of the existing Bitnami instance: versions, data, config and cron
  • New instance from the matching ProvenCloud image, in your account
  • Data and configuration migrated and verified against the original
  • DNS cutover at a time you choose, with the old instance kept as a rollback
  • Old instance decommissioned only after you sign off

04Questions

Before you switch.

More in the FAQ, or ask an engineer.

No. EC2 and Lightsail instances launched from Bitnami images keep running. What stopped is updates: Broadcom ships no new Bitnami builds for AWS after May 20, 2026, so the Apache, PHP, database and application builds under /opt/bitnami stay at the version you launched. The operating system underneath can still be patched with apt.

For a while. AWS stopped publishing newer Bitnami blueprint versions on May 19, 2026. It deprecates the WordPress, WordPress Multisite, LAMP, Nginx and Node.js blueprints packaged by Bitnami on November 19, 2026, and Joomla, Magento, MEAN, Drupal, GitLab, Redmine, Ghost, Django and PrestaShop on May 19, 2027. After those dates you can still create instances from your own snapshots, but not from the blueprint.

A paid Bitnami Secure Images subscription, which Broadcom positions as the drop-in replacement for the free Bitnami images in production. If you would rather run plain EC2 with standard Ubuntu packages, the table on this page lists the ProvenCloud image for each Bitnami one.

No. Each component is installed from its official repository or release onto Canonical’s Ubuntu image, so files live where Ubuntu puts them and services run under systemd. Scripts that call /opt/bitnami/ctlscript.sh or hard-code /opt/bitnami paths need updating; the comparison on this page covers the common ones.

Yes. Our Bitnami to ProvenCloud migration package moves one Bitnami server to the matching ProvenCloud image in your own AWS account and keeps the old instance as a rollback until you sign off. It costs $299 at the founding rate (standard $499), delivered in 5 business days. On your first done-for-you package you pay after delivery, once you have verified the work in your own account.