Sudha Yadav DevOps Engineer

Introduction to AWS CloudFormation

Sudha Yadav's photo
Sudha Yadav
·

6 min read

Introduction to AWS CloudFormation

Introduction

Today we'll explore AWS CloudFormation a powerful tool that allows you to define and manage your AWS infrastructure as code. CloudFormation simplifies the process of provisioning and managing resources enabling you to model and set up your AWS resources with a single text file or template. This post will cover the basics of CloudFormation including creating and managing stacks, using templates and best practices for leveraging infrastructure as code.

What is AWS CloudFormation?

AWS CloudFormation is a service that helps you model and set up your AWS resources so you can spend less time managing those resources and more time focusing on your applications. You create a template that describes all the AWS resources that you want (like Amazon EC2 instances or Amazon RDS databases) and CloudFormation takes care of provisioning and configuring those resources for you.

Key Features of AWS CloudFormation

  1. Infrastructure as Code : Define your infrastructure in code using JSON or YAML templates.

  2. Automated Resource Management : Automate the provisioning and updating of resources.

  3. Consistency and Repeatability : Ensure consistent environments across development, testing and production.

  4. Dependency Management : Automatically handles dependencies between resources.

  5. Change Sets : Preview changes before applying them to your infrastructure.

Getting Started with AWS CloudFormation

Step 1 :- Understanding CloudFormation Templates

CloudFormation templates are JSON or YAML formatted text files that describe your AWS infrastructure. These templates can include several major sections :-

  1. AWSTemplateFormatVersion : The version of the CloudFormation template format.

  2. Description : A text description of the template.

  3. Metadata : Additional information about the template.

  4. Parameters : Input values that can be passed to the template.

  5. Mappings : Static variables for conditional resource creation.

  6. Conditions : Define circumstances under which resources are created or properties are assigned.

  7. Resources : The AWS resources that you want to create.

  8. Outputs : Values that are returned whenever you view your stack’s properties.

Step 2 :- Creating a Simple CloudFormation Template

Let's create a basic CloudFormation template to deploy an Amazon EC2 instance.

AWSTemplateFormatVersion: '2010-09-09'
Description: A simple EC2 instance

Resources:
  MyEC2Instance:
    Type: 'AWS::EC2::Instance'
    Properties:
      InstanceType: t2.micro
      ImageId: ami-0c55b159cbfafe1f0
      KeyName: my-key-pair
      SecurityGroups:
        - default

Outputs:
  InstanceId:
    Description: The Instance ID
    Value: !Ref MyEC2Instance

Step 3 :- Creating a Stack

A stack is a collection of AWS resources that you can manage as a single unit. CloudFormation builds and provisions stacks based on the templates you provide.

  1. Navigate to the CloudFormation Console :-

    • Log in to the AWS Management Console.

    • Search for "CloudFormation" in the AWS services search bar and select it.

  2. Create a New Stack :-

    • Click "Create stack".

    • Choose "With new resources (standard)".

    • Select "Upload a template file" and upload your YAML template.

  3. Specify Stack Details :-

    • Stack name : Enter a name for your stack (e.g. MyEC2Stack).

    • Parameters : Enter values for any parameters defined in the template (none in this simple example).

  4. Configure Stack Options :-

    • Tags : Add tags to identify your stack.

    • Permissions : Assign an IAM role if necessary.

    • Advanced options : Configure stack policy, rollback triggers, etc.

  5. Review and Create :-

    • Review your settings and click "Create stack".

CloudFormation will now create your stack, provisioning the resources defined in your template.

Step 4 :- Managing Stacks

Once your stack is created you can manage it from the CloudFormation console.

  1. View Stack Details :-

    • Click on your stack name to view its details.

    • The "Resources" tab shows the resources created by the stack.

    • The "Outputs" tab displays any output values defined in the template.

  2. Updating a Stack :-

    • To update a stack modify your template file and upload the new version.

    • Select your stack, click "Update" and follow the prompts to apply the changes.

  3. Deleting a Stack :-

    • To delete a stack select it and click "Delete".

    • CloudFormation will delete all resources created by the stack.

Advanced CloudFormation Features

Step 5 :- Using Parameters and Mappings

Parameters allow you to pass input values to your template, making it more flexible and reusable.

  1. Defining Parameters :-
Parameters:
  InstanceType:
    Description: EC2 instance type
    Type: String
    Default: t2.micro
    AllowedValues:
      - t2.micro
      - t2.small
      - t2.medium
    ConstraintDescription: must be a valid EC2 instance type.
  1. Using Parameters in Resources :-
Resources:
  MyEC2Instance:
    Type: 'AWS::EC2::Instance'
    Properties:
      InstanceType: !Ref InstanceType
      ImageId: ami-0c55b159cbfafe1f0
      KeyName: my-key-pair
      SecurityGroups:
        - default

Mappings are static variables that help you create conditional resources.

  1. Defining Mappings :-
Mappings:
  RegionMap:
    us-east-1:
      HVM64: ami-0c55b159cbfafe1f0
    us-west-2:
      HVM64: ami-0bdb828fd58c52235
  1. Using Mappings in Resources :-
Resources:
  MyEC2Instance:
    Type: 'AWS::EC2::Instance'
    Properties:
      InstanceType: t2.micro
      ImageId: !FindInMap [RegionMap, !Ref 'AWS::Region', HVM64]
      KeyName: my-key-pair
      SecurityGroups:
        - default

Step 6 :- Using Conditions

Conditions enable you to create resources based on certain conditions.

  1. Defining Conditions :-
Conditions:
  CreateProdResources: !Equals [ !Ref EnvironmentType, prod ]
  1. Using Conditions in Resources :-
Resources:
  MyProdEC2Instance:
    Type: 'AWS::EC2::Instance'
    Condition: CreateProdResources
    Properties:
      InstanceType: t2.micro
      ImageId: ami-0c55b159cbfafe1f0
      KeyName: my-key-pair
      SecurityGroups:
        - default

Step 7 :- Outputs

Outputs are useful for returning information about the resources in your stack.

  1. Defining Outputs :-
Outputs:
  InstanceId:
    Description: The Instance ID
    Value: !Ref MyEC2Instance
  InstancePublicIP:
    Description: The public IP address of the EC2 instance
    Value: !GetAtt MyEC2Instance.PublicIp

Step 8 :- Change Sets

Change sets allow you to preview the changes CloudFormation will make to your stack before applying them.

  1. Creating a Change Set :-

    • Navigate to your stack in the CloudFormation console.

    • Click "Create Change Set" and upload the updated template.

    • Review the changes and execute the change set if acceptable.

Step 9 :- Nested Stacks

Nested stacks allow you to reuse common templates across different stacks, promoting modular and maintainable infrastructure.

  1. Creating a Nested Stack Template :-
Resources:
  VPCStack:
    Type: 'AWS::CloudFormation::Stack'
    Properties:
      TemplateURL: 'https://s3.amazonaws.com/mybucket/vpc-template.json'
      Parameters:
        VPCID: !Ref VPCID
  EC2Stack:
    Type: 'AWS::CloudFormation::Stack'
    Properties:
      TemplateURL: 'https://s3.amazonaws.com/mybucket/ec2-template.json'
      Parameters:
        SubnetID: !GetAtt VPCStack.Outputs.SubnetID

Best Practices for AWS CloudFormation

Organize Templates

  1. Use YAML : YAML is more readable and supports comments, making it easier to manage complex templates.

  2. Separate Logic : Use nested stacks to separate different layers of your infrastructure (e.g. network, compute, database).

Version Control

  1. Use Version Control : Store your templates in a version control system like Git.

  2. Tag and Label : Use tags and labels to manage different versions and environments (e.g. dev, test, prod).

Security

  1. IAM Roles : Use IAM roles to control access to CloudFormation and the resources it manages.

  2. Parameter Store : Use AWS Systems Manager Parameter Store or AWS Secrets Manager for sensitive information.

Testing and Validation

  1. Linting : Use tools like cfn-lint to validate your templates.

  2. Change Sets : Always create change sets to preview changes before applying them.

Documentation

  1. Template Description : Provide clear descriptions for your templates and resources.

  2. Outputs : Use outputs to provide useful information about your stack.

Conclusion

AWS CloudFormation is an essential tool for automating the provisioning and management of your AWS infrastructure. By defining your infrastructure as code you can ensure consistency, reduce errors and simplify management across multiple environments. In this blog post we covered the basics of CloudFormation, creating and managing stacks using templates and best practices for effective infrastructure management.

Stay tuned for more insights in our upcoming blog posts.

Let's connect and grow on LinkedIn :Click Here

Let's connect and grow on Twitter :Click Here

Happy Cloud Computing!!!

Happy Reading!!!

Sudha Yadav

AWSDevopsCloudCloud ComputingTrainWithShubhamlearningLearning JourneycommunityDevops articlescloudformation