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

AWS Trust Policy Behavior Change #352

Open
transient1 opened this issue Oct 19, 2022 · 0 comments
Open

AWS Trust Policy Behavior Change #352

transient1 opened this issue Oct 19, 2022 · 0 comments

Comments

@transient1
Copy link

Hi. I wanted to verify my understanding of the recent(ish) announcement about how AWS is changing the implicit ability for a role to assume itself as documented here.

The install instruction for kube2iam say to include this policy in the roles you attach to your nodes

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "sts:AssumeRole",
            "Resource": "*"
        }
    ]
}

which clearly allows the nodes to assume a role. However in the AWS announcement they call out that a trust policy that sets those node roles as the principal is both "necessary and sufficient" to allow assumption of that role. I tested this by removing this policy from the nodes, and making sure workloads using the kube2iam annotation were still able to successfully make their API calls to AWS.

Before I go ahead and remove this policy from our instance profiles though I was hoping to verify that there isn't another purpose to this policy that I am missing. Thank you.

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