As the hosting operator, choose which PD AWS MySQL power controls your customers can use for an active service. The client-area steps below cover temporarily starting or stopping the database. Stopping is different from terminating the service or making it permanently cost-free.

Check the effect before stopping

Identify the intended database and dependent applications. Stopping drops active connections and makes the database unavailable until it starts again. Arrange a suitable window and establish the current status before submitting a request.

AWS can automatically restart a stopped database after its allowed stop period. For RDS this is a maximum of seven consecutive days; storage, backups and other applicable charges can continue while stopped. See AWS’s RDS stop guidance for the provider’s conditions.

Customer steps: request and verify the change

1. Open the service’s Overview controls.
2. Choose Stop or Start for the intended state.
3. Review any confirmation and submit once.
4. Follow the request under Activity.
5. Inspect the actual database status until the operation completes.
6. Test application access when it is running again.

A queued request or success message can mean AWS accepted the operation, not that the database has already reached the final state. Do not alternate repeated Start and Stop requests while another operation is still running.

Distinguish billing suspension

A billing-suspended service has different customer-action restrictions. Your Suspend/Unsuspend workflow can queue a busy database’s stop or start, and automation checks for suspended resources that AWS restarted. Keep cron running and inspect the recorded result; do not promise a permanently stopped provider resource from a billing status alone.

Termination is a separate destructive task covered by the removal guide.

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