/ need to be written as ~1 as per the documentation. After playing around I finally got the following to work. Keep in mind that this allows all binary media types.

Globals:
  Api:
    BinaryMediaTypes: ['*~1*']

same issue here when uploading a .txt file it’s working fine but I’m trying a .zip file which throw an 502 BAD GATEWAY error. API Gateway binary type set is

BinaryMediaTypes:
    - "application/zip"
    - "application/octet-stream"

Work around

As mentioned by pyrabbit, set the BinaryMediaTypes to ['*~1*']

In the documentation AWS says "Use ~1 instead of / in the mime types. " but "application~1zip" doesn’t work, maybe the documentation should add more examples of how to use the BinaryMediaTypes with working examples

Also on the doc AWS says “This property is similar to the BinaryMediaTypes property of an AWS::ApiGateway::RestApi resource.” which uses the / maybe a change on the SAM CLI to support the / should be good as we keep the same behaviors and consistency

I had the same issue with SAM CLI 0.19.0. I managed to resolve it by adding “application/octet-stream” to “BinaryMediaTypes” in the SAM yaml file. So now my entry looks like this: Properties: BinaryMediaTypes: [image/*, application/octet-stream] With my Java Lambda I can now get the binary data in a “byte[]” input object. I haven’t verified this in a deployed version yet.

Solved it by having a template like this one

Resources:
  AssetsUploadFunction:
    Type: AWS::Serverless::Function 
    Properties:
      CodeUri: assets/
      Handler: handler
      Runtime: go1.x
      Tracing: Active # https://docs.aws.amazon.com/lambda/latest/dg/lambda-x-ray.html
      Events:
        CatchAll:
          Type: Api 
          Properties:
            Path: /
            Method: PUT
            RestApiId: AssetsAPI

  AssetsAPI:
    Type: AWS::Serverless::Api
    Properties:
      StageName: sandbox
      BinaryMediaTypes:
        - '*~1*'

This one is strange, because it only fails on image types for me. Like .jpg or .png (tested this ones). If I base64 encode my data prior to sending (e.g. base64 image.jpg > image64; curl ... -F 'image64=@image64') works perfectly and I can retrieve the data as a multipart-blob in the event['body'] in my function.

@prenx4x actually, there is still a problem if one uses HttpApi events for lambdas.

I tried to set

Globals:
  Api:
    BinaryMediaTypes:
      - '*~1*'
      - '*/*'
      - 'multipart~1form-data'
      - 'multipart/form-data'
      - 'application~1octet-stream'
      - 'application/octet-stream'

as well as

Resources:
  CrudDebug:
    Type: AWS::Serverless::Function
    Properties:
      Handler: dist/api/functions/crud/index.debug
      Runtime: nodejs14.x
      Timeout: 10
      Environment: *ENV
      Events:
        HttpGet:
          Type: HttpApi
          Properties:
            Path: /crud-debug
            Method: any
            BinaryMediaTypes:
              - '*~1*'
              - '*/*'
              - 'multipart~1form-data'
              - 'multipart/form-data'
              - 'application~1octet-stream'
              - 'application/octet-stream'

But no luck, still getting 502 (BAD GATEWAY) while trying to send files to this lambda.

I need especially HttpApi type of event insteand of Api because the platform for which I am developing requires lambdas to process APIGatewayProxyEventV2. Everything been set up so far, but now I am struggling to create a lambda with the file upload and test it locally.

BTW, I am trying to test file sending by putting this code into my Chrome Dev Tools:

let formData = new FormData();
formData.append('file', (await (await fetch(`https://placekitten.com/300/225?_=${+new Date()}`)).blob()));
formData.append('file', (await (await fetch(`https://placekitten.com/400/300?_=${+new Date()}`)).blob()));
await (await fetch('http://127.0.0.1:3000/crud-debug', {
  method: 'post',
  body: formData,
//   processData: false,
//   contentType: false,
  headers: {
//     'Content-Type': 'application/octet-stream',
  },
})).json();

(changing headers didn’t help too when there was single file; also my app is required to be able to upload multiple files at once).

Maybe I should create separate issue for this? Thanks.

Have added BinaryMediaTypes but no joy 😦

I have the same issue, though I am sending a small .wav file, not an image.

Local output with --debug gives no extra information, it just returns a 502 before attempting to execute anything.

With the same configuration actually deployed to AWS, I can send a file without issue. The issue only occurs with the local api.

I’m having the same issue. I also see the same thing as @yehorb that if i create a txt file contents of the base64 encoding of an image then it works just fine.

I concur. Is there any solution for this?

Is there any solution for this??

Same here with Python3.7 runtime, very annoying…

Getting the same problem here.

Have tried adding a BinaryMediaTypes key to our template.yaml but no luck.

  Api:
    BinaryMediaTypes:
      - image~1png
      - image~1jpeg
      - image~1jpg
      - image~1pdf