Elastic bean stalk environment is not getting created

0

I am facing an issue while creating an Elastic bean stalk environment. Here basically I am trying to launch a basic python application using elastic beanstalk.

Elastic beanstalk log details

Elastic beanstalk event details

Can anyone please help me out, how to overcome this issue.

Anil
已提問 1 年前檢視次數 6687 次
4 個答案
2

Hi, I added these roles AWSElasticBeanstalkWebTier, AWSElasticBeanstalkWorkerTier, AWSElasticBeanstalkMulticontainerDocker still I am getting the same error. Can anyone please help?

已回答 10 個月前
1
已接受的答案

Hi,

The event log suggests that the aws-elasticbeanstalk-ec2-role does not exist, although AWS should create it when you launch an environment using the Elastic Beanstalk console or the EB CLI. Can you verify that it is so in the IAM console? It seems that some users are experiencing this problem with the new console, but also with the CLI when your IAM user hasn't permissions to create roles

If so, create it yourself, attach AWSElasticBeanstalkWebTier, AWSElasticBeanstalkWorkerTier, AWSElasticBeanstalkMulticontainerDocker policies to it, and specify Amazon EC2 as a trusted entity in the trust relationship policy.

profile picture
專家
已回答 1 年前
profile picture
專家
已審閱 1 年前
  • Thanks a lot Mikel, It worked!!

  • I found the reason, AWS is creating role with name 'aws-elasticbeanstalk-service-role' during Launch of new environment which is not as 'aws-elasticbeanstalk-ec2-role'. After creating manually role with name 'aws-elasticbeanstalk-ec2-role' it works.

0

I found this by way of Reddit and StackOverflow, hopefully it helps you and/or someone else.

Steps to manually create an instance profile:

search for "IAM" Users>Add users>username>set permissions select Attach policies directly and add these 4 permissions (AdministratorAccess, AWSElasticBeanstalkMulticontainerDocker, AWSElasticBeanstalkWebTier, AWSElasticBeanstalkWorkerTier) [create a Role]

Roles>create role>{entity type: AWS service, use case: EC2>permissions:same as above} [link Role to the User using the user ARN we just created]

Select Role>Trust relationships>Edit trust policy>Add a principal - {principal type: IAM Roles, ARN: user arn}>Update Policy [Create a new environment]

Service access - (use an existing service role - {existing service role: Role_created, EC2 instance profile: Role_created})

已回答 8 個月前
0

An easier approach is to manually create an Elastic Beanstalk environment manually in the AWS console. I chose a "Ruby" sample application named "roles", and it will create the roles you need. Just delete the environment once it is finished creating.

I do not know why eb create does not do this, as it should.

已回答 6 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南