-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Match IAM service linked role naming with AWS #12387
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
Conversation
… correctly attach the policies
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 30s ⏱️ - 1h 50m 48s Results for commit a6bae2b. ± Comparison against base commit e8907e5. This pull request removes 4096 and adds 144 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
Great. More Parity!! 🥳
Motivation
Currently, our service linked roles will be named
r-<short-id>
.This does not match the AWS naming, as it is usually named
AWSServiceRoleFor<service>
.Also, the service linked roles will not have proper policies attached, rendering them unusable with IAM enforcement.
This PR will increase parity by defining both predefined names for service linked roles (for services LS supports), and a heuristic to get the name for those services which do not.
Also, we will properly reject requests for service linked roles with a suffix for services which do not support it, and attach the correct policies to the service linked roles.
This supersedes #11731
Changes