This repository was archived by the owner on Nov 5, 2024. It is now read-only.
AWS sources and targets cross-account/remote IAM support#1400
Merged
Conversation
040976a to
e33b809
Compare
e33b809 to
7c65d59
Compare
229b44f to
84f148a
Compare
FranBarrera
approved these changes
May 3, 2023
Member
Author
|
@FranBarrera thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AWS components' auth support for cross-account IAM impersonation.
Available auth schemas:
static creds
-client session is created with the IAM user account whose Access Key specified in the spec. Controller also uses the same access key.
IAM Role
-IAM role impersonation available on EKS only. New SA will be created for the adapter, controller's SA requires manual update to include EKS role annotation. STS trust relationship configuration required on IAM.
New: cross-account IAM Role
-after client session is created with the static credentials,
assumeIamRolewill be used to gain IAM permissions. STS trust relationship configuration required on IAM.Resolves #1253