You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the documentation its mentioned that this parameter in Transit Gateway Configuration can be like the below. defaultRouteTablePropagation: enable or disable
When choosing enable, the pipeline is crashing in the middle as it is expecting a route table ID but its not mentioned where it should be provided.
Hi @ahammoud-murex ! Thank you for reaching out and utilizing the Landing Zone Accelerator on AWS (LZA) solution. I've tested out provisioning a TGW with this configuration and was unable to replicate:
In the documentation its mentioned that this parameter in Transit Gateway Configuration can be like the below.
defaultRouteTablePropagation: enable or disable
When choosing enable, the pipeline is crashing in the middle as it is expecting a route table ID but its not mentioned where it should be provided.
AWSAccelerator-NetworkPrepStack-99999999999-eu-west-1 | 0/3 | 4:17:25 PM | UPDATE_FAILED | AWS::EC2::TransitGateway | AWSTESTTgwTransitGateway (AWSTESTTRANSITGATEWAY) Resource handler returned message: "enable DefaultRouteTablePropagation conflicts with PropagationDefaultRouteTableId null (Service: Ec2, Status Code: 400, Request ID: f2a6e5bd-ea36-4947-9418-1666a8834d6c)" (RequestToken: 61ab64e4-e751-0266-45f4-2c78bb4dda3b, HandlerErrorCode: GeneralServiceException)
542 | new TransitGateway (/codebuild/output/src4133/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-ec2/transit-gateway.ts:503:22)
The text was updated successfully, but these errors were encountered: