Question:
I want to serve my lambda microservices through API Gateway which seems not to be a big problem.
Every of my microservices has a JSON-Schema specification of the resource provided. Since it is a static file, I would like to serve it from an S3 Bucket
rather than also running a lambda function to serve it.
So while
|
1 2 |
GET,POST,PUT,DELETE http://api.domain.com/ressources |
should be forwarded to a lambda function. I want
|
1 2 |
GET http://api.domain.com/ressources/schema |
to serve my schema.json from S3.
My naive first approach was to setup the resource and methods for “/v1/contracts/schema – GET – Integration Request” and configure it to behave as an HTTP Proxy with endpoint url pointing straight to the contracts JSON-Schema. I get a 500 – Internal Server error.
|
1 2 3 4 5 6 7 8 9 |
Execution log for request test-request Fri Nov 27 09:24:02 UTC 2015 : Starting execution for request: test-invoke-request Fri Nov 27 09:24:02 UTC 2015 : API Key: test-invoke-api-key Fri Nov 27 09:24:02 UTC 2015 : Method request path: {} Fri Nov 27 09:24:02 UTC 2015 : Method request query string: {} Fri Nov 27 09:24:02 UTC 2015 : Method request headers: {} Fri Nov 27 09:24:02 UTC 2015 : Method request body before transformations: null Fri Nov 27 09:24:02 UTC 2015 : Execution failed due to configuration error: Invalid endpoint address |
Am I on a complete wrong path or do I just miss some configurations ?
Answer:
Unfortunately there is a limitation when using TestInvoke with API Gateway proxying to Amazon S3 (and some other AWS services) within the same region. This will not be the case once deployed, but if you want to test from the console you will need to use a bucket in a different region.
We are aware of the issue, but I can’t commit to when this issue would be resolved.