AWS lightsail documentation change
Summary
Restructured FAQ to add a new question about migration and clarify responsibility for updates. Added links to migration and update management documentation.
Security assessment
The changes emphasize user responsibility for applying security patches and updates, and add references to security documentation. However, there's no evidence of addressing a specific vulnerability or incident.
Diff
diff --git a/lightsail/latest/userguide/amazon-lightsail-faq-bitnami-blueprints.md b/lightsail/latest/userguide/amazon-lightsail-faq-bitnami-blueprints.md index d764ec620..5eba9562c 100644 --- a//lightsail/latest/userguide/amazon-lightsail-faq-bitnami-blueprints.md +++ b//lightsail/latest/userguide/amazon-lightsail-faq-bitnami-blueprints.md @@ -7 +7 @@ -What is happening with Bitnami blueprints on Lightsail?Will my existing instances using blueprints packaged by Bitnami be affected?Can I still create new instances using a Bitnami blueprint after the deprecation date?Am I responsible for applying updates and patches to my existing instances using blueprints packaged by Bitnami? +What is happening with Bitnami blueprints on Lightsail?Will my existing instances using blueprints packaged by Bitnami be affected?Can I still create new instances using a Bitnami blueprint after the deprecation date?Do I need to migrate my existing application to a new instance?Am I responsible for applying updates and patches to my existing instances that use blueprints packaged by Bitnami? @@ -27 +27 @@ Snapshots are point-in-time backups that let you restore your instance from a go -## Am I responsible for applying updates and patches to my existing instances using blueprints packaged by Bitnami? +## Do I need to migrate my existing application to a new instance? @@ -29 +29 @@ Snapshots are point-in-time backups that let you restore your instance from a go -Yes. You are responsible for keeping your running instances up-to-date by applying any software updates and security patches. Customers who maintain instances follow a pattern of manually applying patches and updates. The nature of this responsibility model provides the flexibility and control. Starting May 19, 2026, Lightsail will not provide newer versions of blueprints packaged by Bitnami. Your operational model for maintaining existing instances remains unchanged. +No. As long as you regularly update, patch, and secure the operating system and applications on your instance, you do not need to migrate your existing application. @@ -31 +31,7 @@ Yes. You are responsible for keeping your running instances up-to-date by applyi -When creating a new instance through the Lightsail console or API, use a blueprint packaged by Lightsail to get the up-to-date blueprint. Blueprints packaged by Lightsail are available for WordPress, WordPress Multisite, LAMP, Nginx, and Node.js. +The deprecation does not require you to modify your operating model. If you were updating your operating system and application regularly, you can continue doing that. If you were migrating your application to a new instance every time Lightsail released an updated blueprint, then you can consider migrating now as well. To learn more about how you can migrate your existing application, refer to [Migrating from Bitnami blueprints to Lightsail blueprints](./migrate-from-bitnami-to-lightsail-blueprints.html). + +## Am I responsible for applying updates and patches to my existing instances that use blueprints packaged by Bitnami? + +Yes. Your operational model for maintaining existing instances is not affected. You are responsible for keeping your running instances up-to-date by applying any software updates and security patches. The nature of this responsibility model provides flexibility and control. To learn more, refer to [Update management](./amazon-lightsail-update-management.html). + +When creating a new instance through the Lightsail console or API, we recommend using a blueprint packaged by Lightsail to get the up-to-date blueprint. Blueprints packaged by Lightsail are available for WordPress, WordPress Multisite, LAMP, Nginx, and Node.js.