route53-resolver-dns-firewall
This component is responsible for provisioning Route 53 Resolver DNS Firewall resources, including Route 53 Resolver DNS Firewall, domain lists, firewall rule groups, firewall rules, and logging configuration.
Usage
Stack Level: Regional
Here's an example snippet for how to use this component.
# stacks/catalog/route53-resolver-dns-firewall/defaults.yaml
components:
terraform:
route53-resolver-dns-firewall/defaults:
metadata:
type: abstract
settings:
spacelift:
workspace_enabled: true
vars:
enabled: true
firewall_fail_open: "ENABLED"
query_log_enabled: true
logs_bucket_component_name: "route53-resolver-dns-firewall-logs-bucket"
domains_config:
allowed-domains:
# Concat the lists of domains passed in the `domains` field and loaded from the file `domains_file`
# The file is in the `components/terraform/route53-resolver-dns-firewall/config` folder
domains_file: "config/allowed_domains.txt"
domains: []
blocked-domains:
# Concat the lists of domains passed in the `domains` field and loaded from the file `domains_file`
# The file is in the `components/terraform/route53-resolver-dns-firewall/config` folder
domains_file: "config/blocked_domains.txt"
domains: []
rule_groups_config:
blocked-and-allowed-domains:
# 'priority' must be between 100 and 9900 exclusive
priority: 101
rules:
allowed-domains:
firewall_domain_list_name: "allowed-domains"
# 'priority' must be between 100 and 9900 exclusive
priority: 101
action: "ALLOW"
blocked-domains:
firewall_domain_list_name: "blocked-domains"
# 'priority' must be between 100 and 9900 exclusive
priority: 200
action: "BLOCK"
block_response: "NXDOMAIN"
# stacks/mixins/stage/dev.yaml
import:
- catalog/route53-resolver-dns-firewall/defaults
components:
terraform:
route53-resolver-dns-firewall/example:
metadata:
component: route53-resolver-dns-firewall
inherits:
- route53-resolver-dns-firewall/defaults
vars:
name: route53-dns-firewall-example
vpc_component_name: vpc
Execute the following command to provision the route53-resolver-dns-firewall/example
component using Atmos:
atmos terraform apply route53-resolver-dns-firewall/example -s <stack>
Variables
Required Variables
domains_config
requiredMap of Route 53 Resolver DNS Firewall domain configurations
Type:
map(object({
domains = optional(list(string))
domains_file = optional(string)
}))region
(string
) requiredAWS Region
rule_groups_config
requiredRule groups and rules configuration
Type:
map(object({
priority = number
mutation_protection = optional(string)
# https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_resolver_firewall_rule
rules = map(object({
action = string
priority = number
block_override_dns_type = optional(string)
block_override_domain = optional(string)
block_override_ttl = optional(number)
block_response = optional(string)
firewall_domain_list_name = string
}))
}))vpc_component_name
(string
) requiredThe name of a VPC component where the Network Firewall is provisioned
Optional Variables
firewall_fail_open
(string
) optionalDetermines how Route 53 Resolver handles queries during failures, for example when all traffic that is sent to DNS Firewall fails to receive a reply.
By default, fail open is disabled, which means the failure mode is closed.
This approach favors security over availability. DNS Firewall blocks queries that it is unable to evaluate properly.
If you enable this option, the failure mode is open. This approach favors availability over security.
In this case, DNS Firewall allows queries to proceed if it is unable to properly evaluate them.
Valid values: ENABLED, DISABLED.Default value:
"ENABLED"
logs_bucket_component_name
(string
) optionalFlow logs bucket component name
Default value:
null
query_log_config_name
(string
) optionalRoute 53 Resolver query log config name. If omitted, the name will be generated by concatenating the ID from the context with the VPC ID
Default value:
null
query_log_enabled
(bool
) optionalFlag to enable/disable Route 53 Resolver query logging
Default value:
false
Context Variables
The following variables are defined in the context.tf
file of this module and part of the terraform-null-label pattern.
context.tf
file of this module and part of the terraform-null-label pattern.Outputs
domains
Route 53 Resolver DNS Firewall domain configurations
query_log_config
Route 53 Resolver query logging configuration
rule_group_associations
Route 53 Resolver DNS Firewall rule group associations
rule_groups
Route 53 Resolver DNS Firewall rule groups
rules
Route 53 Resolver DNS Firewall rules
Dependencies
Requirements
terraform
, version:>= 1.3.0
aws
, version:>= 4.9.0
Modules
Name | Version | Source | Description |
---|---|---|---|
iam_roles | latest | ../account-map/modules/iam-roles | n/a |
logs_bucket | 1.8.0 | cloudposse/stack-config/yaml//modules/remote-state | n/a |
route53_resolver_dns_firewall | 0.3.0 | cloudposse/route53-resolver-dns-firewall/aws | n/a |
this | 0.25.0 | cloudposse/label/null | n/a |
vpc | 1.8.0 | cloudposse/stack-config/yaml//modules/remote-state | n/a |
References
- Deploy centralized traffic filtering using AWS Network Firewall
- AWS Network Firewall – New Managed Firewall Service in VPC
- Deployment models for AWS Network Firewall
- Deployment models for AWS Network Firewall with VPC routing enhancements
- Inspection Deployment Models with AWS Network Firewall
- How to deploy AWS Network Firewall by using AWS Firewall Manager
- A Deep Dive into AWS Transit Gateway
- Appliance in a shared services VPC
- Quotas on Route 53 Resolver DNS Firewall
- Unified bad hosts
- cloudposse/terraform-aws-components - Cloud Posse's upstream component