You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, if all you want to do is restrict the permissions of the Lambda itself, it seems that the partially documented attach_policy is a much better option because this keeps the policy managed by Zappa (no need for manual steps).
Might be worth adding this as an option to the "IAM Roles and polices" section because surely this will solve 95% of requirements for users?
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.
Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.
Originally from: Miserlou/Zappa#2079 by jdmwood
The README at https://github.com/Miserlou/Zappa#custom-aws-iam-roles-and-policies-for-execution talks about using
manage_roles: false
to manually set a role for custom permissions.This along with Miserlou/Zappa#244 led me down a rabbit hole.
However, if all you want to do is restrict the permissions of the Lambda itself, it seems that the partially documented
attach_policy
is a much better option because this keeps the policy managed by Zappa (no need for manual steps).Might be worth adding this as an option to the "IAM Roles and polices" section because surely this will solve 95% of requirements for users?
E.g. here is my
settings.json
:And my
aws_attach_policy.json
:(In my case I didn't need much permissions, but you get the idea).
The text was updated successfully, but these errors were encountered: