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
Add documentation on permissions #27
Comments
Can you show me the contents of your |
|
Are you running the commands as an IAM user with reduced permissions? Creating the role, changing the permissions of the role, and deploying is only ever done as your default boto user. The role management is all there to create the roles/permissions for the lambda process itself. |
I see. I think I was running them as an IAM user. I was doing this on a computer I'd never used boto from before. I do my best not to understand AWS permissions so I never have to be responsible for them. |
I think that is the 100% correct strategy. I find it concerning that Full Access didn't somehow just do the right thing. |
I use an IAM User with All S3 permissions which allowed me to successfully call
pywren create_config --bucket_name YOUR_S3_BUCKET_NAME
. Then I tried to runcreate_role
. I gotI attached the
IAMFullAccess
policy to my user and then that command ran successfully. Then I tried to rundeploy_lambda
and I gotI haven't yet figured out how to get around this. :)
Probably need to add some docs explaining how users might configurer AWS permissions.
The text was updated successfully, but these errors were encountered: