[BUG][Functional] Routes - Unable to add multiple static routes targeting the firewall

[joeldesaulniers]

Bug reports which fail to provide the required information will be closed without action.

Required Basic Info

• Accelerator Version: v1.3.8
• Install Type: Upgrade
• Upgrade from version: v1.1.7

Describe the bug When adding multiple static routes within a route table targetting the firewall, the State Machine fails.

Failure Info

• What error messages have you identified, if any: The error from Codebuild project PBMMAccel-DeployPrebuilt is: "Error: There is already a Construct with name ‘FirewallRouteTableName_eni_Proxy_b’ in AccountStack [PerimeterPhase2]".
• What symptoms have you identified, if any: The symptom is that the State Machine fails and the routes are not added to the Route Table.

Required files

• Please provide a copy of your config.json file (sanitize if required) - not provided, but the relevant code is as follows: { "name": "RouteTableName", "routes": [ { "destination": "10.10.10.0/24", "target": "firewall", "name": "Firewall", "az": "b", "port": "Proxy" }, { "destination": "10.10.11.0/24", "target": "firewall", "name": "Firewall", "az": "b", "port": "Proxy" } ] },

Steps To Reproduce Described above.

Expected behavior I expect the State Machine to complete and individual static route entries to be created in the Route Table. Each route entry is targetting the firewall.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

[Brian969]

• Validated as a bug
• Extend fix #743 to include firewall target types (on VPC route tables)
• review all other route types and ensure LID naming allows multiple targets/instances
• do not break existing customers - be creative in LID naming per ticket 743
• also see and fix related ticket #773

[fredbonin]

Fixed in this PR : https://github.com/aws-samples/aws-secure-environment-accelerator/pull/876

[archikierstead]

Will not implement