search

grem11n / terraform-aws-vpc-peering

Terraform module to setup VPC peering connection
https://registry.terraform.io/modules/grem11n/vpc-peering/aws/latest
Apache License 2.0
126 stars 91 forks source link

[BUG] VPC's that have IPv6 blocks don't have ipv6 routes setup. #114

Closed Unverified closed 4 months ago

Unverified commented 6 months ago

Disclaimer Please, check the examples directory in this repository. It contains code samples for some common use cases of this module. Also, CI uses this code to run automated tests. It may be that your use case is already present there.

Please, check the Important Notice section of README. It contains the description of known issues and workarounds as well as the compatibility matrix between Terraform versions and the versions of this module.

Describe the bug A clear and concise description of what the bug is.

If 2 VPC's are peered together that both have IPv6 CIDR's assigned to them no route gets generated for the IPv6 addresses. This will cause for AWS to effectively drop IPv6 traffic so services would be unable to connect to IPv6 endpoints across the peered connections.

Terraform version: What Terraform version do you use? 1.5.7

Module version: What module version do you use? 6.0.0

Error message: Please, provide an output of the error message you get. Http Timeout.

Terraform code that produces the error: Please, put your Terraform code here. If you don't want to disclose your code, please, describe your use case thoroughly.

Standard use case but with 2 vpc that are enabled for dual stack.

Unverified commented 6 months ago

I'm willing to contribute a fix for this, unsure if https://github.com/grem11n/terraform-aws-vpc-peering/pull/110 since depending on how this gets handled this would probably allow for people to update things easier.