Starting August 17, 2023, the maximum number of dedicated proxies that you can enable for an ApsaraDB RDS for MySQL instance or an ApsaraDB RDS for PostgreSQL instance is adjusted. After the adjustment, up to 16 dedicated proxies can be enabled for an RDS instance.
Description
Starting August 17, 2023, the number of dedicated proxies that you can enable for your RDS instance is adjusted based on the status of the dedicated proxy feature on the RDS instance.
If the dedicated proxy feature is disabled for the RDS instance, you can enable 1 to 16 dedicated proxies for the RDS instance when you enable the feature for the first time.
If the dedicated proxy feature is enabled for your RDS instance, the number of dedicated proxies that you can enable for the RDS instance is adjusted based on the following rules:
If the number of the enabled dedicated proxies is greater than 16, you can continue to use the dedicated proxy feature without the need to change the number. You cannot increase the number. However, you can reduce the number to 16 or less.
If the number of the enabled dedicated proxies is less than or equal to 16, you can continue to use the dedicated proxy feature without the need to change the number. You can adjust the number within the range of 1 to 16.
Effective date
August 17, 2023
Usage notes
If you want to call the ModifyDBProxy operation to enable the dedicated proxy feature for an RDS instance, you must set DBProxyInstanceNum to a value that ranges from 1 to 16. If the value is not within the range, you cannot enable the dedicated proxy feature for the RDS instance.
If you want to call the ModifyDBProxyInstance operation to change the number of dedicated proxies that are enabled for an RDS instance, you must set DBProxyInstanceNum to a value that ranges from 1 to 16. If the value is not within the range, you cannot change the number of dedicated proxies for the RDS instance.