Closed vforvarun closed 3 months ago
Hi @vforvarun , thanks for reaching out to the Landing Zone Accelerator team.
The functionality you are describing is not currently supported in the LZA, though you should be able to solve this problem using native Transit Gateway functionality.
When creating the attachment between the VPC and TGW, you can utilize route propagation to automatically add the CIDR of the VPC as a new route to Transit Gateway route table(s).
This can be accomplished in the LZA config one of two ways:
enable
- this will automatically create propagated routes for new VPC attachments created on the Transit Gateway.
Describe the bug We are using IPAM to allocate IP ranges to VPC. While defining Transit Gateway Route tables, I need to provide the Workload accounts's IP address range as "destinationCidrBlock" which is not readily known because it is dynamically allocated by IPAM.
We can use known IP Address Ranges directly in route tables, but I can't seem to find a way in the documentation to refer dynamic IP ranges allocated by IPAM to VPCs in the route tables be it Transit Gateway or any other route tables.
To Reproduce Define a Route table and try to add a destinationCidrBlock which is dynamically allocated by IPAM.
Expected behavior Should be able to refer the IP Address range dynamically allocated by IPAM in route tables.
Please complete the following information about the solution:
Screenshots N/A
Additional context N/A