<?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 Saurav Panda on Medium]]></title>
        <description><![CDATA[Stories by Saurav Panda on Medium]]></description>
        <link>https://medium.com/@saurav.panda?source=rss-9ed063934ef0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XvwANatBgJkzfc5N.</url>
            <title>Stories by Saurav Panda on Medium</title>
            <link>https://medium.com/@saurav.panda?source=rss-9ed063934ef0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:27:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saurav.panda/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[Adding LetsEncrypt SSL to your Namecheap website]]></title>
            <link>https://medium.com/@saurav.panda/adding-letsencrypt-ssl-to-your-namecheap-website-ea529313e2b0?source=rss-9ed063934ef0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea529313e2b0</guid>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[ssl-certificate]]></category>
            <category><![CDATA[lets-encrypt]]></category>
            <category><![CDATA[namecheap]]></category>
            <dc:creator><![CDATA[Saurav Panda]]></dc:creator>
            <pubDate>Mon, 26 Dec 2022 04:51:36 GMT</pubDate>
            <atom:updated>2022-12-26T04:51:36.060Z</atom:updated>
            <content:encoded><![CDATA[<p>SSL (Secured Socket Layer) is one of the most common protocols which help you authenticate, encrypt and decrypt your data while navigating the vast internet.</p><p>Your browser communicates with the URL&#39;s web server whenever you request a URL. During this process, it asks for verification from the server, which comes in the form of an SSL certificate. Over 100+ trusted providers provide SSL certificates. If your SSL certificate is issued by one of these providers, your browser depends on the web server and processes end-to-end encrypted request-response flow.</p><p>Previously, these SSL certificates were expensive ($10 for a single domain/subdomain). Still, thanks to open-source efforts by the Internet Security Research Group (ISRG), we have an open-source provider. <strong>LetsEncrypt </strong>is a free open-source authority that provides SSL certificates for up to 90 days.</p><p>There are two ways to request SSL. The most commonly used way is to create SSL for a single domain/subdomain. This means you make separate SSL certificates for each subdomain. For example, you will generate SSL for example.com and then for subdomain.example.com. The second way is to create a wildcard SSL valid for all the subdomains. In this SSL, you specify that all subdomains are secured using the same certificates.</p><p>So let&#39;s get started with installing the SSL certificate for your website. We will need access to the DNS server records for our website. We will update the DNS records with the challenge token created by the LetsEncrypt.</p><p>The first step is to install the LetsEncrypt software on your mac or Ubuntu instance, which is called certbot. You can find the installation instructions here: <a href="https://eff-certbot.readthedocs.io/en/stable/install.html#installation">https://eff-certbot.readthedocs.io/en/stable/install.html#installation</a>.</p><p>Once installed, we will request the certbot to generate an SSL certificate for our domain example.org and all its subdomain *.example.org. (Note: if you only want SSL for a single domain, remove the wildcard parameter). You can request a wildcard domain-based SSL using the below command. Type this on your terminal:</p><pre>certbot certonly --manual  --preferred-challenges=dns   --email &lt;your_email&gt; --server https://acme-v02.api.letsencrypt.org/directory  --agree-tos  --manual-public-ip-logging-ok -d example.org -d *.example.org</pre><p>As we have two domains specified in the command, we will be given two security prompts that we need to update on our website. Your challenge code will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7PiG5sYcsNJwYfKfW0ni3w.png" /></figure><p>To update the challenge code in your DNS, login to your Namecheap hosting and go to “Domains”. In this, find the domain you want to update and click “Manage”. On the left side, you will find an option called “Modify the zone”. Here create a new TXT record, copy the domain and in the value, copy the given value. You will be creating two such records if you opt for wildcard domains.</p><p>(Note: Its recommended to wait for a few minutes after you update the DNS and then press continue on your terminal to do the authentication)</p><p>You will be shown the following screen on successful authentication with the path to your certificates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdE_7uaebCczDFOnX_iQGg.png" /></figure><p>In your NameCheap hosting, search for SSL/TSL and scroll to the bottom of the page. Select the domain in which you are updating the SSL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VNF3rMAzAlZjEzboH2f7g.png" /></figure><p>You will find your certificate in the path “/etc/letsencrypt/live/&lt;yourdomain&gt;/cert.pem”. You can read the file content on the terminal by using the below command. You can find the certificate in “cert.pem”, your chain (CABundle) in “chain.pem” and your private key in “privkey.pem”. (Note: CABundle has two outputs so ensure you copy both of them together)</p><pre>cat /etc/letsencrypt/live/example.org/cert.pem</pre><p>Once all the fields are filled, click on install, and your website should be successfully installed with an SSL certificate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea529313e2b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating AMI from AWS EC2 instance]]></title>
            <link>https://medium.com/@saurav.panda/creating-ami-from-aws-ec2-instance-e77bd7949d06?source=rss-9ed063934ef0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e77bd7949d06</guid>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[ami]]></category>
            <dc:creator><![CDATA[Saurav Panda]]></dc:creator>
            <pubDate>Mon, 14 Feb 2022 14:20:16 GMT</pubDate>
            <atom:updated>2022-02-14T14:20:16.901Z</atom:updated>
            <content:encoded><![CDATA[<p>AMIs are one of the most efficient ways to create a copy of an EC2 instance.</p><p>You can create an AMI to :</p><ul><li>Make copies of your server with all the configurations</li><li>Make a copy of your server to use it in the autoscaling group as a template</li><li>Backup your server configurations</li></ul><p>So today, we will see how to create an AMI and then use AMI to pop up new EC2 instances.</p><p><strong>Step 1:</strong></p><p>Login to your AWS console and navigate to the EC2 console. In the EC2 console, select the instance you want to create an AMI.</p><p><strong>Step 2</strong></p><p>After selecting the instance, click on <strong>Action</strong> <strong>-&gt; Image and templates -&gt; Create Image.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdt8kgYwXj91g4n9qsURUA.png" /></figure><p><strong>Step 3</strong></p><p>Add the Image name and Image description.</p><p>If No Reboot is not enabled, when an AMI is created, it first shutdowns the instance and then creates a snapshot for AMI creation and finally reboots the instance. No Reboot <em>disabled</em> is the preferred mode of operation while creating AMI to ensure that there are no crashes for current running instance.</p><p>So for current setup, we will not enable the No Reboot mode.</p><p>If you want, you can increase the size of your volume or you can always increase the size in later stages. Note: Decreasing the volume size is tricky once the instance has been created, so the suggested size is the minimum required for your application.</p><p>In our case, we will use 8GB .</p><p>If you want, you can increase the size of your volume or you can always increase the size in later stages. Note: Decreasing the volume size is tricky once the instance has been created, so the suggested size is the minimum required for your application.<br>In our case, we will use 8GB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-A9kvsBUbswYl8XAcm2laQ.png" /></figure><p><strong>Step 4:</strong></p><p>Wait for AMI to be created, It usually takes 5–10 mins but may vary based on the size of your application.</p><p>You can find your AMI by navigating to left navigation tab <strong>Images -&gt; AMIs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1cNBqFxSEdMx2dZgdQgx7w.png" /></figure><p>Once the ami status changes to Available , we can go ahead an create a new instance from AMI by selecting the AMI and clicking on <strong>Launch Instance from image.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_IeFd1Uej4urIduZv5eFfg.png" /></figure><p>You can also find your ami while launching instance from EC2 dashboard. In Step 1 of EC2 creation when you are selecting the AMI, navigate to My AMIs in the left navigation panel and select your AMI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j_9cNbxCzzQg_2cL3QbEdQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e77bd7949d06" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>