<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>AWS on Daman Arora</title>
    <link>https://damanarora.netlify.app/tags/aws/</link>
    <description>Recent content in AWS on Daman Arora</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sat, 16 May 2026 20:00:00 +0000</lastBuildDate><atom:link href="https://damanarora.netlify.app/tags/aws/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS S3: Object Storage</title>
      <link>https://damanarora.netlify.app/posts/aws-s3-object-storage/</link>
      <pubDate>Sat, 16 May 2026 20:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-s3-object-storage/</guid>
      <description>S3 is object storage — durable, effectively infinite, and accessed over an HTTP API. It is the default place to put blobs in AWS: images, backups, logs, static assets, anything.
The core pieces Piece What it is Bucket The top-level container for objects. Its name is globally unique, and it lives in one region. Object A blob plus metadata, addressed by a key. The thing you actually store. Key The object&amp;rsquo;s &amp;ldquo;path&amp;rdquo; — e.</description>
    </item>
    
    <item>
      <title>AWS ELB &amp; ASG: Load Balancing and Auto Scaling</title>
      <link>https://damanarora.netlify.app/posts/aws-elb-and-asg/</link>
      <pubDate>Sat, 16 May 2026 18:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-elb-and-asg/</guid>
      <description>A single EC2 instance is a single point of failure. To make an app highly available and elastic — able to handle variable load and survive failures automatically — AWS gives you two services that work hand in hand: ELB and ASG.
The two pieces Service What it does Question it answers ELB Distributes incoming traffic across multiple EC2s &amp;ldquo;How do users reach my fleet?&amp;rdquo; ASG Adds, removes, and replaces EC2s based on demand or health &amp;ldquo;How big should my fleet be?</description>
    </item>
    
    <item>
      <title>AWS EC2: Instance Storage</title>
      <link>https://damanarora.netlify.app/posts/aws-ec2-instance-storage/</link>
      <pubDate>Sat, 16 May 2026 16:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-ec2-instance-storage/</guid>
      <description>Once an EC2 instance is running, it needs somewhere to put data. AWS gives you three kinds of disk to attach to a VM, and each one behaves very differently.
The options Type Storage Lifecycle Scope EBS Block, network-attached Persistent One AZ Instance Store Block, physically on the host Ephemeral — lost on stop/terminate One host EFS File (NFS), network share Persistent Multi-AZ Mental model EC2 ──attaches──&amp;gt; EBS volume (its own dedicated disk, persistent) EC2 ──has──────&amp;gt; Instance Store (host&amp;#39;s physical NVMe, ephemeral) EC2 ──mounts───&amp;gt; EFS (network file share, many EC2s share it) In plain terms:</description>
    </item>
    
    <item>
      <title>AWS EC2: Elastic Compute Cloud</title>
      <link>https://damanarora.netlify.app/posts/aws-ec2-elastic-compute-cloud/</link>
      <pubDate>Sat, 16 May 2026 14:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-ec2-elastic-compute-cloud/</guid>
      <description>EC2 is the compute layer of AWS — rentable virtual machines. When you need a server to run an application, EC2 is where it lives.
The core pieces Launching an EC2 instance means assembling a handful of parts. Each one answers a specific question.
Piece What it is Instance A running VM AMI The image/template the VM boots from — OS plus pre-installed software Instance Type Sizing — CPU, RAM, network (e.</description>
    </item>
    
    <item>
      <title>AWS IAM: Identity &amp; Access Management</title>
      <link>https://damanarora.netlify.app/posts/aws-iam-identity-and-access-management/</link>
      <pubDate>Sat, 16 May 2026 10:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-iam-identity-and-access-management/</guid>
      <description>IAM is the part of AWS that controls who can do what. Every API call, every console click, and every request a service makes is checked against IAM before it is allowed to proceed.
The 4 building blocks IAM is built from four pieces. Understanding what each one is for makes the rest of the service easy to reason about.
Block What it is Used for User Long-lived credentials Humans Group A bundle of users Sharing permissions Role A temporary, assumed identity Services, federated users, cross-account access Policy JSON rules Attached to a user, group, role, or resource Mental model Principal (user/role) ──has──&amp;gt; Policy ──grants──&amp;gt; Permissions on resources It helps to keep these one-line definitions in mind:</description>
    </item>
    
  </channel>
</rss>
