- Newest
- Most votes
- Most comments
It seems the issue is that the load balancer is not able to select subnets across two different Availability Zones as required.
Please check the following:
- Verify that the VPC has at least two public subnets, each located in a different Availability Zone.
- When creating the load balancer, select one public subnet from Availability Zone 1 and one from Availability Zone 2.
- Ensure the security groups allow access on the listener port and health check port from the load balancer to the target instances.
- Check that no network ACLs are blocking necessary traffic to/from the load balancer subnets
1-VPC has 2 different AZs 2-Load Balancer is created in 2 different AZs (us-west-2b & 2a) 3-I'm launching my application with EB CLI, thus it's creating the Load Balancer itself; I'm only providing it with the subnets' IDs. 4-Checked the ACL associated with the VPC and it has Outbound rule and Inbound rules allowing from-to the internet
You'll first need to create two or more subnets in your VPC. It's typically good practice to create at least one subnet for each availability zone (AZ) in your region. Be sure to select public/private as is appropriate for your architecture.
I can't differentiate between vpc.elb and vpc.ec2; do I need two different VPCs for the creation of EBS ?
Relevant content
- asked 7 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 months ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago
Are those subnets created in different AZs or its the same AZ? Can you verify that?
@Aanchal Agrawal : in different AZ