Auto Scaling
Auto Scaling
AWS Auto Scaling API auto-adjusts EC2 instance count to match load — scaling policies, health checks, lifecycle hooks, multi-AZ distribution.
Native integration with ELB/CloudWatch
Scale-out has cold-start latency (instance launch + warm-up)
CreateLaunchTemplate for the instance template; CreateAutoScalingGroup for the ASG; PutScalingPolicy for scaling rules.
Uptime · 30-day window
GitHub activity
About this API
EC2 Auto Scaling is one of AWS's early core services, letting you "define min/max instance count, scale by which metrics". Most common pattern: target tracking — "keep average CPU utilization at 50%", and AWS auto-calculates required instances. Also step scaling (tiered scaling by metric thresholds) and scheduled scaling (pre-emptive scaling before known peaks). Lifecycle hooks are advanced — insert custom logic on instance launch/terminate (e.g. wait for app warm-up, persist cache). Auto Scaling Group must span multiple AZs for true HA. Forms the AWS auto-scaling trio with ELB (traffic distribution) and CloudWatch (monitoring). In container era, partially replaced by ECS Service / EKS HPA, but underneath still uses ASG.
What you can build
- 1Auto-scale up at peak traffic, scale down at off-peak
- 2Auto-replace failed EC2 instances
- 3Rolling deployments (update some instances first, then continue)
- 4Cost optimization (auto scale to minimum at night)
Strengths & limitations
Strengths
- Native integration with ELB/CloudWatch
- Multiple scaling policies (target tracking, step, scheduled)
- Multi-AZ distribution for HA
Limitations
- Scale-out has cold-start latency (instance launch + warm-up)
- Spot instance interruptions require application-layer handling
- Less friendly to single-instance long-lived connections (WebSocket)
Example request
curl https://github.com/mermade/aws2openapi/<endpoint>Getting started
CreateLaunchTemplate for the instance template; CreateAutoScalingGroup for the ASG; PutScalingPolicy for scaling rules.
FAQ
ASG vs ECS Service?+
For bare EC2 apps: ASG. For containers: ECS Service / EKS HPA (which may still use ASG underneath, but scheduling is per-container).
Can spot instances be used in ASG?+
Yes, via mixed instances policy. Spot interruptions need idempotent application handling.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST
- SDKs
- python, javascript, go, java, csharp, php, ruby
- Response time
- 28 ms
- Last health check
- 5/12/2026, 7:36:33 AM
More from Amazon Web Services
AWS IAM Access Analyzer API analyzes IAM resource policies for over-privileged access or external access — proactively surfaces security risks.
Amazon Chime SDK API embeds real-time audio/video calling and chat into apps (meetings, messaging, PSTN calls).
Amazon CloudFront is the AWS CDN and edge service — accelerates static and dynamic content delivery, a standard for web performance.
Amazon CloudSearch is AWS's managed search service (gradually superseded by OpenSearch Service).
CloudWatch Application Insights API auto-detects application problems — intelligently identifies anomalies (slow SQL queries, memory leaks), reducing manual alarm configuration.
AWS Cognito Identity Pools API issues temporary AWS credentials to frontend apps — identity federation, guest users, direct AWS resource access.
Amazon Cognito User Pools deliver managed user signup, login, password reset, and MFA for applications.
Amazon Connect Contact Lens API uses AI to analyze Amazon Connect calls in real time — sentiment, keywords, compliance detection, auto-summary.