- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
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
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.
Contenuto pertinente
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa