Support of multipart/form-data requests is a relatively new feature for AWS Lambdas. Although, there is such feature, majority of libraries for parsing multipart/form-data requests is based on server technology, which can't be used in case of AWS Lambdas. That's why, AWS Lambda specific multipart/form-data parser was created.
You can find all necessary information there:
- at official github page: https://github.com/serverless/serverless
- nice youtube playlist about serverless: https://www.youtube.com/watch?v=lUTGk64jppM&list=PLzvRQMJ9HDiT5b4OsmIBiMbsPjfp4kfg3
Go to serverless.yml file and add configurations for your AWS Lambda:
method: POST
integration: LAMBDA
method: POST
- because of we are receiving multipart/form-data request.
integration: LAMBDA
- without that I constanly got 502 Error: Bad Gateway, but I don't know why.
Execute command sls deploy
in AWS Lambda folder. (for more information look for sources at step 1)
- Go to API Gateway.
- Select your API in API Gateway interface
- Go to Settings
- Add multipart/form-data binary media type
- Go to Resources -> POST method of your API -> Integration Request
- Check Use Lambda Proxy Integration
- Deploy your API changes
In majority of cases, while working with AWS Lambda, you will need to enable CORS. Unfortunately, standard way of doing it with AWS UI in API Gateway doesn't work in our case. To solve the problem, you need to send Access-Control-Allow-Origin header as a part of response from your lambda. For example:
const response = {
statusCode: 200,
headers: {
"Access-Control-Allow-Origin": "*"
},
body: JSON.stringify(parse(event, true)),
};
callback(null, response);
- Import aws-lambda-multipart-parser with
npm install --save aws-lambda-multipart-parser
command. - Require it in file
const multipart = require('aws-lambda-multipart-parser');
. - Pass your event object to parse function like that
multipart.parse(event, spotText)
, whereevent
is a event object you get from lambda invocation,spotText
- if it'strue
all text files are present in text for after parsing, if it'sfalse
all text files are represented as regular files with Buffer. Parse function will return object representing the request body.
{
"file": {
"type": "file",
"filename": "lorem.txt",
"contentType": "text/plain",
"content": {
"type": "Buffer",
"data": [ ... byte array ... ]
} or String
},
"field": "value"
}
All fields are represented in request body object as a key-value pair. All files are represented as an object with these fields:
- type - indicates that it's a file
- filename - name of uploaded file (the first one)
- contentType - mime-type of file
- content - content of file in form of Buffer (it's planned in future to give a choise between Buffer and text)