<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: JamAl</title>
    <description>The latest articles on DEV Community by JamAl (@jamal_09445e8aefac7b46f2d).</description>
    <link>https://dev.to/jamal_09445e8aefac7b46f2d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4094634%2F0a6ac23c-dc64-4d91-a526-26cb564ab3b2.png</url>
      <title>DEV Community: JamAl</title>
      <link>https://dev.to/jamal_09445e8aefac7b46f2d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jamal_09445e8aefac7b46f2d"/>
    <language>en</language>
    <item>
      <title>Learn AWS CloudFormation</title>
      <dc:creator>JamAl</dc:creator>
      <pubDate>Tue, 25 Aug 2026 18:25:54 +0000</pubDate>
      <link>https://dev.to/jamal_09445e8aefac7b46f2d/learn-aws-cloudformation-3j0n</link>
      <guid>https://dev.to/jamal_09445e8aefac7b46f2d/learn-aws-cloudformation-3j0n</guid>
      <description>&lt;p&gt;is Amazon’s infrastructure-as-code (IaC) service. It lets you define and provision your AWS resources by writing a text file (a “template”) instead of clicking through the console or running commands one by one.&lt;/p&gt;

&lt;p&gt;The core idea&amp;nbsp;￼&lt;/p&gt;

&lt;p&gt;You describe what you want your infrastructure to look like — EC2 instances, S3 buckets, databases, IAM roles, networking, etc. — in a template written in JSON or YAML. CloudFormation reads that template and creates, updates, or deletes the resources for you, in the right order, handling dependencies automatically.&lt;/p&gt;

&lt;p&gt;Key concepts&amp;nbsp;￼&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Template — the file describing your resources and their configuration.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Stack — a running instance of a template. When you deploy a template, CloudFormation creates a stack containing all those resources. You manage them as a single unit; delete the stack and it tears down everything it created.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Change set — a preview of what will change before you apply an update, so there are no surprises.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Parameters / Outputs — inputs you pass in at deploy time (e.g., instance size) and values you export out (e.g., a database endpoint).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Why people use it&amp;nbsp;￼&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Repeatable &amp;amp; consistent — spin up identical environments (dev, staging, prod) from the same template.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Version-controlled — your infrastructure lives in Git alongside your code, with history and code review.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Automatic dependency handling — CloudFormation figures out the correct creation/deletion order.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Safe rollbacks — if a deployment fails partway, it can roll back to the previous working state.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;No extra charge — you only pay for the underlying resources it provisions.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>aws</category>
      <category>cloud</category>
      <category>devops</category>
      <category>infrastructure</category>
    </item>
  </channel>
</rss>
