Updated on 2023-09-12 GMT+08:00

Billed Items

Description

You will be billed for the instance class, storage space, and backup space. For details, see Table 1.

The billed items marked with asterisks (*) are mandatory.

Table 1 DB instance billed items

Billed Item

Description

Billing Mode

Formula

* Instance class

Billed by vCPUs, memory, and instance type. Computing and storage capabilities vary by the number of vCPUs and memory size.

Yearly/Monthly and pay-per-use

Unit price x Required duration

For details about the unit price, see the price of each DB engine in RDS Pricing Details.

* Storage space

Billed based on unified standards.

Yearly/Monthly and pay-per-use

Unit price x Storage capacity x Required duration

For details about the unit price, see the storage price in RDS Pricing Details.

* Backup space

Billed based on unified standards.

Pay-per-use

Unit price x Billed backup capacity x Billed duration

For details about the unit price, see the backup space price in RDS Pricing Details.

NOTE:

The billed duration refers to the length of time the billed backup space was used for.

* Images (for RDS for SQL Server only)

Billed based on unified standards.

Yearly/Monthly and pay-per-use

Unit price x Required duration

(Optional) Cross-region backup

Billed by storage space based on unified standards.

Pay-per-use

Unit price x Storage capacity x Required duration

Unit price of storage space: $0.0002 USD/GB/hour

(Optional) EIP bandwidth

An EIP is required if the DB instance needs to access the Internet.

Billed by bandwidth, traffic, and the EIP reservation price.

  • EIP for a yearly/monthly DB instance: billed by bandwidth.
  • EIP for a pay-per-use DB instance: billed by bandwidth, traffic, or shared bandwidth. You are also charged for IP reservation if you do not bind the EIP to any instance.

Yearly/Monthly and pay-per-use

You can purchase a bandwidth add-on package or a shared traffic package.

Billed by fixed bandwidth

For details about the unit price, see EIP Pricing Details.

(Optional) Monitoring by Seconds (for RDS for MySQL only)

Billed based on unified standards.

Pay-per-use

Unit price x Billed duration

For details about the unit price of Monitoring by Seconds, see Configuring Monitoring by Seconds.

NOTE:

Billed duration: indicates the usage duration of Monitoring by Seconds (1s or 5s).

(Optional) Database proxies (for RDS for MySQL only)

Billed by the proxy instance class (vCPUs and memory) and nodes

Yearly/Monthly and pay-per-use

Unit price x Required duration x Number of proxy nodes

For details about the unit price, see Database Proxy Billing.

(Optional) Deployment in DCC

Billed by storage space based on unified standards.

Yearly/Monthly and pay-per-use

Unit price x Storage capacity x Required duration

For details about the unit price of storage space, see "MySQL Deployed in a DCC" in RDS Pricing Details.

Billing Examples

Suppose you purchased a one-month RDS for MySQL primary/standby DB instance (instance class: general-purpose 2 vCPUs | 4 GB; storage: cloud SSD 40 GB; backup space: 50 GB (40 GB for free); bandwidth: 6 Mbit/s; one-second monitoring) on March 08, 2023, 15:50:04, and renewed the subscription for one more month before the initial subscription expired. That would include two usage periods:

  • Billed usage period 1: March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59
  • Billed usage period 2: April 08, 2023, 23:59:59 to May 08, 2023, 23:59:59
    • From April 08, 2023, 23:59:59 to May 01, 2023, 23:59:59, 20 GB of free backup space was used.
    • From May 01, 2023, 23:59:59 to May 08, 2023, 23:59:59, another 10 GB of backup space was used, which was billed for 168 hours.
    • Monitoring by Seconds was enabled at 23:59:59 on May 04, 2023. Fees were generated from 23:59:59 on May 04, 2023 to 23:59:59 on May 08, 2023 (96 hours).

Figure 1 shows how the total price is calculated.

The prices in the figure are only for reference. For details, see RDS Pricing Details.

Figure 1 Total price for a yearly/monthly DB instance (taking RDS for MySQL as an example)

For more billing examples of a pay-per-use DB instance, see Billing Examples.