# Amazon EC2 Auto Scaling

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling

> Amazon EC2 Auto Scaling is a service that automatically adjusts the number of Amazon EC2 instances in your deployment to maintain performance and minimize costs based on defined conditions such as traffic or resource utilization.

Practice exams covering Amazon EC2 Auto Scaling: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [MLA-C02 AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 10 key features of Amazon EC2 Auto Scaling

Amazon EC2 Auto Scaling dynamically adjusts the number of Amazon EC2 instances in your application to maintain performance and efficiently manage costs by automatically launching or terminating instances based on predefined policies, health status checks, and schedules.

1. **Dynamic Scaling**: Automatically adjusts the number of instances in your application to match demand, maintaining performance and minimizing cost.
2. **Scheduled Scaling**: Allows you to scale your application ahead of known usage patterns by scheduling exactly when and how to scale your application.
3. **Health Checks**: Uses EC2 health checks to monitor instance health and availability and replace terminated or impaired instances to maintain desired capacity. You can also define application-specific custom health checks; instances that fail them are automatically replaced.
4. **Integration with AWS Services**: Seamlessly integrates with other AWS services like Amazon EC2, Amazon CloudWatch, and Elastic Load Balancing for comprehensive cloud resource management.
5. **Predictive Scaling**: Uses machine learning algorithms to automatically predict future traffic patterns and schedule the right number of EC2 instances in advance.
6. **Cost Management**: Optimizes costs through instance rebalancing and offers the possibility to use Spot Instances and Reserved Instances within the auto-scaling groups.
7. **Lifecycle Hooks**: Allows you to perform custom actions by pausing instances as an Auto Scaling group launches or terminates them, giving you greater control over your EC2 instances.
8. **Multiple Scaling Strategies**: Supports multiple scaling strategies such as target tracking scaling, step scaling, and simple scaling policies to fit different use cases.
9. **Availability Zone Balancing**: When you specify multiple Availability Zones for a group, Amazon EC2 Auto Scaling balances instances evenly across those zones as the group scales, improving resilience to failures in a single location.
10. **Spot Capacity Rebalancing**: Capacity Rebalancing monitors Spot Instances for elevated interruption risk and can proactively replace them before interruption.

## Where Amazon EC2 Auto Scaling is used

Amazon EC2 Auto Scaling is used to ensure application availability and optimize resource utilization by automatically adjusting the number of EC2 instances in response to demand, for workloads ranging from dynamic web applications to batch processing and container management.

1. **High Availability and Fault Tolerance**: Amazon EC2 Auto Scaling uses EC2 health checks to monitor instance health and availability and replaces terminated or impaired instances to maintain desired capacity. Application-specific health checks can also be defined to verify that the application responds as expected; instances that fail these custom checks are automatically replaced.
2. **Cost Optimization**: By automatically adjusting the number of Amazon EC2 instances in response to the demand, EC2 Auto Scaling can help reduce costs during off-peak times by terminating instances that are not needed and launching instances during peak times to handle the load. This ensures that you're only paying for the resources you actually need.
3. **Dynamic Scaling for Microservices**: EC2 Auto Scaling can be configured to dynamically scale the resources for microservices architecture based applications. As microservices have varying load patterns and require different resources, EC2 Auto Scaling can adjust the capacity of each service independently, ensuring optimal performance and resource utilization.
4. **Batch Processing Workloads**: For batch processing jobs that require significant computational power for short durations, EC2 Auto Scaling can rapidly provision the necessary resources to complete the job efficiently and terminate them once the job is done. This use case is ideal for data processing, rendering, or any task that requires heavy computational resources intermittently.
5. **Scheduled Scaling for Predictable Workloads**: For workloads with predictable patterns, such as higher usage during business hours and lower usage at night, EC2 Auto Scaling can schedule scaling actions to automatically adjust capacity in anticipation of the changes in demand. This ensures that the application can handle the user load without manual intervention.

## How Amazon EC2 Auto Scaling is priced

Amazon EC2 Auto Scaling is priced based on the underlying EC2 instances or other resources used, without additional charges specifically for the Auto Scaling service itself.

- **On-Demand Instances**: Pay for the compute capacity by the hour or by the second depending on the instances you run with no long-term commitments or upfront payments. This model gives you flexibility to increase or reduce compute capacity on demand and only pay for what you use.
- **Reserved Instances**: Purchase EC2 instances for a one-year or three-year term, and receive a significant discount compared to On-Demand instance pricing. This option is ideal for applications with steady state or predictable usage, offering budget predictability and lower costs in exchange for committing to use EC2 over a longer period.
- **Spot Instances**: Use unused EC2 capacity at a potentially lower price than On-Demand rates. Spot Instances can significantly lower your computing costs for time-flexible and interruption-tolerant applications but can be stopped by EC2 with little notice if the Spot price exceeds an optional maximum price you specify or if capacity is unavailable.
- **Savings Plans**: Commit to a consistent amount of usage (e.g., $10/hour) for a 1-year or 3-year term and receive a lower price compared to On-Demand pricing. Savings Plans offer the flexibility to use the compute option that best suits your needs and still benefit from savings.
- **Dedicated Hosts**: Pay for a physical EC2 server dedicated for your use, which can help you reduce costs by allowing you to use your existing server-bound software licenses. This model offers visibility and control over where your instances run and is useful for regulatory requirements that require physical isolation.
- **No Additional Auto Scaling Fees**: Amazon EC2 Auto Scaling has no additional fees beyond the charges for Amazon EC2, CloudWatch used for scaling policies, and other AWS resources you use.

## Services Amazon EC2 Auto Scaling works with

- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Provides monitoring for AWS cloud resources and applications, enabling Auto Scaling to dynamically adjust capacity based on predefined thresholds or alarms.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: Amazon EC2 Auto Scaling groups are supported resources for DevOps Guru analysis. DevOps Guru analyzes their operational metrics and related events to identify anomalous behavior and provide recommendations.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon EC2 Auto Scaling launches and terminates EC2 instances using launch templates, scaling policies, scheduled actions, and health checks. Groups can combine instance types and purchase options, use Capacity Reservations, and proactively replace at-risk Spot Instances.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: Amazon EC2 Auto Scaling uses the block device mappings in its launch template to create and attach EBS volumes when instances launch. Those mappings also control whether volumes are deleted when Auto Scaling terminates an instance.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: Amazon EC2 Auto Scaling groups provide EC2 capacity for ECS clusters through Auto Scaling group capacity providers. ECS managed scaling adjusts group capacity to accommodate tasks, while managed termination protection helps prevent instances with running tasks from being terminated prematurely.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Amazon EC2 Auto Scaling groups supply worker nodes for EKS managed node groups and can also support self-managed nodes. EKS manages the underlying groups for managed node groups, and Kubernetes Cluster Autoscaler can adjust group capacity when pods need more or fewer nodes.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Amazon EC2 Auto Scaling sends instance lifecycle, scaling activity, instance refresh, and other events to EventBridge. Rules can route these events to automation or notification targets, such as invoking a function when an instance enters a lifecycle-hook wait state.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: Amazon EC2 Auto Scaling groups provide the instances behind GameLift FleetIQ game server groups. FleetIQ manages the underlying group to balance game-server availability and cost, including replacing Spot capacity that becomes unsuitable for game hosting.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: Amazon EC2 Auto Scaling can publish notifications about instance launches, terminations, and related failures to SNS topics. Lifecycle hooks can also send notifications to SNS so subscribers can perform initialization or cleanup before the lifecycle action completes.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: Amazon EC2 Auto Scaling lifecycle hooks can send messages to SQS queues for workers to process before an instance finishes launching or terminating. Worker groups can also scale using a CloudWatch metric that expresses SQS backlog per instance.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon EC2 Auto Scaling launches instances into the VPC subnets selected for a group and applies the security groups specified by its launch template. It can also register and deregister instances with VPC Lattice target groups and use their health checks to identify unhealthy instances.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: Amazon EC2 Auto Scaling groups can be managed through AWS Auto Scaling scaling plans. These plans configure scaling behavior for EC2 groups alongside other supported scalable resources.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Amazon EC2 Auto Scaling groups, scaling policies, scheduled actions, lifecycle hooks, launch configurations, and warm pools can be provisioned with CloudFormation. Stack update policies can coordinate rolling instance replacements when a group's configuration changes.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Amazon EC2 Auto Scaling API activity is recorded by CloudTrail, including changes to groups, scaling policies, and lifecycle hooks. These records help audit who changed desired capacity or modified a group's configuration.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: Amazon EC2 Auto Scaling groups can be associated with CodeDeploy deployment groups. CodeDeploy uses lifecycle hooks to deploy an application revision to newly launched instances before they enter service and can coordinate termination deployments for instances being removed.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: Amazon EC2 Auto Scaling groups receive instance-type recommendations from Compute Optimizer based on their configuration and utilization. These recommendations help identify opportunities to reduce cost or improve performance by changing the instances used by a group.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: Amazon EC2 Auto Scaling group configurations can be recorded and evaluated by AWS Config. Managed rules check settings such as load balancer health checks, multi-Availability Zone placement, and the use of launch templates.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: Amazon EC2 Auto Scaling manages the instance capacity of load-balanced Elastic Beanstalk environments. Elastic Beanstalk configures the group and scaling policies and uses it when performing operations such as rolling or immutable deployments.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: Amazon EC2 Auto Scaling groups can be targeted by Fault Injection Service experiments that simulate instance-launch capacity failures. These experiments test whether scaling and recovery mechanisms behave correctly when requested capacity is unavailable.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon EC2 Auto Scaling uses IAM permissions to control access to its resources and service-linked roles to manage instances and related resources. Lifecycle hooks use service roles when publishing to SNS or SQS, and launch templates can assign IAM instance profiles to launched instances.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon EC2 Auto Scaling can launch instances with EBS volumes encrypted using customer managed KMS keys. The keys must authorize the Auto Scaling service-linked role, with additional grants required for supported cross-account configurations.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Amazon EC2 Auto Scaling supports Lambda functions as custom termination policies to select which instances a group should terminate. Lambda functions can also process lifecycle events delivered through EventBridge, perform initialization or cleanup, and complete the lifecycle action.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: Amazon EC2 Auto Scaling can launch instances from launch templates associated with License Manager self-managed licenses. License Manager tracks license consumption and can enforce configured license limits as the group adds instances.
- **[AWS Local Zones](https://blowstack.com/tools/cloud-services-hub/aws-local-zones)**: Amazon EC2 Auto Scaling can launch instances into subnets in Local Zones. This allows supported workloads to maintain and scale compute capacity close to users while retaining Auto Scaling health checks and replacement behavior.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: Amazon EC2 Auto Scaling groups can be provisioned and maintained through AMS operational automation and change workflows. AMS supports managed changes to group configuration and capacity as part of operating customer infrastructure.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: Amazon EC2 Auto Scaling launch templates can reference subscribed AWS Marketplace AMIs, allowing groups to launch instances with licensed third-party software. Marketplace products delivered through CloudFormation can also provision Auto Scaling groups as part of their deployment.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: Amazon EC2 Auto Scaling can manage instances launched into Outpost subnets. Groups maintain desired capacity and replace unhealthy instances, subject to the instance types and physical capacity available on the Outpost.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon EC2 Auto Scaling supports interface VPC endpoints through PrivateLink. Applications and automation can access its API privately from a VPC without requiring an internet gateway or NAT device.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: Amazon EC2 Auto Scaling groups can be included in Resilience Hub application assessments. Resilience Hub evaluates their configuration and dependencies to identify recovery risks and recommend improvements to application resilience.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: Amazon EC2 Auto Scaling groups can be discovered and organized in tag-based resource groups. This lets operators collect related groups with the other resources belonging to an application or environment.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Amazon EC2 Auto Scaling configurations are evaluated by Security Hub security controls. Findings can identify issues such as groups spanning too few Availability Zones, missing load balancer health checks, or insecure instance launch settings.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: Amazon EC2 Auto Scaling groups can be provisioned as resources in CloudFormation-backed Service Catalog products. Administrators can offer approved scalable application deployments with standardized launch templates, capacity settings, and update procedures.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Amazon EC2 Auto Scaling API operations are available through Step Functions AWS SDK service integrations. Workflows can coordinate actions such as changing desired capacity, starting an instance refresh, or completing a lifecycle action without a separate Lambda function.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Amazon EC2 Auto Scaling lifecycle hooks can be combined with Systems Manager Automation to configure instances before they enter service or perform work before termination. Systems Manager also provides automation for operational tasks involving Auto Scaling groups, including patching their instances.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: Amazon EC2 Auto Scaling groups are inspected by Trusted Advisor checks for issues such as unavailable launch resources and missing load balancer health checks. These checks help identify configurations that could prevent a group from maintaining healthy capacity.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: Amazon EC2 Auto Scaling events can be selected in AWS User Notifications notification configurations. Operators can receive notifications about matching scaling and lifecycle events through configured delivery channels.
- **[AWS Wavelength](https://blowstack.com/tools/cloud-services-hub/aws-wavelength)**: Amazon EC2 Auto Scaling can launch supported instances into subnets in Wavelength Zones. Groups can maintain and adjust capacity for applications deployed at the telecommunications edge.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: Amazon EC2 Auto Scaling groups can use launch templates that Image Builder updates with newly built AMIs through its distribution settings. Groups configured to use the updated launch template version use the new image for subsequent launches; an instance refresh can replace existing instances.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: Amazon EC2 Auto Scaling automatically registers launched instances with attached load balancers or target groups and deregisters terminating instances. Groups can use load balancer health checks to replace unhealthy instances and Application Load Balancer request counts for target tracking scaling.

## What is Amazon EC2 Auto Scaling

Amazon EC2 Auto Scaling is a cloud computing service that automatically adjusts the number of Amazon Elastic Compute Cloud (EC2) instances in your cloud environment. This service is designed to ensure that your application has the right amount of compute capacity to handle the demand at any given time. Its primary goal is to maintain application availability and allow users to scale their Amazon EC2 capacity up or down automatically according to conditions defined by the user.

At its core, Amazon EC2 Auto Scaling helps in enhancing the reliability, availability, and cost-efficiency of applications running on the Amazon Web Services (AWS) infrastructure. It does this by dynamically adjusting the number of EC2 instances in response to real-time demand, mitigating the need for manual intervention. This means that it can automatically launch additional instances when demand spikes to maintain performance and shut down instances during demand dips to reduce costs. The process begins by setting up Auto Scaling groups, which are collections of EC2 instances treated as a logical unit for the purposes of scaling and management. When creating an Auto Scaling group, you specify the minimum and maximum number of instances, desired capacity, and other parameters related to how the group should scale. Within these parameters, you can define scaling policies based on a variety of metrics such as average CPU utilization, network traffic, or even based on custom metrics specific to your application.

A single Auto Scaling group can combine multiple instance types and both Spot and On-Demand Instances. Reserved Instance and Savings Plans discounts can apply to On-Demand Instances in the group.

One of the critical advantages of using Amazon EC2 Auto Scaling is its tight integration with other AWS services such as Amazon CloudWatch for monitoring, AWS Lambda for serverless computing, and Elastic Load Balancing (ELB) for distributing incoming traffic across the instances. This integration allows for a more robust and flexible management system that can automatically respond to changes in traffic by adjusting the capacity, thereby ensuring that your application remains responsive at all times.

Additionally, Amazon EC2 Auto Scaling supports launch configurations and launch templates that define the instance type, AMI (Amazon Machine Image), and other configurations. This means you can automatically start new instances with the desired setup without manual intervention, ensuring that new instances are configured identically to existing ones. It plays a crucial role in disaster recovery by maintaining application availability through the automatic replacement of instances that may fail, become unhealthy, or otherwise become unavailable.

AWS recommends using EC2 launch templates rather than launch configurations because launch templates offer more features.

In summary, Amazon EC2 Auto Scaling is a critical service for businesses and developers that require their applications to be highly available and performant without the overhead of managing and adjusting compute capacity manually. By automating the scaling process based on real-time metrics, it not only optimizes costs but also ensures that applications can handle varying load conditions without human intervention, contributing to smoother operations and a better end-user experience.

Amazon EC2 Auto Scaling uses token-bucket API throttling with a shared API bucket, so calls to operations such as DescribeAutoScalingGroups and DescribeScheduledActions consume the same pool of tokens. Requests that exceed the service's requests-per-second limit are rejected with a RateExceeded error.

## Concepts related to Amazon EC2 Auto Scaling

- [Elasticity](https://blowstack.com/tools/cloud-concepts-hub/elasticity): Elasticity is the ability to increase and decrease computing resources to match changes in workload demand.
- [High availability](https://blowstack.com/tools/cloud-concepts-hub/high-availability): High availability is the design and operation of a system to remain accessible and usable despite component failures or maintenance.
- [Horizontal Scaling](https://blowstack.com/tools/cloud-concepts-hub/horizontal-scaling): Horizontal scaling adjusts capacity by adding or removing servers, containers, or other processing units that share a workload.
- [Fault Tolerance](https://blowstack.com/tools/cloud-concepts-hub/fault-tolerance): Fault tolerance is the ability of a system to continue performing its intended function when one or more components fail.
- [Resource Utilization](https://blowstack.com/tools/cloud-concepts-hub/resource-utilization): Resource utilization is the amount or proportion of available computing capacity that a workload uses over a given period.
- [Health Checks](https://blowstack.com/tools/cloud-concepts-hub/health-checks): Health checks are automated tests that determine whether a component is functioning and suitable for receiving work.
- [Load Balancing](https://blowstack.com/tools/cloud-concepts-hub/load-balancing): Load balancing distributes incoming requests or network connections across multiple targets to improve availability and use capacity efficiently.
- [Immutable Infrastructure](https://blowstack.com/tools/cloud-concepts-hub/immutable-infrastructure): Immutable infrastructure is an operating model in which deployed compute resources are replaced with newly built, versioned resources rather than modified in place.
- [Rolling Deployment](https://blowstack.com/tools/cloud-concepts-hub/rolling-deployment): Rolling deployment updates an application in successive batches while keeping part of the existing deployment available to serve traffic.
- [Fault Isolation](https://blowstack.com/tools/cloud-concepts-hub/fault-isolation): Fault isolation is the design principle of containing failures within defined boundaries so they do not disrupt otherwise healthy parts of a system.
- [Capacity Planning](https://blowstack.com/tools/cloud-concepts-hub/capacity-planning): Capacity planning is the process of estimating workload demand and arranging sufficient resources to meet performance, growth, and resilience requirements within cost constraints.
- [Connection Draining](https://blowstack.com/tools/cloud-concepts-hub/connection-draining): Connection draining is the controlled removal of a backend from new traffic while allowing existing requests or connections time to finish.
- [Failover](https://blowstack.com/tools/cloud-concepts-hub/failover): Failover is the transfer of traffic or processing from a failed or unhealthy resource to a healthy alternative so a service can continue operating.
- [Load Testing](https://blowstack.com/tools/cloud-concepts-hub/load-testing): Load testing evaluates how a system performs under a defined workload to verify capacity, response times, reliability, and scaling behavior.
- [Right-Sizing](https://blowstack.com/tools/cloud-concepts-hub/right-sizing): Right-sizing is matching cloud resource types, configurations, and capacity to workload requirements without unnecessary cost or unacceptable performance risk.
- [Service Level Objectives](https://blowstack.com/tools/cloud-concepts-hub/service-level-objectives): Service level objectives are measurable targets for the reliability and performance of a service over a defined evaluation period.
- [Active-Active Architecture](https://blowstack.com/tools/cloud-concepts-hub/active-active-architecture): Active-active architecture runs multiple production environments simultaneously, distributing live traffic across them so healthy environments can continue serving users when another fails.
- [Amazon EC2 instance types](https://blowstack.com/tools/cloud-concepts-hub/amazon-ec2-instance-types): Amazon EC2 instance types are predefined virtual machine hardware configurations that determine the compute, memory, storage, networking, and accelerator resources available to a workload.
- [Benefits of migrating to the AWS Cloud](https://blowstack.com/tools/cloud-concepts-hub/benefits-of-migrating-to-the-aws-cloud): Benefits of migrating to the AWS Cloud are the operational, financial, and business advantages of using on-demand cloud resources instead of owning and managing all underlying infrastructure.
- [Composite Availability](https://blowstack.com/tools/cloud-concepts-hub/composite-availability): Composite availability is the end-to-end availability of a system determined by its required dependencies, redundant components, and failure relationships.
- [Multi-Tier Architecture](https://blowstack.com/tools/cloud-concepts-hub/multi-tier-architecture): Multi-tier architecture separates an application into independently deployed tiers with distinct responsibilities and controlled network communication.
- [Resiliency](https://blowstack.com/tools/cloud-concepts-hub/resiliency): Resiliency is a system’s ability to withstand disruptions and recover while continuing to meet defined business requirements.
- [Resource Efficiency](https://blowstack.com/tools/cloud-concepts-hub/resource-efficiency): Resource efficiency is the practice of meeting workload requirements with the least necessary compute, storage, networking, and energy consumption.
- [Rightsizing](https://blowstack.com/tools/cloud-concepts-hub/rightsizing): Rightsizing is matching the type, size, and quantity of cloud resources to workload requirements while meeting performance and availability targets at an appropriate cost.
- [Warm Standby](https://blowstack.com/tools/cloud-concepts-hub/warm-standby): Warm standby is a disaster recovery strategy that keeps a scaled-down, functional copy of a production environment running in a separate recovery location.
- [Workload Predictability](https://blowstack.com/tools/cloud-concepts-hub/workload-predictability): Workload predictability is the degree to which an application's future resource demand, usage duration, and operating schedule can be anticipated.

## Amazon EC2 Auto Scaling exam questions

Real practice exam questions on Amazon EC2 Auto Scaling, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A retailer has configured automatic scaling for an Amazon EC2 Auto Scaling group. After a promotional event, a manager wants evidence that compute capacity increased as demand rose and decreased after demand fell. The group's instance-count metrics are enabled. Which approach best demonstrates this behavior without changing the scaling configuration?

**Correct answer:** Use an Amazon CloudWatch dashboard to compare application request volume with the group's in-service instance count throughout the promotion and afterward.

**Explanation:** CloudWatch can display demand metrics alongside Auto Scaling group instance-count metrics over time. This comparison provides evidence that capacity increased during high demand and was released when demand fell, demonstrating elasticity.

### Question 2 (MLA-C02)

**Question:**

A company runs a custom ML inference service on an Amazon EC2 Auto Scaling group. Target tracking adjusts the number of serving instances as traffic changes. Preparing a newly launched instance takes 12 minutes because it must download and validate model artifacts on its encrypted Amazon EBS root volume. Once the artifacts are on disk, starting the instance and loading the model into memory takes 45 seconds.

Unpredictable traffic increases require up to four additional serving instances within 90 seconds. These increases are sufficiently far apart to replenish a reserve of four prepared instances. The company must retain target tracking and minimize EC2 compute charges for reserve capacity while it is idle. The application does not need to preserve in-memory state.

Which solution best meets these requirements?

**Correct answer:** Configure a warm pool that maintains four prepared instances in the Stopped state. Use lifecycle hooks to complete artifact download and validation before instances enter the pool, and verify model readiness before they begin serving traffic.

**Explanation:** A stopped warm pool preserves the prepared EBS volumes without incurring EC2 instance compute charges while the instances are stopped. Instances can start and load the cached model in 45 seconds, meeting the 90-second requirement. Lifecycle hooks coordinate preparation and readiness with the Auto Scaling lifecycle. EBS storage charges still apply.

### Question 3 (SAP-C03)

**Question:**

A company runs a latency-sensitive application in an Amazon EC2 Auto Scaling group. The group has two step scaling policies invoked by Amazon CloudWatch alarms. One policy uses average CPU utilization. The other uses a custom ActiveRequestsPerInstance metric. Both metrics are valid indicators of application load.

Before deploying the configuration, a solutions architect reviews two independent test cases:

• Scale-out test: The desired capacity is 20 instances. Both policies act simultaneously. The CPU policy requests an increase of 6 instances, and the custom-metric policy requests an increase of 10 instances.
• Scale-in test: The desired capacity is reset to 20 instances. Both policies act simultaneously. The CPU policy requests a decrease of 6 instances, and the custom-metric policy requests a decrease of 2 instances.

All instances have equal capacity. Both policies are eligible to act, no instances are warming up, and group capacity limits do not constrain either test. No other scaling actions occur.

The company wants to retain both metric-based responses with the least custom operational logic. Which implementation and expected desired capacities are correct?

**Correct answer:** Keep both policies attached to the group and let EC2 Auto Scaling resolve simultaneous actions. Expect 30 instances after the scale-out decision and 18 instances after the scale-in decision.

**Explanation:** EC2 Auto Scaling supports multiple dynamic scaling policies and chooses the policy that provides the largest resulting capacity when policies act simultaneously. The scale-out candidates are 26 and 30, so it chooses 30. The scale-in candidates are 14 and 18, so it chooses 18. Native arbitration requires no custom coordination.

### Question 4 (SOA-C03)

**Question:**

A company replaces application instances in an Amazon EC2 Auto Scaling group by using instance refresh. The group contains 20 instances. A CloudOps engineer has configured a tested replacement AMI, appropriate healthy-capacity limits, and a 60-second instance warmup.

For the next release, replacement must pause for 15 minutes after 25% of the instances have been replaced and again after 50% have been replaced. These pauses allow engineers to inspect application metrics before more instances are replaced. The refresh must automatically resume after each interval unless it has failed or been cancelled. The existing instance warmup must remain unchanged.

Which instance refresh configuration meets these requirements?

**Correct answer:** Set CheckpointPercentages to [25, 50, 100] and CheckpointDelay to 900 seconds. Retain InstanceWarmup at 60 seconds.

**Explanation:** Instance refresh checkpoints pause replacement at specified completion percentages. A 900-second checkpoint delay provides the required 15-minute intervals before replacement continues automatically. Including 100 as the final checkpoint allows the refresh to replace the entire fleet, while instance warmup remains unchanged.

### Question 5 (DOP-C02)

**Question:**

A company runs an Amazon ECS service on EC2 instances supplied by an Auto Scaling group capacity provider. Managed scaling is enabled with a target capacity of 100%. The service uses only this capacity provider. The Auto Scaling group has a desired capacity of 4 and a maximum capacity of 20. Its mixed instances policy allows m5.large instances (2 vCPUs, 8 GiB of memory) and m5.2xlarge instances (8 vCPUs, 32 GiB of memory), without instance weights.

Each task requires 4 vCPUs and 16 GiB of memory. The four existing instances are m5.2xlarge instances and have no remaining capacity for additional tasks. After the service's desired count increases, additional tasks remain in PROVISIONING. The capacity provider's CapacityProviderReservation metric remains at its target, and no scale-out activity occurs. Subnet addresses, service quotas, and instance availability are not limiting factors.

The task resource requirements cannot be reduced. A DevOps engineer must correct the configuration so that managed scaling automatically provisions capacity for these tasks.

Which change meets this requirement?

**Correct answer:** Remove m5.large from the Auto Scaling group's allowed instance types, and ensure that every remaining allowed instance type can accommodate at least one task.

**Explanation:** ECS managed scaling checks whether provisioning tasks can fit on the smallest instance type allowed by the Auto Scaling group. Tasks that cannot fit are excluded from the scale-out calculation and can remain in PROVISIONING without triggering scaling. The m5.large cannot accommodate this task. Allowing only compatible instance types removes this constraint so that managed scaling can provision the required capacity.

### Question 6 (SAA-C03)

**Question:**

A company runs a stateless customer portal on four EC2 instances in an Auto Scaling group. The group has a minimum and desired capacity of four and uses two private subnets. An Application Load Balancer (ALB) is enabled in two Availability Zones and forwards requests to the group's attached target group.

During a resilience review, a solutions architect discovers that both subnets selected for the Auto Scaling group are in the same Availability Zone. A suitable private subnet already exists in the second Availability Zone. Two application instances can handle the portal's full workload, and all application dependencies can tolerate an Availability Zone failure.

The company requires the portal to continue serving its full workload after either Availability Zone fails, without waiting for replacement instances to launch. Which change should the solutions architect make?

**Correct answer:** Update the Auto Scaling group to use one private subnet in each Availability Zone. Keep its minimum and desired capacity at four, and allow the group to rebalance before completing the resilience review.

**Explanation:** An Auto Scaling group distributes instances across its configured Availability Zones. After rebalancing, the group will normally have two instances in each zone. The surviving zone therefore has enough already-running capacity to serve the full workload while Auto Scaling attempts to replace lost instances.

### Question 7 (ANS-C01)

**Question:**

A company runs a stateless API on EC2 instances in an Auto Scaling group across three Availability Zones. An Application Load Balancer (ALB) forwards requests to an instance-type target group attached to the group. The Auto Scaling group uses EC2 and Elastic Load Balancing health checks.

During scale-out, new instances enter the InService state before loading a local dataset. Loading takes 4–6 minutes after entering InService. The application's /ready endpoint returns HTTP 503 until loading completes and HTTP 200 afterward. The target group checks /ready every 15 seconds, accepts only HTTP 200, and has healthy and unhealthy thresholds of two checks. The Auto Scaling group's health check grace period is 60 seconds, and its default instance warmup is 600 seconds. No lifecycle hooks are configured.

New instances are repeatedly replaced before loading finishes. Existing instances remain healthy and provide sufficient capacity throughout scale-out. The company must allow new instances to complete initialization without routing application requests to them prematurely. Failure detection and automatic replacement behavior must remain unchanged for established instances that have been InService for at least 15 minutes. A longer replacement-protection window for newly launched instances is acceptable.

Which change meets these requirements?

**Correct answer:** Increase the Auto Scaling group's health check grace period to 480 seconds. Keep the target group's health check configuration unchanged.

**Explanation:** The grace period prevents Auto Scaling from replacing initializing instances because of failed load balancer health checks. The 480-second period accommodates the maximum six-minute initialization time and subsequent successful checks. The ALB independently withholds traffic from initializing targets while healthy existing targets remain available. Instances that have been InService for at least 15 minutes are outside both the original and revised grace periods, so their failure detection and replacement behavior remains unchanged.

## Practice Amazon EC2 Auto Scaling in a full exam

Questions on Amazon EC2 Auto Scaling in each practice exam, with every answer option and an explanation for each:

- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 46 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 46 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 27 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 16 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 16 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 9 questions
- [MLA-C02](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 5 questions

## Learn Amazon EC2 Auto Scaling in lessons

16 short lessons on Amazon EC2 Auto Scaling in 6 certification courses.

- CLF-C02: Amazon EC2 Auto Scaling: elastic instance capacity (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-elastic-instance-capacity-clf-c02
- MLA-C02: Amazon EC2 Auto Scaling: maintaining efficient fleet capacity (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-maintaining-efficient-fleet-capacity-mla-c02
- SAP-C03: Amazon EC2 Auto Scaling: scheduled capacity changes (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-scheduled-capacity-changes-sap-c03
- SOA-C03: Amazon EC2 Auto Scaling vs. AWS Auto Scaling (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-vs-aws-auto-scaling-soa-c03
- DOP-C02: Amazon EC2 Auto Scaling: scaling policy behavior (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-scaling-policy-behavior-dop-c02
- SAA-C03: Amazon EC2 Auto Scaling: capacity scaling policies (Premium), https://app.blowstack.com/lessons/amazon-ec2-auto-scaling-capacity-scaling-policies-saa-c03
