Cloud (AWS) Level 3 Task 7: Simplifying Application Deployment with AWS Elastic Beanstalk ERROR BUG

KodeKloud Engineer
,
#1

image
image1583×1010 137 KB

image
image1583×1010 137 KB

Dear Lab Administrator,

I am working on a task to create an Elastic Beanstalk environment for a Python application. However, I’ve encountered significant permission restrictions that are preventing me from completing this task. Specifically:

  1. I’m trying to create an Elastic Beanstalk environment for a Python application.
  2. I don’t have permissions to create or assign IAM roles.
  3. Elastic Beanstalk requires an instance profile to create the environment.
  4. I’m unable to specify or create the required instance profile due to permission restrictions.

Given these constraints, I’m seeking guidance on how to proceed in this restricted environment. Could you please advise on one of the following options:

a) Provide a pre-defined instance profile that I can use with Elastic Beanstalk.
b) Grant the necessary permissions to create and assign IAM roles for Elastic Beanstalk.
c) Suggest an alternative approach to deploy a Python application in this environment if Elastic Beanstalk is not feasible.

Any assistance or direction you can provide would be greatly appreciated.

Thank you for your help.

Best regards,
Julio Cesar Lapaca

#2

Yes, this is bugged.
The @juliocesarlapacakode , the environment does not create all resources as expected.
It happened that the VPC did not have an internet gateway attached to the VPC and therefore and ALB was not created.

I had to attach it myself.

Instance profile issue also happened to me.

Also passRole to Instances is not allowed.

I’m stucked in this lab too

1 Like
#3

image
image1401×526 10.3 KB

I was able to to attach the instance role and EB service role so it can create other services with cloudformation but this is not feasable.

#4

How did you do this, I am stuck here as well. Could you guide all the steps you taken to produce this?

#5

Hi @kk_user1 ,
This lab is not working correctly. You might need to do it several times. But if anything you must create an IAM role for Ec2 instance and a EB role to create the services deployed.