Accessing CloudFront distributions created by Amplify

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

dp7hwi3j7q6f6

### AWS Region

eu-west-3

### Amplify Hosting feature

Deployments

### Is your feature request related to a problem? Please describe:

I want to dynamically enrich meta-tags on a React app without using SSR (Server-Side Rendering). Aside from meta-tags, we don't really need SSR, and to me, meta-tags alone are not a sufficient reason to start migrating to SSR. One potential solution is to use Lambda@Edge. However, I am unable to link that kind of function with the corresponding AWS Amplify CloudFront distributions unless they become transparent to us.

### Describe how you'd like this feature to work

I want the CloudFront distributions created by Amplify to be accessible, specifically in the context of Lambda@Edge functions. Currently, I am facing limitations in linking Lambda@Edge functions to the corresponding AWS Amplify CloudFront distributions. This means that I am unable to take full advantage of Lambda@Edge capabilities within the Amplify setup.

Start by reviewing the linked FAQ and CONTRIBUTING guide, then examine how Amplify Hosting exposes CloudFront distributions for deployments. The requested outcome is access to the corresponding distributions so Lambda@Edge functions can be linked without requiring SSR; the issue does not name implementation files or tests.

Written by the indexing model from the issue text.