Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ec2_transit_gateway_vpc_attachment: add support for "enable_appliance_mode" #16161

Closed
nckbnv opened this issue Nov 12, 2020 · 3 comments · Fixed by #16159
Closed

ec2_transit_gateway_vpc_attachment: add support for "enable_appliance_mode" #16161

nckbnv opened this issue Nov 12, 2020 · 3 comments · Fixed by #16159
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@nckbnv
Copy link
Contributor

nckbnv commented Nov 12, 2020

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 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
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS has just released a new type of load balancer named Gateway Load Balancer.
It supports three design options:

In order to prevent asymmetric routing between GLWB and TGW (so one session could always hit the proper firewall appliance) you need to enable Appliance mode in the transit gateway vpc attachment (as described in the Appliance VPC documentation)

This feature enhancement request is opened based on a suggestion by @bflad made in 16129.

New or Affected Resource(s)

  • ec2_transit_gateway_vpc_attachment

Potential Terraform Configuration

resource "aws_ec2_transit_gateway_vpc_attachment" "example" {
  subnet_ids         = [aws_subnet.example.id]
  transit_gateway_id = aws_ec2_transit_gateway.example.id
  vpc_id             = aws_vpc.example.id
  appliance_mode = true
}

References

@nckbnv nckbnv added the enhancement Requests to existing resources that expand the functionality or scope. label Nov 12, 2020
@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Nov 12, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 12, 2020
@bflad bflad removed the needs-triage Waiting for first response or review from a maintainer. label Nov 12, 2020
@bflad bflad linked a pull request Nov 12, 2020 that will close this issue
@bflad bflad added this to the v3.15.0 milestone Nov 12, 2020
@bflad bflad self-assigned this Nov 12, 2020
@bflad
Copy link
Contributor

bflad commented Nov 12, 2020

Support for this functionality has been merged and will release with version 3.15.0 of the Terraform AWS Provider, today or tomorrow. Thanks to @philnichol for the implementation. 👍

@ghost
Copy link

ghost commented Nov 12, 2020

This has been released in version 3.15.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 for triage. Thanks!

@ghost
Copy link

ghost commented Dec 12, 2020

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!

@ghost ghost locked as resolved and limited conversation to collaborators Dec 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants