From b1cabd20eebe627cd0c92116a957fa58e78bf0dc Mon Sep 17 00:00:00 2001 From: Harrison Ravazzolo <38767391+harrisonravazzolo@users.noreply.github.com> Date: Wed, 6 Nov 2024 12:01:04 -0600 Subject: [PATCH] Update deploy-fleet Guide (#23561) Adding a clarifying point to the AWS deploy docs. --------- Co-authored-by: Rachael Shaw --- docs/Deploy/deploy-fleet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Deploy/deploy-fleet.md b/docs/Deploy/deploy-fleet.md index b1771569a2..c5f611688e 100644 --- a/docs/Deploy/deploy-fleet.md +++ b/docs/Deploy/deploy-fleet.md @@ -125,7 +125,7 @@ This workflow takes about 30 minutes to complete and supports between 10 and 350 terraform apply -target aws_route53_zone.main ``` -9. From the Terminal output, obtain the NS records created for the zone and add them to the parent DNS zone in the AWS Route 53 GUI. +9. From the Terminal output, obtain the NS records created for the zone and add them to the parent DNS zone in the AWS Route 53 GUI. Ensure you're *adding* the subdomain and its NS records to the parent DNS, not changing the NS records for the parent. For example: if the subdomain is `fleet.acme.com` and the NS record is `ns-420.awsdns-52.com`, *add* this record to the parent domain. 10. Run the following command in Terminal: