PD AWS Lightsail lets you offer an additional storage disk when customers order a server. The Extra storage checkout choice selects a separate disk attached to the new instance; it does not enlarge the operating-system disk included in the instance plan.

Decide how the additional disk will be used

For example, a customer might keep application data on a separate disk from the operating system. Decide whether your service includes preparing that disk inside the server or whether the customer will do so. Attaching a disk at AWS does not, by itself, create a mounted filesystem or a Windows drive letter.

Create the Lightsail product and configure its AWS connection before generating checkout choices. Choose a region and availability zone suitable for the offering: an attached disk must be in the same zone as its instance.

Expose Extra storage at checkout

1. Open System Settings → Products/Services → your Lightsail product → Module Settings, then find the Configurable Options section.
2. Tick Extra storage among the checkout dimensions.
3. For a new group, select Generate configurable options. For an existing group, select Save visibility to expose the choice while preserving its prices. Rebuild from AWS (resets prices) is a different operation; use it only when you intend to regenerate the group and review prices again.
4. Review the generated group in WHMCS Configurable Options. Extra storage is a dropdown with None and supported disk sizes.
5. Review the selling price for each size, billing term and currency. The suggested value is a starting point for your offering, not a decision about your final price.
6. Open the customer order form without submitting an order. Check that None and the intended sizes appear for this product, with the expected price changes.

Keep the generated option values matched to the supported sizes. Renaming a label does not change the underlying disk capacity. If you simply need to hide the dimension, use the visibility controls rather than rebuilding an already priced group.

Verify a newly ordered disk

During your next intentional first-service test, select one of the offered sizes and allow provisioning to finish. Check the service's Activity and your AWS account to confirm that the additional disk belongs to the intended instance and has the selected capacity.

Then inspect the disks inside the guest operating system. Identify the additional disk by its size and attachment before preparing it; do not select the system disk or an existing data disk by assumption. Follow your operating system's process for initialising, formatting and mounting a new blank disk, and check that the application can use the intended location.

An existing filesystem should be inspected and mounted appropriately, not formatted as if it were blank. Formatting removes existing data.

Keep disk backups separate from instance recovery

Plan backups for the data placed on this disk. The module's instance snapshot restore carries the attached extra disk across in its current state; it does not roll that disk's contents back to the instance snapshot's time.

For example, restoring yesterday's operating system does not automatically restore yesterday's database files if those files live on the extra disk. Coordinate application and disk backups for the recovery outcome your service promises.

Changing the offering later

Changing the checkout choices prepares future orders. Do not assume that editing a size label or regenerating a group resizes a disk on an existing customer service. Treat changes to existing storage as a separate operation and verify the supported workflow before promising it to a customer.