Database/Server Error Detected

AWS Amplify generated an error while fetching blog posts:

Invalid `prisma.post.findMany()` invocation: Can't reach database server at `dyd-rds.cfi44wq8w2z5.ap-south-1.rds.amazonaws.com:5432` Please make sure your database server is running at `dyd-rds.cfi44wq8w2z5.ap-south-1.rds.amazonaws.com:5432`.

PrismaClientInitializationError: Invalid `prisma.post.findMany()` invocation: Can't reach database server at `dyd-rds.cfi44wq8w2z5.ap-south-1.rds.amazonaws.com:5432` Please make sure your database server is running at `dyd-rds.cfi44wq8w2z5.ap-south-1.rds.amazonaws.com:5432`. at $n.handleRequestError (/var/task/node_modules/@prisma/client/runtime/library.js:121:7615) at $n.handleAndLogRequestError (/var/task/node_modules/@prisma/client/runtime/library.js:121:6623) at $n.request (/var/task/node_modules/@prisma/client/runtime/library.js:121:6307) at async l (/var/task/node_modules/@prisma/client/runtime/library.js:130:9633) at async e (/var/task/.next/server/chunks/ssr/[root-of-the-server]__861a0f3b._.js:1:1609)

Debugging Tips for AWS Amplify:

Check if DATABASE_URL is added to Environment variables in the Amplify Console.
Ensure npx prisma generate is included in your amplify.yml build settings before npm run build.
Verify if your AWS RDS database security groups allow inbound connections from AWS Amplify.