Define the VPC of the serverless functions deployed as part of Next js deployment

### 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

NEW_APP

### AWS Region

us-east-2

### Amplify Hosting feature

SSR

### Question

I want to define the vpc of the serverless functions created as part of the Next.js deployment so that they access other resources defined in a particular vpc.

I couldn't find any documentation on how to define the functions created as part of the next js deployment.
As Next.js is moving towards a database integrated in the framework approach, I think this feature is much needed.

Start with the SSR deployment configuration and the linked FAQ and contributing guide; the issue names no source files, tests, or configuration entry point. Determine how serverless functions created for a Next.js deployment could receive a VPC, and document or implement the supported configuration for the us-east-2 example. Done means the VPC association is defined and its access to resources is verifiable.

Written by the indexing model from the issue text.