2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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 :-)
répondu il y a un mois
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?
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 ans