Demystifying OCI’s Virtual Cloud Network: A Deep Dive into VCN Architecture (Part 1)
AA Virtual Cloud Network (VCN) is the fundamental building block for networking in Oracle Cloud Infrastructure (OCI). It can be thought of as a virtual version of a traditional network that you’d operate in your own data center.
The benefits of using a VCN include:
Isolation– VCNs provide complete isolation from other virtual networks in the cloud. This allows you to have full control over your network environment.
Security– VCNs give you control over security through security lists and network security groups. You can restrict access within subnets as well as between subnets.
Customization– VCNs allow you to fully customize the network environment. You can define subnets, route tables, gateways, and other components to meet your specific needs.
Subnets– A subnet is a subdivision of a VCN that allows you to group related resources together. Subnets can be either public or private.
Route tables– Route tables control the flow of traffic out of a subnet. They specify the destinations that traffic can be routed to.
Security lists– Security lists act as virtual firewalls that control ingress and egress traffic at the subnet level.
Gateways– Gateways connect your VCN to external networks or other VCNs. Common gateways are internet gateways, NAT gateways, service gateways, and peering gateways.
Network security groups– NSGs provide subnet-level and instance-level security through stateful firewall rules.
By leveraging VCNs and their components, you can create a secure, robust, and customizable network environment tailored to your application and use case requirements.
Oracle VCN Architecture
Creating a Virtual Cloud Network
Log in to your Oracle Cloud account and Choose Networking > VirtualCloud Networks
Choose Networking > VirtualCloud Networks
Click on Start VCN Wizard
Click on Start VCN Wizard
Click VCN with Internet Connectivity then Click Start VCN Wizard
Click VCN with Internet Connectivity then Click Start VCN Wizard
Fill in the details as shown in the below images
VCN Name: OCI_HOL_VCN # Example Compartment: Demo # Example VCN CIDR Block: 10.0.0.0/16 # Example Public Subnet CIDR Block: 10.0.2.0/24 # Example Private Subnet CIDR Block: 10.0.1.0/24 # Example Use DNS Hostnames in this VCN: Checked
Then Click Next
Review the details you have filled then click on Create if the details are correct
It will create a VCN with the provided details
Now VCN is created and you can view it by clicking on View Virtual Cloud Network
Congratulations you have created VCN with 1 Public and 1 Private Subnet.
Public Subnets
Public subnets provide resources with access to and from the public internet via an internet gateway. Resources such as web servers, application servers, and load balancers that need to be accessible from the internet should be deployed in public subnets.
In today’s world, technology has become an integral part of our daily lives, and the way we work has been greatly revolutionized by the rise of cloud computing. One of the critical aspects of cloud computing is the ability to run applications and services in a virtualized environment. However, with the emergence of new technologies and trends, there are two popular approaches that have emerged, containerization and virtualization, and it can be confusing to understand the difference between the two. In this blog on Containerization vs Virtualization, we’ll explore what virtualization and containerization are, the key difference between virtualization and containerization, and the use cases they are best suited for. By the end of this article, you should have a better understanding of the two technologies and be able to make an informed decision on which one is right for your business needs. Here, we’ll discuss, – What is Containerization? – What is Virtualization? – Benefits of Con
This successful adoption of cloud technologies is attributed to scalability, security, faster time to market, and team collaboration benefits it offers. With this number increasing rapidly among companies at all levels, organizations are looking forward to the methods that help them: Eliminate platform complexities Reduce information leakage Minimize cloud operation costs To materialize these elements, organizations are actively turning to DevOps culture that helps them integrate development and operations processes to automate and optimize the complete software development lifecycle. In this blog post, we will discuss the step-by-step approach to cloud migration with DevOps. Steps to Perform Cloud Migration With DevOps Approach Automation, teamwork, and ongoing feedback are all facilitated by the DevOps culture in the cloud migration process. This translates into cloud environments that are continuously optimized to support your business goals and enable faster, more seamless migrat
The MongoDB operator is a custom CRD-based operator inside Kubernetes to create, manage, and auto-heal MongoDB setup. It helps in providing different types of MongoDB setup on Kubernetes like- standalone, replicated, and sharded. There are quite amazing features we have introduced inside the operator and some are in-pipeline on which deployment is going on. Some of the MongoDB operator features are:- Standalone and replicated cluster setup Failover and recovery of MongoDB nodes Inbuilt monitoring support for Prometheus using MongoDB Exporter. Different Kubernetes-related best practices like:- Affinity, Pod Disruption Budget, Resource management, etc, are also part of it. Insightful and detailed monitoring dashboards for Grafana. Custom MongoDB configuration support. [Good Read: Migration Of MS SQL From Azure VM To Amazon RDS ] Other than this, there are a lot of features are in the backlog on which active development is happening. For example:- Backup and Restore support TLS encryp
.webp "Virtual Cloud Network")
Comments
Post a Comment