terraform-aws-elastic-beanstalk-environment icon indicating copy to clipboard operation
terraform-aws-elastic-beanstalk-environment copied to clipboard

Allow use of existing IAM role for EC2 instance profile

Open bstascavage opened this issue 5 years ago • 4 comments
trafficstars

What

  • Enhancement of #107 , due to original developer seemingly abandoning the original PR.
    • Adds service_role_name as another 'override', like instance_role_name is in the original PR.
  • Allow the user of the module to specify an existing IAM Role name for the instance profile.
  • Allow the user of the module to specify an existing IAM Role name for the service profile.
  • This IAM role name will be used to create the instance profile that is assigned to the EC2 instances managed by Elastic Beanstalk.

Why

  • Some environments/users do not have the ability to create their own IAM roles/policies, for security reasons. This change allows a user to provide their own IAM role if one already exists.
  • Currently the module creates an IAM role and a series of permissions for the role.
  • It is not possible to specify what permissions to use
  • It is not possible to edit the permissions that are created
  • This limitation severely limits the capability of the EC2 instances if they require other permissions to operate.

References

  • closes #70
  • closes #107

bstascavage avatar Apr 29 '20 01:04 bstascavage

Thanks for PR @bstascavage. We do have tests in this module, can you take a look at them and extend them to test new functionality?

3h4x avatar May 11 '20 13:05 3h4x

This pull request is now in conflict. Could you fix it @bstascavage? 🙏

mergify[bot] avatar Dec 27 '20 20:12 mergify[bot]

Hello @bstascavage and thank you for your PR.

This feature would be a great enhancement to the module, i would be glad to help for reviewing it with Cloudposse team.

Are you still working on this ?

florian0410 avatar Jul 23 '21 16:07 florian0410

@bstascavage please resolve the conflicts

aknysh avatar Dec 31 '21 16:12 aknysh