This repository has been archived by the owner on Feb 5, 2020. It is now read-only.
troubleshooting: private route53 zone configuration #154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
kbrwn
commented
Mar 19, 2018
kbrwn
commented
- This originally found here.
- This change has been tested on tectonic 1.8.9
…oute53 private zone
robszumski
previously approved these changes
Mar 19, 2018
zbwright
reviewed
Mar 19, 2018
| @@ -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 route53 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 route53 module with the `private_zone` parameter. | |||
There was a problem hiding this comment.
... a private Amazon Route 53 DNS zone ... Terraform Route 53 module ...
zbwright
reviewed
Mar 20, 2018
| @@ -65,7 +65,7 @@ This validates that the installer is able to establish a TCP connection with the | |||
|
|
|||
| * __module.dns.data.aws_route53_zone.tectonic: data.aws_route53_zone.tectonic: no matching Route53Zone found"__ | |||
|
|
|||
| Deploying to an private route53 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 route53 module with the `private_zone` parameter. | |||
| 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. | |||
There was a problem hiding this comment.
Deploying to a private ...
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.