Unable to trigger AWS lambda with webhook
See original GitHub issueWe are having an issue triggering our AWS lambda using the Coinbase commerce webhook.
What we tried: Set up Coinbase webhook to trigger AWS lambda function with API Gateway.
What happened: Lambda not triggered. And we received this error message:
Hostname xxxxxx.execute-api.us-east-1.amazonaws.com resolved to a private, loopback, or otherwise reserved IP
What should happen: Our lambda function should execute when webhook is fired.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Receiving events using AWS Lambda function URLs
Under Inbound webhooks using Lambda fURLs, choose Get started. Under Stripe, choose Set up. Under Step 1: Select and event bus, select an...
Read more >Lambda Function is not getting Trigger by Webhook
I have created a lambda function and added an API gateway. I have copy-pasted the endpoint in the webhook, but for some reason...
Read more >Trigger an AWS lambda function by a 3rd party webhook ...
I am thinking of using AWS lambda. Can anyone give me some guidelines how to trigger the AWS lambda function receiving the webhook,...
Read more >Linking webhook to AWS lambda - monday Community Forum
I want to link AWS lambda to Monday.com webhook. i am beginner so any help would be useful thanks! current codes (python3.7) import...
Read more >Build a Github webhook handler with Serverless & AWS Lambda
Let's get started! Before you start. To complete this tutorial, you'll need: The Serverless Framework installed with an AWS account set up; ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Solved it by using a custom domain for my Lambda in AWS API Gateway.
Hey! we are also facing the same issue. How did you solve it? I added a custom domain to my API Gateway, but still coinbase gives the same error.
Hostname xxxxxx.execute-api.us-east-1.amazonaws.com resolved to a private, loopback, or otherwise reserved IP
Thank you for your help.