Support for Customer Managed Policies #128
Open
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 is an attempt to include this functionality into the serverless-iam-roles-per-function repository as it's one of my favorite plugins for my Serverless projects.
I have recently come across this issue where I need to have a project meet some criteria to be compliant with a security check. I have surfaced the web and I didn't find any solution to update the IAM roles created in my Serverless project to use Customer Managed Policy instead of an inline policy.
This was discussed in the Serverless Forum last year, but no solution was found.
My implementation exposes a property at the serverless template level, and for each individual lambda. If someone wants to create CustomerManagedPolicies for a single lambda, they can set the
defaultCreateCustomerManagedPolicy: true
in the specific lambda. Or if they want to have all their lambdas use the managed policy, they can add the propertycustom.serverless-iam-roles-per-function.defaultCreateCustomerManagedPolicy: true
to the serverless template file.