We’re implementing our custom .docx to .pdf converter using AWS lambda in .NET using Aspose.Words (21.5.0). We’ve created a bucket with the folder called Fonts and we’ve uploaded single Roboto font to that folder to test this converting logic.
As a truth of source, we’re using this documentation: https://docs.aspose.com/words/net/integration-in-aws-lambda/.
We’ve copied all the code from the documentation but instead of
builder.Font.Name = "Noto Sans"; we’ve used
builder.Font.Name = "Roboto";
After running this application locally we’ve got perfect results. But once we’ve deployed the application to AWS Lambda the fallback font was used and our custom one wasn’t loaded rendered.
After the debugging, we’ve found that
.GetAvailableFonts().Count returns 1 locally, but 0 remotely and we think this is an issue.
Screenshot 2021-05-19 at 15.35.03.jpg (47.1 KB)
Could you please give us a piece of advice on how we can fix it and start using custom fonts from the S3 bucket in AWS Lambda!
Thanks in advance!