> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://mintlify.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://mintlify.manicule.dev/api/mcp.
> Every agent surface: https://mintlify.manicule.dev/.well-known/llms-manifest.json

# Deploy at a subpath with AWS Route 53 and CloudFront (/deploy/route53-cloudfront)

<!-- agent-signals: reading_time_min: 7 · est_tokens: 2742 · updated: 2026-07-31 -->
Related: [Host docs at a subpath](/deploy/docs-subpath.md), [Deploy at a subpath with Cloudflare Workers](/deploy/cloudflare.md), [Deploy at a subpath with Vercel](/deploy/vercel.md), [Reverse proxy](/deploy/reverse-proxy.md), [Content Security Policy (CSP) configuration](/deploy/csp-configuration.md)

> Deploy your Mintlify documentation at a subpath on AWS using Route 53 for DNS routing and CloudFront as a CDN with Lambda@Edge functions.

To host your documentation at a subpath such as `yoursite.com/docs` using AWS Route 53 and CloudFront, you must configure your DNS provider to point to your CloudFront distribution.

Before configuring AWS, set your base path in your dashboard:

1. Navigate to the [Custom domain setup](https://app.mintlify.com/settings/deployment/custom-domain) page in your dashboard.
2. Enable the **Host at** toggle.
3. Enter your domain.
4. Enter your base path. For example, `/docs` or `/help`.
5. Click **Add domain**.

## Overview

<Note>The following examples use the `/docs` base path. If you use a different base path, replace `/docs` with your base path.</Note>

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 domain verification
* `/docs/*` - Required for subpath routing
* `/docs/` - Required for subpath routing
* `/_mintlify/*` - Required for API playground requests

Route traffic to these paths with a Cache Policy of **CachingEnabled**:

* `/mintlify-assets/*` - Required for CSS, JavaScript, and favicons
* `Default (*)` - Your website's landing page

All Behaviors must have an **origin request policy** of `AllViewerExceptHostHeader`.

The behaviors for your subpath must allow all HTTP methods. CloudFront only allows `GET` and `HEAD` requests by default, which blocks the `POST` requests that Mintlify uses for analytics and other interactive features.

![CloudFront "Behaviors" page with 4 behaviors: /docs/\*, /docs, Default, and /.well-known/\*.](/_assets/778eab4c78c667a479cdee462440788288772fee2713b4a190c30a6a6bf86623)

## Create CloudFront distribution

1. Navigate to [CloudFront](https://aws.amazon.com/cloudfront) inside the AWS console.
2. Click **Create distribution**.

<Frame>![CloudFront Distributions page with the "Create distribution" button emphasized.](/_assets/d0ea384e8fbb70d9fcb72f7b76737642d8f24946dcd308d4087fa95f18dcfa8e)</Frame>

3. For the Origin domain, input `[SUBDOMAIN].mintlify.site` where `[SUBDOMAIN]` is your project's unique subdomain.

<Frame>![CloudFront "Create distribution" page showing "acme.mintlify.site" as the origin domain.](/_assets/c1ff48743bf6f1a19c75e468cfcad629ce3a2fd6bf2231f7166aa7b6e876aad2)</Frame>

4. For "Web Application Firewall (WAF)," enable security protections.

<Frame>![Web Application Firewall (WAF) options with "Enable security protections" selected.](/_assets/501168e35b05a0040f70cc4a991299cf9b2b020ee43f63a0bd96bce44bdc53d1)</Frame>

<Note>WAF rules can block the `POST` requests that Mintlify uses for analytics and other interactive features. If analytics stop appearing in your dashboard after enabling WAF, check your WAF logs for blocked requests to paths under `/docs/_mintlify/`.</Note>

5. The remaining settings should be default.
6. Click **Create distribution**.

## Add default origin

1. After creating the distribution, navigate to the "Origins" tab.

<Frame>![A CloudFront distribution with the "Origins" tab highlighted.](/_assets/68d0451a54902c32b67168288aa874e6c3cd33f70faa8f2c0249d4ddfc11014a)</Frame>

2. Find your staging URL that mirrors the main domain. This varies depending on your landing page host. For example, the Mintlify staging URL is [mintlify-landing-page.vercel.app](https://mintlify-landing-page.vercel.app).

<Info>
  If Webflow hosts your landing page, use Webflow's staging URL. It would look like `.webflow.io`.

  If you use Vercel, use the `.vercel.app` domain available for every project.
</Info>

3. Create a new Origin and add your staging URL as the "Origin domain."

<Frame>![CloudFront "Create origin" page with a "Origin domain" input field highlighted.](/_assets/55edcca882b4223099a914e80837ebdb4bf6eb20db7c4bc9610b0b417da7903b)</Frame>

You should now have two Origins: one with `[SUBDOMAIN].mintlify.site` and another with your staging URL.

<Frame>![CloudFront "Origins" page with two origins: One for mintlify and another for mintlify-landing-page.](/_assets/709bdb525651128eb789a48d29e00130ba7bb7d3e63c82d4336fb57fdd5b65ab)</Frame>

## Set behaviors

Behaviors in CloudFront enable control over the subpath logic. At a high level, you create the following logic:

* **If a user lands on your custom subpath**, go to `[SUBDOMAIN].mintlify.site`.
* **If a user lands on any other page**, go to the current landing page.

1. Navigate to the "Behaviors" tab of your CloudFront distribution.

<Frame>![CloudFront "Behaviors" tab highlighted.](/_assets/7fe20c402e0c6fd3f72b962da86885f6984c9c1bf01b7fb452998d5008e6d385)</Frame>

2. Click the **Create behavior** button and create the following behaviors.

### `/.well-known/*`

Create behaviors for Vercel domain verification paths with a **Path pattern** of `/.well-known/*` and set **Origin and origin groups** to your docs URL.

For "Cache policy," select **CachingDisabled** to ensure these verification requests pass through without caching.

<Frame>![CloudFront "Create behavior" page with a "Path pattern" of "/.well-known/*" and "Origin and origin groups" pointing to the staging URL.](/_assets/8f675d6c4c6ddf9709aefe8acd1eeaaf77a708e003124c63e9dd885c5f705de8)</Frame>

<Info>
  If `.well-known/*` is too generic, you can narrow it down to 2 behaviors at a minimum for Vercel:

  * `/.well-known/vercel/*` - Required for Vercel domain verification
  * `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
</Info>

### Your subpath

Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.site` URL (for example, `acme.mintlify.site`).

* Set "Cache policy" to **CachingDisabled**.
* Set "Origin request policy" to **AllViewerExceptHostHeader**.
* Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**.
* Set "Allowed HTTP methods" to **GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE**.

<Warning>CloudFront only allows `GET` and `HEAD` requests by default. If you don't allow all HTTP methods, CloudFront rejects the `POST` requests that Mintlify uses for analytics, and your dashboard won't show any page views even though your docs load normally.</Warning>

<Frame>![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the acme.mintlify.site URL.](/_assets/bd794c8850674afc4ad6c33850cc81f20ccce1ce248cf28c0073344450f602dd)</Frame>

### Your subpath with wildcard

Create a behavior with a **Path pattern** of your chosen subpath followed by `/*`, for example `/docs/*`, and **Origin and origin groups** pointing to the same `.mintlify.site` URL.

These settings should exactly match your base subpath behavior, with the exception of the **Path pattern**.

* Set "Cache policy" to **CachingDisabled**.
* Set "Origin request policy" to **AllViewerExceptHostHeader**.
* Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**.
* Set "Allowed HTTP methods" to **GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE**.

### `/mintlify-assets/*`

Create a behavior with a **Path pattern** of `/mintlify-assets/*` with **Origin and origin groups** pointing to the `.mintlify.site` URL. This path serves the CSS, JavaScript, and favicons for your documentation from the root of your domain.

* Set "Cache policy" to **CachingOptimized**.
* Set "Origin request policy" to **AllViewerExceptHostHeader**.
* Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**.

### `/_mintlify/*`

Create a behavior with a **Path pattern** of `/_mintlify/*` with **Origin and origin groups** pointing to the `.mintlify.site` URL. This path handles API playground requests from the root of your domain.

* Set "Cache policy" to **CachingDisabled**.
* Set "Origin request policy" to **AllViewerExceptHostHeader**.
* Set "Viewer protocol policy" to **Redirect HTTP to HTTPS**.
* Set "Allowed HTTP methods" to **GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE**.

### `Default (*)`

Edit the `Default (*)` behavior.

<Frame>![A CloudFront distribution with the "Default (*)" behavior selected and the Edit button emphasized.](/_assets/15dcf049dff0893cfac1d80e78aa47a0d516085ecfcd990494bef6c63644763a)</Frame>

1. Change the default behavior's **Origin and origin groups** to the staging URL (for example, `mintlify-landing-page.vercel.app`).

<Frame>![CloudFront "Edit behavior" page with the "Origin and origin groups" input field highlighted.](/_assets/fea262e883d62fe20d498f124f5fdb091d5a87e0f9811e825cb145d992d1334f)</Frame>

2. Click **Save changes**.

### Check that you set up behaviors correctly

If you follow the preceding steps, your behaviors should look like this:

<Frame>![CloudFront "Behaviors" page with 4 behaviors: /docs/*, /docs, Default, and /.well-known/*.](/_assets/778eab4c78c667a479cdee462440788288772fee2713b4a190c30a6a6bf86623)</Frame>

## Preview distribution

To test your distribution, go to the "General" tab and visit the **Distribution domain name** URL.

<Frame>![CloudFront "General" tab with the "Distribution domain name" URL highlighted.](/_assets/9fa89bd7a0095966a1b5670610b429d5573d263c5d9e039ad5d9a2425a8c185c)</Frame>

All pages should route to your main landing page. When you append your chosen subpath, for example `/docs`, the URL should serve your Mintlify documentation.

## Connect with Route 53

Next, connect the CloudFront distribution to your primary domain.

<Note>For this section, you can also refer to AWS's official guide on [Configuring
Amazon Route 53 to route traffic to a CloudFront
distribution](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.html#routing-to-cloudfront-distribution-config).</Note>

1. Navigate to [Route53](https://aws.amazon.com/route53) inside the AWS console.
2. Navigate to the "Hosted zone" for your primary domain.
3. Click **Create record**.

<Frame>![Route 53 "Records" page with the "Create record" button emphasized.](/_assets/0c81da24a26945d69b4fd5df2b0c75146c285e82f87f3b0ceef11633c8d4268c)</Frame>

4. Toggle `Alias` and then **Route traffic to** the `Alias to CloudFront distribution` option.

<Frame>![Route 53 "Create record" page with the "Alias" toggle and the "Route traffic to" menu highlighted.](/_assets/8c9f174784d61ec09959959de93640b6f4654fa696bcf156d1839103ac753291)</Frame>

5. Click **Create records**.

<Note>You may need to remove the existing A record if one currently exists.</Note>

Your documentation is now live at your chosen subpath for your primary domain.

<Note>After you deploy your changes, your documentation is usually available at your subpath within a few minutes. If your setup includes DNS changes, propagation can take 1-4 hours, and in rare cases up to 48 hours. If your documentation is not immediately available, wait before troubleshooting.</Note>