Skip to content

Commit 258c6da

Browse files
authored
DOC-1335 AWS transit gateway (#316)
* DOC-1335 AWS transit gateway * typo * incorporate review feedback * style edits
1 parent f4287a2 commit 258c6da

3 files changed

Lines changed: 27 additions & 0 deletions

File tree

modules/ROOT/nav.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@
3131
**** xref:networking:byoc/aws/vpc-peering-aws.adoc[Add a Peering Connection]
3232
**** xref:networking:configure-privatelink-in-cloud-ui.adoc[Configure PrivateLink in the Cloud UI]
3333
**** xref:networking:aws-privatelink.adoc[Configure PrivateLink with the Cloud API]
34+
**** xref:networking:byoc/aws/transit-gateway.adoc[Add a Transit Gateway]
3435
*** xref:networking:byoc/azure/index.adoc[Azure]
3536
**** xref:networking:azure-private-link.adoc[]
3637
*** xref:networking:byoc/gcp/index.adoc[GCP]

modules/get-started/pages/whats-new-cloud.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ This page lists new features added to Redpanda Cloud.
99

1010
== June 2025
1111

12+
=== Amazon VPC Transit Gateway
13+
14+
For BYOC and BYOVPC clusters on AWS, you can set up an xref:networking:byoc/aws/transit-gateway.adoc[Amazon VPC Transit Gateway] to connect VPCs to Redpanda services while maintaining control over network traffic.
15+
1216
=== Support for additional regions
1317

1418
Serverless clusters now support the following new xref:reference:tiers/serverless-regions.adoc[regions on AWS]: ap-northeast-1 (Tokyo), ap-southeast-1 (Singapore), and eu-west-2 (London).
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
= Add Amazon VPC Transit Gateway
2+
:description: Use a transit gateway to connect your BYOC cluster to AWS VPCs or on-premises networks.
3+
4+
You can set up an https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html[Amazon VPC Transit Gateway^] to connect your internal VPCs to Redpanda services while maintaining full control over network traffic. The transit gateway acts as a central hub for routing traffic between VPCs, enabling communication between a Redpanda cluster and client applications hosted in different VPCs that can be in different AWS accounts.
5+
6+
AWS Transit Gateway is available for BYOC and BYOVPC clusters.
7+
8+
== Set up Amazon VPC Transit Gateway
9+
10+
To set up Amazon VPC Transit Gateway for Redpanda:
11+
12+
. Create a transit gateway in your AWS account.
13+
. Create transit gateway attachments to the VPC hosting Redpanda and the VPC that will communicate to Redpanda (where the producer or consumer resides).
14+
. Update the transit gateway route table with the new routes for transit gateway attachments.
15+
16+
For detailed instructions, see the https://docs.aws.amazon.com/vpc/latest/tgw/tgw-transit-gateways.html[AWS Transit Gateways documentation^].
17+
18+
== Example
19+
20+
The https://github.com/redpanda-data/cloud-examples/blob/9e2083e4bd8392e288ab6991b2a5a9b77a5fb0c5/aws-transit-gateway/README.md[Redpanda Cloud Examples repository^] provides sample Terraform code to set up and manage an Amazon VPC Transit Gateway for accessing Redpanda services across multiple VPCs. It includes steps for when the Redpanda cluster and client applications are hosted in the same AWS account and in different AWS accounts.
21+
22+
NOTE: Your implementation may differ depending on the networking configuration within your VPCs.

0 commit comments

Comments
 (0)