ENV Variables Undefined at Runtime in Turborepo + Next.js on AWS Amplify #9276
Unanswered
Austin-Cometa
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I'm deploying an app from a Turborepo using Next.js on AWS Amplify. The environment variables are defined in the Amplify Console and appear during the build phase (logs confirm process.env values). However, at runtime, when I visit the domain, I get _error, and the server components/middleware used at the start of the app aren't receiving the expected private env vars.
I've tried logging process.env in server components, but none of the environment variables I added in the console are present. Any ideas on why these variables are missing at runtime?
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions