Elastic beanstalk error with IPV6

Question

Due to the new IPV4 cost, I was trying to move our EB environment to IPV6, but it seems either the IPV6 are not supported on Elastic beanstalk or am I missing something?

1. I created a new subnet with IPV6 only
2. Launched the env with those subnets
3. The EB failed launched the instances but can't communicate and the env failed to launch

If this is not supported, any ETA?

Since this costs now, the Elastic beanstalk launched instances with IPv4 should be discounted I guess, as the customers are forced to pay for something which even doesn't exists in AWS to fix on EB. So, no way to manage the cost until IPV6 are supported in EB.

https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

Answer

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:
1. ipv4
2. 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

Answer

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)

```

Elastic beanstalk error with IPV6

Contenido relevante