PD AWS Lightsail can move a service to a larger supported plan using a snapshot and replacement server. Configure the choices deliberately so your customers are not offered a downgrade, an operating-system switch or a move to another AWS account as though it were a normal resize.

Choose compatible targets

Keep the source and target on the same AWS account, region and operating-system family. Choose a larger supported plan. Review the storage configuration too: the module keeps an attached extra disk as it is and refuses a request that requires that disk to grow beyond its current size.

The module’s upgrade process preserves the server through a snapshot-based replacement. It is not a promise of zero downtime or a live in-place capacity change. Agree a maintenance period and take any application-level backup the workload needs.

Configure the offered path

1. Open Packages → Packages and compare the source and intended target Lightsail packages.
2. Check that both use the same AWS account, region and operating-system family, with a supported larger target plan.
3. Review the package group, available customer changes and your billing configuration before offering the target.
4. Check the intended service-change path in Blesta rather than treating an edit to a package default as a completed resize of an existing service.

Carry out and check an agreed change

Use Blesta’s normal supported service-change workflow. Follow the module’s Activity while the snapshot and replacement complete, and avoid submitting a second change while one is pending.

After completion, confirm the service’s plan, memory, storage and application health. An existing static IP is retained through the replacement; without one, check the new public address and any DNS or external services that depend on it. Check attached storage and access before considering the maintenance complete.

Check a rejected or unfinished upgrade

Read the displayed reason and compare the source and target settings: AWS account, region, operating-system family, larger plan and extra-storage requirement. Correct a mismatched offering before requesting that change again. A rejected request is different from a replacement that has already started.

For a started change, open the affected service under PD Modules → PD AWS Lightsail → Clients & Services and read Activity. Compare the recorded operation with the instance state in your own AWS account. If billing shows the new offering while the replacement is still pending, follow the existing operation before accepting another change for your customer.

See the PD AWS Lightsail Blesta guide for related tasks, or explore the module.

Clients who need help with an unexplained module result can follow our reporting guide (client sign-in required).