-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
apigateway.putIntegration type for AWS Lambda #868
Comments
@brianleroux So, if you wanted to call a lambda function, the uri would look something like this: See #769 for more discussion on the topic. |
awesome thx. (had figured this out after looking at swagger gen … docs could use some colour!) |
hmmm. still having troubles.
With the error:
But it looks good to me? |
@brianleroux |
jeez, I didn't even see that period. (must be getting late!) unfortunately still getting an error. these params:
get this:
😬 |
@brianleroux |
@brianleroux |
Awesome! that (sort of) worked!
guessing this means the thing in my credentials needs but struggling though that config (alas) Kind of crazy. Appreciate your help! |
@brianleroux |
result of actually testing (after editing the role tho / the putIntegration On Wed, Jan 13, 2016 at 4:10 PM, Christopher Radek <notifications@github.com
|
Appears the error is role/policy related
|
For reference this is what I'm using in the
(again huge thx for your help in getting this working) |
@brianleroux |
@brianleroux |
👍 I'll be back…! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
It appears that API Gateway does not currently allow to associate an Lambda to a an method request integration. (But maybe I'm just missing how to do it in the docs!)
The text was updated successfully, but these errors were encountered: