Hi Team,
@Nigel posted demo code showing Apigee proxy AWS Lambda calls. Thank you to Laurence from enkidootech.com to confirm that it works.
Thanks for sharing this. I took that sample and tweaked it sightly for my use case, deployed it to Edge Cloud and when I make a call to the API (curl -i) for some reason the output is the full swagger doc. Any idea why that's happening?
Can you post the full curl command ?
curl -i https://.apigee.net/v1/ >
and the output is the full swagger doc in json format.
@Nigel Walters have you gotten this to work without API Gateway in the path? I.e. Apigee -> Lambda?
Hi Alan, yes, we have that working. Within the a127 lambda petstore sample github project you can find an example of Apigee calling AWS Lambda directly here: https://github.com/apigee/a127-lambda-petstore-sample/tree/master/a127_proxy_to_lambda
Please let me know if you have any queries around it.
Thanks @Nigel Walters that's been helpful. Do you know of a way to manage custom http status codes from Lambda within Swagger? As you know Lambda always returns a status 200 but the functionality of the function may need to return a message indicative of status that's not "OK" so is there a way to do this with just Swagger + Lambda? I know API Gateway can do it, but if possible I'd like to eliminate the extra middle man.
Contributors
28 People are following this .
