Status of latest deployment from prod
branch:
Status of latest deployment from dev
branch:
(if the above is failing, it does not imply that the Lambda function is failing)
Turns serialized HTML into PDF, then pushes it into an S3 Bucket.
- Obtain an API key for create_pdf_2 from the AWS API Gateway > API Keys.
- Make the call, shown below with
curl
. The headers (after -H) and JSON (after -d) shown below are required.
curl -X POST \
'<URL>' \
-H "x-api-key: <API KEY>" \
-d '{ "serializedHTML": "...", #--> Will be rendered as PDF then stored as an S3 Object
"serializedHTMLName": "...", #--> Will be the S3 Object Key for the above object
"serializedHTMLHash": "...", #--> Will be stored as Object metadata. Will be sent in the headers in subsequent requests.
"bucketName":"..." }' #--> S3 Bucket
- The PDF will be
- Make the modification.
- Push to dev branch. Wait 1-2 minutes for it to deploy...
- Test with
curl
as shown above. If unsatisfied, goto 1. - Else, push to prod branch.
- Ensure that memory allocated to
create_pdf
is at least 512MB. - If AWS API Gateway (different from AWS Lambda Management Console) settings were modified, ensure that the API has been re-deployed.
- Ensure that the AWS API Gateway has permissions to access Lambda function, and that the Lambda function has permission to putObject and putObjectACL permissions to the S3 bucket.