feat(router): support for static routes

[roleyfoley]

Description

Implements hamlet-io/engine#1331 for AWS

To implement this you need to create a couple of things

In the client account:

• An external service with the transitGateway Id set as the TRANSIT_GATEWAY_ID attribute
• A Gateway using the router engine with a link to this external service

This will attach the client VPC to the Transit Gateway

In the owner account:

• A router component
• An external service with the transitGateway Attachement from the client Id as TRANSIT_GATEWAY_ATTACHMENT attribute
• An IP address group which represents the client VPC Network
• A Static Router on the router which links to the external Service for the transit gateway attachment

Motivation and Context

Allows for transit gateways shared between two AWS accounts, the account who has received the transit gateway can only create attachments, routes, routeTables and propagation configuration can only be managed by the account which owns the gateway.

How Has This Been Tested?

Tested on local deployment

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves the structure or operation of the implementation)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Followup Actions

• None

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• None of the above.

[ml019]

Attachement -> Attachment?

[roleyfoley]

fixeded

[ml019]

Same here -maybe go through and global update?

[roleyfoley]

fixeded