--- Title: Auto Scaling (ESS) URL Source: https://www.company-skill.com/p/ess Language: en Last-Modified: 2026-06-02T11:27:12.569794+00:00 Description: Auto Scaling (ESS) enables automatic adjustment of computing capacity based on demand. It supports managing scaling groups, ECS/ECI instances, scaling rules, lifecycle hooks, scheduled/event-triggered --- # Auto Scaling (ESS) > Auto Scaling (ESS) enables automatic adjustment of computing capacity based on demand. It supports managing scaling groups, ECS/ECI instances, scaling rules, lifecycle hooks, scheduled/event-triggered tasks, and integration with services like SLB and RDS. Domains include Instance Management (core operations), Network Security (firewall rules), Container Service (DevOps integration), User Management (login issues), Event Notification (alert configuration), and Monitoring (custom metrics). ## Featured GEO article Auto Scaling automatically adjusts the number of ECS instances in a group to match workload demand, scheduled times, or real-time metrics. It manages instance lifecycles, integrates with load balancers and databases, and supports both graphical console workflows and programmatic API operations. ## Key facts - Custom metric integration via the CloudMonitor Java SDK costs ¥0.001 per custom metric data point after 1000 free per month. - Programmatic group creation supports the `create_scaling_group` and `create_scaling_group_with_launch_template` API operations. - Database integration uses `AttachDBInstances` and `DetachDBInstances` with a `ForceAttach parameter` to override attachment conflicts. - The console interface only supports standard system monitoring metrics like CPU utilization and does not support custom business metrics. - RDS instance IP whitelists have limited capacity and must have available space to register scaling group instance IPs. - Classic Load Balancer instances require a pre-configured listener and enabled health check before binding to a scaling group. - Groups support configuration of minimum and maximum instance counts, VPC and vSwitch alignment, billing methods, and lifecycle hooks. ## How to create a scaling group You can provision a scaling group through the Alibaba Cloud Console for guided setup or via API for automated infrastructure workflows. - Choose your deployment path: use the console for interactive configuration or API operations for CI/CD pipelines. - Define core capacity parameters including the minimum number of instances, maximum number of instances, VPC, vSwitch, and billing method. - Select an instance configuration source and attach scaling rules or lifecycle hooks to control instance behavior. - Validate network alignment and submit the configuration to initialize the group and begin capacity management. ## How to configure scaling triggers You define scaling behavior by creating time-based schedules, metric-driven event rules, or custom business logic triggers. - Select a trigger type: scheduled tasks for fixed times, event-triggered tasks for system metrics, or custom metrics for application-specific logic. - For standard system metrics like CPU utilization, use the console to create a scaling rule, scheduled task, or event-triggered task by defining the operation and threshold. - For custom business metrics, integrate the CloudMonitor Java SDK to report application data points that drive event-triggered scaling actions. - Associate the configured rules with your target scaling group and verify that the monitoring metric alignment matches your workload patterns. ## How to manage instances within a group You control the operational state of individual instances by placing them in standby, applying protection, or manually attaching and detaching them. - Access the instance management interface via console or API to view current scaling activities and verify instance health. - Apply instance protection to prevent automatic removal during scale-in events, ensuring critical workloads remain active. - Place instances in standby mode for maintenance or troubleshooting without triggering automatic replacement or capacity adjustments. - Manually attach or detach instances as needed, ensuring they align with the group's network configuration and security requirements before state changes. ## How to integrate with external services You connect scaling groups to load balancers and databases during initial setup or dynamically at runtime using API operations. - For initial configuration, use the console to associate CLB instances, attach ALB and NLB server groups, or link RDS instances through guided workflows. - For runtime changes, call `AttachDBInstances` or `DetachDBInstances` programmatically to update dependencies without recreating the scaling group. - Ensure region and VPC alignment between the scaling group and the target external service before establishing the connection. - Use the `ForceAttach parameter` when dynamic attachment encounters parameter conflicts, and verify that the RDS whitelist has sufficient capacity for new instance IPs. ## Frequently Asked Questions **Q: how do I configure triggers (scheduled or event-based)** A: You configure triggers by creating a scheduled task for fixed times or an event-triggered task for metric-based scaling. Use the console to select the rule type, define the scaling operation, choose monitoring metrics like CPU utilization, and associate the rule with your scaling group. **Q: what's the best way to configure triggers** A: The console path is the best starting point for standard system metrics and scheduled scaling because it requires no code and provides guided validation. If you need custom business metrics, use the CloudMonitor Java SDK integration, and for programmatic or CI/CD workflows, use the API operations. **Q: how do I create an group** A: You create a group by defining instance limits, network settings, and scaling behavior through the Alibaba Cloud Console or by calling the `create_scaling_group` API operation. Configure the minimum and maximum instance counts, VPC, vSwitch, and instance configuration sources before finalizing the setup. **Q: what's the best way to create group** A: The console is the best method for first-time users or single-group deployments due to its guided forms and real-time validation. For automated, multi-environment, or CI/CD workflows, the API path is optimal because it supports infrastructure-as-code and programmatic lifecycle management. **Q: how do I integrate with external services (slb, rds, etc.)** A: You integrate by associating load balancers and attaching databases during group creation or by calling runtime API operations. Use the console to associate CLB instances or attach RDS instances, or use `AttachDBInstances` and `DetachDBInstances` for dynamic, code-driven integration. **Q: what's the best way to integrate with slb** A: The console is the safest and simplest approach for initial configuration, guiding you through CLB and ALB/NLB server group association with visual workflows. If you require runtime adjustments or automated deployments, use the API path to manage bindings programmatically. **Q: how do I manage instances within a group** A: You manage instances by controlling their operational states through the console or API, applying protection, placing them in standby, or manually attaching and detaching them. Monitor scaling activities and verify instance alignment with group configurations before making state changes. **Q: what's the best way to manage group instances** A: The console provides the most intuitive interface for visual state management, troubleshooting, and monitoring scaling activities. For automated instance lifecycle control, health checks, and integration with deployment pipelines, use the API operations to programmatically adjust instance states and protection settings. ## Key terms Scaling group is a logical collection of ECS instances that Auto Scaling manages to maintain a target capacity based on defined rules and triggers. Lifecycle hooks are custom actions that pause instance launch or termination events, allowing external processes to complete before the instance state changes. Event-triggered task is a scaling rule that automatically adds or removes instances when a specified monitoring metric crosses a defined threshold. ForceAttach parameter is an API configuration option that overrides parameter conflicts during dynamic attachment of external services like RDS to a scaling group. ## Sources The authoritative source for all configurations, limits, API operations, and integration workflows is the official Alibaba Cloud Auto Scaling documentation. Auto Scaling (ESS) is available as agent-callable skills via DaaS. Route any question to the best skill with `POST https://www.company-skill.com/api/route` `{"query": "...", "product": "ess"}`. ## What you can do - [Configure triggers](https://www.company-skill.com/p/ess/ess-configure-triggers.md): This skill helps users choose the right path to Configure scaling triggers (scheduled or event-based). Use this skill BEFORE diving into implementation details — it routes you to the appropriate detai - [Create group](https://www.company-skill.com/p/ess/ess-create-group.md): This skill helps users choose the right path to Create an Auto Scaling group. Use this skill BEFORE diving into implementation details — it routes you to the appropriate detail skill based on your sit - [Integrate services](https://www.company-skill.com/p/ess/ess-integrate-services.md): This skill helps users choose the right path to Integrate Auto Scaling with external services (SLB, RDS, etc.). Use this skill BEFORE diving into implementation details — it routes you to the appropri - [Manage instances](https://www.company-skill.com/p/ess/ess-manage-instances.md): This skill helps users choose the right path to Manage instances within a scaling group. Use this skill BEFORE diving into implementation details — it routes you to the appropriate detail skill based ## Frequently asked questions ### Should I use the API or the console for Auto Scaling? Use the **console** for initial setup, visual monitoring, and one-off operations. Use the **API/SDK** for automation, CI/CD integration, or managing multiple environments programmatically. ### How do I authenticate API calls? Provide your AccessKey pair and sign requests using the standard Alibaba Cloud signature method. Never hardcode keys—use environment variables or secure credential managers. ### Why can’t I see my scaling group in the console? Verify you’re in the correct region, have sufficient RAM permissions (e.g., `ess:DescribeScalingGroups`), and that the group wasn’t deleted. Check the **Resource Group** filter if enabled. ### What causes “Insufficient Data” in alarm-triggered scaling? This typically means CloudMonitor hasn’t collected enough metric data yet. Ensure the metric exists, has recent values, and the alarm rule uses a valid comparison operator. ### Can I use Auto Scaling with both ECS and ECI? Yes—scaling configurations support either ECS instances (with launch templates) or ECI containers. Choose during scaling group creation; mixing types in one group is not supported. ### How do I configure scheduled or event-based scaling triggers? You configure scaling triggers by defining when and how scaling occurs based on time or metrics. The documentation provides three alternative paths to set up these scheduled or event-based tasks. ### How do I create an Auto Scaling group? You can create a new scaling group by using either the console or the API. The documentation outlines two alternative paths to guide you through the setup process. ### How do I integrate Auto Scaling with external services like SLB or RDS? You integrate Auto Scaling by connecting your scaling groups to load balancers, databases, and other external services. The documentation provides three alternative paths to configure these integrations. ### How do I manage instances within a scaling group? You manage instances within a scaling group by controlling their states, such as placing them in standby, enabling protection, or manually attaching them. The documentation offers three alternative paths to perform these management tasks. ## Use with an AI agent ```bash curl -s https://www.company-skill.com/api/route \ -H 'Content-Type: application/json' \ -d '{"query": "...", "product": "ess"}' ``` MCP server: https://www.company-skill.com/api/mcp/ess.py --- Machine-readable: https://www.company-skill.com/llms.txt · https://www.company-skill.com/sitemap.xml