-
Notifications
You must be signed in to change notification settings - Fork 199
iam-policy-permissions-AWS-HCP #16002
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
Open
DanielOsypenko
wants to merge
2
commits into
red-hat-storage:master
Choose a base branch
from
DanielOsypenko:iam-policy-permissions-AWS-HCP
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: red-hat-storage/ocs-ci
Length of output: 2123
🌐 Web query:
AWS IAM TagOpenIDConnectProvider required permissions ListOpenIDConnectProviderTags TagInstanceProfile ListInstanceProfileTags💡 Result:
To manage tags for AWS IAM OpenID Connect (OIDC) providers and instance profiles, you must grant specific IAM permissions. IAM OIDC Providers To add or list tags for an IAM OIDC provider, you need the following IAM permissions [1][2]: - iam:TagOpenIDConnectProvider: Required to add tags to an OIDC identity provider [1][3]. - iam:ListOpenIDConnectProviderTags: Required to list the tags attached to an OIDC identity provider [1][4]. Note that the iam:TagOpenIDConnectProvider action also requires that you include the iam:ListOpenIDConnectProviderTags action in your policy [1][2]. - iam:UntagOpenIDConnectProvider: Required if you also need to remove tags from an OIDC provider [1][2]. IAM Instance Profiles To add or list tags for an IAM instance profile, you need the following IAM permissions [5]: - iam:TagInstanceProfile: Required to add tags to an instance profile [6][5]. - iam:ListInstanceProfileTags: Required to list the tags attached to an instance profile [5][7]. Similar to OIDC providers, the iam:TagInstanceProfile action requires that you also include the iam:ListInstanceProfileTags action [5]. - iam:UntagInstanceProfile: Required if you also need to remove tags from an instance profile [5]. Example Policy Structure When creating policies for these actions, the Resource field should specify the ARN of the specific provider or instance profile [1][5]. For example: { "Effect": "Allow", "Action": [ "iam:ListOpenIDConnectProviderTags", "iam:TagOpenIDConnectProvider" ], "Resource": "arn:aws:iam::account-number:oidc-provider/ProviderName" } { "Effect": "Allow", "Action": [ "iam:ListInstanceProfileTags", "iam:TagInstanceProfile" ], "Resource": "arn:aws:iam::account-number:instance-profile/InstanceProfileName" }
Citations:
Add the required IAM tag-list permissions.
Add
iam:ListOpenIDConnectProviderTagsandiam:ListInstanceProfileTagsto the statement. Their corresponding tag actions require these permissions.🤖 Prompt for AI Agents