Skip to content
This repository was archived by the owner on Feb 5, 2020. It is now read-only.

troubleshooting: private route53 zone configuration #154

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

troubleshooting: private route53 zone configuration #154

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
651b639
troubleshooting: add section about extra configuration when using a r…
Mar 19, 2018
63e3f67
troubleshooting: grammar fixes
kbrwn Mar 19, 2018
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
12 changes: 12 additions & 0 deletions Documentation/install/aws/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,18 @@ traceroute -T -p 443 <tectonic_cluster_name>.<tectonic_base_domain>

This validates that the installer is able to establish a TCP connection with the Tectonic ingress ELB. This will validate DNS, IP routing and firewall rules between the installer and the Tectonic ingress ELB.

* __module.dns.data.aws_route53_zone.tectonic: data.aws_route53_zone.tectonic: no matching Route53Zone found"__

Deploying to an private Amazon Route 53 DNS zone using the `tectonic_aws_external_private_zone` parameter can result in failure to dectect the zone by the installer. This can be resolved by configuring Terraform Route 53 module with the `private_zone` parameter.

```
# platform/aws/modules/dns/route53/tectonic.tf
data "aws_route53_zone" "tectonic" {
name = "${var.base_domain}"
private_zone=true
}
```

## Domain name can't be changed

The domain configured for Route 53 name service and the domain names selected for Tectonic and Controller DNS names during install cannot be easily changed later. If a cluster's domain name must change, set up a new cluster with the new domain name and migrate cluster work to it.
Expand Down