Add aws hub egress for network transit gateway#84
Open
ppanagiotis wants to merge 1 commit intomainfrom
Open
Conversation
frenchfrywpepper
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a reference Terraform module for customers who need centralized egress via Transit Gateway before deploying a BYOC cluster.
What it provisions:
Usage: Customer runs this module first, then supplies transit_gateway_id and ram_resource_share_arn at Redpanda cluster creation. All spoke egress traffic exits via the hub's
NAT Gateway — no per-VPC NAT Gateway required in the Redpanda spoke VPC.