If it's helpful at all, the culprit seems to be somewhere around here:

micronaut-aws/function-aws-api-proxy/src/main/java/io/micronaut/function/aws/proxy/ApiGatewayServletRequest.java

Lines 267 to 271 in 50153e7

    
           protected MapListOfStringAndMapStringMutableHttpParameters getParametersFromBody(Map<String, String> queryStringParameters) { 
        
               Map<String, List<String>> parameters = null; 
        
               try { 
        
                   parameters = new QueryStringDecoder(new String(getBodyBytes(), getCharacterEncoding()), false).parameters(); 
        
               } catch (IOException ex) {

It's not so much that function-aws-api-proxy doesn't support the way API Gateway handles file uploads, and more that it happens not to support any kind of binary data when it comes from a form.

I ran into this when converting from a collection of Serverless Function-style Lambdas to a single Application Lambda, but it seems like the workaround is to revert back to Serverless Function just for uploads.

	protected MapListOfStringAndMapStringMutableHttpParameters getParametersFromBody(Map<String, String> queryStringParameters) {
	Map<String, List<String>> parameters = null;
	try {
	parameters = new QueryStringDecoder(new String(getBodyBytes(), getCharacterEncoding()), false).parameters();
	} catch (IOException ex) {

Support for multipart upload for API Gateway #270

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions