OCI: Gateway Types and Network Routing Fundamentals Part-4
Internet Gateway (IGW)
An Internet Gateway acts as the door between your VCN (Virtual Cloud Network) and the public internet.
The Internet Gateway supports both inbound and outbound internet traffic.
By default, a compute instance deployed in a public subnet cannot access the internet unless:
An Internet Gateway is created and attached to the VCN.
The route table is configured to direct internet traffic through the Internet Gateway.
The instance has a public IP address assigned.
Oracle manages the availability, redundancy, and maintenance of the Internet Gateway internally.
Key Points
Used primarily for public subnets.
Enables inbound and outbound internet connectivity.
Requires proper route table configuration.
Instances typically need a public IP address to communicate through the Internet Gateway.
Network Address Translation (NAT) Gateway
A NAT Gateway provides internet access to private resources without making them publicly accessible.
If a server is deployed in a private subnet and needs to download operating system updates, RPM packages, application patches, or access external repositories, a NAT Gateway can be used.
The private subnet itself does not have direct internet connectivity. The NAT Gateway provides outbound internet access while keeping the instances private.
Key Points
Used by resources in private subnets.
Supports outbound internet traffic only.
Allows patch downloads, OS updates, and access to external repositories.
Public IP addresses are not required on private instances.
OCI automatically assigns a public IP address to the NAT Gateway itself.
Common Use Cases
Downloading operating system updates.
Downloading RPM packages.
Downloading Oracle patches.
Accessing external repositories and APIs.
Service Gateway (SGW)
A Service Gateway allows resources in a private subnet to access Oracle Cloud services without using the internet.
Service Gateways are created at the VCN level. During creation, you can choose whether the gateway should provide access only to Object Storage or to all supported Oracle services.
Examples of Services Accessed Through Service Gateway
Oracle Cloud Object Storage
Oracle Autonomous Database
Common Use Cases
Backing up databases to Object Storage.
Connecting to Autonomous Database.
Accessing Oracle-managed cloud services privately.
Before Service Gateway
Private instances access Object Storage through the Internet Gateway.
Traffic leaves the VCN and uses public endpoints.
NAT Gateway or public internet access may be required.
Security exposure is higher.
After Service Gateway
Private instances access Object Storage through the Service Gateway.
Traffic remains within Oracle's private backbone network.
No public IP address is required.
Security is improved, and network exposure is reduced.
Dynamic Routing Gateway (DRG)
A Dynamic Routing Gateway (DRG) is a virtual router that connects your OCI VCN to networks outside OCI.
DRG is commonly used to establish private connectivity between OCI and external environments.
Supported Connections
On-premises data centers
Another OCI region through Remote Peering
Other cloud providers such as AWS, Azure, and Google Cloud
Site-to-Site VPN connections
Key Points
Acts as a virtual router between OCI and external networks.
Enables private communication between OCI and on-premises environments.
Supports VPN and FastConnect connectivity.
Used for hybrid cloud architectures and multi-cloud deployments.
Common Use Cases
Connecting an on-premises data center to OCI.
Accessing Oracle E-Business Suite hosted in OCI from a corporate network.
Building hybrid cloud solutions.
Establishing connectivity between OCI regions.
Local Peering Gateway (LPG)
A Local Peering Gateway (LPG) is used to connect two Virtual Cloud Networks (VCNs) within the same OCI region so that resources in both VCNs can communicate using private IP addresses.
Types of VCN Peering
Local VCN Peering
Connects two VCNs within the same OCI region.
Remote VCN Peering
Connects two VCNs located in different OCI regions.
Example: For a Disaster Recovery (DR) setup, your primary database may be running in Region 1 while the DR database runs in Region 2. In such cases, Remote Peering is used.
Configuration
Create LPGs at the VCN level.
Local Peering Gateways (LPGs) work together with route tables.
Configure route tables in the respective subnets.
Allow the required ports in the corresponding Security Lists or Network Security Groups (NSGs).
Example
VCN-A → Application Servers (10.0.0.0/16)
VCN-B → Database Servers (192.168.0.0/16)
Without LPG, these VCNs cannot communicate directly.
By creating:
LPG-A in VCN-A
LPG-B in VCN-B
and establishing a peering connection, the application servers can securely access the database servers over Oracle's private network.
Key Features
Connects VCNs within the same OCI region.
Traffic stays on Oracle's private network.
No Internet Gateway is required.
No NAT Gateway is required.
Provides low-latency and secure communication.
Common Use Cases
Separate application and database VCNs.
Production and shared-services VCNs.
Hub-and-spoke network architectures.
Centralized monitoring or backup VCNs.
Gateway Type | Purpose |
|---|---|
| Internet Gateway (IGW) | Provides inbound and outbound internet access for public subnet resources |
| NAT Gateway | Provides outbound internet access for private subnet resources |
| Service Gateway | Provides private access to OCI services without using the internet |
| Dynamic Routing Gateway (DRG) | Provides private connectivity between OCI and external networks such as on-premises data centers, other OCI regions, and other cloud providers |
| Local Peering Gateway (LPG) | Provides private connectivity between two VCNs within the same OCI region |
| Remote Peering Connection (RPC) | Provides private connectivity between VCNs located in different OCI regions |
Related posts:
OCI: Cloud
Service Models OCI Basis Part-1
OCI:
Understanding Compartments, Users, and Groups in Oracle Cloud Infrastructure
(OCI) Part -2
Comments
Post a Comment