As the hosting operator, guide your customer through PD AWS SQL Server’s client-area power controls when a temporary database interruption is intended. These controls operate on the RDS database linked to the service; stopping the database does not cancel the billing service or retire the resource.

Prepare for the interruption

Open the active customer service and confirm the database and AWS region. Coordinate with the application owner: stopping or rebooting drops active connections. Use the 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.

AWS does not support stopping a SQL Server Multi-AZ instance. Your hosting team should confirm the deployment before using Stop; a visible button does not override that provider restriction.

Customer steps: request one action

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

Work can be queued while AWS completes an earlier operation. A Done entry can mean AWS accepted the operation, rather than that the database has already reached its final state. Repeated clicks are not a useful way to shorten a provider transition.

Understand temporary stopping

Amazon RDS automatically restarts a database after seven consecutive stopped days. Stopping is not permanent retirement and should not be treated as cancelling all provider charges. Keep required recovery points independently of a temporary stop.

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 SQL Server WHMCS guide for related tasks, or explore PD AWS SQL Server.