AWS : Infrastructure Deployment


  • Key concepts
  • CloudFormation

Key concepts

  • CloudFormation
  • Automation: The use of software to create repeatable instructions and processes to replace or reduce human interaction with IT systems
  • Cloud Governance: The people, process, and technology associated with your cloud infrastructure, security, and operations. It involves a framework with a set of policies and standard practices
  • Infrastructure as Code: The process of managing and provisioning computer resources through human and machine-readable definition files, rather than physical hardware configuration or interactive configuration tools like the AWS console
  • IT Audit: The examination and evaluation of an organization’s information technology infrastructure, policies and operations


  • CloudFormation is a AWS service for create infrastructure as code.
  • it’s a yaml file

How to start with CloudFormation

  1. Services -> CloudFormation
  2. Create stack “With new resources (standard)”
  3. Template is ready
  4. Upload a template file
  5. Click “Choose file” button
  6. Select provided YAML file
  7. Next
CloudFormation Template sections
  • Format version
  • Decsription
  • Parameters
  • Resources
  • Outputs


The other option is using terraform to deploy the Terraform. From the experience I would suggest to use the Terraform to deploy resources on AWS.

The CloudFormation is not so handy for me as cloud solution architect (right now may 2021), because of the following reasons:

  • The CloudFormation doesn’t even work properly when I want to destroy e.g. Fargate cluster resources, which are created with AWS wizard.
  • Sometimes I have seen that some resources remain and cause extra unnecessary expenses.

But doesn’t mean I don’t use AWS. I have several project which are running on AWS. Only to solve the described weakness I use Terraform. In this way I can manage (deploy/destroy) resources very easy.

At least I know if I keep the Terraform Satefiles in a right place, I can destroy all the resources, without thinking about it that a resource remains and cause extra unnecessary costs.


You owe your dreams your courage.

Koleka Putuma

Published by parisamoosavinezhad

- Software Engineer - Software Architect - Software and database specialist - Cloud solution architect

One thought on “AWS : Infrastructure Deployment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: