Cloud Formation Example

Posted on by tmack
Banner for Learning Computers post
Imagine you’re a System Administrator tasked with setting up a new environment.  Traditionally, this involves a long checklist: log into the console, click through menus to create a VPC, spin up three VMs, configure storage, attach security groups, and set up a load balancer. If you need a second environment for testing, you have to do it all over again, and hope you didn’t miss a single checkbox.  AWS Cloud Formation turns that manual checklist into a text file.

The Concept: Infrastructure as Code (IaC)

Think of Cloud Formation as a digital blueprint for your data center. In the old days, you’d build a house by hand. With Cloud Formation, you write down the architectural plans (the “Template”) and hand them to a robotic construction crew (the “Cloud Formation Engine”). The crew reads the plans and builds exactly what you asked for. If you want ten more identical houses, you don’t hire ten more crews; you just give the same plans to the robot again.

Real-Life Example for a SysAdmin

Let’s say you need a standard “Web App” setup:
  • Networking: A Virtual Private Cloud (VPC) with public and private subnets.
  • Compute: Two EC2 instances (VMs) running Linux.
  • Security: A Firewall rule (Security Group) allowing port 80 and 443.
Instead of clicking “Create” dozens of times, you write a YAML file that looks like this:
yaml
Resources:
  MyWebServer:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-0abcdef12345
      InstanceType: t3.micro
      SecurityGroups: [ !Ref MyWebSG ]

 Use code with caution.

When you “deploy” this file, Cloud Formation creates a Stack. If you decide later that those VMs need more RAM, you don’t manually resize them.  You update the text file to t3.medium, and Cloud Formation handles the update for you. If the update fails, it automatically rolls back to the previous working version.
Why This Matters to You
  1. Consistency: No more “it works in Dev but not in Prod.” The code is identical.
  2. Version Control: You can put your infrastructure files in Git. If a junior admin makes a mistake, you can “Revert” to yesterday’s version of the server.
  3. Speed: You can tear down and rebuild an entire environment in minutes rather than hours.

Similar Services Elsewhere

If you move to another cloud provider, the concept is the same, but the “brand” changes:
  • Microsoft Azure: Azure Resource Manager (ARM) Templates or Bicep.
  • Google Cloud (GCP): Google Cloud Deployment Manager.
  • Oracle Cloud (OCI): OCI Resource Manager (which is actually built on Terraform).
Speaking of Terraform, it’s the most popular “cloud-agnostic” alternative. While Cloud Formation only works for AWS, Terraform can manage AWS, Azure, and Google Cloud using the same workflow.