-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
multi-account example does not work when using multiple AWS accounts #121
Comments
Same error |
i have the same issue. |
I had to add my peer vpc attachment separately and create the routes separately as well for this to work. main.tf
locals.tf
variables.tf
Hope it helps! |
This issue has been automatically marked as stale because it has been open 30 days |
ping |
This issue has been automatically marked as stale because it has been open 30 days |
ping |
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. |
Description
I am in the process of rolling out a transit gateway network with attached VPCs in multiple AWS accounts. I followed the example provided in the multi-account directory, but the TGW account side will fail with the following error:
NOTE: subnet id replaced by me for clarity
The subnet in question definitely does exist, but the provider used by the resources in the TGW account can not see it because it lives in the peer account.
Versions
Module version [Required]: 2.10.0
Terraform version: Terraform v1.3.9
Provider version(s):
Reproduction Code [Required]
Deploy the multi-account example with two different accounts by configuring the providers to use IAM roles in each account that have full administrative access to each account.
Our AWS infrastructure uses AWS Organizations so the administrative IAM role is named
OrganizationAccountAccessRole
, but any IAM role with sufficient access will do.For example:
Steps to reproduce the behavior:
Not using workspaces and cache was cleared
terraform init
andterraform apply
Expected behavior
The multi account example should work
Actual behavior
Fails with
NOTE: I replaced the actual subnet id with
<peer account subnet id>
to make the error message more understandableThe text was updated successfully, but these errors were encountered: