<?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 Onik Azad on Medium]]></title>
        <description><![CDATA[Stories by Onik Azad on Medium]]></description>
        <link>https://medium.com/@onikazadovey?source=rss-28fce0b3eb07------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*pVTQKjn97esdGU_Q</url>
            <title>Stories by Onik Azad on Medium</title>
            <link>https://medium.com/@onikazadovey?source=rss-28fce0b3eb07------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:15:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@onikazadovey/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[Setting Up an AWS EKS Cluster Using Terraform: A Modular and Production-Oriented Approach]]></title>
            <link>https://medium.com/@onikazadovey/setting-up-an-aws-eks-cluster-using-terraform-a-modular-and-production-oriented-approach-17c4a5f26614?source=rss-28fce0b3eb07------2</link>
            <guid isPermaLink="false">https://medium.com/p/17c4a5f26614</guid>
            <category><![CDATA[modules]]></category>
            <category><![CDATA[ek]]></category>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Onik Azad]]></dc:creator>
            <pubDate>Fri, 10 Apr 2026 16:36:59 GMT</pubDate>
            <atom:updated>2026-04-10T16:36:59.532Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Provisioning cloud infrastructure is no longer just about getting resources up and running. It is about designing systems that are reliable, maintainable, and scalable over time. In this article, I will walk through how to set up an Amazon EKS cluster using Terraform, with a strong emphasis on a modular architecture that reflects real-world engineering practices.</p><p>This approach is not optimized for quick experimentation. It is designed for clarity, reuse, and long-term sustainability.</p><h3>Why Terraform and Why Modularity</h3><p>Terraform allows infrastructure to be defined in a declarative manner. Instead of manually configuring resources, you describe the desired state and let Terraform handle the execution.</p><p>However, as infrastructure grows, a single monolithic configuration becomes difficult to manage. This is where a modular approach becomes essential.</p><p>A Terraform module is a self-contained unit that encapsulates a specific responsibility. Instead of placing all resources in one place, infrastructure is broken down into logical components.</p><h3>What is a Modular Approach</h3><p>A modular approach in Terraform means organizing infrastructure into independent, reusable components. Each module:</p><ul><li>Has a clearly defined responsibility</li><li>Accepts inputs through variables</li><li>Exposes outputs for integration with other modules</li><li>Can be reused across environments or projects</li></ul><p>In this project, the infrastructure is divided into two primary modules:</p><ul><li>A VPC module responsible for networking</li><li>An EKS module responsible for the Kubernetes control plane and worker nodes</li></ul><h3>Why This Approach Matters</h3><p>This structure provides several practical advantages:</p><ul><li><strong>Separation of concerns</strong>: Networking and compute are managed independently</li><li><strong>Reusability</strong>: Modules can be reused in other environments without modification</li><li><strong>Maintainability</strong>: Changes in one module do not impact unrelated components</li><li><strong>Clarity</strong>: The overall architecture is easier to understand and reason about</li><li><strong>Scalability</strong>: The structure naturally supports growth and extension</li></ul><p>This is the same pattern used in production environments where infrastructure is maintained over long periods by multiple engineers.</p><h3>Project Structure</h3><p>The repository is organized to reflect clear boundaries between concerns:</p><pre>eks-cluster-setup/<br>│<br>├── backend/<br>│   ├── main.tf<br>│   └── outputs.tf<br>│<br>├── modules/<br>│   ├── vpc/<br>│   │   ├── main.tf<br>│   │   ├── variables.tf<br>│   │   └── outputs.tf<br>│   │<br>│   └── eks/<br>│       ├── main.tf<br>│       ├── variables.tf<br>│       └── outputs.tf<br>│<br>├── main.tf<br>├── variables.tf<br>└── outputs.tf</pre><p>Each directory exists for a specific reason, and no responsibility is duplicated across layers.</p><h3>Backend Configuration</h3><p>The backend directory is used to configure how Terraform state is stored and accessed.</p><p>State management is a critical aspect of infrastructure provisioning. It keeps track of what has been created and ensures that future changes are applied correctly. Storing state remotely enables collaboration and reduces the risk of inconsistencies.</p><p>Although this example keeps the backend simple, the structure is designed to support remote backends such as S3 with state locking.</p><h3>VPC Module</h3><p>The VPC module defines the networking layer required for the cluster.</p><p>Its responsibilities include:</p><ul><li>Creating the VPC</li><li>Defining subnets</li><li>Configuring routing</li></ul><p>By isolating networking logic into its own module, it becomes possible to reuse the same network design for different workloads or clusters without duplication.</p><p>The module exposes outputs such as subnet identifiers and VPC identifiers, which are then consumed by the EKS module.</p><h3>EKS Module</h3><p>The EKS module is responsible for provisioning the Kubernetes control plane and associated resources.</p><p>Its responsibilities include:</p><ul><li>Creating the EKS cluster</li><li>Managing node groups</li><li>Configuring access and permissions</li></ul><p>The module does not attempt to manage networking. Instead, it relies on inputs provided by the VPC module. This separation ensures that each component remains focused and easier to maintain.</p><h3>Root Configuration</h3><p>The root configuration acts as the orchestration layer.</p><p>It performs the following functions:</p><ul><li>Invokes the VPC module</li><li>Passes its outputs into the EKS module</li><li>Defines the overall flow of resource creation</li></ul><p>This layer is intentionally kept minimal. Its purpose is coordination, not implementation.</p><h3>Variables and Outputs</h3><p>Variables and outputs provide a structured way to manage configuration and data flow.</p><ul><li>variables.tf defines configurable inputs such as region, cluster name, or CIDR ranges</li><li>outputs.tf exposes important values such as cluster endpoints and network identifiers</li></ul><p>This separation allows the infrastructure to be flexible without compromising clarity.</p><h3>Deployment Workflow</h3><p>Once the configuration is defined, the deployment process follows a predictable sequence:</p><pre>terraform init<br>terraform plan<br>terraform apply</pre><p>Each step serves a specific purpose:</p><ul><li>init prepares the working directory</li><li>plan provides a preview of changes</li><li>apply executes the desired state</li></ul><p>This workflow ensures that infrastructure changes are deliberate and reviewable.</p><h3>Design Considerations</h3><p>Several design decisions were made to keep the implementation aligned with production practices:</p><ul><li>Modules are kept small and focused</li><li>Dependencies between modules are explicit</li><li>Configuration is centralized and predictable</li><li>The directory structure reflects logical ownership</li></ul><p>These decisions reduce cognitive overhead and make the system easier to extend.</p><h3>Conclusion</h3><p>A modular Terraform design is not simply an organizational preference. It is a foundational practice for building infrastructure that can evolve without becoming fragile.</p><p>By separating networking and compute into independent modules and using a clean orchestration layer, this project demonstrates how to approach infrastructure design with discipline and clarity.</p><p>This pattern can be extended to include additional components such as load balancers, monitoring systems, or deployment pipelines, without disrupting the existing structure.</p><p>The goal is not just to provision resources, but to create infrastructure that remains understandable and reliable as it grows.</p><p>For the complete implementation, refer to the repository:<br><a href="https://github.com/mdanikazad/terraform_projects/tree/main/eks-cluster-setup">https://github.com/mdanikazad/terraform_projects/tree/main/eks-cluster-setup</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17c4a5f26614" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unveiling the Path to Mastery Crafting Excellence as a Junior Linux System Administrator in the…]]></title>
            <link>https://medium.com/@onikazadovey/unveiling-the-path-to-mastery-crafting-excellence-as-a-linux-system-administrator-in-the-modern-age-3c083aefbe6?source=rss-28fce0b3eb07------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c083aefbe6</guid>
            <category><![CDATA[habit-building]]></category>
            <category><![CDATA[system-administration]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Onik Azad]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 04:58:28 GMT</pubDate>
            <atom:updated>2023-08-16T15:26:57.144Z</atom:updated>
            <content:encoded><![CDATA[<h3>Unveiling the Path to Mastery Crafting Excellence as a Junior Linux System Administrator in the Modern Age</h3><p>A good personality trait of a skilled person is the ability to sharpen their axe (keep gaining knowledge). In this modern era, there is no alternative to having proper knowledge and skill if anyone wants to compete in this fast-changing world. Today, I will be sharing a few thoughts that might be helpful for individuals who aspire to become proficient Linux system administrators.</p><p><strong>Avoid seeking support or help:</strong> I apologize for my frank words, but it’s an uncomfortable truth that holds true for everyone. So, here’s my perspective. If you genuinely wish to deeply understand system administration, you must rely on your own efforts by researching documentation. If you believe that relying on others’ help will propel you forward, then trust that such a day may never come in your life. There is only one person in this world who can aid you in learning, improving, and achieving the seemingly impossible, and that person is you. The mindset of independently deciphering challenges will set you apart from others. I’m not suggesting that you shouldn’t seek assistance; naturally, you can engage with experts, but always ensure that you have given your best effort.</p><p><strong>Commence by reading documentation:</strong> The key here is to underscore the importance of reading documentation. Let’s say you intend to install a LAMP server on your Linux machine. Refrain from blindly copying and pasting commands from any online source. Instead, read the material carefully, endeavor to comprehend its functioning, and determine its relevance to your objectives. It’s always wise to peruse the documentation before entering commands. Remember, you’re not merely a typist with fast fingers; you’re an engineer capable of logical thinking.</p><p><strong>Prioritize automation:</strong> Whatever commands you acquire, adopt the mindset of not manually executing them next time. Creating small scripts will simplify your life; you’ll enhance your ability to tackle complex problems through coding efficiency. Start with modest undertakings and never give up. BASH is a great initial choice. Even without prior coding experience, you can develop solid bash scripting skills with consistent effort over 3 to 6 months. Subsequently, you can explore Python or GO, depending on your needs.</p><p><strong>Embrace solitary learning: </strong>Perhaps you, like me, believe that a supportive team environment fosters learning. However, trust me, this isn’t always the case. Each person’s learning journey follows a distinct path with unique styles. Ultimately, you know best what approach suits you. Cultivating a habit of independent learning will undoubtedly render you self-reliant.</p><p><strong>Conquer the most challenging task:</strong> Establishing priorities and accomplishing tasks accordingly holds significance. With a plethora of tools available, aspiring to master them all is unrealistic. What you can do is establish clear priorities along with feasible deadlines. If feasible, articulate your goals in writing and devise a strategy for their attainment. Then, address them one by one. Remember, whatever you initiate, see it through to completion, and attain a comprehensive understanding before moving on to another subject.</p><p><strong>Cultivate your distinctiveness:</strong> Your footprint or signature is distinctive. By this, I mean you should possess something that represents your identity, such as your GitHub profile. Whenever you engage in independent research and development, nurture the habit of crafting meticulous documentation and uploading it to your GitHub repository. Over time, whether a year or later, you’ll be astounded by your progress.</p><p><strong>Review, Review, Review:</strong> This is a crucial aspect often underestimated. Code reviewing is a distinctive skill possessed by few. Avoid hasty conclusions and submitting tasks without adequate review. Foster the practice of reviewing both your own and others’ work. This skill will significantly facilitate your career advancement.</p><p>The insights and experiences I’ve shared above were not acquired overnight. I’m always eager to assist others in finding a clear path towards their goals. Take care and enjoy your journey.</p><p>“I would like to dedicate this blog to <a href="https://medium.com/u/d02cb98172a6">Dewan Shamsul Alam</a>, from whom I learned Linux, and also to <a href="https://medium.com/u/7b45993f7128">Shudarshon Chaki</a>, who has been instrumental in guiding me on the path to becoming a self-dependent engineer.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c083aefbe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>