Step-by-Step Guide to Setting Up Terraform, AWS CLI, and Your AWS Environment

Winnie Wambui — Wed, 18 Mar 2026 17:56:18 +0000

Introduction

Setting up your environment correctly is the foundation of working with Terraform. In this guide, I’ll walk through how I installed Terraform, configured the AWS CLI, and connected everything to AWS.

1. Setting Up AWS

Created an AWS account
Enabled MFA for security
Created an IAM user with programmatic access
Attached necessary permissions

2. Installing AWS CLI

Installed AWS CLI and configured it:

3. Installing Terraform

Downloaded and installed Terraform, then verified:

4. Connecting Terraform to AWS

Terraform automatically uses AWS CLI credentials.

Tested connection using:

VSCode Extensions

I installed the following extensions in Visual Studio Code:

HashiCorp Terraform
AWS Toolkit

SETUP CHALLENGES
1.Confusion Between Root User and IAM User*
Initially, I was unsure whether to use root credentials or create a new user.

Solution:
I learned that it is best practice to create an IAM user with programmatic access instead of using the root account. I created a dedicated user and generated Access Key ID and Secret Access Key.

2.AWS CLI Configuration Errors
After running aws configure, some commands failed due to incorrect credentials.

Solution:
I rechecked my credentials and region, then reconfigured using aws configure.

CHAPTER TWO LEARNINGS
From Chapter 2, I learned how Terraform authenticates with AWS.
Terraform does not store credentials directly. Instead, it relies on credentials configured through the AWS CLI using the aws configure command. These credentials are stored locally and used whenever Terraform interacts with AWS services.

Terraform uses:

Access Key ID
Secret Access Key
Default region to authenticate and provision infrastructure on AWS.

What Happens If You Use Root Credentials?
Using root credentials is strongly discouraged because:

The root account has full administrative access
Any mistake could lead to serious security risks or unexpected charges
It violates security best practices

Using an IAM user is safer because:

It follows the principle of least privilege
Permissions can be controlled and limited
It reduces risk in case credentials are exposed

Conclusion

By completing this setup, I now have a fully working environment ready to deploy infrastructure using Terraform.

What is Infrastructure as Code and Why It’s Transforming DevOps

Winnie Wambui — Wed, 18 Mar 2026 12:22:04 +0000

Introduction

In today’s fast-paced tech world, building software is no longer just about writing code—it’s about delivering it reliably, consistently, and at scale. This is where Infrastructure as Code (IaC) comes in.

IaC is one of the core practices driving the success of modern DevOps, helping teams automate infrastructure, reduce errors, and move faster.

What is Infrastructure as Code (IaC)?

Infrastructure as Code is the practice of managing and provisioning infrastructure (servers, databases, networks) using code instead of manual processes.

Instead of:

Clicking through dashboards
Running manual commands
Configuring servers one by one You write code that defines your infrastructure, and tools automatically create and manage it for you.

The Problem IaC Solves
Before IaC:

Infrastructure was set up manually
Environments were inconsistent
Deployments were slow and error-prone

IaC solves this by:

Making infrastructure repeatable and consistent
Reducing human error
Enabling automation and scalability

Declarative vs Imperative Approaches
When working with IaC, there are two main approaches:

Imperative (How to do it)
You define step-by-step instructions.

Example mindset:
“First create a server, then install software, then configure it.”

Similar to scripting (e.g., Bash, Python)
More control, but harder to manage at scale

Declarative (What you want)
You define the desired end state, and the tool figures out how to achieve it.

Example mindset:
“I want 2 servers running this application.”

Simpler and more predictable
Automatically handles changes and updates

💡 Most modern IaC tools—including Terraform—use the declarative approach, which is why they are so powerful.

Why Terraform is Worth Learning
Terraform has become one of the most popular IaC tools—and for good reason:

1. Cloud-Agnostic
Works with:

AWS
Azure
Google Cloud
And many others You write once, deploy anywhere

2. Declarative and Simple
You define what you want, and Terraform handles the rest.

3. Version Control for Infrastructure
Your infrastructure is stored as code:

Track changes
Collaborate with teams
Roll back when needed

4. Automation Friendly
Terraform integrates easily with CI/CD pipelines, making deployments faster and safer.

5. Strong Community & Ecosystem
With a huge community and many reusable modules, you don’t have to start from scratch.

My 30-Day Challenge Goals

Go from beginner to confident in Infrastructure as Code.
Build real projects, not just learn theory.
Stay consistent and share my journey.