ππ«ππ§π¬π’π πππππ°ππ² π’π§ πππ -
Transit Gateway acts like a switch hub or in other words "Star Topology".
Transit Gateway is similar to VPC peering whereas Transit Gateway enables connectivity with Onpremise. Firewall CIDR but VPC peering doesn't.
Consider you create a Transit Gateway in an AWS account- 1 and under AWS Organization account-1 you have child accounts 2,3,4,5 using Resource Access Manager you can share resources in AWS account -1 with other AWS child accounts, it is a global service.
Means Transit Gateway of one region can be connected with VPCs of other regions as well other AWS accounts.
The VPC attachment can be seen in the account where Transit Gateway was originally created. Maximum 4 Transit Gateway can be created per Account.
Each transit Gateway can have 5000 attachment.
Transit Gateway can be connected with Site to site VPN, Direct Connect.
When creating a Site to Site VPN we have to Choose Transit Gateway, we need to create a virtual private gateway ( enables connectivity from VPN to Onpremise)
We need to create a customer gateway ( input the information that pops up, ie the details you get from customer)
Static route - From VPN the destination is mentioned
Dynamic route - From VPN the destination could be reached via other routes as well.
Transit Gateway was earlier inter region specific later it's has changed to a global service
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)