<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS on DevLogs</title><link>https://blog.param.sh/tags/aws/</link><description>Recent content in AWS on DevLogs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 28 Mar 2026 18:23:33 +0530</lastBuildDate><atom:link href="https://blog.param.sh/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>I PASSED AWS DEVELOPER ASSOCIATE TODAY!!</title><link>https://blog.param.sh/posts/aws-developer-associate-exam-review/</link><pubDate>Sat, 28 Mar 2026 18:23:33 +0530</pubDate><guid>https://blog.param.sh/posts/aws-developer-associate-exam-review/</guid><description>&lt;h2 id="tldr"&gt;
 TL;DR
 &lt;a class="heading-link" href="#tldr"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;YEP! Today is the day after 2 months of grinding on &lt;a href="https://skillbuilder.aws" class="external-link" target="_blank" rel="noopener"&gt;SkillBuilder&lt;/a&gt; solving N number of Builder Labs / Digital Courses / Learning Plans I have enrolled and completed just to over-prepare for the Associate exam (more on this later) coz I was nervous &amp;#x1f605;&amp;hellip; I finally cleared AWS Certified Developer Associate examination today with a whopping score of &lt;strong&gt;839&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Exam went really smooth, I encountered some tricky questions in the examination but most were just a read-through. Some questions were a bummer with very long context, then asked, &amp;ldquo;How would you debug microservices performance in production?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Part 3.1: Setting up AWS infra for hosting a mail server</title><link>https://blog.param.sh/posts/setting-up-your-own-mail-server/</link><pubDate>Sun, 15 Mar 2026 03:55:13 +0530</pubDate><guid>https://blog.param.sh/posts/setting-up-your-own-mail-server/</guid><description>&lt;div class="notice note"&gt;
 &lt;div class="notice-title"&gt;
 &lt;i class="fa-solid fa-sticky-note" aria-hidden="true"&gt;&lt;/i&gt;Note
 &lt;/div&gt;
 &lt;div class="notice-content"&gt;This walkthrough is part of the &lt;a href="https://blog.param.sh/series/cloning-gmails-architecture" &gt;Cloning Gmail&amp;rsquo;s Architecture&lt;/a&gt; series. For better context, I suggest you to start from &lt;a href="https://blog.param.sh/posts/mail-server-communications-101/" &gt;Part 1&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;

&lt;p&gt;In this tutorial, we will look how we can deploy an EC2 instance, assign an Elastic IP (static public IP), enable port access for SMTP / IMAP communications and more, to configure the infrastructure for self-hosting a private email server.&lt;/p&gt;
&lt;h3 id="pre-requisites"&gt;
 Pre-Requisites
 &lt;a class="heading-link" href="#pre-requisites"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Have an AWS Account and basic knowledge on how to setup an EC2 instance in AWS.&lt;/li&gt;
&lt;li&gt;Know about mail protocols and how mail communication works.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;If you have any other cloud provider as your preference feel free to jump to the &lt;a href="#setting-up-the-mail-server" &gt;Setting up the Mail Server&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Part 2: What do you need to self-host an email server?</title><link>https://blog.param.sh/posts/self-hosting-an-email-server-stack/</link><pubDate>Sun, 08 Mar 2026 22:21:21 +0530</pubDate><guid>https://blog.param.sh/posts/self-hosting-an-email-server-stack/</guid><description>&lt;h2 id="selecting-the-stack"&gt;
 Selecting the Stack
 &lt;a class="heading-link" href="#selecting-the-stack"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;This series begins with replacing Gmail using a fully self-hosted mail system on AWS. The goal is not just email independence — it is learning real infrastructure, security, and operational ownership.&lt;/p&gt;
&lt;p&gt;This post explains the selected stack, what alternatives were considered, and why these choices were made.&lt;/p&gt;
&lt;h1 id="tldr---final-stack-overview"&gt;
 TL;DR - Final Stack Overview
 &lt;a class="heading-link" href="#tldr---final-stack-overview"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hosting:&lt;/strong&gt; Amazon EC2 (1-year Reserved Instance)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mail Server:&lt;/strong&gt; iRedMail&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mail Client:&lt;/strong&gt; Mozilla Thunderbird&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Domain Registrar:&lt;/strong&gt; Namecheap&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DNS Provider:&lt;/strong&gt; Namecheap DNS&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Keep reading if you want to know about the comparisons made in order to reach to these final verdicts.&lt;/p&gt;</description></item></channel></rss>