Use HTTP API instead of REST API for API Gateway

developmentseed / cogeo-mosaic-tiler

Serve Map tile from Cloud Optimized GeoTIFF mosaics.

MIT License

12 stars 6 forks source link

Use HTTP API instead of REST API for API Gateway #12

Closed kylebarron closed 4 years ago

kylebarron commented 4 years ago

Now that lambda proxy has full support for using API Gateway's HTTP API, there's really no reason not to default to it, especially since the default serverless.yml doesn't have any auth in the API Gateway configuration. The HTTP API is faster and cheaper.

Closes #1 (Isn't that funny how the numbering is now up to #13 and I did most of that 😅)

vincentsarago commented 4 years ago

we will need to fix https://github.com/vincentsarago/lambda-proxy/issues/44 before merging this !