Fully enable IPv6 in the VPC (as new opt-in variable) #5
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.
Hallo from Berlin 👋
I noticed that the VPC resource always has IPv6 on, and there's a variable to set
dualstack
on the ALB, but there were some pieces missing in the middle. Specifically the default route and security group ingress for IPv6 traffic.When I applied the module as-is, the ALB's AAAA records were created, but trying to connect to them just resulted in a timeout / no packets in response.
This PR adds a variable to preserve previous behavior by default, but any new users looking for dualstack will probably want to enable it. I'm not sure how dualstack would be used right now unless you update the routing manually after setting up this module.
In my fork I also added a couple ARN outputs and a variable for specifying the IPv4 newbits. I figured I'd submit this PR first and ask if the other variable and outputs make sense for a further PR.
Thanks for your module and time!