-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Can't associate VPCs in second account with non-default route table #27
Comments
Hey @2stacks, did you ever figure out this issue? Im bumping into the exact same problem. As you mentioned, the VPC attachment needs to be created in Account B but the association/propagation or routes need to be created in Account A. The module tries to create all resources in Account B and fails. Any help would be appreciated. |
I ended up forking the module and rewriting a lot of it. I don't know if
I'll have time to contribute upstream but perhaps I can answer any
questions you have.
…On Wed, Jun 2, 2021, 8:49 AM morp86 ***@***.***> wrote:
Hey @2stacks <https://github.com/2stacks>, did you ever figure out this
issue? Im bumping into the exact same problem.
As you mentioned, the VPC attachment needs to be created in Account B but
the association/propagation or routes need to be created in Account A. The
module tries to create all resources in Account B and fails.
Any help would be appreciated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADUNEHEOZE7YH2DYLI7VYHTTQYSEDANCNFSM4TXLRJUA>
.
|
Thanks for your quick reply. Id be mainly interested in the part you used to get the association / propagation working for attachments created in other accounts, if thats included in your code. If you wouldn't mind sharing your TGW code, I might be able to figure out / pull the parts I need. |
Quite a few people are reporting this issue (including myself) @antonbabenko @tfhartmann can you take a look here? Any help would be appreciated. |
Was there supposed to be a link? I plan to upload what I have for comment/collaboration. It's fairly opinionated so it may not make a good module but perhaps it can be used to improve the existing TGW module. |
To close the loop here. I ended rewriting allot of the code as well. The way to get around creating the resources in the wrong account is by adding an addition config block to you TGW module section. Section for TGW account: module "transit_gateway" { #Takes care of sharing the TGW resource to other accounts using AWS RAM. providers = { tags_name = "xxxxx" #Creates TGW in Networking account #Create route table association and propagation for Customer VPC attachments
#Module for attachment in customer account: module "account1234567890" { providers = { ram_resource_share_enabled = true config = { Hope this helps! |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
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. |
Versions
terraform = v0.13.5
aws provider = v3.2.0
transit-gateway module = 1.3.0
Module settings
Account A
Account B
For this to work, the VPC attachment needs to be created in Account B but the association/propagation or routes need to be created in Account A. The module tries to create all resources in Account B and fails.
Error messages;
The text was updated successfully, but these errors were encountered: