Anders Wasen

Yep, me too and all font's becomes `Open Sans` it seems... Following!

I downloaded the .ttf files and added them to the repository with a fonts.conf file as I never got it loading from a URL and that worked... However, we have...

I too am stuck on this and the fonts I add are not being used/added in AWS runtime. Works fine locally using localstack but running the same in Lambda on...

Ok, a little progress... I did "force" it to use the `/var/task/fonts` path for fonts by changing this in `source/index.js` and the rebuilding: ``` if (['AWS_Lambda_nodejs10.x', 'AWS_Lambda_nodejs12.x'].includes(process.env.AWS_EXECUTION_ENV) === true) {...

First off, thanks SO MUCH for this @jeremydaly. It's awesome! Secondly, @nitesmeh, can you confirm that the Data API should not consume connections? (And thanks for taking your time helping...

@ortonomy We have that exact same issue after increasing our use of AppSync! We have one express based server (Elastic Beanstalk) which is still using native DB connection to PG...

Well, this is a farse from AWS... We found the same `commit` @deel77 some time ago (sorry for not thinking about reporting it here)... We were eagerly awaiting Serverless v2...

@obataku From the discussions I've had with AWS and can "reveal" it would seem that Aurora Serverless v2 is a complete rebuild of Aurora (non-Serverless) where they've added the "serverless"...

I ran a test both using the `local-data-api` Docker container locally and using the Aurora Serverelss in AWS and they both return: ``` { "numberOfRecordsUpdated": 0, "records": [ [ {...

I've tried to just rename the commands and hooks to `kmsencrypt` and `kmsdecrypt` and that seems to do it. It no longer "collides" with `serverless-secrets-plugin`