<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Patan Fardeen Khan on Medium]]></title>
        <description><![CDATA[Stories by Patan Fardeen Khan on Medium]]></description>
        <link>https://medium.com/@pathanfardeen555?source=rss-927328876901------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Patan Fardeen Khan on Medium</title>
            <link>https://medium.com/@pathanfardeen555?source=rss-927328876901------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:10:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pathanfardeen555/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Deploying Palo Alto Networks VM-Series Firewall on Oracle Cloud Infrastructure (OCI)]]></title>
            <link>https://medium.com/@pathanfardeen555/deploying-palo-alto-networks-vm-series-firewall-on-oracle-cloud-infrastructure-oci-54a66ba8a1c5?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/54a66ba8a1c5</guid>
            <category><![CDATA[oci-security]]></category>
            <category><![CDATA[oci-networking]]></category>
            <category><![CDATA[palo-alto-networks]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 13:01:23 GMT</pubDate>
            <atom:updated>2026-11-15T13:01:23.988Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_z4pvw6vMn--7HVEm5ZzA.png" /></figure><p>Security is one of the most important aspects of any cloud infrastructure. When deploying applications and managing workloads in the cloud, having a proper network security solution is essential.</p><p>Recently, as part of my hands-on work with Oracle Cloud Infrastructure (OCI), I deployed a Palo Alto Networks VM-Series firewall using the OCI Marketplace.</p><p>The deployment was part of a Disaster Recovery (DR) infrastructure setup. In this article, I am sharing the steps I followed to deploy the firewall, from selecting the Marketplace image to creating and verifying the compute instance.</p><h3>Step 1: Selecting the Firewall Image from OCI Marketplace</h3><p>I started by logging in to the OCI Console and navigating to the Marketplace.</p><p>I searched for Palo Alto Networks and selected the <strong>Palo Alto Networks VM-Series Bundle2–4 OCPUs</strong> image.</p><p>The Marketplace provides different software solutions that can be deployed directly on OCI compute instances.</p><p>Before proceeding, I reviewed the available package information, pricing model, and software version.</p><p>The selected image was based on the PAYGO (Pay As You Go) pricing model.</p><p>One thing to remember is that Marketplace software charges and OCI infrastructure charges are separate. It is important to review the estimated cost before deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FO4oJFIIxr-g-uz8Bz9AQg.png" /></figure><h3>Step 2: Launching the Marketplace Image</h3><p>After selecting the firewall image, I clicked on Launch Instance.</p><p>OCI displayed the publisher’s disclaimer and the terms and conditions.</p><p>I reviewed and accepted the required terms and selected the appropriate compartment for the deployment.</p><p>Once this was completed, OCI redirected me to the compute instance creation.</p><h3>Step 3: Configuring the Compute Instance</h3><p>In the instance creation wizard, I started with the basic configuration.</p><p>I provided an appropriate instance name and selected the required compartment.</p><p>For the compute shape, I selected <strong>VM.Standard.E5.Flex</strong>.</p><p>Flexible shapes are useful because they allow compute resources to be configured according to workload requirements.</p><p>I also selected the required Availability Domain for the deployment.</p><p>At this stage, I made sure the selected Marketplace image and compute configuration were appropriate for the firewall deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*f_zDBvilivLp9BsyX3h3kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dw6vyNcQQEw-k-JidQgZMA.png" /></figure><h3>Step 4: Configuring Network Settings</h3><p>Networking is one of the most important parts of deploying a virtual firewall.</p><p>For this deployment, I selected an existing Virtual Cloud Network (VCN) and its management subnet.</p><p>I used the existing network infrastructure instead of creating a new VCN during instance provisioning.</p><p>The primary VNIC was configured with a private IPv4 address.</p><p>I manually assigned the required private IP address from the available subnet range.</p><p>I did not assign a public IP address because the management interface was intended to be accessed through private network connectivity.</p><p>This approach helps avoid exposing the management interface directly to the internet.</p><p>Before deploying a firewall, it is important to understand the existing VCN, subnet, route table, security lists, and network security group configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*cqtvLoeqECqanX-vzkeDMw.png" /></figure><h3>Step 5: Configuring SSH Keys</h3><p>During the instance creation process, OCI provided different options for SSH key configuration.</p><p>The available options included:</p><ul><li>Generate a new SSH key pair.</li><li>Upload an existing public key.</li><li>Paste a public key.</li><li>Launch without SSH keys.</li></ul><p>I selected the option to generate a new SSH key pair.</p><p>I downloaded the generated private and public keys during the deployment process.</p><p>The private key should always be stored securely because it is required for SSH-based access when applicable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*Teextl4aeE_j8aVci9F41Q.png" /></figure><h3>Step 6: Configuring the Boot Volume</h3><p>Next, I configured the boot volume for the firewall instance.</p><p>For this deployment, I selected the following settings:</p><ul><li>Boot Volume Size: 100 GB</li><li>Boot Volume Performance: 10 VPU</li><li>Expected IOPS: 6,000</li><li>Throughput: 48 MB/s</li><li>Performance Type: Balanced</li></ul><p>The boot volume contains the operating system and the software image required to run the instance.</p><p>It is important to select appropriate storage settings based on the workload and the requirements of the selected Marketplace image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*ZrEzzNujQqUaZS_JNbnh3g.png" /></figure><h3>Step 7: Reviewing and Creating the Instance</h3><p>Before creating the instance, I reviewed the complete configuration.</p><p>I verified the following:</p><ul><li>Instance configuration</li><li>Selected Marketplace image</li><li>Compute shape</li><li>Availability Domain</li><li>Network and subnet selection</li><li>Private IP assignment</li><li>SSH key configuration</li><li>Boot volume settings</li></ul><p>After reviewing everything, I clicked Create.</p><p>OCI started provisioning the compute instance using the selected Palo Alto Networks VM-Series image.</p><p>Initially, the instance appeared in the Provisioning state.</p><p>After the provisioning process was completed, the instance status changed to Running.</p><h3>Step 8: Verifying the Deployment</h3><p>Once the instance was running, I opened the instance details page and navigated to the Networking tab.</p><p>I verified that the primary VNIC was attached to the expected subnet and that the private IP address had been assigned successfully.</p><p>I also checked the associated route table and confirmed that no public IPv4 address had been assigned.</p><p>This confirmed that the compute instance was successfully created and attached to the intended network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*Y3DjK1hu3Rr66tH56of9RQ.png" /></figure><h3>Important Points to Consider</h3><p>Based on this deployment experience, here are a few things worth checking when deploying Palo Alto Networks VM-Series on OCI:</p><p><strong>1. Network Configuration</strong></p><p>Make sure the VCN, subnet, route tables, and security rules are properly configured.</p><p><strong>2. Management Access</strong></p><p>Plan how administrators will securely access the firewall management interface. Private connectivity through VPN or an approved management network is recommended.</p><p><strong>3. Firewall Licensing</strong></p><p>Review the Marketplace licensing model and complete the required firewall licensing and activation steps.</p><p><strong>4. Compute Resources</strong></p><p>Choose a suitable compute shape based on the firewall image requirements and expected workload.</p><p><strong>5. Routing Configuration</strong></p><p>Proper routing is essential to ensure that network traffic follows the intended path through the firewall.</p><p><strong>6. High Availability</strong></p><p>For production environments, consider the appropriate high-availability architecture and failover requirements.</p><h3>Conclusion</h3><p>Deploying the Palo Alto Networks VM-Series firewall through OCI Marketplace was a useful hands-on experience.</p><p>I was able to work through the complete instance provisioning process, including Marketplace image selection, compute configuration, network attachment, private IP assignment, SSH key configuration, and boot volume setup.</p><p>This activity also helped me gain more practical experience with OCI Marketplace, compute services, VCN networking, and cloud security infrastructure.</p><p>There is more to explore beyond instance provisioning, particularly firewall management, routing, security policies, and traffic inspection.</p><p>I look forward to continuing my learning and sharing more practical experiences from Oracle Cloud Infrastructure.</p><p><strong>Technologies and Services Used</strong></p><ul><li>Oracle Cloud Infrastructure (OCI)</li><li>OCI Marketplace</li><li>Palo Alto Networks VM-Series Firewall</li><li>OCI Compute</li><li>Virtual Cloud Network (VCN)</li><li>Subnets and Route Tables</li><li>Virtual Network Interface Cards (VNIC)</li><li>SSH Key Authentication</li></ul><p><strong>Author:</strong> Patan Fardeen Khan</p><p>#OracleCloud #OCI #OracleACE #PaloAltoNetworks #CloudSecurity #NetworkSecurity #CloudNetworking #DisasterRecovery</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a66ba8a1c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring an OCI Service Gateway for a Disaster Recovery Network]]></title>
            <link>https://medium.com/@pathanfardeen555/configuring-an-oci-service-gateway-for-a-disaster-recovery-network-48e742d8fd4a?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/48e742d8fd4a</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[oci-service-gateway]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 11:35:41 GMT</pubDate>
            <atom:updated>2026-11-10T12:35:59.691Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>As part of preparing a Disaster Recovery (DR) network in Oracle Cloud Infrastructure (OCI), I worked on configuring a Service Gateway to enable private connectivity between the VCN and supported Oracle Cloud services.</p><p>The objective was to prepare the network for accessing regional OCI services without requiring traffic to traverse the public internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*37mrJLaclBnF1yyPH6sJhg.png" /></figure><p>In this article, I’ll share the Service Gateway creation process, the associated networking considerations, and an interesting routing issue I encountered during the configuration.</p><h3>1. Understanding the Service Gateway</h3><p>An OCI Service Gateway provides private access from a Virtual Cloud Network (VCN) to supported Oracle services within the same region.</p><p>One of its main advantages is that resources in private subnets can access supported Oracle services without requiring public IP addresses or routing traffic through the public internet.</p><p>For example, a private compute instance can access supported Object Storage endpoints through the Oracle network.</p><h3>2. Preparing the Service Gateway</h3><p>Before creating the gateway, I reviewed the existing DR VCN and its networking configuration.</p><p>The environment already had the following components:</p><ul><li>Virtual Cloud Network</li><li>Public and private subnets</li><li>Internet Gateway</li><li>NAT Gateway</li><li>Custom route tables</li><li>Custom security lists</li></ul><p>The Service Gateway was the next component in the network preparation process.</p><h3>3. Creating the Service Gateway</h3><p>I created the Service Gateway manually through the OCI Console.</p><p>The configuration included:</p><ul><li><strong>Name:</strong> Generic DR Service Gateway</li><li><strong>Compartment:</strong> Network</li><li><strong>Services:</strong> All regional services in the Oracle Services Network</li></ul><p>For the service selection, I chose the regional Oracle Services Network option.</p><p>The gateway was created successfully and became available in the VCN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Al84zIaAd-JomN36vtiALg.png" /></figure><h3>4. Understanding Route Table Configuration</h3><p>Creating a Service Gateway alone does not automatically enable traffic to pass through it.</p><p>The relevant subnet route tables must contain a route rule with:</p><ul><li><strong>Target Type:</strong> Service Gateway</li><li><strong>Destination Service:</strong> Regional Oracle Services Network</li><li><strong>Target:</strong> The newly created Service Gateway</li></ul><p>Only subnets whose route tables contain the required rule can use the Service Gateway for the corresponding service traffic.</p><p>This is an important part of the implementation that should not be overlooked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9IL8e77ymou3SuLkOQcjA.png" /></figure><h3>5. A Routing Conflict I Encountered</h3><p>While adding the Service Gateway route, I encountered an OCI API error.</p><p>The route table already contained a default route pointing to the Internet Gateway:</p><p>0.0.0.0/0 → Internet Gateway</p><p>When I attempted to add the All Services in Oracle Services Network destination through the Service Gateway to the same route table, OCI rejected the configuration.</p><p>The error indicated that an Internet Gateway target cannot be used together with a Service Gateway target for All Services in the same route table.</p><p>This was an important practical learning point.</p><p>Instead of removing the existing internet route without reviewing its impact, I paused the change to confirm the appropriate routing design.</p><p>The routing requirements need to account for the existing public and private subnet paths and the intended use of the Service Gateway.</p><h3>6. Security List Considerations</h3><p>Alongside gateway creation, I reviewed the security-list configuration.</p><p>Security lists control the ingress and egress traffic permitted for resources within a subnet.</p><p>For Service Gateway connectivity, the security rules must permit the required traffic to the Oracle Services Network.</p><p>A Service Gateway does not replace security-list rules or route-table configuration. All three components must work together:</p><ul><li>Service Gateway</li><li>Route table</li><li>Security rules</li></ul><p>Security rules should follow the required application ports and approved network access policies.</p><h3>7. Key Takeaways</h3><p>This activity reinforced a few important OCI networking concepts:</p><ul><li>A Service Gateway provides private access to supported regional Oracle services.</li><li>Creating the gateway does not automatically configure subnet routing.</li><li>Each subnet requires an appropriate route-table rule to use the gateway.</li><li>Security lists must permit the required traffic.</li><li>Existing Internet Gateway and NAT Gateway routes must be considered when designing Service Gateway routing.</li><li>OCI route validation should be completed before making changes to existing production network paths.</li></ul><h3>Conclusion</h3><p>The Service Gateway was successfully created through the OCI Console as part of the DR network preparation.</p><p>During the route configuration, I encountered a restriction involving the coexistence of an All Services Service Gateway route and an Internet Gateway route in the same route table.</p><p>Rather than changing existing routes without validation, I kept the routing change under review for confirmation of the intended network design.</p><p>This activity provided useful hands-on experience with OCI Service Gateway configuration and highlighted the importance of understanding route-table dependencies before implementing network changes.</p><p>Further DR networking activities, including DRG integration and firewall deployment, will be covered in subsequent articles.</p><p>#OracleCloudInfrastructure #OCI #ServiceGateway #CloudNetworking #DisasterRecovery #OracleACE</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48e742d8fd4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an OCI Disaster Recovery Network Foundation Using Terraform]]></title>
            <link>https://medium.com/@pathanfardeen555/building-an-oci-disaster-recovery-network-foundation-using-terraform-30ee118c0665?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/30ee118c0665</guid>
            <category><![CDATA[oci-networking]]></category>
            <category><![CDATA[oraclecloudinfrastructure]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 11:20:06 GMT</pubDate>
            <atom:updated>2026-11-10T11:20:06.207Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>While working on a Disaster Recovery (DR) infrastructure preparation activity in Oracle Cloud Infrastructure (OCI), I had the opportunity to build the initial networking foundation using Terraform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-6xxRqdFKItrEQ6TkBdIPA.png" /></figure><p>The objective was to prepare a separate network environment for DR workloads, organize the network into multiple subnets, and provision the required networking components through Infrastructure as Code (IaC).</p><p>In this article, I’ll walk through the approach, the resources created, and a few practical things I learned during the deployment.</p><h3>1. Understanding the Network Design</h3><p>Before starting the Terraform configuration, I reviewed the existing network architecture and identified the subnet requirements for the DR environment.</p><p>The VCN was planned with a private IPv4 CIDR range and divided into six subnets based on their intended roles.</p><p>The subnet design covered:</p><ul><li>Load Balancer</li><li>Management</li><li>Trust</li><li>SD-WAN Public</li><li>SD-WAN Core</li><li>SD-WAN Controller</li></ul><p>Separating these network components into individual subnets makes it easier to manage routing, security policies, and future firewall integration.</p><h3>2. Provisioning Resources Using Terraform</h3><p>Rather than creating every resource manually through the OCI Console, I used Terraform to automate the deployment.</p><p>The configuration included:</p><ul><li>OCI provider configuration</li><li>Existing VCN reference</li><li>Internet Gateway</li><li>NAT Gateway</li><li>Six route tables</li><li>Six security lists</li><li>Six subnets</li></ul><p>I used Terraform variables and local definitions to keep the configuration organized and avoid repeating similar resource definitions.</p><h3>3. Internet Gateway and NAT Gateway</h3><p>Two important networking components were provisioned as part of the initial setup.</p><p><strong>Internet Gateway</strong></p><p>The Internet Gateway provides a path for communication between the VCN and the public internet when the applicable routing and security rules permit it.</p><p><strong>NAT Gateway</strong></p><p>The NAT Gateway supports outbound internet connectivity for resources in private subnets without requiring those resources to have public IP addresses.</p><p>OCI automatically assigned a public IP address to the NAT Gateway during creation. There was no need to manually assign a public IP to the gateway.</p><h3>4. Route Tables and Security Lists</h3><p>I created separate route tables and security lists for the six subnets.</p><p>The initial routing design included:</p><ul><li>Internet Gateway routes for designated public subnets.</li><li>NAT Gateway routes for designated private subnets.</li></ul><p>Security lists were configured with outbound traffic rules, and ingress rules were subsequently added according to the approved network requirements.</p><p>Keeping these configurations separate for each subnet provides flexibility when implementing more detailed network security and traffic-control policies.</p><h3>5. Terraform Validation</h3><p>Before provisioning the resources, I performed the standard Terraform initialization and validation steps.</p><p><strong>terraform init<br>terraform fmt<br>terraform validate<br>terraform plan</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*LQjv3iXAzTe4UdPHiQf5kg.png" /></figure><p>After reviewing the execution plan, I applied the configuration:</p><p><strong>terraform apply</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*EVohXWAIcSMCFOqBX3IzYg.png" /></figure><p>The deployment completed successfully:</p><p><strong>20 resources added, 0 changed, 0 destroyed.</strong></p><p>The resources included the gateways, route tables, security lists, and six subnets.</p><h3>6. Verifying the Deployment</h3><p>After deployment, I verified the resources through Terraform state:</p><p><strong>terraform state list</strong></p><p>I also used the OCI CLI to confirm that the subnets were created successfully and had reached the AVAILABLE lifecycle state.</p><p>This verification was useful because a successful Terraform apply should always be followed by checking the actual state of the provisioned cloud resources.</p><p><strong>Figure : Verifying all six subnet deployments in OCI Console.</strong></p><p>The OCI Console confirms that all six regional subnets were successfully provisioned and reached the Available state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*brVPJ9LqTg6Gf61LJvqI2w.png" /></figure><h3>7. Practical Learnings</h3><p>A few important takeaways from this activity:</p><ul><li>Terraform makes repeatable OCI network deployments easier to manage.</li><li>Subnet planning should be completed before provisioning resources.</li><li>Separate route tables provide greater control over network traffic.</li><li>NAT Gateway allows private resources to access external services without public IP addresses.</li><li>Terraform state and OCI CLI are useful together for deployment verification.</li><li>Network routing and security rules should be reviewed before connecting production workloads.</li></ul><h3>Conclusion</h3><p>The initial DR network foundation was successfully provisioned using Terraform.</p><p>This activity provided practical experience in OCI networking, Infrastructure as Code, subnet planning, gateway configuration, and deployment validation.</p><p>The next stage involves configuring the Service Gateway, integrating the existing DRG, and preparing the network for firewall deployment.</p><p>I’ll cover those activities separately in the upcoming articles.</p><p>#OracleCloudInfrastructure #OCI #Terraform #CloudNetworking #DisasterRecovery #InfrastructureAsCode #OracleACE</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30ee118c0665" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring Site-to-Site IPSec VPN Connectivity Between OCI DR Riyadh and an On-Premises Network]]></title>
            <link>https://medium.com/@pathanfardeen555/configuring-site-to-site-ipsec-vpn-connectivity-between-oci-dr-riyadh-and-an-on-premises-network-6fc4dc878601?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fc4dc878601</guid>
            <category><![CDATA[site-to-site-vpn]]></category>
            <category><![CDATA[ipsec-tunnel]]></category>
            <category><![CDATA[oracle-cloud]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 08:57:50 GMT</pubDate>
            <atom:updated>2026-11-09T08:57:50.970Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Disaster Recovery (DR) infrastructure is useful only when it can communicate with the systems and networks required to support business operations during a disaster.</p><p>While working on OCI Disaster Recovery infrastructure in the Riyadh region, I worked on setting up secure connectivity between the OCI DR environment and the organization’s on-premises network using Oracle Cloud Infrastructure (OCI) Site-to-Site VPN.</p><p>The objective was to prepare a secure network communication path between the DR environment and the on-premises infrastructure so that required services can communicate during DR operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RrNprExuoGHVAguFubH9vA.png" /></figure><p>In this article, I will walk through the configuration activities performed in OCI.</p><h3>Understanding the Architecture</h3><p>OCI Site-to-Site VPN provides encrypted connectivity between an on-premises network and an OCI Virtual Cloud Network (VCN) through IPSec tunnels.</p><p>For this implementation, the key components were:</p><ul><li><strong>Customer-Premises Equipment (CPE):</strong> Represents the on-premises VPN device in OCI.</li><li><strong>Dynamic Routing Gateway (DRG):</strong> Acts as the network gateway connecting the VCN with external networks.</li><li><strong>Site-to-Site VPN:</strong> Provides encrypted IPSec connectivity between OCI and the on-premises VPN device.</li><li><strong>IPSec Tunnels:</strong> Provide the VPN tunnel endpoints for secure communication.</li><li><strong>Static Routing:</strong> Used to define the on-premises network CIDR ranges that need to be reachable through the VPN.</li></ul><h3>Implementation Steps</h3><h3>1. Creating Customer-Premises Equipment (CPE)</h3><p>The first step was to create a CPE in the OCI Riyadh region.</p><p>The CPE represents the organization’s on-premises VPN device within OCI.</p><p>During creation, the following information is required:</p><ul><li>CPE name.</li><li>Public IP address of the on-premises VPN device.</li><li>Appropriate compartment.</li></ul><p>Once the CPE was created, it became available for use when configuring the Site-to-Site VPN connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RmyeHoDu0F4qZslnM_bqBA.png" /></figure><h3>2. Configuring the Site-to-Site VPN</h3><p>After creating the CPE, I proceeded with creating a Site-to-Site IPSec VPN connection.</p><p>The configuration involved selecting:</p><ul><li>The Customer-Premises Equipment (CPE).</li><li>The OCI Dynamic Routing Gateway (DRG).</li><li>The required routing configuration.</li><li>The appropriate network CIDR information.</li></ul><p>This established the OCI-side configuration required for communication between the DR environment and the on-premises network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQpaCRnMrrRzX4FO313AMg.png" /></figure><h3>3. Configuring IPSec Tunnels</h3><p>As part of the VPN configuration, OCI provided two IPSec tunnels.</p><p>Both tunnels were configured with static routing.</p><p>The two-tunnel setup provides alternative VPN paths and supports redundancy at the tunnel level.</p><p>Each tunnel has its own:</p><ul><li>Oracle VPN endpoint IP address.</li><li>IPSec configuration parameters.</li><li>Tunnel lifecycle state.</li><li>IPSec status.</li></ul><p>The corresponding configuration must also be applied on the on-premises VPN device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1HIlaJgixeiIx9xwpTQfPg.png" /></figure><h3>4. Reviewing Tunnel Configuration</h3><p>After creating the VPN connection, I reviewed the tunnel information in the OCI Console.</p><p>The tunnel configuration showed:</p><ul><li>Two available IPSec tunnels.</li><li>Static routing as the routing type.</li><li>Available lifecycle states for both tunnels.</li></ul><p>It is important to distinguish between the tunnel lifecycle state and IPSec status. A tunnel showing an Available lifecycle state does not necessarily mean the VPN connection is operational.</p><p>The IPSec status and actual network traffic must also be validated.</p><h3>Important Validation Activities</h3><p>After completing the OCI-side configuration, the following activities are important before considering the connectivity operational:</p><ol><li>Apply the OCI-generated IPSec parameters on the on-premises VPN device.</li><li>Verify that the IKE and IPSec security associations are established.</li><li>Confirm that both tunnel statuses are UP, where redundancy is required.</li><li>Validate static route configuration on both sides.</li><li>Review DRG route tables and VCN route tables.</li><li>Verify security lists, NSGs and on-premises firewall policies.</li><li>Perform connectivity tests between the on-premises network and the DR environment.</li></ol><p>These checks help identify routing, firewall, and tunnel negotiation issues.</p><h3>Why This Configuration Matters for DR</h3><p>Establishing connectivity between OCI DR infrastructure and the on-premises network is an important part of disaster recovery planning.</p><p>It helps prepare the environment for:</p><ul><li>Secure communication between DR and on-premises networks.</li><li>Access to required internal services during DR operations.</li><li>Network integration between cloud and on-premises infrastructure.</li><li>A more reliable DR connectivity design through redundant IPSec tunnels.</li></ul><p>However, actual DR readiness also depends on application dependencies, routing, firewall policies, and successful end-to-end testing.</p><h3>Conclusion</h3><p>This activity provided practical experience with OCI networking components, including CPE creation, DRG integration, Site-to-Site IPSec VPN configuration, and tunnel setup in the Riyadh DR region.</p><p>Rather than waiting until a disaster occurs, preparing and validating network connectivity in advance helps reduce the complexity of future DR operations.</p><p>I will continue working on the connectivity validation and network integration activities as part of the DR infrastructure preparation.</p><h3>Oracle Cloud Infrastructure Resources</h3><ul><li><a href="https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/overviewIPsec.htm">OCI Site-to-Site VPN Overview</a></li><li><a href="https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/creatingCPE.htm">OCI Customer-Premises Equipment (CPE)</a></li><li><a href="https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/settingupIPsec.htm">OCI Site-to-Site VPN Configuration</a></li></ul><p>#OracleCloud #OCI #OracleACE #OracleACEAssociate #CloudNetworking #IPSecVPN #DisasterRecovery #DR #CloudInfrastructure #Networking</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fc4dc878601" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving OCI Load Balancers Between Compartments: A Practical DR Infrastructure Management Activity]]></title>
            <link>https://medium.com/@pathanfardeen555/moving-oci-load-balancers-between-compartments-a-practical-dr-infrastructure-management-activity-1c4e9e6d62ec?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c4e9e6d62ec</guid>
            <category><![CDATA[oracle-cloud]]></category>
            <category><![CDATA[load-balancer]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 07:08:58 GMT</pubDate>
            <atom:updated>2026-11-03T07:08:58.609Z</atom:updated>
            <content:encoded><![CDATA[<p>Managing cloud infrastructure is not just about provisioning resources. Organizing resources properly, maintaining access controls, and keeping the infrastructure structured are equally important.</p><p>Recently, as part of a Disaster Recovery (DR) infrastructure management activity in Oracle Cloud Infrastructure (OCI), I worked on moving existing DR Load Balancers from the <strong>Non-Prod compartment to the Network compartment</strong> in the Saudi Arabia Central (Riyadh) region.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*8-z6hjARmyzfLe1I.jpg" /></figure><p>In this article, I’ll share why we performed this activity, how I moved the resources, and what I verified afterward.</p><h3>1. Understanding the Requirement</h3><p>The DR environment had three Load Balancers provisioned under the Non-Prod compartment.</p><p>However, from an infrastructure management and resource organization perspective, network-related resources needed to be maintained under the dedicated Network compartment.</p><p>The objective was to move the existing Load Balancers without recreating them.</p><p>The three Load Balancers were:</p><ul><li>DR-Einvoice_Public-LB</li><li>DR-FTP-LB</li><li>DR-Bidding_Public_LoadBalancer</li></ul><p><strong>Region:</strong> Saudi Arabia Central (Riyadh)</p><p><strong>Source Compartment:</strong> Non-Prod</p><p><strong>Destination Compartment:</strong> Network</p><h3>2. Why Move Load Balancers to a Network Compartment?</h3><p>In OCI, compartments help organize and isolate cloud resources logically.</p><p>Maintaining network-related resources in a dedicated compartment provides several operational advantages:</p><ul><li>Better resource organization and visibility.</li><li>Centralized management of network infrastructure.</li><li>Easier IAM policy administration.</li><li>Improved separation between application resources and network resources.</li><li>Simplified infrastructure inventory and auditing.</li></ul><p>A well-organized compartment structure also makes day-to-day cloud operations easier to manage.</p><h3>3. Moving Load Balancers in OCI</h3><p>I performed the activity directly through the OCI Console.</p><p>The steps were:</p><p><strong>Step 1: Open the Load Balancers page</strong></p><p>Navigate to:</p><p>Networking → Load Balancers</p><p>Select the Riyadh region and the source compartment (Non-Prod).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*5TMkhCkbY1g6KjmvDe-0IQ.png" /></figure><p><strong>Step 2: Identify the Load Balancers</strong></p><p>Review the existing Load Balancers and identify the resources that need to be moved.</p><p><strong>Step 3: Select the Move Resource option</strong></p><p>Open the required Load Balancer details and select the Move Resource option from the Actions menu.</p><p><strong>Step 4: Select the destination compartment</strong></p><p>Choose the Network compartment as the destination.</p><p>Review the selected destination and confirm the move.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*sU3JmkzsSZ7ohurrHmWDOw.png" /></figure><p><strong>Step 5: Repeat the process</strong></p><p>Repeat the same procedure for the remaining two Load Balancers.</p><h3>4. Post-Migration Validation</h3><p>After completing the operation, I selected the Network compartment and verified that all three Load Balancers were visible there.</p><p>The validation included:</p><ul><li>Confirming all three Load Balancers were listed under Network.</li><li>Checking that their lifecycle state remained Active.</li><li>Verifying the public IP addresses.</li><li>Reviewing the overall health status.</li></ul><p>The public IP addresses remained unchanged in the post-move console view:</p><p>One important observation: all three Load Balancers continued to show Critical overall health. This was treated as a separate health investigation rather than an issue caused or resolved by the compartment move.</p><h3>5. Important Considerations</h3><p>Before moving resources between compartments, consider the following:</p><ol><li><strong>IAM Policies:</strong> Verify that the required permissions exist in the destination compartment.</li><li><strong>Resource Access:</strong> Check whether existing users and groups will retain the necessary access after the move.</li><li><strong>Monitoring:</strong> Review alarms, monitoring configurations, and notification access.</li><li><strong>Configuration Validation:</strong> Verify listeners, backend sets, health checks, and other Load Balancer configurations.</li><li><strong>Change Management:</strong> Follow the organization’s approval process before performing changes in production or DR environments.</li></ol><p>Always validate the resource configuration and application connectivity after the operation.</p><h3>6. Final Outcome</h3><p>The compartment migration was completed successfully.</p><p>All three existing DR Load Balancers were moved from the Non-Prod compartment to the Network compartment in the Riyadh region.</p><p>This activity helped align the DR infrastructure with the intended compartment organization without recreating the Load Balancer resources.</p><h3>Conclusion</h3><p>This was a small but valuable infrastructure management activity.</p><p>In cloud operations, maintaining a proper compartment structure is important for resource governance, access management, and long-term infrastructure administration.</p><p>Working on these real-world OCI activities has helped me gain more practical experience in managing and organizing cloud infrastructure.</p><p><strong>Thanks for reading!</strong></p><p>#OracleCloud #OCI #OracleACE #CloudInfrastructure #LoadBalancer #CloudNetworking #DisasterRecovery #CloudOperations</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c4e9e6d62ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up OCI WAF for DR Load Balancers Before We Actually Need Them]]></title>
            <link>https://medium.com/@pathanfardeen555/setting-up-oci-waf-for-dr-load-balancers-before-we-actually-need-them-410782fcac95?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/410782fcac95</guid>
            <category><![CDATA[oracle-cloud]]></category>
            <category><![CDATA[web-application-firewall]]></category>
            <category><![CDATA[oci-security]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 17:24:10 GMT</pubDate>
            <atom:updated>2026-10-30T17:24:10.223Z</atom:updated>
            <content:encoded><![CDATA[<p>When people talk about disaster recovery, the conversation is usually about standby servers, replication and failover. Security tends to get pushed to “we’ll sort it out when we switch over”. I’ve never liked that. If something goes wrong and you’re already under pressure, the last thing you want is to be building firewall rules from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCrIYgWpyByPal1J0WVbMQ.png" /></figure><p>So on a recent project, I set up Oracle Cloud Infrastructure (OCI) Web Application Firewall (WAF) for the Load Balancers in our DR region, well before any failover. The primary region already had a WAF policy running, so my job was simple on paper: make DR match it.</p><p>Here’s how it went.</p><h3>The DR setup</h3><p>The DR region had three Load Balancers, each fronting a different application service. Their backend instances were switched off, which is normal for DR, but the Load Balancers themselves were already there. That meant I could attach WAF to them right away without waiting for the apps to be running.</p><h3>Step 1: Create the WAF policy</h3><p>I went to <strong>Identity &amp; Security → Web Application Firewall → Policies</strong> in the DR region and created a new policy in our non-production compartment. Once it was created, I checked that the status showed Active before moving on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*ezD9NWNvbgwkLx7d91KzWw.png" /></figure><p><em>The new policy in Active state</em></p><h3>Step 2: Attach the Load Balancers</h3><p>Next, in the Firewalls tab, I used the add firewalls option and linked all three DR Load Balancers to the policy. Each one got its own firewall entry, and all three came up as Active.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*cg3Hlzj5ZARY_REhKYpDtg.png" /></figure><p><em>Three firewalls attached to the same policy, all Active</em></p><p>Something I liked here: one policy can cover several Load Balancers. If they share the same security requirements, you don’t need to maintain three separate policies.</p><h3>Step 3: Protection rules</h3><p>This was the part that needed the most care. I opened the existing policy from the primary region and copied its approach, so both regions would behave the same way.</p><p>OCI tags some protection capabilities as Recommended. These cover common attack types like SQL injection and cross-site scripting. I selected everything with that tag, which came to 29 capabilities. The rest of the rule looked like this:</p><p><strong>Setting</strong></p><p><strong>Value</strong></p><p>Protection capabilities</p><p>29 (all tagged Recommended)</p><p>Default action</p><p>Pre-configured 401 Response Code Action</p><p>Body inspection</p><p>Disabled</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*BeDwD3ts_3XFNoqJzzS6gA.png" /></figure><p><em>Protection rule with 29 capabilities</em></p><p>I kept the 401 response action and left body inspection off purely because that’s what the primary region uses. Consistency mattered more to me than tweaking things in DR.</p><h3>Why bother doing this early?</h3><p>Because DR activation is already a long checklist. Every security task you can finish ahead of time is one less thing to worry about on the day. Doing this now means:</p><p>• DR security matches what we run in the primary region</p><p>• Incoming traffic is protected from the moment the DR apps come up</p><p>• There are fewer manual steps during failover</p><p>• Security checks become part of DR readiness, not an afterthought</p><p>That said, I haven’t treated it as finished. The policy still needs to be tested with real application traffic before I’d call DR fully ready.</p><h3>What I took away from it</h3><p>It gave me a much clearer picture of how WAF policies and firewall attachments fit together. It also reminded me how easy it is for Production and DR to drift apart if nobody checks. A WAF policy that exists is not the same as a WAF policy that’s been reviewed, so access control, rate limiting, protection rules and logs all still need a proper look.</p><h3>Wrapping up</h3><p>We now have a DR WAF policy with three Load Balancers attached and 29 recommended protections enabled, built on the same baseline as the primary region. I’m still working through validating the remaining pieces.</p><p><strong>My main takeaway: DR readiness isn’t only about having infrastructure available. The security side needs to be set up and tested before the day you need it.</strong></p><p><strong>Services used: </strong>OCI, OCI Web Application Firewall, OCI Load Balancer, OCI Identity &amp; Security</p><p>#OracleCloud #OCI #OracleACE #OracleACEProgram #CloudSecurity #WAF #DisasterRecovery #CloudInfrastructure</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=410782fcac95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Isolating and Restoring Network Access to an OCI Compute Instance Using Network Security Groups…]]></title>
            <link>https://medium.com/@pathanfardeen555/isolating-and-restoring-network-access-to-an-oci-compute-instance-using-network-security-groups-b3fd89fbdd86?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3fd89fbdd86</guid>
            <category><![CDATA[oracle-cloud]]></category>
            <category><![CDATA[network-security-group]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 09:23:23 GMT</pubDate>
            <atom:updated>2026-10-21T09:23:23.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>Isolating and Restoring Network Access to an OCI Compute Instance Using Network Security Groups (NSGs)</h3><p><em>Hands-on experience with Oracle Cloud Infrastructure networking</em></p><h3>Introduction</h3><p>While working with Oracle Cloud Infrastructure (OCI), I came across a scenario where three compute instances were running in the same subnet, but their network access requirements were different.</p><p>Two instances had Network Security Groups (NSGs) associated with their VNICs, while the third instance was intentionally kept without an NSG association to maintain network isolation.</p><p>Later, when network connectivity needed to be restored for the third instance, I reviewed its networking configuration and associated the appropriate NSG.</p><p>This practical exercise helped me better understand how NSGs work in OCI and why network access should always be reviewed at multiple layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*CPJUOV85dCck3Ihw6eYlEQ.png" /></figure><h3>Understanding the Environment</h3><p>The environment consisted of:</p><ul><li>Three OCI compute instances in the same subnet.</li><li>Two instances with NSGs already associated.</li><li>One instance without an NSG association.</li><li>A private subnet with a configured route table.</li><li>A requirement to control access to the third instance independently.</li></ul><p>The objective was to understand how to restore the required network connectivity without unnecessarily changing the existing subnet or private IP configuration.</p><h3>What Are Network Security Groups in OCI?</h3><p>Network Security Groups are used to control network traffic for selected resources in Oracle Cloud Infrastructure.</p><p>Unlike security lists, which apply at the subnet level, NSGs apply to the VNICs of the resources associated with them.</p><p>NSGs support two types of security rules:</p><p><strong>Ingress rules:</strong> Control incoming traffic to the associated resources.</p><p><strong>Egress rules:</strong> Control outgoing traffic from the associated resources.</p><p>These rules can be configured based on the required source or destination, IP protocol, and port ranges.</p><p>For example, an administrator may allow SSH access on TCP port 22 from an approved management subnet while restricting unnecessary traffic.</p><h3>Step 1: Review the Compute Instance</h3><p>I opened the OCI Console and navigated to the compute instance’s networking details.</p><p>Under the Primary VNIC section, I reviewed the following information:</p><ul><li>Private IPv4 address</li><li>Associated subnet</li><li>Route table</li><li>Network Security Groups</li><li>Private DNS configuration</li></ul><p>The instance had a private IP address and was connected to the intended private subnet. However, no NSG was associated with its primary VNIC.</p><p>This was an important starting point because I needed to understand the existing network configuration before making any changes.</p><h3>Step 2: Review the Existing NSG Rules</h3><p>Before associating an NSG, I reviewed the NSG already used by the other two instances.</p><p>I verified that its ingress and egress rules allowed the required network traffic.</p><p>This step is important because associating an NSG does not automatically guarantee connectivity. The rules must match the actual access requirements, and the routing and operating system firewall must also permit the connection.</p><p>I also considered the subnet’s security list because OCI evaluates applicable NSG and security-list rules together.</p><h3>Step 3: Associate the NSG with the Instance</h3><p>After reviewing the configuration, I returned to the compute instance’s networking page.</p><p>I followed these steps:</p><ol><li>Open the compute instance in the OCI Console.</li><li>Navigate to the <strong>Networking</strong> tab.</li><li>Locate the <strong>Primary VNIC</strong> section.</li><li>Click <strong>Edit</strong> beside Network Security Groups.</li><li>Select the appropriate existing NSG.</li><li>Save the changes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxeh3YFESldK0wpEAukjAg.png" /></figure><p>This associated the selected NSG with the instance’s VNIC, making the NSG’s rules applicable to that VNIC.</p><p>Since the NSG was shared with other instances, I also considered the security implications of applying the same rules to the third instance.</p><h3>Step 4: Verify Network Connectivity</h3><p>After updating the configuration, the next step was to verify that the required connectivity was available.</p><p>Depending on the environment, validation can include:</p><ul><li>Testing connectivity from an authorized source.</li><li>Checking the required application port.</li><li>Verifying SSH or RDP access, where applicable.</li><li>Reviewing the subnet route table and any required VPN or FastConnect connectivity.</li><li>Checking the operating system firewall and service status.</li><li>Reviewing OCI monitoring metrics if the instance remains unresponsive.</li></ul><p>For a private instance, the source system must also have a valid network path to the instance’s private IP address.</p><p>It is important to distinguish between an instance being in the <strong>Running</strong> state and the operating system actually being responsive. OCI can report an instance as running even when the OS or a network service is not responding.</p><h3>An Important Networking Lesson</h3><p>One key takeaway from this exercise is that <strong>not associating an NSG does not, by itself, guarantee network isolation</strong>.</p><p>OCI security lists and NSGs are separate security mechanisms. If a subnet security list allows traffic, a VNIC without an NSG can still receive that traffic, subject to the other network and host-level controls.</p><p>Similarly, attaching an NSG with permissive rules may expose the instance to more traffic than intended.</p><p>For this reason, network isolation should be designed and verified across all applicable security rules, routing paths, and operating system controls.</p><p>When multiple instances share a subnet, their individual access requirements should be considered before applying a shared NSG.</p><h3>Best Practices</h3><p>Based on this exercise, I would recommend the following practices when managing network access in OCI:</p><ol><li><strong>Review before changing:</strong> Check the VNIC, subnet, route table, NSGs, and security lists before modifying the configuration.</li><li><strong>Apply least privilege:</strong> Allow only the source addresses, protocols, and ports required by the workload.</li><li><strong>Be careful with shared NSGs:</strong> Associating a shared NSG can change the effective access available to an instance.</li><li><strong>Validate after every change:</strong> Test the required connectivity instead of assuming that a successful configuration update means the issue is resolved.</li><li><strong>Document isolation requirements:</strong> Keep a clear record of why an instance is isolated and what approvals are needed to restore access.</li></ol><h3>Conclusion</h3><p>This hands-on activity gave me a better understanding of how network security groups are associated with VNICs in Oracle Cloud Infrastructure and how they contribute to controlling network access.</p><p>It also reinforced an important point: troubleshooting connectivity is not just about adding or removing an NSG. It requires understanding how security rules, routing, and operating system configuration work together.</p><p>I continue to build my practical OCI knowledge by working on real infrastructure scenarios and documenting the lessons learned along the way.</p><p>#Oracle Cloud Infrastructure, #OCI, #Cloud Networking, #Network Security Groups, #Cloud Infrastructure, #Oracle Cloud</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3fd89fbdd86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cost Optimization in OCI: Stopping Unused UAT and DR Compute Instances]]></title>
            <link>https://medium.com/@pathanfardeen555/cost-optimization-in-oci-stopping-unused-uat-and-dr-compute-instances-60000eee6018?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/60000eee6018</guid>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[oci]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 11:54:03 GMT</pubDate>
            <atom:updated>2026-10-05T11:54:03.888Z</atom:updated>
            <content:encoded><![CDATA[<p>While working on OCI infrastructure, one of the areas I recently looked at was <strong>cost optimization for UAT and DR environments</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c3lZS0yWHP_QF5mO.png" /></figure><p>In production environments, servers generally need to be available all the time. But the same is not always true for UAT, testing, and some DR environments.</p><p>We had a few UAT/DR servers that were not required to be running continuously. So, as part of the cost optimization activity, we reviewed the servers and stopped the instances that were not currently required.</p><h3>Why did we stop the servers?</h3><p>In OCI, Compute instances consume compute resources while they are running. If a server is not being used but is still running, we are still consuming compute capacity unnecessarily.</p><p>For example, UAT environments may mainly be required when:</p><ul><li>The application team is testing something</li><li>A deployment needs to be validated</li><li>A DR test is planned</li><li>Some maintenance activity is being performed</li></ul><p>Outside these requirements, keeping all the servers running 24/7 may not be necessary.</p><p>So instead of keeping the servers running all the time, we decided to stop the required instances and start them again whenever they are needed.</p><h3>What I checked before stopping the instances</h3><p>I didn’t simply stop the servers directly.</p><p>Before stopping them, the important thing was to understand whether they were currently being used by any application or process.</p><p>I checked the environment and identified the instances belonging to the UAT/DR setup.</p><p>The servers included different types of workloads such as application servers, database servers and supporting servers.</p><p>I also considered whether stopping a particular server could affect any dependency, scheduled activity, backup, replication or testing activity.</p><p>This is particularly important for DR servers because some of them may be involved in replication or other recovery-related activities.</p><h3>OCI Compute Instances</h3><p>The instances were reviewed from the <strong>OCI Compute Instances</strong> page.</p><p>For example, the environment had instances with different configurations, including:</p><ul><li>VM.Standard.E3.Flex</li><li>VM.Standard.E4.Flex</li><li>VM.Standard.E5.Flex</li></ul><p>They also had different OCPU and memory allocations.</p><p>This is important from a cost perspective because a larger instance running continuously can have a much bigger impact than a small test server.</p><p>After confirming that the required servers were not needed at that time, we stopped the instances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*ZvBYn1vta0Ak_pakU2vMeA.png" /></figure><h3>What happens when we stop an OCI Compute instance?</h3><p>Stopping an instance stops the compute workload, but it does not mean that every resource associated with the instance becomes free of cost.</p><p>For example, attached storage such as boot volumes and block volumes can continue to exist.</p><p>So cost optimization should not be considered only from the Compute perspective.</p><p>We should also review the resources associated with the instance and understand which resources are still required.</p><p>For example:</p><p><strong>Compute instance stopped.</strong></p><p>→ Compute consumption reduced</p><p>→ Attached storage remains</p><p>→ Other associated resources may still have charges.</p><p>This is why it is important to review the complete infrastructure rather than assuming that stopping an instance removes all costs.</p><h3>One thing I learned from this activity</h3><p>One thing I found useful from this exercise is that <strong>cost optimization doesn’t always require a major infrastructure change</strong>.</p><p>Sometimes we already have the required infrastructure, but we are using it continuously even though the workload is required only for a limited period.</p><p>For UAT and testing environments, a simple operational change like stopping instances outside working hours or when testing is completed can help reduce unnecessary compute usage.</p><p>The same approach can be extended further by scheduling the start and stop of non-production environments.</p><p>For example, instead of manually starting and stopping servers every day, we can look at automation based on the team’s working hours and application requirements.</p><h3>Things to consider before stopping a DR server</h3><p>I would be more careful with DR servers compared to normal development or UAT servers.</p><p>Before stopping a DR instance, I would verify:</p><ol><li>Whether replication is currently running.</li><li>Whether any application depends on the server.</li><li>Whether backups are scheduled.</li><li>Whether monitoring or alarms depend on the server.</li><li>Whether any DR testing is planned.</li><li>Whether the client/application team has confirmed that the server can be stopped.</li></ol><p>A cost-saving activity should not introduce an availability or recovery problem.</p><h3>Final thoughts</h3><p>This was a relatively simple activity, but it is a good example of how day-to-day cloud operations can contribute to cost optimization.</p><p>Instead of looking only at the OCI bill at the end of the month, regularly reviewing running resources can help identify workloads that don’t need to run continuously.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60000eee6018" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring OCI Network Changes with Events and Notifications]]></title>
            <link>https://medium.com/@pathanfardeen555/monitoring-oci-network-changes-with-events-and-notifications-77ab978e4312?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/77ab978e4312</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[oracle-cloud]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 12:50:29 GMT</pubDate>
            <atom:updated>2026-09-24T12:50:29.804Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I set up and tested automatic email alerts in Oracle Cloud Infrastructure</h3><p>When several administrators can manage cloud networking, it helps to know when important changes happen. I wanted our team to receive an email when selected networking resources changed in Oracle Cloud Infrastructure (OCI).</p><p>I used OCI Events to match resource activity and OCI Notifications to send messages to a team email topic. The setup was straightforward. The most useful part was tracing a test event through each stage when the first notification didn’t arrive right away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*CPJUOV85dCck3Ihw6eYlEQ.png" /></figure><p><strong>The flow:</strong> Networking change → Events rule → Notifications topic → email subscriptions</p><h3>The requirement:</h3><p>I wanted to monitor changes to networking resources such as:</p><ul><li>Virtual Cloud Networks (VCNs)</li><li>Subnets</li><li>Route tables</li><li>Security lists</li><li>Network Security Groups (NSGs)</li><li>Internet, NAT, and service gateways</li><li>Dynamic Routing Gateways (DRGs)</li><li>Other networking resources relevant to our environment</li></ul><p>The team needed to receive notifications automatically, without relying on someone to report each change manually.</p><h3>Step 1: Create an Events rule</h3><p>In the OCI Console, I went to <strong>Observability &amp; Management → Events Service → Rules</strong> and created a rule with a clear name and description.</p><p>Compartment scope matters. An Events rule matches events from resources in the compartment where the rule is created and its child compartments. To cover resources across an environment, create the rule at the appropriate parent level and make sure the resources you want to monitor are in that compartment hierarchy. A rule doesn’t automatically cover sibling compartments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gavM6up--rfINIYpw71nHA.png" /></figure><h3>Step 2: Choose the event conditions</h3><p>Under <strong>Rule Conditions</strong>, I selected <strong>Event Type</strong> and chose <strong>Networking</strong> as the service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUI7PPOklMF4Hj1Eq8XLgw.png" /></figure><p>Then I selected the event types relevant to our environment. Examples include create, update, and delete events for VCNs, subnets, route tables, security lists, and supported gateway types.</p><p>The available operations differ by resource type, so I checked the OCI event type list and selected the operations we wanted to detect. For example, <strong>Create Security List</strong> and <strong>Update Security List</strong> are separate event types. Selecting only the update event won’t detect a newly created security list.</p><h3>Step 3: Send matching events to Notifications</h3><p>Under <strong>Actions</strong>, I selected <strong>Notifications</strong> and chose the existing Notifications topic. The topic already had the team’s email subscriptions, and I confirmed their status was <strong>Active</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gYUZy1pDBHb1xWPL1fLSA.png" /></figure><p>I didn’t need a Monitoring alarm for this use case. Events rules respond to resource activity, such as creating a security list. Monitoring alarms respond to metric conditions, such as CPU utilization exceeding a threshold.</p><h3>Step 4: Test the rule</h3><p>After creating the rule, I created a test security list in a VCN. The email didn’t arrive immediately, so I checked the flow stage by stage instead of repeatedly changing the configuration.</p><p>First, I opened the rule’s monitoring metrics and checked <strong>Events Matched</strong>. It showed one matched event. That confirmed the rule matched the network activity.</p><p>Next, I checked <strong>Events Delivered</strong>. It also showed one successful delivery, indicating that Events had sent the matching event to its configured action.</p><h3>Step 5: Check the Notifications topic</h3><p>I opened the Notifications topic’s monitoring metrics and checked:</p><ul><li><strong>Published Messages Count</strong> to see whether Notifications received a message</li><li><strong>Delivered Messages Count</strong> to see whether messages reached subscription endpoints</li><li><strong>Failed Messages Count</strong> to check for delivery failures during the test period</li></ul><p>This gave me a useful troubleshooting sequence: network activity → Events Matched → Events Delivered → Published Messages → Delivered Messages → email endpoint.</p><p>These metrics help identify how far the event travelled. A successful Notifications delivery means the message reached a subscription endpoint; it doesn’t tell you whether someone read the email.</p><p>After checking the flow, I confirmed that the email notification arrived.</p><h3>What I learned</h3><p>Compartment placement determines which resources a rule can cover. For broad coverage, the rule needs to be in the right parent compartment.</p><p>Event selection matters too. Create, update, and delete operations are separate events, and the available operations vary by resource type. The rule needs to include the specific activity you want to detect.</p><p>Finally, checking metrics in order makes troubleshooting clearer. Events metrics show whether an event matched and was delivered to an action. Notifications metrics show whether a message was published and delivered to subscription endpoints.</p><p>OCI Events and OCI Notifications provide a practical way to make networking changes more visible to a team. I found the end-to-end troubleshooting approach just as useful as the configuration: follow the event from the original resource change through to its notification endpoint.</p><p>#Oracle Cloud Infrastructure # OCI #Cloud Computing · #Networking · #DevOps</p><p><strong>References:</strong> <a href="https://docs.oracle.com/en-us/iaas/Content/Events/Reference/eventsproducers.htm">OCI networking event types</a> · <a href="https://docs.oracle.com/en-us/iaas/Content/Events/Concepts/filterevents.htm">Matching events with filters</a> · <a href="https://docs.oracle.com/en-us/iaas/Content/Events/Reference/eventsmetrics.htm">Events metrics</a> · <a href="https://docs.oracle.com/en-us/iaas/Content/Notification/Reference/notificationmetrics-reference.htm">Notifications metrics</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77ab978e4312" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OCI Block Volume Backup Cleanup After Moving to a New Backup Tool]]></title>
            <link>https://medium.com/@pathanfardeen555/oci-block-volume-backup-cleanup-after-moving-to-a-new-backup-tool-40282c1aba9e?source=rss-927328876901------2</link>
            <guid isPermaLink="false">https://medium.com/p/40282c1aba9e</guid>
            <category><![CDATA[block-volume]]></category>
            <category><![CDATA[oci]]></category>
            <dc:creator><![CDATA[Patan Fardeen Khan]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 09:33:34 GMT</pubDate>
            <atom:updated>2026-09-07T09:33:34.108Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>As part of our OCI infrastructure work, I worked on reviewing the Block Volume backups in one of our DR environments.</p><p>Earlier, some of the Block Volumes had manual backups created in OCI. Later, the client started using a separate backup tool to manage the backups.</p><p>Because of this, we had to check whether the old OCI backups were still required or whether they were already covered by the new backup tool.</p><p>I reviewed the existing backups and, after getting the required confirmation and approval, we terminated the backups that were no longer needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*CPJUOV85dCck3Ihw6eYlEQ.png" /></figure><h3>What was the issue?</h3><p>There were multiple manual Block Volume backups available in OCI.</p><p>Some of these backups were created earlier for backup and recovery purposes. After the client started using the new backup tool, keeping the same backups in OCI could result in duplicate backup copies.</p><p>This can also increase backup storage usage and make it difficult to manage which backup solution should be used during recovery.</p><p>So, instead of keeping all the old backups, I reviewed them and identified the backups that were no longer required.</p><h3>What I checked before removing the backups</h3><p>I did not directly delete the backups.</p><p>Before terminating them, I checked the following:</p><ul><li>Which Block Volume the backup belonged to</li><li>Backup creation date</li><li>Backup status</li><li>Backup size</li><li>Whether the volume was covered by the new backup tool</li><li>Whether the backup was still required for DR</li><li>Whether there were any retention requirements</li><li>Whether the backup was needed for any rollback or recovery activity</li><li>Confirmation from the concerned team/client</li></ul><p>After confirming that the backups were no longer required, the termination activity was performed.</p><h3>OCI Backup Cleanup</h3><p>The OCI console showed multiple Block Volume backups.</p><p>For example:</p><p>BackupStatusSizeDR Block Volume Backup 1Terminated~1732 GBDR Block Volume Backup 2Terminated~1731 GBDR Block Volume Backup 3Terminating~1731 GBDR Block Volume Backup 4Available~1706 GB</p><p>The actual server and compartment names are not shown here for security reasons.</p><p>Some backups were already terminated, while one backup was in the <strong>terminating</strong> state.</p><p>I monitored the backup status after starting the termination to make sure the operation was completed successfully.</p><h3>Why did we remove the old backups?</h3><p>The main reason was that the client had moved to a different backup tool.</p><p>The new backup tool was responsible for taking the required backups.</p><p>Keeping the old OCI manual backups when they were no longer required could result in:</p><ul><li>Duplicate backups</li><li>Additional backup storage usage</li><li>Unnecessary cost</li><li>More backup resources to manage</li><li>Confusion during a recovery activity</li></ul><p>Therefore, removing the obsolete backups helped us keep the OCI environment cleaner and easier to manage.</p><h3>Before the Change</h3><p>The backup setup was similar to this:</p><pre>OCI Compute Server<br>       |<br>       +---- Block Volume<br>       |<br>       +---- OCI Manual Backup<br>       |<br>       +---- New Backup Tool</pre><p>This meant that the same workload could have backup coverage from two different places.</p><p>Below shows termination of backups</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*fClw-wInGriHGM_rHmWAXw.png" /></figure><h3>After the Change</h3><p>After reviewing the requirements:</p><pre>OCI Compute Server<br>       |<br>       +---- Block Volume<br>                  |<br>                  +---- New Backup Tool</pre><p>The required backup solution was retained, while the unnecessary OCI manual backups were removed.</p><h3>What I Learned</h3><p>This activity helped me understand that backup cleanup should not be done only based on the backup age or size.</p><p>Before deleting a backup, we should always check whether it is still required.</p><p>Some important points I learned are:</p><ol><li>We should understand who is responsible for the backup.</li><li>We should confirm that the new backup solution is actually protecting the workload.</li><li>We should check the retention requirement before deleting old backups.</li><li>We should confirm that the backup is not required for DR or rollback.</li><li>We should take approval before removing production/DR backups.</li><li>We should monitor the backup state after starting the termination.</li><li>We should check the impact on storage and cost after cleanup.</li></ol><h3>Important OCI Point</h3><p>One thing I learned from this activity is that we should also be careful when deleting Block Volume backups because backups can have relationships with other backups.</p><p>For example, deleting a full backup can affect the data that needs to be retained with an incremental backup.</p><p>So, we should understand the backup chain before deleting backups and should not assume that the displayed backup size is the exact amount of cost that will be saved.</p><h3>Benefits</h3><p>After the cleanup:</p><ul><li>Unnecessary OCI backups were removed.</li><li>Backup management became simpler.</li><li>Duplicate backup storage was avoided.</li><li>The backup responsibility became clearer.</li><li>The OCI environment was cleaner.</li><li>There was potential to reduce backup storage cost.</li></ul><p>The exact cost saving should be calculated from OCI usage/billing data rather than estimating it only from the backup size.</p><h3>Conclusion</h3><p>This was a small but useful OCI infrastructure activity.</p><p>The main learning for me was that <strong>backup management is not only about creating backups. It is also important to regularly review them and remove backups that are no longer required.</strong></p><p>When an organization starts using a new backup solution, the existing OCI backups should be reviewed carefully before making any changes.</p><p>The correct approach is:</p><p><strong>Review → Validate → Get Approval → Terminate → Verify</strong></p><p>This helps avoid unnecessary storage while making sure that the required backup and recovery protection is still available.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40282c1aba9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>