This topic describes the billing rules for the dedicated proxy feature of ApsaraDB RDS for MySQL.
Overview of a dedicated proxy
A dedicated proxy serves as the network proxy between a database and an application. The dedicated proxy is used to distribute all read and write requests from the application to the database. If you have a large number of read and write requests, we recommend that you use the read/write splitting feature of a dedicated proxy to forward read and write requests to the primary and read-only instances. This way, the number of requests sent to the primary instance is reduced. For more information about how to enable the read/write splitting feature, see Enable and configure the dedicated proxy feature for an ApsaraDB RDS for MySQL instance.
Precautions
- Proxy instances, read-only RDS instances, and primary RDS instances are separately billed.
- If the primary RDS instance is released, the enabled proxy instances are automatically released. You are no longer charged for the dedicated proxy feature.
Billing
- To view the details about the enabling operation, perform the following operations: Log on to the ActionTrail console, go to the Event Detail Query page, and then find the event whose Resource Type is ACS::RDS::DbProxy. The details include the time when the feature is enabled, the user who enables the feature, and the IP address of the user.
- For more information about how to disable the dedicated proxy feature, see Disable the dedicated proxy feature for an ApsaraDB RDS for MySQL instance.
Billing methods
By default, the dedicated proxy feature is disabled, and no fees are generated. If you enable the dedicated proxy feature, you are charged an hourly fee for the feature based on the pay-as-you-go billing method. Fees are deducted from your account every hour. To check the bills of the dedicated proxy feature, find the billing item whose Billing Item Code is MaxscaleChargedSliceNum on the Details tab.
Pricing
Region | Price | |
---|---|---|
Name | Code | USD/hour/proxy |
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 |
India (Mumbai) | ap-south-1 | 0.231 |
Singapore (Singapore) | ap-southeast-1 | 0.271 |
Australia (Sydney) | ap-southeast-2 | 0.273 |
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 |