2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Thank you, I solved it, I guess the issue was related with permissions policies: I deleted the environment, created a new one and when I chose the ec2 instance profile, this time I created a new set of policies according the suggestion pointed there in the form in a pop-up window. Now on the public URL the site I'm trying to deploy I get "502 Bad Gateway, nginx" but that's a different story :-)
con risposta 2 mesi fa
0
Hello.
Is the security group created in the same VPC that you selected when you created your ElasticBeanstalk environment?
Also, will the EC2 I'm trying to launch with ElasticBeanstalk be launched in the same VPC as the security group?
Contenuto pertinente
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata 4 anni fa
- AWS UFFICIALEAggiornata 2 anni fa