VPC Access for SSR Compute Runtime

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [x] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d38o4skyg8ykrk

### AWS Region

us-east-1

### Amplify Hosting feature

Not Applicable

### Question

Hello! I am trying to connect to my RDS database inside the Next.js backend as defined [here](https://beta.nextjs.org/docs/routing/route-handlers).

My RDS database is not public and I'm trying to figure out how I could connect to it from my app. Does an amplify hosted app have visibility and access to other aws services to allow this or is that not possible? For context, I'm attempting to use the Prisma ORM to connect to the database. [This](https://github.com/prisma/prisma-examples/tree/latest/javascript/rest-nextjs) is an example of how my project is structured.

If it's not possible for the app to connect to a private RDS database, would I need to make the database publicly accessible, and if so, how could I do that securely?

Thanks!

Start by reviewing FAQ.md and the linked Next.js route-handler and Prisma example to understand the reported SSR database-access setup. Determine whether Amplify Hosting supports access to a private RDS database and document the supported connectivity or secure-public-access path; the issue provides no repository entry point or test.

Written by the indexing model from the issue text.