EACCES error when deploying to Lambda functions

Bug description

Using Prisma with NestJS and PlanetScale, which is deployed to a Lambda. I have made the query engine binary available as a layer. The location of this layer is:

/opt/prisma-binary

I have set the above value as PRISMA_QUERY_ENGINE_BINARY. When I try to run a create request, I get the following error:

Invalid `this.prisma.user.create()` invocation in
/var/task/src/lambda.js:482655:43

  482652     throw new Error("Not found. Proceeding to create!");
  482653   }
  482654 } catch (_a4) {
→ 482655   user = await this.prisma.user.create(
  spawn /opt/prisma-binary EACCES
    at RequestHandler.request (/var/task/src/lambda.js:123709:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async PrismaService._request (/var/task/src/lambda.js:124590:22)
    at async AuthService.verifyOTP (/var/task/src/lambda.js:482655:20) {
  code: 'EACCES',
  clientVersion: '3.15.2',
  meta: undefined
}

This works locally, but gives the above error on lambda.

Running it on ARM and not the x86 machines.

How to reproduce

Source Code: core-feat-serverless.zip

Execute: yarn install

Change the serverless.yml file to any dummy org you create in your Serverless Dashboard. then run

yarn sls deploy

Expected behavior

Lambda function should be deployed.

Prisma information

Environment & setup

• OS:
• Database:
• Node.js version:

Prisma Version

Prisma version 3.15.2

[samrith-s]

@janpio Here is the PR for it #3767

[samrith-s]

Will do. Here is the feature request #15289