Closed yannickvranckx closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
@yannickvranckx It looks like you are passing the TGW attachment ID instead of the TGW ID into transit_gateway_id
. Passing in aws_ec2_transit_gateway_vpc_attachment.sandbox.transit_gateway_id
should address the issue.
@yannickvranckx It looks like you are passing the TGW attachment ID instead of the TGW ID into
transit_gateway_id
. Passing inaws_ec2_transit_gateway_vpc_attachment.sandbox.transit_gateway_id
should address the issue.
This was the issue, can't believe I missed that one
The issue was the TGW ID being the attachment ID.
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
Using the terraform resource "aws_route" to add a route to a route table, it says the transit gateway attachment does not exist, while clearly being active in the account.
Code used:
It will just get stuck in "Still Creating" for about 2-3 minutes and then it will state that the attachment ID does not exist. While i can see it in the account and being active, using the AWS Console it just works.
References
No response
Would you like to implement a fix?
None