1

I have a lambda function that I'd like to trigger via HTTP request.

When I click add trigger to a lambda function, I get an API Gateway API set up with:

 method: ANY

Great. Now, when viewing this lambda function, I see a trigger has been configured.

However, I would like to restrict the trigger to only allow POST requests.

So I deleted the API Gateway method ANY, and created a new method POST, under the same resource, using an integration type of Lambda Function. I select my region, and sure enough, my existing lambda function is autocompleted.

However, when I view the triggers tab on the lambda function itself, it shows that there are no triggers.

What am I missing?

1
  • 1
    I had the same exact issue. Lambda function gets triggered with POST method nonetheless. I assumed it must be a GUI issue and the trigger won't appear in the Triggers tab unless the method was ANY. Commented Jan 18, 2017 at 18:48

1 Answer 1

5

If you need flexible control of the API, I would suggest to use the API Gateway console to mange your API. Lambda triggers should only be used for simple use-cases - API methods configured through API Gateway will not show up in the Lambda triggers list.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.