# LAMP by Bitnami
**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](amazon-lightsail-faq-bitnami-blueprints.md)
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](migrate-from-bitnami-to-lightsail-blueprints.md).
This section covers topics related to instances that use LAMP packaged by Bitnami. If you're not sure which vendor packaged your blueprint, see [Identify your blueprint vendor](#identify-blueprint-vendor). If your instance uses the LAMP blueprint packaged by Lightsail, see [LAMP](amazon-lightsail-lamp-lightsail.md) instead.
**Topics**
+ [Launch and configure instances that use LAMP packaged by Bitnami](amazon-lightsail-quick-start-guide-lamp-bitnami.md)
+ [Enable HTTPS on instances that use LAMP packaged by Bitnami with Let's Encrypt and Certbot](amazon-lightsail-using-lets-encrypt-certificates-with-lamp.md)
+ [Connect instances that use LAMP packaged by Bitnami to an Aurora database](amazon-lightsail-connect-lamp-instance-to-aurora-database.md)
+ [Identify your blueprint vendor](#identify-blueprint-vendor)
## Identify your blueprint vendor
Before you begin, confirm which vendor packaged your instance blueprint. Navigate to your instance's management page in the Lightsail console and check the blueprint information in the header. It shows either "Lightsail" or "Bitnami" as the vendor.
The following example shows an instance that uses WordPress packaged by Lightsail:
