r/aws_dx_gateway_association: Allowed prefix support

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Direct Connect gateway associations now support configuration of allowed prefixes.
This functionality was added in AWS SDK v1.19.4:

... This release also enables Direct Connect Gateway owners to allocate allowed prefixes from each associated VPCs.

Related:

• Add support for Direct Connect Gateway #2140
• Add support for Direct Connect Gateway #4896
• Direct Connect gateway multi-account support #8100
• deps: github.com/aws/aws-sdk-go@v1.19.4 #8108

[ewbankkit]

Proposed syntax:

resource "aws_dx_gateway_association" "example" {
  dx_gateway_id  = "${aws_dx_gateway.example.id}"
  vpn_gateway_id = "${aws_vpn_gateway.example.id}"

  allowed_prefixes  = [
    "210.52.109.0/24",
    "175.45.176.0/22",
  ]
}

[bflad]

Support for this on the existing aws_dx_gateway_association resource has been merged and will release with version 2.8.0 of the Terraform AWS Provider, likely later this week.

[nywilken]

This has been released in version 2.8.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!