---

Introduction

Modern cloud applications require infrastructure that is:

• Repeatable
• Version Controlled
• Automated
• Secure
• Easy to Deploy

Imagine manually creating the following AWS resources every time you deploy a Spring Boot application:

• VPC
• Subnets
• Internet Gateway
• NAT Gateway
• Route Tables
• Security Groups
• IAM Roles
• Application Load Balancer
• ECS Cluster
• Amazon ECR
• Amazon Aurora
• Route53
• CloudWatch
• WAF

This process is slow, error-prone, and difficult to reproduce.

AWS provides two Infrastructure as Code (IaC) solutions:

• AWS CloudFormation
• AWS Cloud Development Kit (CDK)

These tools let you define your infrastructure as code, making deployments consistent and repeatable.

---

Learning Objectives

After completing this article, you will understand:

• What is Infrastructure as Code?
• AWS CloudFormation
• AWS CDK
• Stacks
• Constructs
• Templates
• Change Sets
• Nested Stacks
• CDK Apps
• CDK Constructs
• CloudFormation vs CDK
• Terraform vs CloudFormation
• Production Best Practices

---

What is Infrastructure as Code?

Infrastructure as Code (IaC) means defining infrastructure using code instead of manually creating resources through the AWS Console.

Benefits:

• Version Control
• Automation
• Repeatability
• Faster Deployments
• Easy Rollback
• Reduced Human Errors

---

Why CloudFormation?

Without IaC

AWS Console

↓

Create VPC

↓

Create ALB

↓

Create ECS

↓

Deploy Spring Boot

Manual configuration increases operational risk.

---

With CloudFormation

CloudFormation Template

↓

Deploy Stack

↓

Entire Infrastructure Created

---

High-Level Architecture

flowchart LR

Developer

CloudFormation

AWS

SpringBootInfrastructure

Developer --> CloudFormation
CloudFormation --> AWS
AWS --> SpringBootInfrastructure

---

Enterprise Architecture

flowchart TD

Developer

GitHub

CodePipeline

CloudFormation

VPC

ECS

Aurora

ALB

CloudWatch

Developer --> GitHub
GitHub --> CodePipeline
CodePipeline --> CloudFormation

CloudFormation --> VPC
CloudFormation --> ECS
CloudFormation --> Aurora
CloudFormation --> ALB
CloudFormation --> CloudWatch

---

What is AWS CloudFormation?

AWS CloudFormation is AWS's native Infrastructure as Code service.

You define infrastructure in:

• YAML
• JSON

CloudFormation provisions and manages AWS resources automatically.

---

CloudFormation Components

Component	Description
Template	Infrastructure Definition
Stack	Running Infrastructure
Resource	AWS Resource
Parameter	User Input
Output	Generated Value
Change Set	Preview Changes

---

CloudFormation Workflow

flowchart LR

WriteTemplate

Validate

CreateStack

Deploy

AWSResources

WriteTemplate --> Validate
Validate --> CreateStack
CreateStack --> Deploy
Deploy --> AWSResources

---

CloudFormation Template

Example:

Resources:

  MyBucket:

    Type: AWS::S3::Bucket

    Properties:

      BucketName: codewithvenu-assets

Deploy:

aws cloudformation deploy \
--template-file template.yaml \
--stack-name springboot-stack

---

Stack

A Stack is a collection of AWS resources created from one CloudFormation template.

Example:

springboot-production

Contains:

• VPC
• ECS
• ALB
• RDS
• IAM

---

Parameters

Parameters make templates reusable.

Example:

Parameters:

  Environment:

    Type: String

Supported values:

dev

test

stage

prod

---

Outputs

Example:

Outputs:

  LoadBalancerDNS:

    Value: !GetAtt ApplicationLoadBalancer.DNSName

Outputs can be referenced by other stacks or CI/CD pipelines.

---

Change Sets

Before deployment:

Current Stack

↓

Preview Changes

↓

Apply Changes

This helps avoid unexpected infrastructure modifications.

---

Nested Stacks

Large infrastructures should be split into smaller templates.

Example:

network.yaml

ecs.yaml

database.yaml

security.yaml

Advantages:

• Easier maintenance
• Faster deployments
• Better reusability

---

AWS CDK

AWS CDK (Cloud Development Kit) lets you define AWS infrastructure using programming languages instead of YAML or JSON.

Supported languages:

• Java
• TypeScript
• Python
• C#
• Go

---

Why CDK?

Instead of writing long YAML templates:

Resources:

  VPC:

    Type: AWS::EC2::VPC

You write familiar application code.

Example (Java):

Vpc vpc = Vpc.Builder.create(this, "Vpc")
        .maxAzs(2)
        .build();

CDK generates the CloudFormation template automatically.

---

CDK Architecture

flowchart LR

Developer

AWSCDK

CloudFormation

AWS

Developer --> AWSCDK
AWSCDK --> CloudFormation
CloudFormation --> AWS

---

CDK Components

Component	Purpose
App	Entry Point
Stack	Infrastructure Unit
Construct	Reusable Component
Resource	AWS Resource

---

CDK Project Structure

springboot-cdk

├── src
├── lib
├── bin
├── pom.xml
├── cdk.json
└── README.md

---

CDK Commands

Initialize project

cdk init app --language java

Synthesize template

cdk synth

Preview changes

cdk diff

Deploy

cdk deploy

Destroy

cdk destroy

---

CDK Example

Create S3 Bucket

Bucket.Builder.create(this, "AssetsBucket")
        .bucketName("codewithvenu-assets")
        .build();

---

Spring Boot Infrastructure

Typical resources:

• VPC
• ALB
• ECS Cluster
• ECR Repository
• IAM Roles
• Aurora Database
• CloudWatch
• Route53

---

Infrastructure Architecture

flowchart TD

CloudFormation

VPC

ALB

AmazonECS

Aurora

CloudWatch

Route53

CloudFormation --> VPC
CloudFormation --> ALB
CloudFormation --> AmazonECS
CloudFormation --> Aurora
CloudFormation --> CloudWatch
CloudFormation --> Route53

---

CloudFormation vs CDK

CloudFormation	AWS CDK
YAML/JSON	Java, TypeScript, Python, C#, Go
Declarative	Imperative
Native AWS	Built on CloudFormation
Large templates	Less boilerplate
Good for simple stacks	Better for complex applications

---

Terraform vs CloudFormation

Terraform	CloudFormation
Multi-cloud	AWS Only
HashiCorp Language (HCL)	YAML/JSON
Community Modules	AWS Native
Excellent for hybrid cloud	Deep AWS integration

---

CI/CD Integration

CloudFormation and CDK integrate with:

• GitHub Actions
• AWS CodePipeline
• Jenkins
• GitLab CI
• Azure DevOps

Deployment flow:

Git Push

↓

Build

↓

Deploy Infrastructure

↓

Deploy Spring Boot

---

Monitoring

Monitor:

• Stack Events
• Deployment Status
• Rollbacks
• Drift Detection
• CloudWatch Metrics

---

Drift Detection

CloudFormation detects configuration drift.

Example:

Template

↓

AWS Resource Modified Manually

↓

Drift Detected

Helps maintain infrastructure consistency.

---

Production Architecture

flowchart TD

Developer

GitHub

GitHubActions

CloudFormation

VPC

ALB

AmazonECS

Aurora

CloudWatch

Route53

AWSWAF

Developer --> GitHub
GitHub --> GitHubActions
GitHubActions --> CloudFormation

CloudFormation --> VPC
CloudFormation --> ALB
CloudFormation --> AmazonECS
CloudFormation --> Aurora
CloudFormation --> Route53
CloudFormation --> AWSWAF

AmazonECS --> CloudWatch

---

Common Errors

Stack Creation Failed

Check:

• IAM Permissions
• Resource Limits
• Template Syntax

---

Stack Update Failed

Review:

• Stack Events
• Change Set
• Resource Dependencies

---

Drift Detected

Run Drift Detection.

Synchronize template with actual infrastructure.

---

CDK Deployment Failed

Verify:

• AWS Credentials
• Bootstrap completed (cdk bootstrap)
• Region configuration

---

Best Practices

• Store templates in Git
• Use Parameters for environments
• Split large templates into Nested Stacks
• Use Outputs for integration
• Enable Stack Policies for critical resources
• Use Change Sets before production deployments
• Prefer CDK for complex infrastructure
• Use CloudFormation Drift Detection
• Automate deployments using CI/CD
• Tag all AWS resources
• Avoid manual infrastructure changes

---

Developer Checklist

Before production deployment:

• CloudFormation template validated
• Parameters configured
• Outputs verified
• Nested Stacks organized
• Change Set reviewed
• CDK bootstrapped (if using CDK)
• IAM permissions configured
• Stack deployed successfully
• Drift Detection enabled
• CloudWatch monitoring configured

---

Interview Questions

What is AWS CloudFormation?

AWS CloudFormation is AWS's Infrastructure as Code service that provisions and manages AWS resources using declarative templates.

---

What is AWS CDK?

AWS Cloud Development Kit (CDK) allows developers to define cloud infrastructure using familiar programming languages. CDK synthesizes these definitions into CloudFormation templates.

---

What is a Stack?

A Stack is a collection of AWS resources created and managed together by CloudFormation.

---

What is a Change Set?

A Change Set previews infrastructure changes before they are applied to an existing CloudFormation stack.

---

What is Drift Detection?

Drift Detection identifies differences between the CloudFormation template and the actual deployed AWS resources.

---

When should you choose CloudFormation vs CDK?

Use CloudFormation when working with straightforward declarative templates or existing AWS-native infrastructure. Use CDK when building complex, reusable infrastructure using programming languages and software engineering practices.

---

Summary

In this article, we explored AWS CloudFormation and AWS CDK for provisioning Spring Boot infrastructure.

We covered:

• Infrastructure as Code
• CloudFormation templates
• Stacks
• Parameters
• Outputs
• Change Sets
• Nested Stacks
• AWS CDK
• Constructs
• CI/CD integration
• Drift Detection
• Production best practices

AWS CloudFormation and AWS CDK enable teams to automate infrastructure provisioning, improve consistency, and integrate infrastructure changes into modern DevOps pipelines. Combined with GitHub Actions, CodePipeline, Amazon ECS, Route53, and CloudWatch, they provide a powerful foundation for managing enterprise Spring Boot deployments on AWS.

---