-
-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass Task Exec. policy ARN as an input variable or default to AmazonECSTaskExecutionRolePolicy #7
Comments
I'm also interested in having policy_arn as an input variable that defaults to its current value. Right now I have to include AWS CLI credentials into the docker image, which isn't optimal from a security PoV. |
#7 pass ECs task exec. policy as input variable
I've just tried this, and it does not work if the policy ARN is a computed value, or anything other than a string literal:
When running:
It looks to me like the only means of having Atlantis run with AWS credentials using this module is to bake static creds into the atlantis container, unless I'm missing something? |
I'm getting the same error as kerin. Terraform v0.11.11 and this module's release v1.11.0 |
I am curious how we can deal with the credentials usage for stuff other than AWS resources? |
this issue appears to be resolved with the latest versions - please update and let us know if there are any additional issues that need attention, thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
terraform-aws-atlantis/main.tf
Line 186 in 508eb0c
When I tried to use
atlantis plan
orapply
I found that it needed permissions for at least for (depending on the config files of course):among others.
Initially I began by attaching existing policies, before I determine the which ones are most restrictive. Alternatively, one could pass the overly permissive https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html#jf_administrator if they're confident that the Task runs securely.
The text was updated successfully, but these errors were encountered: