AWS - Transit Gateway ,Static Routing In Transit Gateway Usecases Of Transit Gateway | Demo| Part-2
AWS - Transit Gateway ,Static Routing In Transit Gateway Usecases Of Transit Gateway | Demo| Part-2
Transit Gateway Attachments are the components that establish the connections between network resources and the Transit Gateway. They define the association between the Transit Gateway and various types of resources, such as Virtual Private Clouds (VPCs), VPN connections, or Direct Connect gateways.
Transit Gateway Attachments serve as the endpoints for traffic to enter or exit the Transit Gateway. By attaching resources to the Transit Gateway, you can enable communication between those resources using the Transit Gateway as a central hub.
Here are a few types of Transit Gateway Attachments:
VPC Attachment: This type of attachment allows you to connect VPCs to the Transit Gateway. By attaching a VPC, you enable communication between that VPC and other attached resources within the Transit Gateway. This eliminates the need for VPC peering relationships or VPN connections between each pair of VPCs.
VPN Attachment: A VPN Attachment allows you to connect a VPN connection to the Transit Gateway. This enables secure communication between on-premises networks or remote networks and the resources attached to the Transit Gateway.
Direct Connect Attachment: With a Direct Connect Attachment, you can connect a Direct Connect gateway to the Transit Gateway. This allows you to extend your on-premises network to the cloud and establish connectivity with the resources associated with the Transit Gateway.
Peering Attachment: Transit Gateway also supports peering attachments, which allow you to establish peering relationships between Transit Gateways in different AWS accounts. Peering attachments enable communication between VPCs attached to different Transit Gateways, providing a scalable and centralized solution for interconnecting multiple AWS accounts.
By utilizing Transit Gateway Attachments, you can create a hub-and-spoke network architecture, where the Transit Gateway acts as a central hub for communication between various resources. This simplifies network connectivity, improves scalability, and reduces the need for complex point-to-point connections.
Association: Association refers to the process of attaching network resources, such as Amazon Virtual Private Clouds (VPCs), VPN connections, or Direct Connect gateways, to a Transit Gateway. When you associate a network resource with a Transit Gateway, it allows traffic to flow between the associated resource and other resources within the transit gateway.
For example, if you associate multiple VPCs with a Transit Gateway, the VPCs can communicate with each other directly through the transit gateway, without the need for complex peering configurations.
Propagation: Propagation is the mechanism through which route information is shared across the Transit Gateway. When you propagate a route, it means you are instructing the Transit Gateway to distribute that route to the associated resources.
Each network resource associated with the Transit Gateway has its own routing tables. By propagating routes, you can ensure that the routing tables of the associated resources are populated with the appropriate routes, allowing traffic to flow correctly between them.
For example, if you have multiple VPCs associated with a Transit Gateway, you can propagate routes from one VPC to another. This enables VPCs to reach subnets in other VPCs via the Transit Gateway, without needing to create individual peering connections between each pair of VPCs.
#aws
#TransitGateway
#association
#propagation
#awsnetworking
#staticrouting