Skip to content

fix(dcgw): add request to get the VPC ID for TGW #7568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cloudjumpercat merged 3 commits into from
Oct 20, 2026
Merged

fix(dcgw): add request to get the VPC ID for TGW #7568

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ee332c9
add request to get the vpc id
cloudjumpercat Oct 13, 2026
1d4b3c2
flip steps
cloudjumpercat Oct 14, 2026
3897ecd
Apply batched suggestions from code review
cloudjumpercat Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 30 additions & 26 deletions app/dedicated-cloud-gateways/transit-gateways.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,32 +53,21 @@

## AWS configuration for Transit Gateway peering

This process includes three main steps:

1. Create and share the [Transit Gateway in AWS](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html):

1. Navigate to **VPC > Transit Gateways** in the AWS Console.
1. Select **Create transit gateway**, provide a name, and create the gateway.
1. Save the Transit Gateway ID.
1. Open the **Resource Access Manager**, and select **Create Resource Share**.
1. Choose **Transit Gateways** as the resource type and select the newly created gateway.
1. Name the resource share and retain default managed permission settings.
1. Enable **Allow external accounts**, choose **AWS Account**, and enter the **AWS ID** from the {{site.konnect_short_name}} UI (**API Gateway > Networks**).
1. Create the resource share and save the resulting **RAM Share ARN**.

{:.warning}
> **RAM share requirements:**
> * The same Transit Gateway can be used in multiple networks, but they must be shared by different RAM shares.
> * Create a separate RAM share for each shared resource (do not include multiple resources in a single RAM share).

2. Accept the Transit Gateway Attachment in AWS:

1. Go to **VPC > Transit Gateway Attachments** in the AWS Console.
1. Locate the incoming attachment request from the {{site.konnect_short_name}} AWS Account ID.
1. Accept the request to establish the connection.
1. **Important:** Make sure a Transit Gateway Attachment is set up for each AWS VPC that needs to send or receive traffic.

Each AWS VPC that needs to send or receive traffic must have its own Transit Gateway attachment.
Create and share the [Transit Gateway in AWS](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html):

1. Navigate to **VPC > Transit Gateways** in the AWS Console.
1. Select **Create transit gateway**, provide a name, and create the gateway.
1. Save the Transit Gateway ID.
1. Open the **Resource Access Manager**, and select **Create Resource Share**.
1. Choose **Transit Gateways** as the resource type and select the newly created gateway.
1. Name the resource share and retain default managed permission settings.
1. Enable **Allow external accounts**, choose **AWS Account**, and enter the **AWS ID** from the {{site.konnect_short_name}} UI (**API Gateway > Networks**).
1. Create the resource share and save the resulting **RAM Share ARN**.

{:.warning}
> **RAM share requirements:**
> * The same Transit Gateway can be used in multiple networks, but they must be shared by different RAM shares.
> * Create a separate RAM share for each shared resource. **Do not** include multiple resources in a single RAM share.

## {{site.konnect_short_name}} configuration for Transit Gateway peering

Expand Down Expand Up @@ -128,6 +117,21 @@

1. In the AWS Console, go to **VPC > Transit Gateway Attachments**.
1. Wait for an attachment request from the Konnect AWS Account ID.
1. If you have more than one pending attachment request, look up each network's Kong-side AWS VPC ID. You can find the network ID by clicking **Networks** in the {{site.konnect_short_name}} sidebar:

{% capture network_vpc_id %}
<!--vale off-->
{% konnect_api_request %}
url: /v2/cloud-gateways/networks/$KONNECT_NETWORK_ID
status_code: 200
region: global
method: GET
{% endkonnect_api_request %}
<!--vale on-->
{% endcapture %}
{{ network_vpc_id | indent }}

Match the value in `provider_metadata.vpc_id` against the VPC ID shown for each pending attachment request in the AWS console.
1. Accept the request.

Ensure that each AWS VPC requiring traffic forwarding has its own Transit Gateway attachment.
Expand All @@ -153,4 +157,4 @@
* Ensure Network ACLs permit traffic between AWS VPCs and Kong DCGW.
1. Confirm connectivity by testing communication between your AWS VPC resources and Kong DCGW endpoints with `ping`, `telnet`, or `traceroute`).

Once the transit gateway attachment is successful and you've configured routing in your AWS VPC, add a route where the upstream services are running, and configure the route to forward all traffic for the {{site.konnect_short_name}} managed VPC via the transit gateway. This ensures that traffic from the {{site.konnect_short_name}} data plane reaches the service and the response packets are routed back correctly.

Check warning on line 160 in app/dedicated-cloud-gateways/transit-gateways.md

View workflow job for this annotation

GitHub Actions / Vale 

[vale] reported by reviewdog 🐶
[base.AvoidTemporalWords] Avoid time-relative wording ('Once the'). Docs go stale. Use 'after' or 'when' for sequence, and state the version or condition instead of what is current.

Raw Output:
{"message": "[base.AvoidTemporalWords] Avoid time-relative wording ('Once the'). Docs go stale. Use 'after' or 'when' for sequence, and state the version or condition instead of what is current.", "location": {"path": "app/dedicated-cloud-gateways/transit-gateways.md", "range": {"start": {"line": 160, "column": 1}}}, "severity": "INFO"}
Loading