Skip to main content
Version: 6.1.0

Structsure supports provisioning Route 53 for either intra-vpc, private DNS resolution, or public-facing DNS resolution.

Enabling and Configuring the Route 53 Terragrunt Module

The Route 53 Module is disabled by default. The following is an example that can be used to update the env.hcl file:

locals {
modules = {
route53 = true
}

route53_inputs = {
domain = "example.com"

# If given a list of VPCs, it will make the route 53 zone private
# and associate the zone with each VPC
vpc_ids = ["some-vpc-id"]

# Associates a wildcard record and points it at `app_nlb_dns_name`.
# `app_nlb_dns_name` defaults to the public-facing app load balancer created by the cluster module
# app_nlb_dns_name = "some_custom_load_balancer_DNS_name"

# Associates a record for Keycloak and Vault when the cluster module is configured
# to place those apps on the passthrough load balancer.
# `passthrough_nlb_dns_name` defaults to the public-facing passthrough load balancer created by the cluster module
# passthrough_nlb_dns_name = "some_custom_load_balancer_DNS_name"

# list of additional records to resolve
records = [
# Example:
# {
# # subdomain to resolve
# name = "your_app"
# # load balancer CNAME to resolve to
# record = "some_load_balancer.elb.us-east-2.amazonaws.com"
# },
]
}
}