Amplify Using Incorrect Environment Variables Across Multiple AWS Accounts
I’m facing a strange issue with environment variables.
Amplify Using Incorrect Environment Variables Across Multiple AWS Accounts
I’m facing a strange issue with environment variables.
Amplify Using Incorrect Environment Variables Across Multiple AWS Accounts
I’m facing a strange issue with environment variables.
CSS issue after deploying in aws amplify, Next js app router
The issue is CSS like z-index, fixed, and absolute works on Vercel but not on AWS Amplify, it happened after deployment, I already reverted the commits and re-deployed the version that was working but nothing changed.
The problem is the issue is happening in specific components.
I’m using App-Router, Next: 14.2.3
@aws-amplify/backend: Module not found: Can’t resolve ‘path’
In my next.js application, that I am trying to deploy to AWS amplify, I am using @aws-amplify/backend in order to access secrets using as described here. However I always get an error as shown below.