-
Notifications
You must be signed in to change notification settings - Fork 137
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
Option to use existing IAM roles instead of dynamically creating roles #114
Comments
I've done this with https://gordon.readthedocs.io/en/latest/lambdas.html#role Does that work for you? |
Even when providing the ARN I still get en exception from it attempting to call My settings.yml
Running apply:
|
Looks like what Gordon really cares about is the account id. We can just add that as an config var: Line 454 in c9b83ea
|
Next issue is that gordon.contrib.lambdas had a policy defined, so even if you have a role configured for your application, gordon still tries to create one for the contrib function. See: |
I would like the option of the CloudFormation template to make use of existing IAM roles, instead of dynamically creating them.
One scenario is when the user running Gordon, or manually creating the CloudFormation stack, does not have IAM privileges.
The text was updated successfully, but these errors were encountered: