-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support cross-account CloudWatch events #2005
Conversation
…low mode to override parsing account_id from event
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.
i'm convinced, thanks for the pr.
based on #2001 |
Please can someone provide a simple of example policy of this change?does it mean I can run one lambda across multiple accounts? if so is there only periodic support or event too? |
@stevelaver this is intended to work for events. Here's a sample policy to autotag all buckets from member accounts. The lambda is deployed once in a central account.
In order for this to work, you also need to deploy the following snippet of CloudFormation into each member account to send events back to the central account:
|
Address #1415 by assuming a member role from LambdaMode
assume_member
from within the LambdaMode resolve_resourcesaccount_id
from the event for subclasses ofLambdaMode
region
from the event for subclasses ofLambdaMode