Starting October 17, 2023, each ApsaraDB RDS for MySQL instance on RDS Cluster Edition includes one dedicated database proxy at no charge.
In this topic, "dedicated database proxy" refers to one proxy enabled on a proxy instance with 2 CPU cores. Proxy specifications scale with the number of proxies: Specifications = 2 CPU cores × number of proxies. For example, three proxies give you 6 CPU cores (2 × 3 = 6).
Effective date
October 17, 2023
Application scope
To qualify for the free dedicated database proxy, your RDS instance must meet all of the following requirements:
Runs RDS Cluster Edition
To upgrade from RDS High-availability Edition, see Upgrade the RDS edition from RDS High-availability Edition to RDS Cluster Edition. To upgrade from RDS Basic Edition, see Upgrade the RDS edition from RDS Basic Edition to RDS Cluster Edition.
Runs MySQL 5.7 or MySQL 8.0
Resides in a zone other than Hangzhou Zone C or Hangzhou Zone D
If your instance is in an unsupported zone, migrate it to a supported zone first, then enable the dedicated proxy feature. For instructions, see Migrate an ApsaraDB RDS for MySQL instance across zones.
Billing
| Scenario | Charge |
|---|---|
| 1 proxy enabled | Free |
| More than 1 proxy enabled | First proxy is free; the rest are charged at the standard rate |
Example: If you enable four proxies, you are charged for three.
For full pricing details, see Billing rules for dedicated database proxies.
If you enable the dedicated database proxy feature for your RDS instance that runs RDS Cluster Edition, you can use one enabled database proxy free of charge from October 17, 2023.
How database proxy works
The dedicated database proxy sits between your application and the database. All application requests go through the proxy, which routes them to the appropriate node.
On RDS Cluster Edition, the proxy implements read/write splitting across the primary and secondary nodes. Connect through the read-only endpoint to reach secondary nodes directly, or use the dedicated proxy feature for more advanced capabilities:
| Capability | Description |
|---|---|
| Read/write splitting | Routes read and write traffic to the appropriate nodes automatically |
| Connection pooling | Reuses database connections to reduce overhead from frequent opens and closes |
| Latency threshold | Routes read requests away from secondary nodes that are lagging behind the primary |
| Transaction splitting | Routes individual statements within a transaction to the optimal node |
For more information, see Database proxies. To enable the feature, see Enable the dedicated proxy feature.
What's next
New instances: Create an RDS Cluster Edition instance on the ApsaraDB RDS buy page. For instructions, see Create an ApsaraDB RDS for MySQL instance.
Existing instances on RDS Basic Edition or RDS High-availability Edition: Upgrade the RDS edition to RDS Cluster Edition. For Basic Edition instances, see Upgrade the RDS edition from RDS Basic Edition to RDS Cluster Edition. For High-availability Edition instances, see Upgrade the RDS edition from RDS High-availability Edition to RDS Cluster Edition.
Before creating a new instance or upgrading, review the Application scope to confirm your instance qualifies.