-
Notifications
You must be signed in to change notification settings - Fork 0
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
Unable to create forwarder module in regions other than us-east-1 #1
Comments
hi @qpre. I will try to reproduce, the zip file should be accessible from anywhere, will double check. As for your question, yes forwarder lambda have to be in the same region as the CW groups. |
I tried to access the zip file from the browser and it works, so I doubt thats the issue. Can you show an example code of your module? |
Hey, thanks for your answer
it's normal that it works in a browser because you already have an url for the asset, what does not work is here:
when deploying a lambda with an s3 asset, the asset must be in the same region as where the lambda is deployed.
|
I've just tried to install the TF forwarder following the docs and I'm running into the exct same error -- attempting to provision in us-west-2 fwiw https://axiom.co/docs/send-data/cloudwatch
|
when trying to use the module using aws provider with regions like
eu-west-3
the zip for the lambda is not reachable.as I'm guessing the lambda from us-east-1 won't forward logs from CW groups in eu-west-3, is there a way to circumvent this ?could the lambda zip directory be shipped with the module ?
The text was updated successfully, but these errors were encountered: