AWS API Gateway Method to Serve static content from S3 Bucket

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 re

Answer 1

In one of my setups I put a CloudFront distribution in front of both an API Gateway and an S3 bucket, which are both configured as origins.

I did mostly it in order to be able to make use of an SSL certificate issued by the AWS Certificate manager, which can only be set on stand-alone CloudFront distributions, and not on API Gateways.

Answer 2

I just had a similar error, but for a totally different reason: if the s3 bucket name contains a period (as in data.example.com or similar), the proxz request will bail out with a ssl certification issue!

Answer 3

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.