1. Login to AWS Console: Go to https://aws.amazon.com/ and login to your AWS account using your credentials.
2. Navigate to EC2 Dashboard: Once logged in, navigate to the EC2 Dashboard by clicking on the “Services” dropdown menu at the top of the page and selecting “EC2” under the Compute section.
3. Select Load Balancers: In the EC2 Dashboard, under the “Load Balancing” section in the navigation pane on the left, click on “Load Balancers”.
4. Identify the Classic Load Balancer: Find the Classic Load Balancer that is configured with multiple Availability Zones.
5. Edit Load Balancer: Select the Classic Load Balancer by clicking on its name, and then click on the “Listeners” tab.
6. Edit Listener Configuration: In the Listeners tab, click on the “Edit” button to edit the listener configuration.
7. Edit Availability Zones: In the Edit Listener Configuration window, you will see the option to select the Availability Zones for the load balancer. Deselect the additional Availability Zones that you want to remove from the configuration.
8. Save Changes: After deselecting the additional Availability Zones, click on the “Save” button to apply the changes.
9. Verify Configuration: Once the changes are saved, verify that the Classic Load Balancer is now configured to use only the desired Availability Zones.

​

1. List the Availability Zones associated with the Classic Load Balancer:

aws elb describe-load-balancers --load-balancer-name <your-load-balancer-name> --query 'LoadBalancerDescriptions[*].AvailabilityZones'

2. Identify the extra/unwanted Availability Zones that need to be removed from the Classic Load Balancer configuration.
3. Deregister the instances from the extra/unwanted Availability Zones:

aws elb deregister-instances-from-load-balancer --load-balancer-name <your-load-balancer-name> --instances <instance-id-1> <instance-id-2> ...

4. Disable the extra/unwanted Availability Zones from the Classic Load Balancer:

aws elb disable-availability-zones-for-load-balancer --load-balancer-name <your-load-balancer-name> --availability-zones <unwanted-az-1> <unwanted-az-2> ...

5. Verify the updated configuration of the Classic Load Balancer to ensure that it is now configured with the desired number of Availability Zones:

aws elb describe-load-balancers --load-balancer-name <your-load-balancer-name> --query 'LoadBalancerDescriptions[*].AvailabilityZones'

1. Identify the Load Balancer: First, you need to identify the Classic Load Balancer that is configured with multiple availability zones.
2. Update Load Balancer Configuration: You will need to update the Load Balancer configuration to ensure that it is only associated with a single availability zone.
3. Use Boto3 Library: Boto3 is the AWS SDK for Python, which allows you to interact with AWS services using Python. You can use Boto3 to make API calls to AWS Elastic Load Balancer service.
4. Install Boto3: If you haven’t already installed Boto3, you can do so using pip:
   pip install boto3
   
5. Write Python Script: Here is an example Python script that uses Boto3 to update the availability zones for a Classic Load Balancer:
   import boto3
   
   elb_client = boto3.client('elb')
   
   # Specify the name of the Classic Load Balancer
   load_balancer_name = 'your-load-balancer-name'
   
   # Specify the availability zones that you want the Load Balancer to be associated with
   availability_zones = ['us-west-1a']
   
   elb_client.enable_availability_zones_for_load_balancer(
       LoadBalancerName=load_balancer_name,
       AvailabilityZones=availability_zones
   )
   
6. Run the Script: Save the script in a file, for example, update_elb_availability_zones.py, and run it using Python:
   python update_elb_availability_zones.py
   
7. Verify Configuration: After running the script, verify that the Classic Load Balancer is now associated with only the specified availability zone.

# Classic Load Balancer in a VPC: add a subnet from a new AZ
resource "aws_elb" "CLASSIC_LB_VPC" {
  name = "CLASSIC_LB_NAME" # replace with the load balancer's name

  # Include ALL required subnets here, including at least one in a new AZ
  # Each subnet must be in the same VPC and a distinct Availability Zone
  subnets = [
    "EXISTING_SUBNET_ID_1", # replace with an existing subnet ID
    "EXISTING_SUBNET_ID_2", # replace with an existing subnet ID
    "NEW_SUBNET_ID_IN_NEW_AZ", # replace with a subnet ID in an AZ not yet used by this ELB
  ]

  security_groups = [
    "SECURITY_GROUP_ID", # replace with appropriate security group ID(s)
  ]

  listener {
    instance_port     = 80
    instance_protocol = "http"
    lb_port           = 80
    lb_protocol       = "http"
  }

  # Other arguments as needed (health_check, cross_zone_load_balancing, etc.)
}

# Classic Load Balancer in EC2-Classic: add a new Availability Zone
resource "aws_elb" "CLASSIC_LB_EC2_CLASSIC" {
  name = "CLASSIC_LB_NAME" # replace with the load balancer's name

  # Include ALL required AZs here, including the new one
  availability_zones = [
    "EXISTING_AZ_1",      # e.g. "us-east-1a"
    "EXISTING_AZ_2",      # e.g. "us-east-1b"
    "NEW_AVAILABILITY_ZONE", # e.g. "us-east-1c", not already associated
  ]

  listener {
    instance_port     = 80
    instance_protocol = "http"
    lb_port           = 80
    lb_protocol       = "http"
  }

  # Other arguments as needed
}

• CLASSIC_LB_VPC / CLASSIC_LB_EC2_CLASSIC with your Terraform resource names.
• CLASSIC_LB_NAME with the existing Classic Load Balancer name.
• EXISTING_SUBNET_ID_* with the current subnet IDs shown by aws elb describe-load-balancers.
• NEW_SUBNET_ID_IN_NEW_AZ with a subnet in the same VPC, in an Availability Zone not already used, and with sufficient free IPs.
• EXISTING_AZ_* with current availability zones.
• NEW_AVAILABILITY_ZONE with an additional AZ in the same region that is not already enabled.
• SECURITY_GROUP_ID with appropriate security group IDs.

• For the VPC ELB: an in-place update on aws_elb.CLASSIC_LB_VPC with subnets gaining NEW_SUBNET_ID_IN_NEW_AZ.
• For the EC2-Classic ELB: an in-place update on aws_elb.CLASSIC_LB_EC2_CLASSIC with availability_zones gaining NEW_AVAILABILITY_ZONE.