Deleting Pay-per-Use DB Instances or Read Replicas

Scenarios

To release resources, you can delete DB instances or read replicas billed on the pay-per-use basis as required on the Instances page.

Constraints

• DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are complete.
• If a backup of a DB instance is being restored, the instance cannot be deleted.
• A maximum of 50 pay-per-use DB instances can be deleted at a time.
• If you delete a pay-per-use DB instance, its automated backups will also be deleted and you will no longer be billed for them. Manual backups, however, will be retained and generate additional costs.

• If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
• You will not be billed for the instances that were not successfully created.
• Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
• You can rebuild a DB instance that was deleted up to 7 days ago from the recycle bin.
• You can use a manual backup to restore a DB instance. For details, see Restoring a DB Instance from Backups.

Deleting a Pay-per-Use DB Instance

1. Log in to the management console.
2. Click in the upper left corner and select a region.
3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
4. On the Instances page, locate the primary DB instance to be deleted and choose More > Delete in the Operation column.
   Figure 1 Deleting a DB instance
   

5. In the displayed dialog box, enter delete, select Yes for Confirm, select I have read this warning and understand the risks., and click Yes to deliver the request.
6. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

   Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

7. Refresh the DB instance list later to confirm that the deletion was successful.

Deleting a Pay-per-Use Read Replica

1. Log in to the management console.
2. Click in the upper left corner and select a region.
3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
4. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
5. Locate the read replica to be deleted and click More > Delete in the Operation column.
6. In the displayed dialog box, enter delete, select Yes for Confirm, select I have read this warning and understand the risks., and click Yes to deliver the request.
7. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

   Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

8. Refresh the DB instance list later to check that the deletion is successful.

Deleting Pay-per-Use DB Instances in Batches

1. Log in to the management console.
2. Click in the upper left corner and select a region.
3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
4. On the Instances page, select the RDS for MySQL pay-per-use DB instances to be deleted and choose More > Delete above the DB instance list.
5. In the displayed dialog box, click Yes.
6. If you have enabled operation protection, click Send Code in the displayed Identity Verification dialog box and enter the obtained verification code. Then, click OK.

   Two-factor authentication improves the security of your account. For details about how to enable operation protection, see Identity and Access Management User Guide.

7. Refresh the DB instance list later to check that the deletion is successful.