diff --git a/tech_docs/cloud/aws_studies.md b/tech_docs/cloud/aws_studies.md
index 81d2239..661e21a 100644
--- a/tech_docs/cloud/aws_studies.md
+++ b/tech_docs/cloud/aws_studies.md
@@ -1,3 +1,168 @@
+### AWS, Azure, and GCP Gateway Types: Comprehensive Overview
+
+---
+
+#### AWS Gateway Types
+
+**1. Internet Gateway (IGW)**
+
+**Purpose**: Enables instances in a VPC (Virtual Private Cloud) to connect to the internet.
+
+**Features**:
+- **Inbound and Outbound Traffic**: Facilitates inbound traffic from the internet to instances with public IPs and outbound traffic from instances to the internet.
+- **Elastic Scaling**: Automatically scales horizontally to accommodate your incoming and outgoing traffic requirements.
+- **High Availability**: A highly available, managed service that ensures reliability and uptime.
+- **Security**: Can be paired with Security Groups and Network ACLs for controlling and filtering traffic to instances.
+
+**Use Case**: Hosting public-facing applications such as web servers, where direct internet access is required.
+
+**Equivalent in Azure**: **Azure Internet Gateway**
+- Provides similar functionality to allow outbound internet access for virtual machines and services.
+
+**Equivalent in GCP**: **GCP Internet Gateway**
+- Functions similarly to enable internet access for Google Cloud resources.
+
+---
+
+**2. NAT Gateway**
+
+**Purpose**: Allows instances in a private subnet to connect to the internet or other AWS services without exposing the instances to incoming internet traffic.
+
+**Features**:
+- **Network Address Translation**: Manages the translation of private IP addresses to public IP addresses for outbound traffic.
+- **Scalability**: Automatically scales up to handle bursts of traffic.
+- **High Availability**: Highly available within a single Availability Zone.
+- **Cost-Effective**: You pay for the data transfer and the duration the gateway is running.
+
+**Use Case**: Providing internet access for software updates, patches, and other resources to instances in private subnets while maintaining security.
+
+**Equivalent in Azure**: **Azure NAT Gateway**
+- Offers outbound-only internet connectivity for virtual networks.
+
+**Equivalent in GCP**: **GCP Cloud NAT**
+- Provides similar outbound connectivity for instances without public IP addresses.
+
+---
+
+**3. VPC Peering**
+
+**Purpose**: Connects two VPCs so that they can communicate with each other as if they are within the same network.
+
+**Features**:
+- **Private IP Communication**: Enables communication using private IP addresses.
+- **Cross-Region Peering**: Supports inter-region VPC peering, allowing VPCs in different regions to communicate.
+- **No Single Point of Failure**: Does not rely on a single gateway or point, increasing reliability.
+
+**Use Case**: Connecting microservices, applications, or resources across different VPCs for enhanced modularity and security.
+
+**Equivalent in Azure**: **Azure VNet Peering**
+- Connects virtual networks within or across Azure regions.
+
+**Equivalent in GCP**: **GCP VPC Peering**
+- Allows VPCs to communicate within and across regions.
+
+---
+
+**4. Transit Gateway**
+
+**Purpose**: Connects VPCs and on-premises networks through a central hub, simplifying network management.
+
+**Features**:
+- **Centralized Hub**: Acts as a hub to connect multiple VPCs and on-premises networks, reducing the number of individual connections.
+- **Scalable and Highly Available**: Designed to handle large-scale network architectures with high availability.
+- **Inter-Region Support**: Facilitates communication across regions.
+- **Simplified Management**: Centralized management and monitoring of your network infrastructure.
+
+**Use Case**: Large organizations with complex network topologies requiring simplified and scalable interconnection between multiple VPCs and on-premises networks.
+
+**Equivalent in Azure**: **Azure Virtual WAN**
+- Provides a similar centralized hub for connecting different networks.
+
+**Equivalent in GCP**: **GCP Cloud Interconnect**
+- Offers connectivity between on-premises networks and Google Cloud.
+
+---
+
+**5. PrivateLink**
+
+**Purpose**: Allows secure, private connectivity between VPCs and AWS services without using public IPs.
+
+**Features**:
+- **Interface Endpoints**: Uses VPC endpoints to connect to AWS services privately.
+- **Intra-AWS Network**: Keeps traffic within the AWS network, enhancing security and reducing latency.
+- **Service Integration**: Integrates seamlessly with AWS services such as S3, API Gateway, and more.
+
+**Use Case**: Accessing AWS services securely from within a VPC, without exposing data to the public internet.
+
+**Equivalent in Azure**: **Azure Private Link**
+- Provides private access to Azure services over a private endpoint.
+
+**Equivalent in GCP**: **GCP Private Service Connect**
+- Offers private connectivity to Google services without using public IPs.
+
+---
+
+**6. Customer Gateway**
+
+**Purpose**: Connects an on-premises network to an AWS VPC through a Site-to-Site VPN.
+
+**Features**:
+- **VPN Concentrator**: Acts as a VPN concentrator on the customer side of a VPN connection.
+- **IPsec Protocol**: Uses the IPsec protocol for secure communication.
+- **Interoperability**: Compatible with many on-premises VPN devices and solutions.
+
+**Use Case**: Establishing a secure, encrypted connection between on-premises networks and AWS VPCs for hybrid cloud architectures.
+
+**Equivalent in Azure**: **Azure VPN Gateway**
+- Provides similar functionality to connect on-premises networks to Azure VNet.
+
+**Equivalent in GCP**: **GCP Cloud VPN**
+- Enables secure connections between on-premises networks and Google Cloud VPC.
+
+---
+
+**7. Virtual Private Gateway (VGW)**
+
+**Purpose**: Serves as the VPN concentrator on the AWS side of a Site-to-Site VPN connection.
+
+**Features**:
+- **Secure VPN Termination**: Terminates VPN connections and routes traffic between the VPC and the VPN connection.
+- **Redundancy**: Provides redundancy and high availability for VPN connections.
+- **Integration**: Integrates with AWS Direct Connect for dedicated network connections.
+
+**Use Case**: Facilitating secure VPN connections from on-premises networks to AWS for secure, reliable data transfer and communication.
+
+**Equivalent in Azure**: **Azure Virtual Network Gateway**
+- Functions similarly for terminating VPN connections in Azure.
+
+**Equivalent in GCP**: **GCP Cloud Router**
+- Works with Cloud VPN and Cloud Interconnect to route traffic.
+
+---
+
+**8. Storage Gateway**
+
+**Purpose**: Integrates on-premises IT environments with AWS storage infrastructure.
+
+**Features**:
+- **Multiple Configurations**: Supports file, volume, and tape gateway configurations to meet various storage needs.
+- **Hybrid Cloud Storage**: Provides seamless integration with AWS storage services like S3, Glacier, and EBS.
+- **Data Transfer**: Efficiently transfers data to and from AWS storage, enabling backup, disaster recovery, and data migration.
+
+**Use Case**: Hybrid cloud storage solutions for backup, disaster recovery, and extending on-premises storage capacities to AWS.
+
+**Equivalent in Azure**: **Azure StorSimple**
+- Hybrid cloud storage solution integrating on-premises and Azure storage.
+
+**Equivalent in GCP**: **GCP Transfer Appliance**
+- Provides data transfer services between on-premises environments and Google Cloud storage.
+
+---
+
+These gateways from AWS, Azure, and GCP provide robust solutions to a wide range of networking and data transfer needs, enabling users to build flexible, scalable, and secure architectures in the cloud. By leveraging these services, organizations can optimize their cloud infrastructure to meet specific business requirements across different cloud providers.
+
+---
+
 Certainly! Here's a recommended setup for working with CloudFormation templates on a Debian 12 workstation using Vim as your text editor, along with command-line tools and linters to ensure best practices:
 
 1. Install Vim: