Elastic Beanstalk with Loadbalancer - No Data from Instance for new Environments

Question

Hello,
we have multiple environments with the same configuration: Application Loadbalancer with min 1 / max 1  t2 instance, to assign SSL certificates. Loadbalancer in subnet a and b, instance in subnet b. I created some in the past, the last 1 month ago. And all work fine.
But now when i create a new one with default settings and example application, it wont work with the loadbalancer. I tried a few times with PHP 8.1 and Node 18, configuration is the same as the current working environments.
Elastic Beanstalk gets Status No Data, cannot communicate with the instance. The EC2 instances get no IPV4-DNS, in the past every instance automatically got the IP. Dont know if it is the only problem here.
If i switch to single instance, everything works. Has something changed with the loadbalancers? Are there default security groups that i have to use to get it work?

Thanks in advance.

Best Regards,
Andreas

Answer

It seems that we got it.
With Loadbalancer it needs the option "public ip address". That was not neccessary on older applications with PHP <= PHP 8.0 and NodeJS 14.

Answer

Hello.

Does this mean that deploying more than 2 EC2s will cause an error?  
Also, are "enableDnsHostnames" and "enableDnsSupport" set to "True" in the VPC you are using?  
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-support

By the way, if you want to change the security group, you can follow the procedure in the following document.  
https://repost.aws/knowledge-center/elastic-beanstalk-add-security-group  
https://repost.aws/knowledge-center/security-group-elastic-beanstalk

Answer

Hello,
no, the problem is with 1 EC2 instance via Loadbalancer.
The VPC DNS Settings are set, thats why earlier environments worked / still working. There was no changes on our side.
Regards,
Andreas

Elastic Beanstalk with Loadbalancer - No Data from Instance for new Environments

Relevant content