Skip to content

Commit f3c804a

Browse files
tweak byod docs
1 parent 909b963 commit f3c804a

File tree

1 file changed

+13
-18
lines changed

1 file changed

+13
-18
lines changed

docs/tutorials/use-your-own-domain-name.mdx

Lines changed: 13 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -3,25 +3,17 @@ title: How to Use Your Own Domain
33
sidebar_position: 600
44
---
55

6-
# How to Use Your Own Domain
7-
8-
In our latest version of [Defang BYOC](https://docs.defang.io/docs/concepts/defang-byoc) (Bring Your Own Cloud), you can now use your own domain name. (Currently, this new feature is not applicable to [Defang Playground](https://docs.defang.io/docs/concepts/defang-playground))
6+
# How to Use Your Own Domain with AWS
97

108
<iframe width="560" height="315" src="https://www.youtube.com/embed/n4RlMpsdTbs?si=_Ru6tobSbi9LT4Q1" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
119

10+
## Prerequisites
1211

13-
## Step 1 - Check your [Defang BYOC](../concepts/defang-byoc.md) settings
14-
15-
* Make sure you [install the latest version of the Defang CLI](../getting-started#install-the-defang-cli.md)
16-
* Then, make sure you have properly [authenticated your AWS account](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html). The Defang CLI makes use of AWS environment variables like `AWS_PROFILE`, `AWS_REGION`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY`, so make sure the correct values are set for those.
17-
18-
If you use the AWS CLI, you can verify that your are authenticated against AWS using the following command (note that the AWS CLI itself is not required to use the Defang CLI in BYOC mode):
19-
```bash
20-
aws sts get-caller-identity
21-
```
12+
* [A Defang Account](/docs/concepts/authentication)
13+
* [The Defang CLI](/docs/getting-started#install-the-defang-cli)
14+
* [AWS Account Credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html)
2215

23-
24-
## Step 2 - Setup a Hosted Zone in AWS Route 53
16+
## Step 1 - Setup a Hosted Zone in AWS Route 53
2517

2618
:::info
2719
**If you purchased your domain with AWS, you can skip this step.**
@@ -31,8 +23,7 @@ For Defang to be able to manage your domain, you need to create a [public hosted
3123

3224
<img src="/img/domains-tutorial/zone.png" alt="Hosted Zone UI Screenshot" style={{maxWidth: 650}} />
3325

34-
35-
## Step 3 - Configure your DNS settings in your domain registrar
26+
## Step 2 - Configure your DNS settings in your domain registrar
3627

3728
:::info
3829
**If you purchased your domain with AWS, you can skip this step.**
@@ -43,7 +34,7 @@ You'll need to create NS records in your domain registrar that point to the AWS
4334
![CloudFlare NS Records Screenshot](/img/domains-tutorial/ns-records.png)
4435

4536

46-
## Step 4 - Set up Your Compose File
37+
## Step 3 - Set up Your Compose File
4738
In your compose file, specify the domain name you want to use, for example
4839

4940
```yaml
@@ -59,7 +50,7 @@ services:
5950
```
6051
6152
62-
## Step 5 - Deploy
53+
## Step 4 - Deploy
6354
Run the following command to deploy your service:
6455
```bash
6556
defang compose up
@@ -68,3 +59,7 @@ defang compose up
6859
This will deploy your service and set up the necessary DNS records in Route 53 as seen in the screenshot below as well as provision SSL certificates. You can now access your service at the domain you specified in your compose file.
6960

7061
<img src="/img/domains-tutorial/route53-records.png" alt="Route 53 DNS Records Screenshot" />
62+
63+
***
64+
65+
For a deeper discussion of how to use a custom domain with Defang, see our [Domain](/docs/concepts/domains) concept docs.

0 commit comments

Comments
 (0)