<?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>DevOps on Daman Arora</title>
    <link>https://damanarora.netlify.app/tags/devops/</link>
    <description>Recent content in DevOps on Daman Arora</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sun, 17 May 2026 18:00:00 +0000</lastBuildDate><atom:link href="https://damanarora.netlify.app/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Deployments: Managing Infrastructure at Scale</title>
      <link>https://damanarora.netlify.app/posts/aws-deployments-infrastructure-at-scale/</link>
      <pubDate>Sun, 17 May 2026 18:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-deployments-infrastructure-at-scale/</guid>
      <description>Once you understand the building blocks of AWS, the next question is practical: how do you get an app onto AWS, and how do you manage it afterward? Five services cover this, and they group neatly by the job they do.
The mental map ┌─────────────────────────────────────────────────────┐ │ DEFINE infrastructure as code │ │ • CloudFormation (YAML/JSON templates) │ │ • CDK (real code → compiles to CFN) │ ├─────────────────────────────────────────────────────┤ │ DEPLOY applications │ │ • Elastic Beanstalk (PaaS, all-in-one) │ │ • CodeDeploy (push code to existing fleet) │ ├─────────────────────────────────────────────────────┤ │ MANAGE running infrastructure │ │ • Systems Manager (SSM) │ └─────────────────────────────────────────────────────┘ CloudFormation CloudFormation is declarative AWS infrastructure as code.</description>
    </item>
    
  </channel>
</rss>
