Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Transit Gateway and PrivateLink

This revision card explains Transit Gateway and PrivateLink. It starts from the need that mesh VPC peering explodes as account count grows; SaaS over internet adds risk. It describes transit Gateway is a hub for VPC/on-prem routing. PrivateLink exposes services via interface endpoints privately. The how-to section covers how to attach VPCs to TGW with separate route tables; create interface endpoints for AWS/SaaS APIs. An example on the card is ten app VPCs share one TGW; payments API consumed via PrivateLink, not public URL.

Transit Gateway and PrivateLink Mesh VPC peering explodes as account count grows; SaaS over internet adds risk. Transit Gateway is a hub for VPC/on-prem routing. PrivateLink exposes services via interface endpoints privately. Attach VPCs to TGW with separate route tables; create interface endpoints for AWS/SaaS APIs. Ten app VPCs share one TGW; payments API consumed via PrivateLink, not public URL
Transit Gateway and PrivateLink · Download PNG
Read card text

What this card says

Why do we need it?

Mesh VPC peering explodes as account count grows; SaaS over internet adds risk.

What is it?

Transit Gateway is a hub for VPC/on-prem routing. PrivateLink exposes services via interface endpoints privately.

TGW / PrivateLink

How to do it

Attach VPCs to TGW with separate route tables; create interface endpoints for AWS/SaaS APIs.

Example

Ten app VPCs share one TGW; payments API consumed via PrivateLink, not public URL.

See all AWS revision cards