-
Notifications
You must be signed in to change notification settings - Fork 201
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
Cloudwatch and Lambda Region Specific #80
Comments
@zbuckholz yeah, this is a bit of an oversight on AWS's part. :-( |
I have a ticket opened, if they provide a solution or work around I'll share the knowledge. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across this great documentation while searching for a recent problem I encountered. I hope you can update the documentation with a solution.
I have deployed a lambda function in us-west-2 to monitor cloudwatch for ec2 power changes, which then updates Route53. Today I attempted to utilize us-west-1 and noticed the lambda function in us-west-2 doesn't have access to cloudwatch events in us-west-1.
There appears to be no way to setup a trigger for lambda that can use cloudwatch events in a different region.
The text was updated successfully, but these errors were encountered: