Skip to content
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

iam:GetRole still needed #144

Open
candlerb opened this issue Aug 18, 2017 · 0 comments
Open

iam:GetRole still needed #144

candlerb opened this issue Aug 18, 2017 · 0 comments

Comments

@candlerb
Copy link

According to changelog comment 44e92e7, "Adding aws-account-id to your settings will make gordon not require any IAM permissions" as of commit fba74a0.

But this needs clarification. Whilst gordon itself may not perform an IAM lookup, it still needs IAM permissions in order to deploy a stack.

Even when providing aws-account-id I still needed to provide these or else I got cloudformation failures:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1503051480000",
            "Effect": "Allow",
            "Action": [
                "iam:CreateRole",
                "iam:PutRolePolicy",
                "iam:DeleteRole",
                "iam:DeleteRolePolicy",
                "iam:GetRole"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

The first four were required to get as far as creating the stack, and GetRole seems to be required as part of lambda deployment:

CREATE_FAILED | AWS::Lambda::Function | ContribLambdasVersion | AccessDenied. User doesn't have permission to call iam:GetRole

Relates to #124.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant