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

r/aws_vpn_connection: Allow migration from VGW to TGW without recreating resource #8500

Closed
ewbankkit opened this issue May 2, 2019 · 6 comments · Fixed by #19311
Closed
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Milestone

Comments

@ewbankkit
Copy link
Contributor

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

As of AWS SDK v1.19.22 VPN Connections can be migrated from VGW to TGW w/o recreation:

This release adds an API for the modification of a VPN Connection, enabling migration from a Virtual Private Gateway (VGW) to a Transit Gateway (TGW), while preserving the VPN endpoint IP addresses on the AWS side as well as the tunnel options.

Requires:

@ewbankkit ewbankkit added the enhancement Requests to existing resources that expand the functionality or scope. label May 2, 2019
@ewbankkit
Copy link
Contributor Author

The ModifyVpnConnection API allows migration of:

  • An existing virtual private gateway to a new virtual private gateway
  • An existing virtual private gateway to a transit gateway
  • An existing transit gateway to a new transit gateway
  • An existing transit gateway to a virtual private gateway

@github-actions

This comment has been minimized.

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label May 7, 2021
@abohne
Copy link

abohne commented May 10, 2021

Any update?

@ghost ghost removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label May 10, 2021
@ewbankkit
Copy link
Contributor Author

Relates #11284.

@github-actions github-actions bot added this to the v3.72.0 milestone Jan 11, 2022
@github-actions
Copy link

This functionality has been released in v3.72.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
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 19, 2022
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants