---
Title: Integrate services
URL Source: https://company-skill.com/p/ess/ess-integrate-services
Language: en
Description: You want to connect your Auto Scaling scaling groups to external Alibaba Cloud services like Classic Load Balancer (CLB), Application/NLB server groups, or ApsaraDB RDS instances, either during…
---

# Integrate services

Part of **Auto Scaling (ESS)**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to connect your Auto Scaling **scaling groups** to external Alibaba Cloud services like **Classic Load Balancer (CLB)**, Application/NLB **server groups**, or **ApsaraDB RDS instances**, either during initial setup, at runtime, or to fix integration failures.

- Can Auto Scaling work with RDS?

## Decision Tree

Pick the best path for your situation:

- **If** you are performing **initial configuration** of a scaling group and using standard Alibaba Cloud services like **Classic Load Balancer (CLB)** or **ApsaraDB RDS instances** → Use SLB// (go to *ess/ess-instance*)
- **If** you need to **dynamically attach or detach** external resources **during runtime** (e.g., in CI/CD or multi-environment deployments) using **API operations** → Use API (go to *ess/ess-instance*)
- **If** your integration is already configured but you observe issues like **health check fails**, **404 error**, or **permission denied** when accessing **SLB backend server group** or **RDS** → Use SLB/RDS (go to *ess/ess-instance*)
- **Otherwise (default)** → Start with **SLB//** — it’s the safest for first-time users and covers basic integration via guided UI.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| SLB// | low | No | No | Only supports binding during scaling group creation/modification; no runtime changes | `ess/guide/ess-instance` |
| API | medium | Yes | Yes | Uses **ForceAttach parameter** to override conflicts during dynamic attachment | `ess/api/ess-instance` |
| SLB/RDS | medium | No | No | Requires checking **ess:DescribeScalingInstances** and **ess:SetInstancesProtection** status | `ess/troubleshooting/ess-instance` |

## Path Details

### Path 1: SLB//

**Brief Description**: This path uses the Auto Scaling console to perform actions like **Associate CLB Instance**, **Associate ALB and NLB Server Groups**, **Attach RDS Instances**, **Associate ApsaraDB RDS Instance**, and **Disassociate from SLB and RDS**. It guides users through linking **scaling groups** to external services with visual workflows, ensuring region and VPC alignment.

**Key technical facts**:  
*(All fields omitted as fact_card contains only prerequisites/limitations, no runtime/billing data)*

**When to Use**:
- Auto Scaling

### Path 2: API

**Brief Description**: This approach uses **API operations** such as `AttachDBInstances` and `DetachDBInstances` to manage dependencies between **scaling groups** and **ApsaraDB RDS instances** programmatically. It supports the **ForceAttach parameter** to resolve **parameter conflict** scenarios during dynamic attachment.

**Key technical facts**:  
*(All fields omitted as fact_card contains only prerequisites/limitations, no runtime/billing data)*

**When to Use**:
- CI/CDAuto Scaling

### Path 3: SLB/RDS

**Brief Description**: This path focuses on diagnosing integration failures using ESS APIs like **ess:DescribeScalingInstances**, **ess:SetInstancesProtection**, **ess:EnterStandby**, **ess:ExitStandby**, and **ess:RemoveInstances**. It addresses issues such as instances not joining the **SLB backend server group**, **health check fails**, or **404 error** during association.

**Key technical facts**:  
*(All fields omitted as fact_card contains no runtime/billing data)*

**When to Use**:
- Auto Scaling
- permission denied

## FAQ

Q: Which path should I start with?
A: If you’re setting up integration for the first time and don’t need runtime changes, start with **SLB//**. It ensures correct region/VPC alignment and walks you through **Associate CLB Instance** and **Attach RDS Instances** safely.

Q: What if my **private IP address whitelist** is full but I used the console path?
A: You’ll hit a failure during scaling because new instances can’t be added to the RDS whitelist. The console doesn’t auto-expand whitelist capacity — you must manually free slots before scaling.

Q: If I need to dynamically switch RDS instances across environments but chose the console path, what happens?
A: You’ll be unable to update bindings without recreating or modifying the scaling group manually each time — defeating automation. The console path **does not support runtime adjustments**, so CI/CD pipelines will break.

Q: Can I use the troubleshooting path to set up integration for the first time?
A: No. The troubleshooting path assumes integration is already configured. Using it for initial setup will leave your **scaling groups** unconnected to **SLB backend server group** or **ApsaraDB RDS instances**.

Q: Why do I get a **404 error** when associating SLB even after correct setup?
A: This often occurs if the **Classic Load Balancer (CLB)** and scaling group are in different regions or VPCs — a prerequisite enforced by the console but easily missed in API usage. Verify alignment before retrying.

Q: Does the API path handle **parameter conflict** automatically?
A: No — you must explicitly use the **ForceAttach parameter** to override conflicts (e.g., duplicate instance IDs). Without it, the API call fails silently or returns an error.

Q: What if **health check fails** on new instances added to SLB?
A: This is a symptom addressed by the troubleshooting path. Causes include missing security group rules, incorrect listener configuration, or delayed RDS whitelist sync — all requiring diagnostic steps using **ess:DescribeScalingInstances**.

Q: 如果我需要在多环境部署中自动化管理外部服务绑定，但选择了控制台路径（SLB//），会发生什么？
A: 控制台路径不支持自动化脚本或程序化方式管理绑定关系，因此你的CI/CD流程将无法自动更新SLB或RDS绑定，导致部署失败或配置不一致。

Q: 如果我要求运行时动态挂载或解绑外部资源，但选择了控制台路径（SLB//），会怎样？
A: 控制台路径仅支持在伸缩组创建时或修改时绑定外部服务，无法在运行时动态调整。你将无法实现动态挂载需求，必须手动干预。

Q: 如果我已有CI/CD流程需要程序化集成，但选择了控制台路径（SLB//），结果如何？
A: 控制台路径不支持程序化集成，你的CI/CD流程将无法自动完成绑定操作，破坏自动化部署流程。

## Related queries

integrate auto scaling with slb, bind slb to scaling group, attach rds to ess, associate clb instance, link rds with auto scaling, connect ess to database, how to integrate ess with external services, can auto scaling work with rds, why scaling group not attaching to slb, slb backend server group no

---
Part of [Auto Scaling (ESS)](https://company-skill.com/p/ess.md) · https://company-skill.com/llms.txt