IT-4204: Add IAM permission boundary for synapse llm lambda exec role #1336
+32
−0
Conversation
This file contains 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
|
Forgot to add that this policy will be added as dependency to new IAM-related permissions given to the SSO LlmDeveloper role (which currently does not have any IAM permissions beyond iam:PassRole). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR creates a managed policy that's going to be used as an IAM permission boundary. The boundary will be associated with roles created by LLM developers, the roles are assumed by lambda functions.
See https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html
and https://aws.amazon.com/blogs/security/when-and-where-to-use-iam-permissions-boundaries/
Note: only put minimal boundary here