Request - DNSSEC validation on the Route 53 Resolver in your VPC

[cageyv]

aws >= 3.24.0
hashicorp/terraform-provider-aws#17012
hashicorp/terraform-provider-aws#16837
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_resolver_dnssec_config

resource "aws_vpc" "example" {
  cidr_block           = "10.0.0.0/16"
  enable_dns_support   = true
  enable_dns_hostnames = true
}

resource "aws_route53_resolver_dnssec_config" "example" {
  resource_id = aws_vpc.example.id
}

Potential Module Configuration

module "vpc" {
  source = "terraform-aws-modules/vpc/aws"

  name = "my-vpc"
  cidr = "10.0.0.0/16"

  azs             = ["eu-west-1a", "eu-west-1b", "eu-west-1c"]
  private_subnets = ["10.0.1.0/24", "10.0.2.0/24", "10.0.3.0/24"]
  public_subnets  = ["10.0.101.0/24", "10.0.102.0/24", "10.0.103.0/24"]

  enable_nat_gateway = true
  enable_vpn_gateway = true
  
  enable_dnssec_resolver = true
 
  tags = {
    Terraform = "true"
    Environment = "dev"
  }
}

[github-actions]

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

[github-actions]

This issue was automatically closed because of stale in 10 days

[bryantbiggs]

hi @cageyv , this should be addressed in the next version which is under development here https://github.com/clowdhaus/terraform-aws-vpc-v4

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.