Why Infrastructure as Code matters in AWS - See It in Action

Why Infrastructure as Code matters

📖 Scenario: You are working as a cloud engineer for a small company. The company wants to manage its cloud resources in a way that is easy to repeat, track, and fix if something goes wrong. They heard about Infrastructure as Code (IaC) and want to try it out.

🎯 Goal: Build a simple AWS infrastructure using code to create a virtual server (EC2 instance) and understand why managing infrastructure this way is helpful.

📋 What You'll Learn

Create a dictionary with the exact AWS resource details

Add a configuration variable for the instance type

Use a loop or comprehension to prepare the resource setup

Complete the code with the final resource declaration

💡 Why This Matters

🌍 Real World

Companies use Infrastructure as Code to manage cloud resources reliably and quickly, avoiding manual setup errors.

💼 Career

Cloud engineers and DevOps professionals use IaC daily to automate and maintain cloud infrastructure efficiently.

1

Create the AWS resource details dictionary

Create a dictionary called aws_resources with these exact entries: 'EC2Instance': 'MyFirstInstance', 'AMI': 'ami-0abcdef1234567890', 'KeyName': 'MyKeyPair'

AWS

# Create the aws_resources dictionary with the specified entries
# Your code here

Hint

Think of aws_resources as a list of things you want to create in AWS, with names and IDs.

2

Add the instance type configuration

Add a variable called instance_type and set it to the string 't2.micro' to specify the size of the EC2 instance.

AWS

aws_resources = {
    'EC2Instance': 'MyFirstInstance',
    'AMI': 'ami-0abcdef1234567890',
    'KeyName': 'MyKeyPair'
}
# Add the instance_type variable below
# Your code here

Hint

The instance type tells AWS how powerful your virtual server should be.

3

Prepare the resource setup with a dictionary comprehension

Create a new dictionary called resource_setup using a dictionary comprehension that includes all items from aws_resources and adds a new key 'InstanceType' with the value from instance_type.

AWS

aws_resources = {
    'EC2Instance': 'MyFirstInstance',
    'AMI': 'ami-0abcdef1234567890',
    'KeyName': 'MyKeyPair'
}
instance_type = 't2.micro'
# Create resource_setup dictionary with all aws_resources plus 'InstanceType'
# Your code here

Hint

Use a dictionary comprehension to copy aws_resources and then add the instance type.

4

Complete the AWS EC2 instance resource declaration

Add a variable called ec2_instance and set it to a dictionary with the keys 'Name', 'ImageId', 'KeyName', and 'InstanceType' using the corresponding values from resource_setup.

AWS

aws_resources = {
    'EC2Instance': 'MyFirstInstance',
    'AMI': 'ami-0abcdef1234567890',
    'KeyName': 'MyKeyPair'
}
instance_type = 't2.micro'
resource_setup = {key: value for key, value in aws_resources.items()}
resource_setup['InstanceType'] = instance_type
# Create ec2_instance dictionary with keys 'Name', 'ImageId', 'KeyName', 'InstanceType'
# Your code here

Hint

This dictionary represents the final EC2 instance setup you would use in your Infrastructure as Code script.

Practice

1. Why is Infrastructure as Code (IaC) important when managing cloud resources?

easy

A. It requires manual configuration for every deployment.

B. It makes cloud setups repeatable and reduces manual errors.

C. It slows down the deployment process.

D. It prevents teams from collaborating on infrastructure.

Solution

1. Step 1: Understand IaC purpose

   IaC automates cloud setup, making it repeatable and consistent.

2. Step 2: Compare options

   Only It makes cloud setups repeatable and reduces manual errors. describes IaC benefits correctly; others describe drawbacks or false statements.

3. Final Answer:

   It makes cloud setups repeatable and reduces manual errors. -> Option B

4. Quick Check:

   Repeatable setup = A [OK]

Hint: IaC automates setup to avoid manual mistakes [OK]

Common Mistakes:

• Thinking IaC requires manual steps every time
• Believing IaC slows deployment
• Assuming IaC blocks team collaboration

2. Which of the following is the correct way to define an AWS S3 bucket using Infrastructure as Code in AWS CloudFormation?

easy

A. "Resources": { "MyBucket": { "Type": "AWS::S3::Bucket" } }

B. "Resources": { "MyBucket": { "Type": "AWS::EC2::Instance" } }

C. "Resources": { "MyBucket": { "Type": "AWS::Lambda::Function" } }

D. "Resources": { "MyBucket": { "Type": "AWS::DynamoDB::Table" } }

Solution

1. Step 1: Identify resource type for S3 bucket

   The correct CloudFormation type for an S3 bucket is "AWS::S3::Bucket".

2. Step 2: Match option with correct type

   "Resources": { "MyBucket": { "Type": "AWS::S3::Bucket" } } uses "AWS::S3::Bucket"; others use unrelated resource types.

3. Final Answer:

   "Resources": { "MyBucket": { "Type": "AWS::S3::Bucket" } } -> Option A

4. Quick Check:

   S3 bucket type = AWS::S3::Bucket [OK]

Hint: S3 bucket type always AWS::S3::Bucket in CloudFormation [OK]

Common Mistakes:

• Confusing resource types like EC2 or Lambda for S3
• Using incorrect syntax for resource definition
• Forgetting to include the "Resources" key

3. Given this AWS CloudFormation snippet:

{
  "Resources": {
    "MyBucket": {
      "Type": "AWS::S3::Bucket",
      "Properties": {
        "BucketName": "my-unique-bucket-123"
      }
    }
  }
}

What will happen when this template is deployed twice without changes?

medium

A. The bucket will be created twice with different names.

B. The deployment will fail due to duplicate bucket name.

C. The deployment will succeed, leaving the existing bucket unchanged.

D. A new bucket with the same name will overwrite the old one.

Solution

1. Step 1: Understand idempotency in IaC

   CloudFormation is idempotent: deploying the same template to the same stack twice detects no changes and succeeds without modifying resources.

2. Step 2: Analyze bucket name uniqueness

   S3 bucket names must be unique globally, but CloudFormation tracks the resource by logical ID in the stack, recognizing the existing bucket on redeploy.

3. Step 3: Determine deployment behavior

   The second deployment succeeds without recreating or failing, as the state matches.

4. Final Answer:

   The deployment will succeed, leaving the existing bucket unchanged. -> Option C

5. Quick Check:

   Idempotent deployment succeeds without changes = B [OK]

Hint: Same template redeploy updates existing resources safely [OK]

Common Mistakes:

• Thinking duplicate buckets with same name can be created
• Assuming deployment fails on second run without changes
• Believing new bucket overwrites old one forcibly

4. You wrote this AWS CloudFormation snippet but deployment fails:

{
  "Resources": {
    "MyBucket": {
      "Type": "AWS::S3::Bucket",
      "Properties": {
        "BucketName": 12345
      }
    }
  }
}

What is the error and how to fix it?

medium

A. Type value is incorrect; change to AWS::S3::BucketName.

B. BucketName cannot be set manually; remove the property.

C. Resources key is missing; add it at the root level.

D. BucketName must be a string, not a number; fix by quoting the name.

Solution

1. Step 1: Identify property type error

   BucketName must be a string; 12345 is a number causing syntax error.

2. Step 2: Correct the property value

   Fix by enclosing bucket name in quotes, e.g., "12345" or a valid string.

3. Final Answer:

   BucketName must be a string, not a number; fix by quoting the name. -> Option D

4. Quick Check:

   BucketName type string required = C [OK]

Hint: Bucket names must be strings in quotes [OK]

Common Mistakes:

• Using numbers without quotes for string properties
• Changing resource type incorrectly
• Removing required keys like Resources

5. A team wants to use Infrastructure as Code to manage their AWS environment. Which of these practices best supports collaboration and safe deployments?

hard

A. Store IaC templates in a shared version control system and review changes before deployment.

B. Manually update cloud resources directly in the AWS console to avoid template errors.

C. Allow each team member to deploy changes independently without coordination.

D. Avoid using version control to speed up deployments.

Solution

1. Step 1: Identify collaboration best practice

   Using version control allows tracking changes and team reviews.

2. Step 2: Evaluate deployment safety

   Reviewing changes before deployment prevents mistakes and conflicts.

3. Step 3: Compare options

   Only Store IaC templates in a shared version control system and review changes before deployment. supports collaboration and safe deployments; others increase risk or reduce control.

4. Final Answer:

   Store IaC templates in a shared version control system and review changes before deployment. -> Option A

5. Quick Check:

   Version control + reviews = safe collaboration [OK]

Hint: Use version control and reviews for safe IaC teamwork [OK]

Common Mistakes:

• Skipping version control for speed
• Deploying without team coordination
• Making manual changes outside IaC