WEB_COMPUTE and CloudFormation Cache Policy

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

dd3lf3a1pnht

### AWS Region

ap-south-1

### Amplify Hosting feature

Deployments

### Question

Our production instance of Amplify runs on WEB_DYNAMIC and we have seen issues with the total cookie size going above 8KB, it throws a RequestHeaderSectionTooLarge error. Changing Cookie settings to "None" from "All" fixes the issue. This happens every time we run a deployment.

We tried to reproduce this in our development instance of Amplify that runs on WEB_COMPUTE. The total cookie size does go above 8KB but we are unable to reproduce the same. Also there's no visibility into CloudFront and other resources in WEB_DYNAMIC.

This leads me to 2 questions

- Does amplify allow higher request header size for WEB_COMPUTE? If so what is it? This let's us understand the constraints we need to be mindful of.
- Can we get an insight on CloudFront settings? And is it possible to modify it using CDK/CloudFormation if we need to?

Start by reviewing the documented behavior and limits for WEB_COMPUTE and WEB_DYNAMIC deployments, including the CloudFront settings visible to each mode. The issue is done when it has authoritative answers about request-header limits and whether the relevant CloudFront settings can be inspected or changed through CDK or CloudFormation.

Written by the indexing model from the issue text.