DEV Community: theebikasri jagadees

Exploring AWS Transit Gateway

theebikasri jagadees — Tue, 15 Sep 2026 20:15:50 +0000

Theebikasri Meets Transit Gateway: Exploring AWS Transit Gateway
Introduction

Cloud computing has changed the way organizations build and manage their applications and infrastructure. Instead of maintaining all their servers and networking equipment physically, organizations can use cloud services provided by companies such as Amazon Web Services (AWS). As cloud environments become larger, organizations may have multiple networks, applications, departments and workloads that need to communicate with each other.

One AWS service designed to solve this networking challenge is AWS Transit Gateway. AWS Transit Gateway acts as a central networking hub that connects multiple Amazon Virtual Private Clouds (VPCs) and other supported networks. It helps organizations manage communication between different networks without having to create individual connections between every network.

In simple terms, AWS Transit Gateway can be compared to a central traffic controller. Instead of every network connecting directly to every other network, the networks can connect to the Transit Gateway, which manages where the traffic should go.

What is AWS Transit Gateway?

AWS Transit Gateway is a network service that provides a central connection point for multiple Amazon VPCs and other networks. It works as a regional virtual router that forwards traffic between connected networks based on routing information.

A VPC is an isolated virtual network created inside AWS. An organization may have different VPCs for different purposes. For example, one VPC may contain a web application, another may contain an AI/ML application and another may contain databases.

Without a central networking solution, connecting many VPCs can become difficult to manage. AWS Transit Gateway provides a centralized architecture where multiple VPCs can be attached to one Transit Gateway.

The networks connected to a Transit Gateway are called attachments. Transit Gateway supports VPC attachments as well as other connectivity options such as VPN connections, Direct Connect gateways, Transit Gateway Connect attachments and Transit Gateway peering.

AWS created Transit Gateway to simplify network connectivity and routing in environments containing multiple VPCs and networks.

How AWS Transit Gateway Works

The working of AWS Transit Gateway can be understood through a simple flow.

First, an organization creates a Transit Gateway in an AWS Region. After creating it, the required VPCs or other supported networks are connected to the Transit Gateway using attachments.

Next, routing needs to be configured. Transit Gateway uses Transit Gateway route tables to determine where network traffic should be forwarded. When traffic enters the Transit Gateway, it checks the destination IP address and uses the appropriate route to forward the traffic to the required network.

For example, suppose an organization has three VPCs: VPC A, VPC B, and VPC C. All three VPCs are connected to the Transit Gateway. If a resource in VPC A needs to communicate with a resource in VPC B, the traffic can travel from VPC A to the Transit Gateway. The Transit Gateway checks its routing information and forwards the traffic to the VPC B attachment.

For communication to work correctly, appropriate routes must also be configured in the VPC route tables. The Transit Gateway route table determines which attachment should receive the traffic.

Key Features of AWS Transit Gateway

Centralized Network Connectivity

One of the main features of AWS Transit Gateway is centralized network connectivity. Multiple VPCs can connect to a single Transit Gateway. This reduces the need to create and maintain many individual connections between VPCs.

For example, if an organization has separate VPCs for development, testing, production and databases, these networks can be connected through a central Transit Gateway.

Transit Gateway Route Tables

Transit Gateway uses route tables to control how traffic moves between its attachments. A route contains a destination and the attachment through which traffic should be forwarded.

For example:

Destination Target
10.1.0.0/16 VPC A
10.2.0.0/16 VPC B
10.3.0.0/16 VPC C

When traffic reaches the Transit Gateway, it checks the destination address and selects the appropriate route.

Transit Gateway also supports route propagation and route-table associations, which help administrators manage routing between different network attachments.

Multiple Network Attachments

Transit Gateway is not limited to connecting VPCs. It can also work with supported VPN connections, Direct Connect gateways, Transit Gateway Connect attachments and Transit Gateway peering.

This makes it possible to create hybrid network architectures where cloud resources can communicate with networks outside AWS.

For example, a college could have an existing campus network and AWS-based VPCs. With suitable connectivity and configuration, the campus network and AWS environment can communicate through the Transit Gateway architecture.

Network Isolation

Transit Gateway route tables can be used to control which networks can communicate with each other. Different groups of networks can be associated with different route tables.

For example, a college could separate its student project network from an administrative network. Routing can be configured so that only the required traffic is allowed between them.

This helps organizations design controlled network communication instead of allowing every connected network to communicate freely.

College/Student Use Case

AWS Transit Gateway can be useful in a college or university environment where different departments and projects use separate cloud networks.

Consider a college with an AI/ML department, a web development department, a research laboratory, and a student project environment. Each department could have its own VPC.

For example:

                   AWS Transit Gateway
                           |
         ┌─────────────────┼─────────────────┐
         |                 |                 |
         ▼                 ▼                 ▼
      AI/ML VPC       Student VPC       Research VPC
         |                 |                 |
     ML Projects       Web Projects     Research Data

Suppose an AI/ML project needs to access a dataset or service located in another VPC. Instead of creating separate connections between every VPC, the required VPCs can be attached to the Transit Gateway. Routing rules can then determine which networks are allowed to communicate.

This provides a practical example of how cloud networking could be organized across different departments and student projects.

Another use case is a college that has both an on-campus data center and cloud-based applications. A VPN or Direct Connect-based architecture can be used to connect the campus environment with AWS, while Transit Gateway provides centralized routing for connected AWS networks.

Simple Practical Example

Consider an organization with three VPCs:

VPC A = 10.1.0.0/16
VPC B = 10.2.0.0/16
VPC C = 10.3.0.0/16

The three VPCs are attached to an AWS Transit Gateway.

The Transit Gateway route table could contain routes such as:

Destination Target
10.1.0.0/16 VPC A attachment
10.2.0.0/16 VPC B attachment
10.3.0.0/16 VPC C attachment

Suppose a server in VPC A wants to communicate with a server in VPC B.

The communication flow would be:

Server in VPC A
↓
VPC A Route Table
↓
AWS Transit Gateway
↓
Transit Gateway Route Table
↓
VPC B Attachment
↓
Server in VPC B

This example demonstrates the basic purpose of Transit Gateway: receiving traffic from one connected network and routing it toward another connected network according to the configured routes.

Advantages of AWS Transit Gateway

AWS Transit Gateway provides several advantages for organizations managing multiple networks.

The first advantage is centralized management. Instead of managing a large number of separate network connections, administrators can use a central Transit Gateway.

The second advantage is scalability. As an organization adds more VPCs and networks, they can be connected to the existing Transit Gateway architecture.

The third advantage is simplified routing. Transit Gateway route tables provide a central place to manage routing between connected networks.

Another advantage is hybrid connectivity. Transit Gateway can be used with supported VPN and Direct Connect architectures to connect AWS environments with on-premises networks.

Transit Gateway can also be shared across AWS accounts using AWS Resource Access Manager, which can be useful for organizations that operate multiple AWS accounts.

Limitations and Things to Consider

Although AWS Transit Gateway simplifies large network architectures, there are several things to consider.

Cost

AWS Transit Gateway is a paid service. Charges can include costs for Transit Gateway attachments and data processing. Additional networking services used with Transit Gateway may also have their own charges. Therefore, users should monitor their AWS usage and remove resources that are no longer required.

Complexity

Transit Gateway simplifies connectivity but does not remove the need for networking knowledge. Users need to understand VPC route tables, IP addressing, attachments, routing, and network security.

Routing Configuration

Incorrect routing configurations can prevent communication between networks or cause traffic to travel through an unintended path. Route tables should therefore be planned carefully.

Security

Connecting networks does not automatically mean that every resource should be accessible. Security groups, network ACLs, firewalls, IAM permissions, and appropriate routing controls should be configured according to the application's requirements.

Regional Considerations

Transit Gateway operates as a regional networking service. Connecting networks across different AWS Regions requires additional architecture, such as Transit Gateway peering.

Cost

AWS Transit Gateway follows a usage-based pricing model. The cost depends on factors such as the number and type of attachments and the amount of data processed through the Transit Gateway.

For students using AWS for learning or projects, it is important to monitor the AWS Billing dashboard and remove unnecessary resources after completing practical experiments.

Before using Transit Gateway for a real application, users should check the current AWS pricing documentation because AWS pricing can change over time.

Security Considerations

Security is an important part of network design. Transit Gateway should not be treated as the only security mechanism.

Administrators should carefully configure VPC route tables, Transit Gateway route tables, security groups, network ACLs, and other security services where required.

Network isolation can also be implemented using Transit Gateway route tables. This allows administrators to control which attachments can exchange traffic.

For example, a student project VPC may need access to a research VPC but should not automatically have access to an administrative VPC. Routing can be designed to reflect these requirements.

Conclusion

AWS Transit Gateway is a cloud networking service that provides a central way to connect multiple VPCs and other supported networks. It works like a central router that receives network traffic and forwards it according to configured routing rules.

Its important features include centralized connectivity, Transit Gateway route tables, multiple attachment types, network isolation, and hybrid connectivity.

For a college environment, Transit Gateway can be useful when different departments, research laboratories, and student projects use separate cloud networks that need controlled communication.

Learning AWS Transit Gateway also helps students understand an important part of cloud computing: applications do not work independently. Different servers, databases, applications, and networks need to communicate with each other, and networking services such as Transit Gateway help create this communication structure.

For me, exploring AWS Transit Gateway provides an opportunity to understand the networking infrastructure behind cloud applications and how AWS can be used to build organized, scalable and controlled network environments.

References
AWS Documentation — What is AWS Transit Gateway?
https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html
AWS Documentation — How Transit Gateways Work
https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html
AWS Documentation — Amazon VPC Attachments for Transit Gateway
https://docs.aws.amazon.com/vpc/latest/tgw/tgw-vpc-attachments.html
AWS Documentation — Transit Gateway Route Tables
https://docs.aws.amazon.com/vpc/latest/tgw/tgw-route-tables.html
AWS — AWS Transit Gateway Pricing
https://aws.amazon.com/transit-gateway/pricing/

Day1:Session on AWS Infrastructure Foundation-EC2,S3 and networking

theebikasri jagadees — Tue, 15 Sep 2026 07:28:52 +0000

From S3 Static Hosting to a Global Website with CloudFront and Route 53

As part of my hands-on AWS learning, Day 1 focused on understanding the fundamentals of AWS infrastructure and deploying a static portfolio website using AWS services.

The session covered the following core concepts and services:

IAM — Identity and Access Management
EC2 — Elastic Compute Cloud
S3 — Simple Storage Service
AWS Networking fundamentals
Presigned URLs
CloudFront — Content Delivery Network
Route 53 — DNS and domain routing

The main hands-on activity was hosting my portfolio website using Amazon S3 and configuring CloudFront for global content delivery.

AWS Infrastructure Foundation

The session began with an introduction to AWS infrastructure and the role of different cloud services.

EC2 — Elastic Compute Cloud

Amazon EC2 provides virtual computing resources in the AWS Cloud. It can be used to run applications, backend services, websites, and other workloads that require computing power.

The session introduced the basic purpose of EC2 as a fundamental AWS compute service.

IAM — Identity and Access Management

IAM is used to manage identities and control access to AWS resources.

It helps define:

Who can access AWS resources
Which resources they can access
What actions they are allowed to perform

For the hands-on session, a temporary AWS user account was provided to access the required resources.

This gave me an understanding of how authentication and authorization are handled within AWS.

Amazon S3 — Simple Storage Service

The main practical activity started with Amazon S3.

Amazon S3 is an object storage service that can be used to store different types of data, including:

Images
Videos
Documents
Website files
Application data

For this session, I used S3 to store and host the files required for my portfolio website.

Creating an S3 Bucket

The first step was creating an S3 bucket.

S3 bucket names must be globally unique, meaning the same bucket name cannot already exist anywhere in AWS.

After creating the bucket, I also added tags using key-value pairs to help identify and organize the resource.

For example:

Key: Project
Value: Portfolio

Default Encryption

Next, I explored the default encryption configuration for the S3 bucket.

Encryption helps protect objects stored in S3 by encrypting the data at rest.

Understanding storage security is an important part of working with cloud infrastructure.

Presigned URLs

Another concept covered during the session was the use of presigned URLs.

A presigned URL provides temporary access to a specific S3 object without requiring the entire bucket to be made publicly accessible.

This can be useful when a file needs to be shared temporarily while keeping the underlying S3 resource protected.

Hosting a Portfolio Website Using S3

The main hands-on task was deploying my portfolio website.

I uploaded my index.html file to the S3 bucket.

The index.html file acts as the entry point for the static website.

Static Website Configuration

After uploading the website file, I configured the required settings under the Properties section of the S3 bucket.

The static website hosting configuration allows S3 to serve the HTML content as a website.

S3 Permissions and Bucket Policy

The next step involved configuring the access settings for the bucket.

Under the Permissions section, I worked with:

Block Public Access settings
Bucket Policy

These settings determine how users and AWS services can access the objects stored in the bucket.

Understanding permissions was an important part of the deployment because storage configuration and access control need to be considered together.

Deploying Through Amazon CloudFront

After configuring the S3 website, I used Amazon CloudFront for content delivery.

CloudFront is AWS's Content Delivery Network (CDN). It distributes content through a global network of edge locations so that content can be delivered from locations closer to users.

For the portfolio website, the basic architecture became:


text
User
  |
  v
CloudFront
  |
  v
Amazon S3
  |
  v
index.html

8. Route 53

The session also introduced **Amazon Route 53**, which is AWS's DNS service.

Route 53 can be used to manage domain names and route users to AWS resources such as CloudFront distributions.

The overall request flow can be represented as:

text
User
  |
  v
Route 53
  |
  v
CloudFront
  |
  v
Amazon S3
  |
  v
Portfolio Website


This helped me understand how DNS, content delivery, and storage services can work together as part of a web deployment.

9. Final Architecture

The complete architecture from this hands-on session can be summarized as:

                  User
                   |
                   v
                Route 53
              DNS Routing
                   |
                   v
               CloudFront
                  CDN
                   |
                   v
                Amazon S3
             Static Website
                   |
                   v
               index.html


Each service has a specific responsibility:

| Service    | Purpose                                 |
| ---------- | --------------------------------------- |
| IAM        | Identity and access management          |
| EC2        | Cloud computing                         |
| S3         | Object storage and static website files |
| CloudFront | Global content delivery                 |
| Route 53   | DNS and domain routing                  |

Key Takeaways

Day 1 session 1 helped me move from understanding individual AWS services to seeing how they can work together in a real deployment.

The most important concepts I learned were:

1. Creating and configuring an S3 bucket
2. Understanding globally unique S3 bucket names
3. Configuring default encryption
4. Understanding S3 permissions and bucket policies
5. Using presigned URLs for temporary object access
6. Hosting a static website using S3
7. Using CloudFront as a CDN
8. Understanding the role of Route 53 in DNS routing
9. Understanding the basic relationship between storage, DNS, and content delivery

The practical part of the session was particularly useful because I was able to take a simple `index.html` file and understand the steps involved in making it accessible through AWS infrastructure.


![ ](https://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/4m60phl9uhdykhdf1klt.png)

What's Next?

This session gave me a foundation for understanding AWS infrastructure and cloud-based application deployment.

Going forward, I want to explore how these foundational services connect with compute, databases, networking, security, and application deployment to build more complete cloud-based systems.

**Day 1 session 1 complete. More cloud infrastructure to explore.**

#AWS #AmazonS3 #CloudFront #Route53 #IAM #EC2 #CloudComputing #AWSCloud #DevOps #AIML #LearningInPublic