## TL;DR

On your Function add copyFiles from node_modules/.prisma/client/libquery_engine-rhel-openssl-3.0.x.so.node to.prisma/client/libquery_engine-rhel-openssl-3.0.x.so.node, and set the environment variable PRISMA_QUERY_ENGINE_LIBRARY to that same path.

## Steps

1. Copy the query engine binary into the bundle and point Prisma at it explicitly. On your Function add copyFiles from node_modules/.prisma/client/libquery_engine-rhel-openssl-3.0.x.so.node to .prisma/client/libquery_engine-rhel-openssl-3.0.x.so.node, and set the environment variable PRISMA_QUERY_ENGINE_LIBRARY to that same path. Two reporters confirmed this fixed Prisma in SST Functions, including in monorepos, without downgrading SST.

## When to use

You are seeing this: After upgrading SST from v3.3.14 to v3.3.16, every Lambda using Prisma failed at runtime with Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". Use this skill when you run into "Prisma Client could not locate the Query Engine for runtime rhel-openssl-3.0.x after SST v3.3.16 upgrade".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: v3.3.14, v3.3.16. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.