add support for S3

[theburningmonk]

maybe something along the lines of

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /
        method: post
        action: GetObject # maps to s3:GetObject action
        bucket: "hard-coded bucket name"
        key: "hard-coded object key"
        cors: true
    - s3:
        path: /{filename}
        method: post
        action: PutObject # maps to s3:PutObject action
        bucket: "hard-coded bucket name"
        # let caller specify the key via path parameter
        key.$: filename
        cors: true

[erezrokah]

References:
https://docs.aws.amazon.com/apigateway/latest/developerguide/integrating-api-with-aws-services-s3.html
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-as-s3-proxy-export-swagger-with-extensions.html

For what it's worth, another solution I'm using to easily access S3 from a client app is setting cognito resources manually as described here and using the amplify storage library to access the bucket.

[theburningmonk]

FYI, I'm working on this right now, found those same references in the AWS docs.

If you can control the client side then going straight from client to S3 would be easier, or even using signed URLs. The use case I currently have is for a webhook to ingest data from a 3rd-party which sends large payloads (but still under the 10MB limit for API GW) which we want to ship to S3 first before processing with Lambda.

[horike37]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀