[New Resources]: Default TGW association and propagation route table settings

[Michagogo]

Description

By default, a transit gateway is created with one route table, with new attachments being automatically set up to associate with that route table and to propagate routes to it. Each of those two behaviors can be suppressed at creation, and if both are disabled the route table is not created. After creation, it’s possible to turn that behavior on and off, with enabling it requiring the user to specify a route table ID. Splitting up the route table can be desirable for use cases such as forcing all traffic through a firewall, inspection appliance, etc. (by having the default association RT be one that sends everything to the central VPC, with the appliance then sending it back through the TGW, where that connection is the only one associated with the default propagation RT). There currently seems to be no way to achieve this in Terraform - the author of my team’s module resorted to taking a region and profile name as variables and making the changes using a null resource with local-exec provisioners to make AWS CLI calls.

Conceptually this would ideally be an argument to the TGW resource itself, but in practice that doesn’t seem likely to be possible because route tables are created in the context of a TGW so you couldn’t reference one on the resource itself.

Requested Resource(s) and/or Data Source(s)

aws_ec2_transit_gateway_default_{propagation,association}

Potential Terraform Configuration

resource "aws_ec2_transit_gateway_default_propagation" {
  transit_gateway_id = foo
  transit_gateway_route_table_id = bar
}

References

No response

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[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.