<?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 Raju R on Medium]]></title>
        <description><![CDATA[Stories by Raju R on Medium]]></description>
        <link>https://medium.com/@rrayak69?source=rss-f30af0a374e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bJMyuU9F9iaaDy00</url>
            <title>Stories by Raju R on Medium</title>
            <link>https://medium.com/@rrayak69?source=rss-f30af0a374e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:05:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rrayak69/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[Configuring AWS Site-to-Site VPN Across Mumbai and Singapore Regions(acts like on-prem)Using…]]></title>
            <link>https://medium.com/@rrayak69/configuring-aws-site-to-site-vpn-across-mumbai-and-singapore-regions-acts-like-on-prem-using-479a7ca204e4?source=rss-f30af0a374e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/479a7ca204e4</guid>
            <dc:creator><![CDATA[Raju R]]></dc:creator>
            <pubDate>Wed, 08 Jan 2025 10:30:57 GMT</pubDate>
            <atom:updated>2025-01-08T10:30:57.680Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring AWS Site-to-Site VPN Across Mumbai and Singapore Regions(acts like on-prem)Using OpenSWAN</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVRu711R6NOQzPbFSyYVJA.jpeg" /></figure><p>In this project, we will set up a <strong>Site-to-Site VPN</strong> to establish secure communication between an <strong>AWS environment</strong> and a <strong>simulated on-premises environment</strong>. The architecture we’ll implement is outlined below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*gUloqBPCyibhazPVq4AsPA.png" /></figure><h3>Key Services Commonly Used in a Site-to-Site VPN Setup:</h3><p><strong>Amazon VPC (Virtual Private Cloud):</strong></p><ul><li>VPC serves as the core networking construct in AWS, offering an isolated virtual network to launch resources, including those participating in the Site-to-Site VPN connection.</li></ul><p><strong>Amazon Virtual Private Gateway (VGW):</strong></p><ul><li>The VGW acts as the AWS-side VPN endpoint, enabling secure communication between your AWS VPC and the on-premises network.</li></ul><p><strong>Customer Gateway (CGW):</strong></p><ul><li>The CGW represents the on-premises VPN endpoint, including details such as the public IP address of the on-premises VPN device.</li></ul><p><strong>Site-to-Site VPN Connection:</strong></p><ul><li>This service establishes and manages secure, encrypted communication between the Virtual Private Gateway and the Customer Gateway. It involves configuring encryption settings, routing, and pre-shared keys.</li></ul><p><strong>Amazon EC2 Instances (Optional):</strong></p><p>EC2 instances can serve as VPN appliances or resources requiring connectivity through the Site-to-Site VPN.</p><p><strong>AWS Identity and Access Management (IAM):</strong></p><ul><li>IAM ensures secure access control by managing permissions and roles for creating and managing Site-to-Site VPN resources.</li></ul><p><strong>Security Groups and Network ACLs:</strong></p><ul><li>These tools regulate inbound and outbound traffic to and from VPC resources, playing a key role in securing communication over the Site-to-Site VPN.</li></ul><h3>Step 1: AWS Configuration in Mumbai Region</h3><ul><li>Create AWS VPC:</li><li>Name: Mumbai-VPC (optional)</li><li>CIDR Block: 10.0.0.0/16</li><li>Name: AWS-SIDE-SUBNET</li><li>CIDR Block: 10.0.1.0/24</li><li>Create Route Table in AWS-ROUTE</li><li>Define routes for the VPC and associate with the subnet.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W5bgWy6z2iZXvwP26Qp-nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kF7c5_yCC3BnpOEsfBtc6w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ac5V9ZnXKSY1A-qsuLR34w.png" /></figure><p>Launch a test instance (Private) in Mumbai region to test the connectivity</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yoJlCw6S9tSFiIB7288_iA.png" /></figure><h3>Step 2: Singapore Region Configuration(Acts like on prem VPN instance)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRuGqu32Q0kqgLW-tSfWwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-XyGHl93ddsijpppGoMQoA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*likI36Edn3cic-p5iJIzfg.png" /></figure><h3>Step 3: Create CGW,VGW, Site-to-Site In Mumbai region</h3><p>CGW Ip address should be given, which was created at Singapore region VPN instance Static IP</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFy14GRz32aIQLQofmvqDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HLZwj_TFBeno0r0Nvfz5lw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OEpnn0lFL8zz4_hv8cT7gQ.png" /></figure><h3>Step 4: Install Openswan in VPN-Instance</h3><ul><li>Download Configuration: VENDOR-GENERIC from Mumbai region after configuring site-to-site</li><li>Follow the steps from the configuration file and do modification as below</li></ul><p>sudo yum install libreswan -y</p><p>Vi /etc/sysctl.conf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*awsy8v7h-jKOG-9_Dac6aA.png" /></figure><p><strong>Vi /etc/ipsec.conf</strong></p><p>uncomment : include /etc/ipsec.d/*.conf</p><p>save the file</p><p><strong>Vi /etc/ipsec.d/aws.conf</strong></p><p>add the configuration details available in the VENDOR-GENERIC file and do modifications given below</p><p><strong>[root@ip-172–16–2–88 ~]# cat /etc/ipsec.d/aws.conf</strong><br>conn Tunnel1<br> authby=secret<br> auto=start<br> left=%defaultroute<br> leftid=52.77.240.127<br> right=13.234.107.54<br> type=tunnel<br> ikelifetime=8h<br> keylife=1h<br> phase2alg=aes256-sha1;modp2048<br> ike=aes256-sha1;modp2048<br> keyingtries=%forever<br> keyexchange=ike<br> <strong>leftsubnet=172.16.0.0/16<br> rightsubnet=10.0.0.0/16</strong><br> dpddelay=10<br> dpdtimeout=30<br> dpdaction=restart_by_peer<br>[root@ip-172–16–2–88 ~]# ^C</p><p><strong>vi /etc/ipsec.d/aws.secrets</strong></p><p>add the secrets value append in the downloaded file and save it</p><p>Start the ipsec service and see the status</p><p>systemctl start ipsec.service<br>systemctl status ipsec.service</p><p><strong>Step 5 : Check the all the routes given Properly</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yf-1xO8VgFYMPD4eirqivQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*igKurs8zDFSbDGCfl34kng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*60V6R-3A-5Bi9PxulppgBg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BstfBWZ97WWzppexUAeHtA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hmg_JVDHrPeZKsjVpYDnA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tW8MpO7Vu1cKg8gob3E0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*gVUaHqaOgaRyAC3nrGwWbw.png" /></figure><p><strong>Validation and Testing:</strong></p><ul><li>Verify connectivity and VPN tunnel status.</li></ul><p><strong>Conclusion:</strong></p><ul><li>Key takeaways.</li><li>Potential use cases for Site-to-Site VPN in cloud architectures.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=479a7ca204e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Scalable AWS Deployment with ECS Fargate & ALB]]></title>
            <link>https://medium.com/@rrayak69/building-a-scalable-aws-deployment-with-ecs-fargate-alb-b7f30ab69098?source=rss-f30af0a374e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7f30ab69098</guid>
            <dc:creator><![CDATA[Raju R]]></dc:creator>
            <pubDate>Sun, 15 Dec 2024 12:01:55 GMT</pubDate>
            <atom:updated>2024-12-15T12:01:55.043Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In the fast-paced world of modern application development, scalability, reliability, and ease of deployment are paramount. Cloud services like AWS offer powerful tools to simplify these challenges. In this article, I’ll walk you through the steps to deploy a Dockerized application on AWS using <strong>Amazon ECS Fargate</strong>, <strong>Application Load Balancer (ALB)</strong>, and <strong>Amazon Route 53</strong>.</p><p>This journey will take you from building a Docker image to mapping a custom domain, ensuring your application is ready to handle production workloads seamlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hhZTHpDjDIo9ZMOQ1eageg.jpeg" /></figure><h3>Architecture Overview</h3><p>🔍 <strong>Workflow Steps</strong>:</p><ol><li><strong>Build and Push Docker Image</strong>: Explain how the Docker image is created and uploaded to Amazon ECR.</li><li><strong>Create ECS Cluster and Task Definition</strong>: Describe the setup of an ECS Fargate Cluster and the connection to the ECR image via Task Definitions.</li><li><strong>Deploy ECS Service with ALB</strong>: Discuss the ECS Service configuration and integration with ALB for load balancing.</li><li><strong>Map DNS with Route 53</strong>: Detail the setup of custom domain mapping to the ALB’s DNS.</li></ol><p>Steps :</p><p><strong>Step 1</strong>: Install AWS CLI on your system:-</p><p>Choose the OS of your system then download &amp; install AWS CLI</p><p>in your system:-</p><p><a href="https://docs.aws.amazon.com/cli/latest/userguide/getting-startedinstall.">https://docs.aws.amazon.com/cli/latest/userguide/getting-startedinstall.</a>html</p><p><strong>Step 2</strong>: Install Docker on your system:-</p><p> Choose the OS of your system &amp; install Docker in your system:-</p><p><a href="https://docs.docker.com/engine/install/">https://docs.docker.com/engine/install/</a></p><p><strong>Step 3:</strong></p><h3>Steps to Create an AWS IAM User</h3><p><strong>Step 1: Log in to AWS Console</strong></p><ol><li>Log in to the AWS Management Console.</li><li>Navigate to the <strong>IAM Console</strong>.</li><li>Click on <strong>Users</strong> &gt; <strong>Add user</strong>.</li></ol><p><strong>Step 2: Configure User Details</strong></p><ol><li>Enter a <strong>user name</strong> (e.g., ecs-deployment-user).</li><li>Select <strong>Programmatic access</strong> to enable AWS CLI/API access.</li><li>Click <strong>Next: Permissions</strong>.</li></ol><p><strong>Step 3: Assign Permissions</strong></p><ol><li>Attach the following policies:</li></ol><ul><li>AmazonEC2ContainerRegistryFullAccess</li><li>AmazonECS_FullAccess</li><li>AdministratorAccess (or create custom policies for specific access needs).</li></ul><p><strong>Step 5: Save Access Keys</strong></p><ol><li>Securely download or copy the <strong>Access Key ID</strong> and <strong>Secret Access Key</strong>.</li><li>These keys will be needed for programmatic access through AWS CLI or API.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1f-PVqoZiYH55zf7gmgVgg.png" /></figure><p><strong>Step 4: Create an ECR (Elastic Container Registry):</strong></p><ol><li>Log in to the AWS Management Console.</li><li>Search for <strong>ECR</strong> and select it.</li><li>Click on <strong>Create repository</strong> and enter a repository name, then click <strong>Create repository</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RbpA9JqR8gKmktmAQ5Pccw.png" /></figure><p><strong>Step 5: Configure AWS CLI and create a Dockerfile:</strong></p><ol><li>Open <strong>CMD</strong> and run:<br>aws configure<br>Enter your <strong>Access key</strong>, <strong>Secret key</strong>, <strong>Region</strong>, and <strong>Output format</strong>.</li><li>Create a project folder and then a Dockerfile inside it. Use this code for your Dockerfile:</li></ol><pre># Use Red Hat Universal Base Image 9<br>FROM docker.io/redhat/ubi9<br><br># Install httpd<br>RUN yum install -y httpd<br><br># Add a custom index.html<br>COPY index.html /var/www/html/index.html<br><br># Expose port 80<br>EXPOSE 80<br><br># Start httpd when the container launches<br>CMD [&quot;httpd&quot;, &quot;-D&quot;, &quot;FOREGROUND&quot;]</pre><p>Create a basic index.html file with the following content:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>&lt;head&gt;<br>&lt;title&gt;Test page/title&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>&lt;h1&gt;This is a test page&lt;/h1&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p><strong>Step 6: Push Docker image to ECR:</strong></p><ol><li>In AWS ECR, click on <strong>View push commands</strong>.</li><li>Copy and paste the push commands into your CMD and run them to push the Docker image to ECR.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_YyV8ypzXiNLCA3Tb2Ka9g.png" /></figure><p><strong>Step 7: Create ECS (Elastic Container Service), Task Definition, and Service:</strong></p><ol><li>In AWS, go to <strong>ECS</strong> and click on <strong>Create cluster</strong>.</li><li>Name your cluster and select the type as <strong>AWS FARGATE</strong>, then click <strong>Create</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBa6g29biR-dhoMXOOMOtw.png" /></figure><ol><li>Next, create a <strong>Task Definition</strong>:</li></ol><ul><li>Provide a name for the task definition.</li><li>In the container section, enter a container name, select your ECR repository, and specify the container port (80 for HTTP).</li><li>Name the task family and click <strong>Create</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YJ3DJSjd_q17fhtibNOTQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqGfbECBUgNI1-XrFamPkA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIQGt_gxmb4OxZC5t4hgGQ.png" /></figure><p><strong>Step 8 </strong>: Now, create a service:</p><ul><li>Choose <strong>Application type: Task</strong>.</li><li>Select the task family and configure security group settings:</li><li>Choose <strong>HTTP</strong> type and select <strong>Source: Anywhere</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msg7s27Ja2QU7CdTY-zvIw.png" /></figure><p>Step 9 : Click <strong>Create</strong> to finish the ECS setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0Z_O5e8IRG7Nn04xbUJ0A.png" /></figure><p><strong>Step 9 : Verify the deployment:</strong></p><ul><li>Access the public IP &amp; with ALB dns name of your ECS service and verify that the <strong>index.html</strong> page is displayed with the message “This is a test page”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1dWLvuC86mOwEuNAFXerHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbUCzAAb-USByCLzkZsZEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*4Hgp0LfiZaZezIbqJRGm0Q.png" /></figure><p>Step 10 :</p><p>Map the ALB DNS name to your custom domain using AWS Route 53 or your domain provider to access the content via the specified domain.</p><blockquote>This blog post guides readers through the entire process of containerizing an application and deploying it on AWS ECS, starting from building the image to configuring ECS and checking the final deployment.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7f30ab69098" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>