diff --git a/advanced/subpath/route53-cloudfront.mdx b/advanced/subpath/route53-cloudfront.mdx
index ed35c3718..96fe460ab 100644
--- a/advanced/subpath/route53-cloudfront.mdx
+++ b/advanced/subpath/route53-cloudfront.mdx
@@ -8,29 +8,23 @@ import Propagating from "/snippets/custom-subpath-propagating.mdx";
To host your documentation at a `/docs` subpath using AWS Route 53 and CloudFront, you need to configure your DNS provider to point to your CloudFront distribution.
-## Proxies with Vercel deployments
+## High-level overview
-If you use AWS CloudFront as a proxy with Vercel deployments, you must configure CloudFront to avoid interfering with Vercel's domain verification and SSL certificate provisioning.
-
-Improper CloudFront configuration can prevent Vercel from provisioning Let's Encrypt SSL certificates and cause domain verification failures.
-
-### Required path allowlist
-
-CloudFront must allow traffic to these specific paths without caching or blocking:
+Route traffic to these paths with a Cache Policy of **CachingDisabled**:
- `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
-- `/.well-known/vercel/*` - Required for Vercel domain verification
+- `/.well-known/vercel/*` - Required for domain verification
+- `/docs/*` - Required for subpath routing
+- `/docs/` - Required for subpath routing
-These paths should be configured to bypass CloudFront caching and pass through directly to your origin.
+Route traffic to this path with a Cache Policy of **CachingEnabled**:
-### Header forwarding requirements
+- `/mintlify-assets/_next/static/*`
+- `Default (*)` - Your websites landing page
-You must create a custom origin request policy that forwards the `HOST` header and client IP information correctly. This is critical for Vercel's verification processes.
+All Behaviors must have the an **origin request policy** of `AllViewerExceptHostHeader`.
-1. Create a custom origin request policy named `VercelCloudFrontProxy`.
-2. Include the `Origin` and `CloudFront-Viewer-Address` headers.
-
-You must include the `CloudFront-Viewer-Address` header in your origin request policy or cache policy headers configuration to forward the header to your origin.
+
## Create CloudFront distribution
@@ -120,12 +114,7 @@ If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a m
Create a behavior with a **Path pattern** of `/docs` with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`).
- Set "Cache policy" to **CachingOptimized**.
-- In "Origin request policy", create an origin request policy named **VercelCloudFrontProxy**. That forwards the `Origin` and `CloudFront-Viewer-Address` headers.
-
-
- 
-
-
+- Set "Origin request policy" to **AllViewerExceptHostHeader**.
- Set Viewer Protocol Policy to **Redirect HTTP to HTTPS**
@@ -139,9 +128,15 @@ Create a behavior with a **Path pattern** of `/docs/*` and **Origin and origin g
These settings should exactly match `/docs`. With the exception of the **Path pattern**.
- Set "Cache policy" to **CachingOptimized**.
-- Set "Origin request policy" to **VercelCloudFrontProxy**.
+- Set "Origin request policy" to **AllViewerExceptHostHeader**.
- Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**
+### `/mintlify-assets/_next/static/*`
+
+ - Set "Cache policy" to **CachingOptimized**
+ - Set "Origin request policy" to **AllViewerExceptHostHeader**
+ - Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**
+
### `Default (*)`
Lastly, we're going to edit the `Default (*)` behavior.
diff --git a/advanced/subpath/vercel.mdx b/advanced/subpath/vercel.mdx
index 4c8362ac8..f8c1aa688 100644
--- a/advanced/subpath/vercel.mdx
+++ b/advanced/subpath/vercel.mdx
@@ -51,6 +51,7 @@ Your external proxy must allow traffic to these specific paths without blocking,
- `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
- `/.well-known/vercel/*` - Required for Vercel domain verification
+- `/mintlify-assets/_next/static/*` - Required for static assets
These paths should pass through directly to your Vercel deployment without modification.
diff --git a/images/cloudfront/all-behaviors.png b/images/cloudfront/all-behaviors.png
index c1ee521b9..762c11f87 100644
Binary files a/images/cloudfront/all-behaviors.png and b/images/cloudfront/all-behaviors.png differ
diff --git a/images/cloudfront/behavior-1.png b/images/cloudfront/behavior-1.png
index 85f6b49f6..329b9dc91 100644
Binary files a/images/cloudfront/behavior-1.png and b/images/cloudfront/behavior-1.png differ