Skip to content
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

Can I run Lambda cross region/account #1071

Closed
victorh3 opened this issue Apr 11, 2017 · 1 comment
Closed

Can I run Lambda cross region/account #1071

victorh3 opened this issue Apr 11, 2017 · 1 comment

Comments

@victorh3
Copy link

victorh3 commented Apr 11, 2017

Running custodian on lambda scheduled mode. Function is deployed on us-east-1, but can I make this same function run on us-west-2? Expanding to other accounts if we have consolidated billing? I'd rather have 1 lambda function than 10+ for each account and region

@victorh3 victorh3 changed the title Can I run Lambda cross region/accoutn Can I run Lambda cross region/account Apr 11, 2017
@kapilt
Copy link
Collaborator

kapilt commented Apr 17, 2017

lambda policies are deployed to a particular region, and are currently bound to that region. to deploy to multiple regions, run custodian against that region to deploy a separate lambda function there. for regions that don't support lambda, lambda policies can't be employed and a poll policy (default) should be used. cross account lambda policies are not supported. there's some back story there that should be re-verified, namely when cloudwatch events was first released that it didn't support cross account targets, ditto for config. note that even then neither of those is zero footprint, as they rely on the target account and region having a cloudwatch event or config rule.

@kapilt kapilt closed this as completed Apr 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants