Closed IonutAdriann closed 1 year ago
Done, for this there had to be a series of steps completed:
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}) [We have successfully launched an environment]
For creating a CI/CD environment in
AWS
we need to set upIAM
inAWS
and specific roles forBeanstalk
to consume.For now there might seem to be a naming issue but I'll investigate further.