ApsaraDB RDS for MySQL provides two types of database proxies: general-purpose and dedicated. General-purpose database proxies are free. Dedicated database proxies are billed on a pay-as-you-go basis, charged per proxy per hour.
Proxy types and pricing at a glance
| Proxy type | Billing | Notes |
|---|---|---|
| General-purpose | Free | — |
| Dedicated | Pay-as-you-go (per proxy-hour) | RDS Cluster Edition includes one proxy free |
Billing rules for dedicated database proxies
Dedicated database proxies use pay-as-you-go billing. Fees are deducted once per hour. By enabling dedicated database proxies in the ApsaraDB RDS console, you acknowledge and agree to the billing rules.
To view charges, go to the Bill Details page and find the billable item whose Billing Item Code is MaxscaleChargedSliceNum.
RDS Cluster Edition
Starting October 17, 2023, one dedicated database proxy (2 CPU cores) is included free of charge for each RDS Cluster Edition instance.
| Scenario | What you pay |
|---|---|
| One dedicated database proxy (2 CPU cores) enabled | Free |
| More than one dedicated database proxy enabled | Pay-as-you-go for all proxies except the first one (2 CPU cores) |
Example: If you enable four dedicated database proxies, you are charged for three.
In this context, one dedicated database proxy equals one proxy with a specification of 2 CPU cores. The total specification equals the unit specification (2 CPU cores) multiplied by the number of proxies. For example, three proxies have a combined specification of 6 CPU cores (2 × 3 = 6).
Proxy node specifications:
The specification of a database proxy equals the sum of the specifications of all its proxy nodes. For example, if two proxy nodes in Zone A each have 1 CPU core and two proxy nodes in Zone B each have 2 CPU cores, the total specification is 6 CPU cores (1 × 2 + 2 × 2 = 6). The number of proxy nodes equals the total specification divided by the unit specification (2 CPU cores): for a 6-CPU-core proxy, that is 3 nodes (6 ÷ 2 = 3).
For more information about the free proxy offer, see [Special offers/Price changes] One dedicated proxy is provided free of charge for ApsaraDB RDS for MySQL instances on RDS Cluster Edition.
RDS High-availability Edition
Dedicated database proxies are disabled by default and generate no charges until enabled. Once enabled, all dedicated database proxies are billed on a pay-as-you-go basis, with fees deducted once per hour.
Example: If you enable four dedicated database proxies, you are charged for all four.
If you upgrade from a shared database proxy to a dedicated database proxy, the dedicated database proxy is free for at least one year. For details, see Upgrade a shared database proxy to a dedicated database proxy. You cannot directly upgrade a shared database proxy to a general-purpose database proxy. To change the proxy type from dedicated to general-purpose after upgrading from a shared proxy, see Modify database proxy configurations and Database proxy typesBilling Details.
Prices
| Region | Price (USD/proxy-hour) | |
|---|---|---|
| Name | Code | |
| China (Hangzhou) | cn-hangzhou | 0.173 |
| China (Shanghai) | cn-shanghai | 0.173 |
| China (Qingdao) | cn-qingdao | 0.173 |
| China (Beijing) | cn-beijing | 0.173 |
| China (Zhangjiakou) | cn-zhangjiakou | 0.120 |
| China (Hohhot) | cn-huhehaote | 0.173 |
| China (Shenzhen) | cn-shenzhen | 0.173 |
| China (Heyuan) | cn-heyuan | 0.173 |
| China (Chengdu) | cn-chengdu | 0.173 |
| China (Hong Kong) | cn-hongkong | 0.297 |
| Japan (Tokyo) | ap-northeast-1 | 0.288 |
| Singapore | ap-southeast-1 | 0.271 |
| Malaysia (Kuala Lumpur) | ap-southeast-3 | 0.253 |
| Indonesia (Jakarta) | ap-southeast-5 | 0.271 |
| Germany (Frankfurt) | eu-central-1 | 0.243 |
| UK (London) | eu-west-1 | 0.280 |
| UAE (Dubai) | me-east-1 | 0.377 |
| US (Virginia) | us-east-1 | 0.237 |
| US (Silicon Valley) | us-west-1 | 0.284 |
Usage notes
-
Dedicated database proxies, read-only instances, and primary RDS instances are billed independently.
-
When a primary RDS instance is released, its database proxies are automatically released and billing stops.
-
To disable database proxies before releasing an instance, see Disable the database proxy feature.
-
To audit proxy activity, log on to the ActionTrail console, go to the Advanced Event Query page, and search for events whose Resource Type is acs::rds::dbproxy. The results include the time the proxy was enabled, the operator, and their IP address.