--- title: "Change Auto Scaling settings" slug: "db-clouddbserverless-scaling" updated: 2026-10-08T07:09:14Z published: 2026-10-08T07:09:14Z canonical: "guide.ncloud-docs.com/db-clouddbserverless-scaling" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Change Auto Scaling settings Available in VPC You can easily change the Auto Scaling settings configured during the DB cluster creation process. You can also designate static replicas for each zone, which remain active regardless of workload. Changes to the autoscaling settings and static replica settings take effect immediately and do not require a restart. Note - By default, DB management features are available when the DB instance status is **Running**. - The available menus for DB management features differ depending on the DB cluster and DB instance. To change Auto Scaling settings in the DB management menu: 1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Database** > **Cloud DB Serverless**. 2. Click the **DB Cluster** menu. 3. In the DB cluster list, click the DB cluster you want to change, and then click **[DB Management]**. 4. In the **Auto Scaling settings** menu, change the required options. - Auto Scaling settings: Specify whether to enable the feature that automatically adjusts the number of replicas. - Average CPU usage: Enter a value between 30% and 99%. - Average number of connections: Enter a value between 500 and 30,000. - Replica increase setting: Enter a value between 1 and 15. - Static Replica settings: Number of static replicas for each zone that are maintained regardless of workload. - It is created in the specified zone and excluded from Auto Scaling adjustments. Units: The same DB cluster settings are applied to all units. - Can be configured regardless of whether Auto Scaling is enabled. 5. Change the setting and click **[Save]**. Caution - If the number of static replicas is reduced, instances in the corresponding zone are deleted starting with the most recently created instance, and any connected sessions are disconnected. - You cannot disable the Multi-Zone setting if a static replica exists in a different zone from the primary. - Static replicas are excluded from promotion candidates during failover. Note When Auto Scaling is disabled, the number of replicas in the current DB cluster remains unchanged. Note Average CPU usage is calculated based on current CPU usage compared to the CPU corresponding to the set maximum unit. Note You can configure up to 15 replicas in total, including 1 default replica, static replicas, and the maximum number of Auto Scaling replicas.