# Ensure EC2 Auto Scaling Group Uses MultipEnsure EC2 Auto Scaling Group Uses Multiple Availability Zonesle Availability Zones

- Source: https://support.icompaas.com/support/solutions/articles/62000233479-ensure-ec2-auto-scaling-group-uses-multipensure-ec2-auto-scaling-group-uses-multiple-availability-zon
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability**

-   **Level 2**

#### **Description**

Configuring your EC2 Auto Scaling Group to span multiple Availability Zones ensures high availability and fault tolerance. By distributing resources across multiple AZs, you minimize the risk of disruption caused by zone-specific outages. This configuration is critical for maintaining application resilience and improving overall system reliability.

#### **Rationale**

-   Improved Fault Tolerance: Spreads resources across multiple AZs, reducing the risk of downtime due to Regional disruptions.
    
-   Enhanced Availability: Ensures instances are launched in healthy and available AZs during scaling operations.
    
-   Compliance: Aligns with best practices for highly available cloud architectures.
    

#### **Impact**

**Pros:**

-   Provides a robust and highly available environment for your workloads.
    
-   Balances load efficiently across AZs, improving performance.
    
-   Reduces the single point of failure associated with using only one AZ.
    

**Cons:**

-   May increase network latency if AZs are not geographically close.
    
-   Slightly more complex to configure and manage compared to single AZ setups.
    

#### **Default Value**

By default, an Auto Scaling Group may be created with only one Availability Zone unless additional subnets spanning multiple AZs are explicitly configured.

#### **Pre-Requisite**

IAM Permissions Required:

-   autoscaling:CreateAutoScalingGroup
    
-   autoscaling:UpdateAutoScalingGroup
    
-   autoscaling:DescribeAutoScalingGroups
    
-   AWS CLI installed and configured.
    

#### **Remediation**

#### **Test Plan:**

**Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to EC2 > Auto Scaling Groups.
    
3.  Select your Auto Scaling Group and view its Details.
    
4.  Verify that the Availability Zones or Subnets span multiple zones within the Region.
    

**Using AWS CLI:**

1.  Describe the Auto Scaling Group:  
    
    aws autoscaling describe-auto-scaling-groups --auto-scaling-group-names <asg-name>
    
2.  Check the AvailabilityZones field in the output for multiple AZs.
    

### **Implementation Steps:**

**Using AWS Console:**

1.  Navigate to EC2 > Auto Scaling Groups.  
    ![](https://support.icompaas.com/assets/kb/8845a64a746c45d4.png) ![](https://support.icompaas.com/assets/kb/e3ff77fe00ed00a3.png)  
    
2.  Select the Auto Scaling Group to edit.  
    ![](https://support.icompaas.com/assets/kb/07d96d8f560c5362.png) 
    
3.  Click Edit and update the Network section:
    
    -   Add subnets from multiple Availability Zones within the same Region.
        
    -   Ensure load balancers (if used) are configured across these AZs.![](https://support.icompaas.com/assets/kb/e8cb39149182711f.png)
        
4.  Save the updated configuration.
    

**Using AWS CLI:**

1.  Update the Auto Scaling Group to span multiple AZs:  
    
    aws autoscaling update-auto-scaling-group \\
    --auto-scaling-group-name <asg-name> \\
    --vpc-zone-identifier "<subnet-id-1>,<subnet-id-2>,<subnet-id-3>"
    

2.  Verify the updated configuration:  
    
    aws autoscaling describe-auto-scaling-groups --auto-scaling-group-names <asg-name>
    

#### **Backout Plan**

#### **Using AWS Console:**

1.  #### If using multiple Availability Zones causes issues, sign in to the AWS Management Console.
    
2.  #### Navigate to EC2, then to Auto Scaling Groups.![](https://support.icompaas.com/assets/kb/2403fef773cab760.png)   
    ![](https://support.icompaas.com/assets/kb/d649c84db6e5c747.png)  
    
3.  #### Select the Auto Scaling Group and go to the Network section.  
    ![](https://support.icompaas.com/assets/kb/6f0deae316056a24.png) 
    
4.  #### Change the Availability Zones to a single Availability Zone if necessary.
    
    #### ![](https://support.icompaas.com/assets/kb/cf7bfe1f7cb8c280.png)
    
5.  #### Save the changes and verify that the Auto Scaling Group is now using a single AZ.
    

#### **Using AWS CLI:**

1.  #### To revert to a single Availability Zone, run:  
    
    aws autoscaling update-auto-scaling-group --auto-scaling-group-name <ASG\_NAME> --availability-zones <SINGLE\_AZ>
    
2.  #### Verify that the Auto Scaling Group is now using only a single Availability Zone:  
    
    aws autoscaling describe-auto-scaling-groups --auto-scaling-group-name <ASG\_NAME>
    

#### **References**

-   [AWS Auto Scaling Documentation](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html)
    
-   [Configuring Availability Zones for Auto Scaling Groups](https://docs.aws.amazon.com/autoscaling/ec2/userguide/auto-scaling-basics.html#as-basic-network)
    
-   [Best Practices for Resilient Architectures in AWS](https://docs.aws.amazon.com/wellarchitected/latest/framework/operational-excellence.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.