As the hosting operator, guide your customer through PD AWS PostgreSQL’s client-area power controls when a temporary database interruption is intended. Start, Stop and Reboot operate on the database already linked to the service; they do not cancel its billing record or create a replacement.

Prepare for the interruption

Open the active service in the customer area and check its database, backing, region and current status. Coordinate with anyone using the application: stopping or rebooting interrupts database connections. Use controls offered by that service. If a control is unavailable, your hosting team should check the affected service’s configuration, backing and actual state. Use the original service’s offered controls; another endpoint or another service is not a substitute.

Customer steps: request one action

1. Open the service’s Overview.
2. Choose Stop to pause a running database, Start for a stopped one, or Reboot for a restart.
3. Read and confirm the displayed interruption message where one is shown.
4. Follow the request under Activity.
5. Wait for the resulting database state before reconnecting the application or issuing another action.

Requests can be queued while AWS finishes an earlier operation. A Done entry can mean AWS accepted the change; check the resulting status separately. Repeated clicks are not a useful way to shorten a provider transition.

Understand temporary stopping

AWS automatically starts a database after seven consecutive stopped days on both RDS and Lightsail. Stopping is not permanent retirement and should not be treated as cancelling all provider charges.

If the database does not reach the expected state, compare the original Activity request with the resource in your AWS account. Follow an operation still processing rather than submitting another change just to refresh its status.

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