Skip to content

Commit f6791ba

Browse files
Add AWS Amplify to vendor-specific-records
1 parent c13fcea commit f6791ba

File tree

1 file changed

+34
-7
lines changed

1 file changed

+34
-7
lines changed

src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx

Lines changed: 34 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ title: Vendor-specific DNS records
55

66
---
77

8-
import { Render } from "~/components"
8+
import { Render, GlossaryTooltip, Example } from "~/components"
99

10-
This article requires prior knowledge of DNS record management via the Cloudflare dashboard. To learn more, refer to Cloudflare's article on [managing DNS records](/dns/manage-dns-records/how-to/create-dns-records/).
10+
This article requires prior knowledge of DNS record management via the Cloudflare dashboard. To learn more, refer to Cloudflare's article on [managing DNS records](/dns/manage-dns-records/how-to/create-dns-records/).
1111

1212
## Google
1313

@@ -46,7 +46,7 @@ AWS customers must [update their domain's nameservers](https://docs.aws.amazon.c
4646

4747
Find the [URL](https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-bucket-intro.html) for your bucket.
4848

49-
Then, [create a `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) in Cloudflare. For example, if the full host URL of the bucket is `files.example.com.s3.amazonaws.com`, you would add a `CNAME` record similar to the following:
49+
Then, [create a `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) in Cloudflare. For example, if the full host URL of the bucket is `files.example.com.s3.amazonaws.com`, you would add a `CNAME` record similar to the following:
5050

5151
```txt
5252
files CNAME files.example.com.s3.amazonaws.com
@@ -58,14 +58,41 @@ For help setting up DKIM in SES, refer to the [Amazon documentation](https://doc
5858

5959
### Amazon ELB configuration
6060

61-
Refer to [Amazon's ELB help content](http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html) for guidance on ELB configuration at Amazon, but generally you should:
61+
Refer to [Amazon's ELB help content](http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html) for guidance on ELB configuration at Amazon, but generally you should:
6262

63-
Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cloudflare for the hostname you receive from AWS, for example:
63+
Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cloudflare for the hostname you receive from AWS, for example:
6464

65+
<Example>
6566
| Type | Name | Target | Proxy status |
6667
| ------- | ----- | -------------------------------------------- | ------------ |
6768
| `CNAME` | `elb` | `<AWS_HOSTNAME>.<REGION>._elb.amazonaws.com` | Proxied |
69+
</ Example>
6870

71+
### Amazon Amplify
72+
73+
To use Cloudflare DNS with AWS Amplify, refer to the [Amplify help content](https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html) and follow the instructions for **manual configuration**.
74+
75+
You will need at least two `CNAME` records:
76+
77+
- A <GlossaryTooltip term="proxy status">DNS-only</GlossaryTooltip> `CNAME` to validate your domain ownership, which should look like the following:
78+
79+
<Example>
80+
| Type | Name | Target | Proxy status | Flatten |
81+
| ------- | ----- | -------------------------------------------- | ------------ |---------|
82+
| `CNAME` | `<UNIQUE_STRING>.example.com` | `<UNIQUE_STRING>.mhbtsbpdnt.acm-validation.aws` | DNS only | False |
83+
</Example>
84+
85+
:::caution
86+
<Render file="cname-flattening-callout" />
87+
:::
88+
89+
- One `CNAME` for the <GlossaryTooltip term="apex domain">apex domain</GlossaryTooltip> and/or for each of the subdomains that you want to proxy through Cloudflare.
90+
91+
<Example>
92+
| Type | Name | Target |
93+
| ------- | ----- | -------------------------------------------- |
94+
| `CNAME` | `blog` | `<AMPLIFY_HOSTNAME>.cloudfront.net` |
95+
</Example>
6996
***
7097

7198
## Microsoft
@@ -76,9 +103,9 @@ For information about the records to Microsoft 365, refer to [Microsoft's docume
76103

77104
### Microsoft Azure
78105

79-
Follow Microsofts instructions on [configuring Azure DNS settings](https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain).
106+
Follow Microsoft's instructions on [configuring Azure DNS settings](https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain).
80107

81-
Then, add Azures required records to [Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/).
108+
Then, add Azure's required records to [Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/).
82109

83110
***
84111

0 commit comments

Comments
 (0)