File Processor

Convert Office (docx, pptx, xlsx) to PDF at scale.

Support for custom fonts to conversion. See the fonts folder for supported fonts. Add your own to support even more.

Functions:

• HTTP endpoint
• SQS queue

Dependencies

• Serverless Framework
• AWS Lambda
• LibreOffice 6.4 Lambda Layer (https://github.com/shelfio/libreoffice-lambda-layer)

Config

Uses the serverless-config.dev.json or the serverless-config.prod.json to handle different AWS resources, such as buckets, SQS etc.

Uses SSM Parameter Store (console.aws.amazon.com/systems-manager/parameters) to keep your API-Key safe. Visit the AWS console to setup your parameters.

You have to create FileProcessor/dev/ApiKey

Usage

HTTP Endpoint

Once deployed, you can hit the api like this:

curl --location 
--request POST 'https://someurl.execute-api.eu-west-1.amazonaws.com/dev/api/v1/file/convert' \
--header 'X-API-KEY: my-custom-api-key' \
--header 'Content-Type: application/json' \
--data-raw '{
    "url": "https://my-website.com/path/to/doc.pptx"
}'

HTTP Response:

{
    "output_url": "https://office-file-processor-dev.s3.eu-west-1.amazonaws.com/conversions/1608127441661/doc.pdf"
}

SQS Event

With SQS Queue we can use much higher processing time for complex documents. Secondly we can use SQS to integrate to a service in a private network.

{
    "bucket": "office-file-processor-dev",
    "key": "path/to/doc.pptx"
}

Optionally, you can specify the file ACL, and a http callback if you need to communicate to a service with the conversion results.

{
    "bucket": "office-file-processor-dev",
    "key": "path/to/doc.pptx",
    "acl": "public-read",
    "callback_url": "https://example.com/your/callback/route?id=123456789"
}

DEPLOYMENT

Deploy Dev

serverless deploy --stage dev --verbose

Deploy Production

serverless deploy --stage prod --verbose