# Intro to Infrastructure as Code (IaC) in AWS context

Hello devs

This post is about the following AWS picture:

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1670792957085/WQ2uz_iBb.png align="center")

Ok ... We have here in the cloud parts of the picture the following AWS cloud components:

*   [Cloudformation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html) - Infrastructure as Code service from AWS to deploy aws components
    
*   [S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) - object storage service, you can deploy here big data
    
*   [Cloudfront](https://aws.amazon.com/cloudfront/) - CDN service from AWS
    
*   [Lambda](https://aws.amazon.com/lambda/) - Serverless on AWS 🚀
    
*   ....
    

**The list can be around 200 services 😀**

To deploy these AWS services you have many options. If you quickly test around you can use the AWS console. But if you want more reproducible architecture with CI/CD chain or deployments over stages with many accounts, in Cloud-Native development there are solutions named under the buzzword **IaC (Infrastructure as Code)**.

IaC code creates your infrastructure which is composed of cloud services, like S3. **The advantage is we can handle your infrastructure like source code** 😀

# Entering Cloudformation

Cloudformation is IaC service from AWS which accepts *YML* or *JSON* formatted files and deploys the described infrastructure from these files. Yes, Cloudformation is a setup as *YML* or *JSON* file 😀

For example, the following snippet describes an S3-Bucket (*YML*\-formatted):

```plaintext
 MyS3Bucket:
    Type: 'AWS::S3::Bucket'
    Properties:
      BucketName: !Join
        - '-'
        - - !Ref S3BucketName
          - !Ref 'AWS::Region'
```

The problem with Cloudformation is, these YML or JSON files can be very complex for big cloud architectures. Refactoring can be a disaster, therefore over the years many IaC frameworks are developed, so we enter **IaC Frameworks** or **abstractions over Cloudformation**

*   [Terraform](https://www.terraform.io/)
    
*   [Pulumi](https://www.pulumi.com)
    
*   [CDK (from AWS)](https://docs.aws.amazon.com/cdk/latest/guide/home.html)
    
*   [Serverless Framework](https://www.serverless.com/)
    
*   [**SST**](https://docs.serverless-stack.com/installation)
    

There are much more frameworks, every one with his strength and different paradigm.

All these frameworks produces in AWS as cloud provider, Cloudformation code except Terraform and Pulimi, which creates and deploys your services. Framworks like CDK, Serverless Framework or SST is only **abstraction** over Cloudformation, to make it easier to develop your infrastructure.

For example following SST-Snippet creates an S3-Bucket named Uploads.

```plaintext
let bucket = new sst.Bucket(this, "Uploads");
```

You see the difference, SST framework in this case uses another abstraction layer over CDK and has a programming paradigm for creating IaC 😀

Happy Coding 😀