Choose the AWS backing before selling a PostgreSQL database through PD AWS PostgreSQL. RDS and Lightsail use different plan values and expose different management capabilities; changing the name of a plan does not make them interchangeable.

Match the backing to the service

Amazon RDS offers the module’s in-place instance-class changes, storage growth and per-database IP firewall. Lightsail uses managed-database bundles with their included resources. The module does not offer a separate Lightsail IP allow-list or in-place Lightsail resizing.

Both backings support the module’s available start, stop, reboot and manual-snapshot controls. Recovery is a separate administrator workflow, rather than an implied Restore button in the customer page. AWS account permissions must cover whichever service you choose.

Save matching defaults

1. Open the package’s Module tab.
2. Choose Backing service, then the intended region.
3. Select a plan from that backing’s choices.
4. Review PostgreSQL version, storage where applicable and public accessibility.
5. Save and inspect the actual accepted order choices before provisioning.

The module-panel connection test makes an RDS read. It does not validate a Lightsail database creation request. Curated bundle and version examples also need checking against current AWS availability.

Keep migrations separate

Changing a package’s backing does not move existing PostgreSQL data. Establish a destination, usable recovery point, application cutover and service tracking with the administrator before moving a live service. Do not delete the original database or press Create again to force a migration. See recovery planning before making changes to the source.

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