Skip to content

Update custom-domain.mdx #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update custom-domain.mdx #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/custom-domain.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ If you are following our latest <DocLink id="quick-start" name="cookiecutter" />

## API Gateway

For API Gateway Lamby users, their Custom Domain Name featue is the only way to get <DocLink id="assets" /> working correctly by removing the stage path. You can optionally add a CloudFront distribution above this for edge caching. Custom Domain Name Steps:
For API Gateway Lamby users, their Custom Domain Name feature is the only way to get <DocLink id="assets" /> working correctly by removing the stage path. You can optionally add a CloudFront distribution above this for edge caching. Custom Domain Name Steps:

- [Secure Certificate with ACM](#secure-certificate-with-acm)
- [API Gateway Custom Domain Names](#api-gateway-custom-domain-names)
Expand Down Expand Up @@ -60,12 +60,12 @@ Basic reference steps for creating a CloudFront distribution. If you are editing
- Allowed HTTP Methods: GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE
- Cached HTTP Methods: ✔️ OPTIONS
- Cache key and origin requests:
- 🔘 Legacy cache settings:
- Legacy cache settings:
- Headers: Include the following headers
- Accept
- Query Strings: All
- Cookies: All
- 🔘 Use origin cache headers
- Use origin cache headers
- Settings:
- Price Class: Use only North America and Europe
- Alternate domain name (CNAME): myapp.example.com
Expand All @@ -77,7 +77,7 @@ Feel free to create an additional behavior for the `/assets` path using the `Cac

### Create a Route53 Record

From here all we need is a DNS entry in Route53 that points to our origin. Typically this would be to your CloudFront distribution. Like the one you may have created for your [Function URLs](#function-url) or your [API Gateway](#api-gateway] custom domain name.
From here all we need is a DNS entry in Route53 that points to our origin. Typically this would be to your CloudFront distribution. Like the one you may have created for your [Function URLs](#function-url) or your [API Gateway](#api-gateway) custom domain name.

- AWS Console -> Route 53 -> Hosted zones
- Click on your domain
Expand Down