- Newest
- Most votes
- Most comments
From the Elastic beanstalk architecture, a key component is the Elastic Load balancer [1]. As of today you can configure your Application Load Balancer so that clients can communicate with the load balancer using IPv4 addresses only, or using both IPv4 and IPv6 addresses (dualstack) [2]. These are the two supported IP address types:
- ipv4
- dualstack
As such an IPv6 addresses only is not supported due to the Elastic Load balancer's limitation. However, Deploying the EC2 instance in private subnet and the ELB in public subnet will reduce the number of public IP addresses provisioned.
References:
[1] Elastic beanstalk architecture: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts-webserver.html
[2] Elastic Load balancer IP address type limitation: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-ip-address-type.html
Also see elb-configure-with-ipv6.
I selected "Crate new dedicated ELB" while creating the EB environment, it didn't worked either. It seems that the elastic beanstalk is creating a load balancer, and have some validation which fails due to the subnets I have selected are IPV6 only.
Creating load balancer failed Reason: Resource handler returned message: "Not enough IP space available in subnet-026c00273a8af5ec3. ELB requires at least 8 free IP addresses in each subnet. (Service: ElasticLoadBalancingV2, Status Code: 400, Request ID: 3610e1a7-eef2-47bb-bfb9-67e759e41512)" (RequestToken: 2d40c9e9-bd5c-4186-5a29-72b9a19287fa, HandlerErrorCode: InvalidRequest)
Relevant content
- asked 8 months ago
- asked 2 years ago
- asked 3 months ago
- asked a month ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
At the moment, Elastic Beanstalk is not in the list of AWS services that support IPv6, although EC2 and Elastic Load Balancing are.