Auto Scaling Event Delivery Pipeline

Scenario

Developers need this pipeline when deploying stateless application tiers requiring dynamic capacity adjustments via Auto Scaling (ESS) while maintaining strict observability. By integrating ESS with SLB and RDS, and routing scaling lifecycle events through EventBridge (EB), teams can trigger external monitoring webhooks, archive audit logs in OSS, or push real-time alerts to MQTT brokers without custom polling scripts.

Integration steps

1. Bind SLB & RDS to Scaling Group: Use CreateScalingGroup with LoadBalancerIds and DBInstanceIds to attach infrastructure during initial configuration.

aliyun ess CreateScalingGroup --ScalingGroupName "app-tier" --VpcId "vpc-xxx" --LoadBalancerIds '["lb-xxx"]' --DBInstanceIds '["rm-xxx"]'

2. Define Scaling Triggers: Create CreateScalingRule and attach to CloudMonitor via CreateAlarmTask to automate capacity changes.
3. Provision EventBridge Bus: Isolate scaling telemetry with CreateEventBus --EventBusName "ess-scaling-events".
4. Capture ESS Events: Use PutRule with an event pattern filtering scaling outcomes:

{"source":["acs.ess"],"detail-type":["Scaling Activity Status Change"],"detail":{"ScalingActivityStatus":["Success","Failed"]}}

5. Configure API Destination: Route to external monitoring using Bearer Token auth:

aliyun eventbridge CreateApiDestination --Name "monitor-webhook" --Endpoint "https://api.monitor.io/hooks" --AuthParameters '{"Type":"BearerToken","BearerTokenParameters":{"Token":"${API_KEY}"}}'

6. Add OSS & MQTT Targets: Attach Target configurations to the rule pointing to acs:oss:::audit-bucket and acs:mqtt:::broker-id.
7. Validate Pipeline: Execute ExecuteScalingRule and verify delivery via EB console metrics or DescribeEventBus.

Architecture

ESS manages instance lifecycle, automatically registering ECS nodes with the SLB server group and updating RDS whitelists. ESS emits structured lifecycle events to the Alibaba Cloud event bus. EventBridge intercepts these events using pattern-matching rules, applies optional transformations, and reliably routes payloads to configured targets: HTTP API Destinations for real-time monitoring, OSS for immutable audit logs, and MQTT brokers for edge alerting. EB handles retries, dead-letter queues, and authentication, fully decoupling scaling logic from downstream consumers.

Prerequisites

• Active VPC, CLB/NLB instance, and ApsaraDB RDS in the same region
• RAM role with AliyunESSFullAccess and AliyunEventBridgeFullAccess
• Valid API endpoint, OSS bucket with write permissions, and MQTT broker credentials
• CloudMonitor alarm rules configured to trigger scaling activities

Common pitfalls

• IAM Permission Gaps: EB requires AliyunEventBridgeRole to write to OSS or invoke API Destinations; missing sts:AssumeRole causes silent delivery failures.
• Event Pattern Mismatch: Omitting detail-type or detail.ScalingActivityStatus in PutRule drops events.
• Network Isolation: API Destinations and MQTT brokers must be publicly accessible or linked via PrivateLink; outbound HTTPS blocks break delivery.
• Token Expiry: Hardcoded Bearer tokens in ApiDestination expire without rotation, causing 401 errors.
• Attachment Limits: Exceeding CLB backend server limits or RDS IP whitelist capacity during rapid scale-out triggers ESS failures logged as Failed events.

Typical questions

• send scaling events to external API
• ESS events to OSS
• auto scaling event notification EventBridge
• monitor scaling activities externally
• ESS EventBridge integration
• scaling event delivery pipeline
• 把伸缩事件发送到外部API
• 弹性伸缩事件投递到OSS

Q: How do I deliver Auto Scaling events to external destinations using EventBridge? A: EventBridge captures scaling activity events and delivers them to external monitoring APIs, an OSS bucket for audit logging, or an MQTT broker for real-time alerting. This configuration combines Auto Scaling integration with external services and EventBridge destination delivery to route the events accordingly.