<?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 Hyndavi Nanduri on Medium]]></title>
        <description><![CDATA[Stories by Hyndavi Nanduri on Medium]]></description>
        <link>https://medium.com/@venkatahyndavi?source=rss-2b229be0deb9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1uIWUFIGZm51kUUa</url>
            <title>Stories by Hyndavi Nanduri on Medium</title>
            <link>https://medium.com/@venkatahyndavi?source=rss-2b229be0deb9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:48:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@venkatahyndavi/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 a video streaming application on EC2 using Docker and AWS Developers Tools.]]></title>
            <link>https://medium.com/@venkatahyndavi/deploying-a-video-streaming-application-on-ec2-using-docker-and-aws-developers-tools-8aa4cf7b2bdf?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aa4cf7b2bdf</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Thu, 25 Jul 2024 16:39:29 GMT</pubDate>
            <atom:updated>2024-07-25T16:39:29.674Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Clone this Repository</strong>: <a href="https://github.com/hyndavinandurii/CodePipeline-Project">https://github.com/hyndavinandurii/CodePipeline-Project</a></h4><h3>Project Architecture:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RG2oOznQ71mk1CufXOsNw.png" /></figure><h3>Setting Up CodeCommit:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwepDVGUSvfLb7K_BoTDCQ.png" /></figure><h3>Create IAM User:</h3><ul><li>Go to the IAM console and create a user.</li><li>Click on Create User -&gt; User details -&gt; Next.</li><li>Add Permission for full access to CodeCommit.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ost9BNyMtxJjhSLgTbxanQ.png" /></figure><ul><li>Click on Create for the user.</li><li>Click on the user and go to the security credentials section</li><li>Now we are going to create SSH credentials for this user.</li><li>Go to the terminal and run this command</li></ul><p>ssh-keygen</p><ul><li>Keep all the default values.</li><li>Copy the public key using cat ~/.ssh/id_rsa.pub. Paste it into the security credentials, and SSH public key for the CodeCommit section, and copy the SSH key id.</li><li>Go back to the repository and copy the URL for the git connection.</li><li>Now run</li></ul><p>cd ~/.ssh <br>touch config</p><ul><li>Host git-codecommit.*.amazonaws.com</li><li>User &lt;paste the id of ssh key (can find after you paster your key in aws )-&gt; IdentityFile ~/.ssh/id_rsa</li><li>Now we can connect to this repo.</li><li>Run this command now</li></ul><p>git clone &lt;SSH URL&gt;</p><ul><li>Now copy all the content from my git repository to your code commit repository.</li><li>And do a git push.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*rK--KlGTLVl2Mq_7" /></figure><h3>Setting Up CodeBuild:</h3><ul><li>Click on Create build project</li><li>Follow this steps</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*4_rg5BYmH_hOML_Y" /></figure><ul><li>In this project, we will build and push a Docker image to the DockerHub repository.</li><li>So, We need DockerHub credentials like Username and Password.</li><li>Also, we are using a free API to consume movie/TV data in this Project. <a href="https://www.themoviedb.org/">TMDB</a>.</li></ul><h3>Using AWS System Manager for storing secrets</h3><ul><li>Goto AWS System Manager dashboard.</li><li>Click on Parameter Store -&gt; Create parameter</li><li>In Parameter details</li></ul><p><em>Add</em> DockerHub Username</p><p><em>Name:</em> /myapp/docker-credentials/username</p><p><em>Type:</em> SecureString</p><p><em>Value: Add Your DockerHub Username</em></p><p><em>Add</em> DockerHub Password</p><p><em>Name:</em> /myapp/docker-credentials/password</p><p><em>Type:</em> SecureString</p><p><em>Value: Add Your DockerHub Password or secret token</em></p><p><em>Add</em> TMDB API Key</p><p><em>Name:</em> /myapp/api/key</p><p><em>Type:</em> SecureString</p><p><em>Value: Add Your TMDB API key</em></p><ul><li>Also, Add Permission in CodeBuild Created Role to assess Parameters from CodeBuild to System Manager</li><li>For this, Create an inline policy.</li></ul><p>{<br> “Sid”: “Statement1”,<br> “Effect”: “Allow”,<br> “Action”: [<br> “ssm:GetParameters”<br> ],<br> “Resource”: [<br> “arn:aws:ssm:*:{AWS Account ID 12 Digit}:parameter/*”<br> ]<br> }</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*FHlZ-AZPh7PTN2G9" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*oz6j_9hSXdp_DUyV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*gDpOCttewb4S6_ai" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*vUOyLGDyAubCDuWD" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*tJ7CM62lDGPJU95X" /></figure><h3>Build Artifact store in S3 Bucket</h3><p>In the CodeBuild console Click on Edit button -&gt; Artifacts -&gt; Type: “S3” -&gt; put Uplode Location.</p><h3>Create CodeDeploy Application</h3><ul><li>Create Application and Compute platform is EC2/On-premises</li></ul><p>Create Service role (Give permissions -</p><p>1.AmazonEC2FullAccess</p><p>2.AmazonEC2RoleforAWSCodeDeploy</p><p>3. AmazonS3FullAccess</p><p>4.AWSCodeDeployeFullAccess</p><p>5.AWSCodeDeployRole</p><p>6.AmazonEC2RoleforAWSCodeDeployLimitaccesstoS3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*EH8hgBqWivKdIiIN" /></figure><h3>Create EC2 instance</h3><p>Click Launch Instances</p><ul><li>Amazon Linux -&gt; t2.micro</li><li>Also, Create a Service Role for EC2 to access s3 &amp; CodeDeploy</li><li>Goto IAM Dashboard -&gt; Create Role -&gt; Service Role -&gt; EC2</li><li>Add this permission</li></ul><ol><li>AmazonEC2FullAccess</li><li>AmazonEC2RoleforAWSCodeDeploy</li><li>AmazonS3FullAccess</li><li>AWSCodeDeployFullAccess</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*fVZyogkIg7wyVx3r" /></figure><ul><li>Give Role name -&gt; Click on Create Role</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*EQn_IERP-F4F-VLA" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/771/0*jyKAXdXlCnG5OoeK" /></figure><ul><li>Add this Script to the User Data section.</li><li>Or Just run it manually.</li><li>For Ubuntu</li></ul><p>#!/bin/bash<br>sudo apt update<br>sudo install docker.io<br>sudo apt install ruby-full<br>wget cd /home/ubuntu wget <a href="https://aws-codedeploy-ap-south-1.s3.ap-south-1.amazonaws.com/latest/install">https://aws-codedeploy-ap-south-1.s3.ap-south-1.amazonaws.com/latest/install</a><br>chmod +x ./install<br>sudo ./install auto<br>sudo service codedeploy-agent status</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*1rDN8s8558Rm0a9j" /></figure><h3>Create CodeDeploy Group</h3><ul><li>Create a CodeDeploy Group using the following Steps.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*bYjfwAOUAhAY0qbX" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*1SvXNs9tSdELBXFD" /></figure><ul><li>Click On Create Deployment</li><li>Start Deployment</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*IN_ANbO-eHwrcYmx" /></figure><h3>Create CodePipeline</h3><ul><li>Step 1: Choose pipeline setting -&gt; PipelineName &gt; Service role</li><li>Step 2: Add source stage -&gt; CodeCommit &gt; RepoName &gt; BranchName &gt; Select CodePipeline periodically for changes(For automation)</li><li>Step 3: Add build stage -&gt; BuildProvider &gt; Region &gt; ProjectName &gt; Single build</li><li>Step 4: Add deploy stage -&gt; DeployProvider &gt; Region &gt; AppName &gt; Deployment group</li><li>Step 5: Review</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*k5OOP3HnDI5Oalfj" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*A2lWdMWuGSWEzqzx" /></figure><h3>CodeBuild History</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*lUrPAbMAmSJMIOYF" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*fVMgJqF5U37v0cRH" /></figure><h3>CodeDeploy History</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*JtZjn8SZjbbnZ2p8" /></figure><h3>Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ry90dEbbbNIBqTaG" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aa4cf7b2bdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a Django Application to Amazon ECS with Load Balancer]]></title>
            <link>https://medium.com/@venkatahyndavi/deploying-a-django-application-to-amazon-ecs-with-load-balancer-6022fff669da?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6022fff669da</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Sun, 21 Jul 2024 18:35:25 GMT</pubDate>
            <atom:updated>2024-07-21T18:35:25.080Z</atom:updated>
            <content:encoded><![CDATA[<p>Deploying a Django application to Amazon ECS (Elastic Container Service) with a load balancer ensures high availability, scalability, and reliability. In this guide, we’ll walk through the steps to achieve this.</p><p>Git_Repo: <a href="https://github.com/hyndavinandurii/python-django-application.git">https://github.com/hyndavinandurii/python-django-application.git</a></p><h3>1. Prepare Your Django Application</h3><p>Before deploying, make sure your Django application is Dockerized. Here’s a basic Dockerfile for a Django application:</p><p>Make sure you replace myproject.wsgi:application with the appropriate path for your Django project’s WSGI application.</p><h3>2. Create an Amazon ECR Repository</h3><p>Amazon Elastic Container Registry (ECR) is a managed container registry service. Follow these steps to create a repository:</p><p><strong>Navigate to ECR Console:</strong></p><ul><li>Go to the <a href="https://console.aws.amazon.com/ecr">Amazon ECR Console</a>.</li></ul><p><strong>Create a Repository:</strong></p><ul><li>Click on <strong>Repositories</strong> in the left pane.</li><li>Click <strong>Create repository</strong>.</li><li>Enter a repository name (e.g., django-app).</li><li>Click <strong>Create repository</strong>.</li></ul><h3>2. Build and Push Docker Image to ECR</h3><p><strong>Authenticate Docker to ECR:</strong></p><p>Run the following command to get login credentials:</p><ul><li>aws ecr get-login-password --region &lt;your-region&gt; | docker login --username AWS --password-stdin &lt;your-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com</li></ul><p><strong>Build Docker Image:</strong></p><ul><li>Navigate to the directory containing your Dockerfile.</li><li>Build the Docker image:</li><li>docker build -t django-app .</li></ul><p><strong>Tag Docker Image:</strong></p><ul><li>Tag the image with the ECR repository URI:</li><li>docker tag django-app:latest &lt;your-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com/django-app:latest</li></ul><p><strong>Push Docker Image:</strong></p><ul><li>Push the image to ECR:</li><li>docker push &lt;your-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com/django-app:latest</li></ul><h3>3. Create an ECS Cluster</h3><p><strong>Navigate to ECS Console:</strong></p><ul><li>Go to the <a href="https://console.aws.amazon.com/ecs">Amazon ECS Console</a>.</li></ul><p><strong>Create a Cluster:</strong></p><ul><li>Click <strong>Create Cluster</strong>.</li><li>Choose <strong>EC2 Linux + Networking</strong> or <strong>Fargate</strong> based on your needs.</li><li>Enter a cluster name (e.g., django-cluster).</li><li>Click <strong>Create</strong>.</li></ul><h3>4. Create a Task Definition</h3><p><strong>Navigate to Task Definitions:</strong></p><ul><li>Go to the <strong>Task Definitions</strong> tab in the ECS Console.</li><li>Click <strong>Create new Task Definition</strong>.</li></ul><p><strong>Configure Task Definition:</strong></p><ul><li>Select <strong>Fargate</strong> or <strong>EC2</strong> based on your cluster type.</li><li>Enter a task definition name (e.g., django-task).</li><li>Set the <strong>Task Role</strong> if necessary.</li><li>Configure the container:</li><li><strong>Container Name:</strong> django-container</li><li><strong>Image:</strong> &lt;your-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com/django-app:latest</li><li><strong>Port Mappings:</strong> Map container port 8000 to host port 8000.</li><li>Configure task size and other settings as needed.</li><li>Click <strong>Create</strong>.</li></ul><h3>5. Create an ECS Service</h3><p><strong>Navigate to Services:</strong></p><ul><li>Go to the <strong>Services</strong> tab in the ECS Console.</li><li>Click <strong>Create</strong>.</li></ul><p><strong>Configure Service:</strong></p><ul><li>Select the cluster created earlier.</li><li>Choose <strong>Fargate</strong> or <strong>EC2</strong> based on your task definition.</li><li>Enter a service name (e.g., django-service).</li><li>Set the <strong>Number of Tasks</strong>.</li><li>Under <strong>Load Balancing</strong>, select <strong>Application Load Balancer</strong>.</li><li>Choose the load balancer and target group (create a target group if needed).</li><li>Configure other settings and click <strong>Next</strong>.</li></ul><h3>6. Create and Configure an Application Load Balancer (ALB)</h3><p><strong>Navigate to EC2 Console:</strong></p><ul><li>Go to the <a href="https://console.aws.amazon.com/ec2">EC2 Management Console</a>.</li></ul><p><strong>Create Load Balancer:</strong></p><ul><li>Click on <strong>Load Balancers</strong>.</li><li>Click <strong>Create Load Balancer</strong>.</li><li>Choose <strong>Application Load Balancer</strong>.</li></ul><p><strong>Configure Load Balancer:</strong></p><ul><li><strong>Name:</strong> Enter a name (e.g., django-alb).</li><li><strong>Scheme:</strong> Choose <strong>Internet-facing</strong>.</li><li><strong>IP Address Type:</strong> Select <strong>ipv4</strong>.</li><li><strong>Listeners:</strong> Default is port 80 (HTTP).</li><li><strong>Availability Zones:</strong> Select the VPC and subnets.</li></ul><p><strong>Configure Security Groups:</strong></p><ul><li>Select or create a security group allowing inbound traffic on port 80.</li></ul><p><strong>Configure Routing:</strong></p><ul><li>Create a new target group:</li><li><strong>Name:</strong> Enter a name (e.g., django-target-group).</li><li><strong>Protocol:</strong> HTTP</li><li><strong>Port:</strong> 8000</li><li><strong>Health Checks:</strong> Set the path (e.g., /).</li></ul><p><strong>Review and Create:</strong></p><ul><li>Review settings and click <strong>Create Load Balancer</strong>.</li></ul><h3>7. Update ECS Service with Load Balancer</h3><p><strong>Navigate to ECS Console:</strong></p><ul><li>Go to the <strong>Services</strong> tab.</li><li>Select your service and click <strong>Update</strong>.</li></ul><p><strong>Configure Load Balancer:</strong></p><ul><li>In the <strong>Load Balancing</strong> section, select the Application Load Balancer.</li><li>Choose the target group created earlier.</li></ul><p><strong>Update Service:</strong></p><ul><li>Complete additional configurations and click <strong>Update Service</strong>.</li></ul><h3>8. Verify Deployment</h3><p><strong>Check Load Balancer:</strong></p><ul><li>Go to the <strong>Load Balancers</strong> section in the EC2 console.</li><li>Ensure the load balancer is <strong>active</strong> and check the <strong>DNS name</strong>.</li></ul><p><strong>Access Your Application:</strong></p><ul><li>Use the DNS name to access your Django application.</li></ul><p><a href="http://my-load-balancer-1234567890.us-west-2.elb.amazonaws.com/">http://tic-tac-lb-955898877733.ap-south-1.elb.amazonaws.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*hprB1w3O-XAEN6AO4T_QDA.png" /></figure><p>Thanks for reading😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6022fff669da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a Rock, Paper, Scissor Game to AWS EC2 with Apache]]></title>
            <link>https://medium.com/@venkatahyndavi/deploying-a-rock-paper-scissor-game-to-aws-ec2-with-apache-2ef9e2d408c2?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ef9e2d408c2</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Tue, 16 Jul 2024 17:13:45 GMT</pubDate>
            <atom:updated>2024-07-16T17:22:46.583Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Introduction:</strong></h3><p>In this article, I’ll walk you through the process of deploying a classic Rock, Paper, Scissors game to an AWS EC2 instance using Apache as the web server. Rock, Paper, Scissors is a simple yet engaging game that everyone has played at some point, making it a perfect candidate for showcasing deployment skills on a cloud platform.</p><h3>Why AWS EC2?</h3><p>Amazon EC2 (Elastic Compute Cloud) provides resizable compute capacity in the cloud, making it ideal for hosting applications that require flexibility, scalability, and control over computing resources. By deploying our game on EC2, we leverage AWS’s robust infrastructure to ensure reliable performance and seamless scalability, while Apache serves as a versatile web server capable of handling our game’s frontend needs.</p><h3>Overview: Deployment Process and Tools Used</h3><p>In this section, I will outline the step-by-step deployment process of the Rock, Paper, Scissors game on an AWS EC2 instance with Apache. This deployment showcases the integration of frontend development with cloud infrastructure, emphasizing the use of scalable and reliable AWS services.</p><p><strong>Deployment Process:</strong></p><ol><li><strong>Setting Up the AWS EC2 Instance</strong>:</li></ol><ul><li>Begin by provisioning an EC2 instance through the AWS Management Console. Choose the appropriate instance type and configuration based on the game’s requirements for computing power and memory.</li></ul><p><strong>2. Installing and Configuring Apache Web Server</strong>:</p><ul><li>Install Apache on the EC2 instance to serve as the web server for hosting the game’s frontend. Configure Apache to handle HTTP requests and serve static files like index.html, styles.css, and script.js.</li></ul><p><strong>3. Uploading Game Files to the EC2 Instance</strong>:</p><ul><li>Upload game files to EC2 Instance or clone it from git repository. Ensure correct permissions are set for the files to be accessible by Apache.</li></ul><p><strong>4. Testing the Deployment</strong>:</p><ul><li>Validate the deployment by accessing the game through the EC2 instance’s public IP address or domain name. Test different aspects such as game functionality, responsiveness, and performance.</li></ul><p><strong>Tools Used:</strong></p><ul><li><strong>AWS EC2</strong>: Utilized for scalable virtual computing instances in the cloud.</li><li><strong>Apache Web Server</strong>: Configured to serve the frontend files and handle HTTP requests.</li><li><strong>SSH/SFTP</strong>: Used for secure file transfer to the EC2 instance.</li><li><strong>AWS Management Console</strong>: Interface for managing EC2 instances and configuring AWS services.</li><li><strong>Linux Command Line</strong>: Executed commands for installing software and managing files on the EC2 instance.</li></ul><p><strong>Git-URL</strong>: <a href="https://github.com/hyndavinandurii/Game_Application">https://github.com/hyndavinandurii/Game_Application</a></p><p>Finally, i deployed this game to AWS EC2 instance using below link:</p><p>http://<a href="http://3.110.106.50/">http://3.110.106.50/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJ--SRLPlvvm1oe2VEIViw.png" /></figure><p>Once you access via your instance’s public ip or public dns, you’ll be seeing the game like this. you can start playing by selevcting your choice like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TWntFh_f_dHdRujejOC6YA.png" /></figure><p>This deployment process highlights the synergy between frontend development and cloud infrastructure, demonstrating how AWS EC2 and Apache facilitate the hosting of web applications with reliability and scalability. Follow along as I delve into each step with practical insights and best practices for deploying applications on AWS.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ef9e2d408c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Kubernetes Networking ~]]></title>
            <link>https://medium.com/@venkatahyndavi/kubernetes-networking-47f863668f0f?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/47f863668f0f</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Tue, 25 Jun 2024 08:46:02 GMT</pubDate>
            <atom:updated>2024-06-25T08:46:02.721Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Kubernetes networking</strong> is a critical aspect of managing containerized applications in a distributed environment. It ensures that containers within a Kubernetes cluster can communicate with each other, with external users, and with other services smoothly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*EELox6vmtr6U88TRJ8y9YQ.gif" /></figure><p>Let’s explore the key concepts and components of Kubernetes networking:</p><p><strong>🟠Pod Networking:</strong></p><p>- Pods share the same network namespace and can communicate via localhost.</p><p>- Kubernetes assigns each Pod a unique IP address for inter-node communication.</p><p><strong>🟠Service Networking:</strong></p><p>- Services provide stable endpoints for accessing Pods.</p><p>- ClusterIP, NodePort, and LoadBalancer are common Service types for internal and external access.</p><p><strong>🟠Ingress Networking:</strong></p><p>- Ingress manages external access to Services based on HTTP/HTTPS rules.</p><p>- Ingress controllers handle traffic routing to Services within the cluster.</p><p><strong>🟠Network Policies:</strong></p><p>- This defines rules for Pod-to-Pod communication and access to external resources.</p><p>- It enables fine-grained control over network traffic within the cluster.</p><p><strong>Container Network Interface (CNI):</strong></p><p>- A standard for defining plugins that handle networking in container runtimes.</p><p>- Used by Kubernetes to manage network interfaces and IP addresses.</p><p><strong>Networking Plugins:</strong></p><p>- Kube-Proxy manages network rules for routing traffic to Services.</p><p>- CoreDNS resolves DNS queries for Kubernetes Services and Pods.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47f863668f0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‍Deploying React-to-do application on to EKS Cluster✨]]></title>
            <link>https://medium.com/@venkatahyndavi/deploying-react-to-do-application-on-to-eks-cluster-78b4c12bbf4e?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/78b4c12bbf4e</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Sun, 23 Jun 2024 17:25:15 GMT</pubDate>
            <atom:updated>2024-06-23T17:25:15.555Z</atom:updated>
            <content:encoded><![CDATA[<h3>Amazon EKS :</h3><p>Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed <a href="https://aws.amazon.com/kubernetes/">Kubernetes</a> service. It enables you to scale your Kubernetes clusters up and down easily based on the demand of your workloads. It simplifies running Kubernetes on AWS without needing to install and operate your own Kubernetes control plane or nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*JVQ-8Jocwqg8hFfPtTnpRQ.jpeg" /></figure><p>To deploy your React To-Do application on an Amazon EKS cluster, you’ll need to create several Kubernetes manifests and follow specific steps to set up your environment. Below, I’ll guide you through the process:</p><h3>Pre-requisites:</h3><ol><li>Install AWS CLI : First we need to install AWS CLI</li><li>Configure your AWS CLI credentials: Both eksctl and the AWS CLI require that you have AWS credentials configured in your environment. The <strong>aws configure</strong> command is the fastest way to set up your AWS CLI installation for general use.</li><li>Install eksctl : eksctl is a simple CLI tool for creating clusters on EKS</li><li>Install and configure kubectl : Kubernetes uses the <strong>kubectl</strong> command-line utility for communicating with the cluster API server.</li></ol><p>Here is the github link:</p><p><a href="https://github.com/hyndavi03/react-to-do">https://github.com/hyndavi03/react-to-do</a></p><p><strong>Step 1: Set Up Your EKS Cluster</strong></p><p><strong>Create an EKS Cluster</strong>: You can create an EKS cluster using the AWS Management Console, AWS CLI, or eksctl. For simplicity, we’ll use eksctl here. Install using Fargate</p><p>eksctl create cluster — name react-cluster — region ap-south-1 — fargate</p><p><strong>Configure kubectl</strong>: Make sure kubectl is configured to communicate with your EKS cluster</p><p>aws eks — region ap-south-1 update-kubeconfig — name react-cluster</p><p><strong>Step 2: Create Docker Image and Push to ECR</strong></p><p><strong>Create ECR Repository</strong>: Create a repository in Amazon Elastic Container Registry (ECR).</p><p>aws ecr create-repository — repository-name react-repo — region ap-south-1</p><p><strong>Build and Push Docker Image</strong>:</p><p>aws ecr get-login-password — region ap-south-1 | docker login — username AWS — password-stdin &lt;aws-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com</p><p># Build the Docker image</p><p>docker build -t react-todo-app .</p><p># Tag the Docker image</p><p>docker tag react-todo-app:latest &lt;aws-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com/react-repo:latest</p><p># Push the Docker image</p><p>docker push &lt;aws-account-id&gt;.dkr.ecr.&lt;your-region&gt;.amazonaws.com/react-repo:latest</p><h3>configure IAM OIDC provider</h3><p>export cluster_name=react-cluster</p><p>oidc_id=$(aws eks describe-cluster — name $cluster_name — query “cluster.identity.oidc.issuer” — output text | cut -d ‘/’ -f 5)</p><p>eksctl utils associate-iam-oidc-provider — cluster $cluster_name — approve</p><p><strong>Setting up alb addon:</strong></p><p>Run below command to download IAM policy</p><p>curl -O <a href="https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.4/docs/install/iam_policy.json">https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.4/docs/install/iam_policy.json</a></p><p>Create IAM Policy</p><p>Create IAM Roleaws iam create-policy \<br> — policy-name AWSLoadBalancerControllerIAMPolicy \<br> — policy-document file://iam_policy.json</p><p>Create IAM Role</p><pre>eksctl create iamserviceaccount \<br>  --cluster=&lt;your-cluster-name&gt; \<br>  --namespace=kube-system \<br>  --name=aws-load-balancer-controller \<br>  --role-name AmazonEKSLoadBalancerControllerRole \<br>  --attach-policy-arn=arn:aws:iam::&lt;your-aws-account-id&gt;:policy/AWSLoadBalancerControllerIAMPolicy \<br>  --approve</pre><h3>Deploy ALB controller</h3><p>→ Add helm repo</p><p>helm repo add eks <a href="https://aws.github.io/eks-charts">https://aws.github.io/eks-charts</a></p><p>→ update this repo</p><p>helm repo update eks</p><p>→ Install</p><p>helm install aws-load-balancer-controller eks/aws-load-balancer-controller \ <br> -n kube-system \<br> — set clusterName=&lt;your-cluster-name&gt; \<br> — set serviceAccount.create=false \<br> — set serviceAccount.name=aws-load-balancer-controller \<br> — set region=&lt;region&gt; \<br> — set vpcId=&lt;your-vpc-id&gt;</p><p>Verify that the deployments are running:</p><p>kubectl get deployment -n kube-system aws-load-balancer-controller</p><h3>Create Fargate profile:</h3><p>eksctl create fargateprofile \<br> — cluster react-cluster \<br> — region ap-south-1 \<br> — name alb-sample-app \<br> — namespace react-space</p><h3>Deploy the deployment, service and Ingress:</h3><p>kubectl apply -f deployment.yaml</p><p>kubectl apply -f service.yaml</p><p>Access the application using load balancer:</p><p><a href="http://k8s-default-reacttod-5ee1e38867-49c006ac8fde1e7c.elb.ap-south-1.amazonaws.com/">http://k8s-default-reacttod-5ee1e38867-49c006ac8fde1e7c.elb.ap-south-1.amazonaws.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*-wSqtL4jQIBHXveVcRFSRw.png" /></figure><p>You can add your to-do activities here like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*U3TOHn_K4t52iml0LRUtzw.png" /></figure><p>🙌 Finally deployed application on to AWS EKS.</p><p>Thanks for reading 😍.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78b4c12bbf4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying NodeJS Application on AWS EC2 Instance — Step by Step]]></title>
            <link>https://medium.com/@venkatahyndavi/deploying-nodejs-application-on-aws-ec2-instance-step-by-step-48c3a758f43f?source=rss-2b229be0deb9------2</link>
            <guid isPermaLink="false">https://medium.com/p/48c3a758f43f</guid>
            <dc:creator><![CDATA[Hyndavi Nanduri]]></dc:creator>
            <pubDate>Sat, 22 Jun 2024 16:35:19 GMT</pubDate>
            <atom:updated>2024-06-22T16:35:19.392Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Deploying NodeJS Application on AWS EC2 Instance — Step by Step</strong></h3><p>Hello there🌻</p><p>In this article, we are going to see how one can deploy a NodeJS application on to AWS EC2 ubuntu instance and access the same in the browser.</p><p>Setting Up the AWS EC2 Instance</p><ol><li><strong>Creating EC2 instance in AWS:</strong></li></ol><p>Here is the Link : <a href="https://medium.com/@misalPav103/launching-your-first-ec2-instance-a422862e09c2">“Launching your first EC2 Instance”</a></p><p>As a very first step here in the process we need to configure a AWS EC2 instance and SSH into the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*Ic3oKls6AxwgS9y3d-U17g.png" /></figure><p>2. <strong>Installing Node.js and Git:</strong></p><p>sudo apt update -y</p><p>curl -sL <a href="https://rpm.nodesource.com/setup_14.x">https://rpm.nodesource.com/setup_14.x</a> | sudo bash -</p><p>sudo apt install -y nodejs</p><p>sudo apt install -y git (if git is not installed)</p><p>3. <strong>Check Installations:</strong></p><p>node — version</p><p>git — version</p><p>4. <strong>Clone the repository from GitHub</strong></p><p>github_url: <a href="https://github.com/hyndavi03/Nodejs-Application">https://github.com/hyndavi03/Nodejs-Application</a></p><p>5. <strong>Setup CI/CD pipeline using GitHub Actions:</strong></p><p>To do so create .github/workflows folder and create your workflow there.</p><p>4. <strong>Adding Secrets to GitHub Repository</strong></p><p>Adding AWS credentials and other secrets:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uD1P1-cDKTlC5BbUGiA1yQ.png" /></figure><p>5. <strong>Run the workflow:</strong></p><p>Once your workflow got succeeded, go ahead and try to access your application</p><p>6. <strong>Access the running application</strong></p><p><a href="http://13.201.32.249:3000/">http://13.201.32.249:3000/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*sJAZlxWD0By15QD3aIYE-Q.png" /></figure><p><strong>If this post was helpful, please do follow and click the clap 👏 button below to show your support 😄</strong></p><p><strong>Thank you for reading💖</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48c3a758f43f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>