DEV Community: Mercy Ndonga

🧱 Terra Biteʒ 3: Instance Gratification ⚡️

Mercy Ndonga — Wed, 28 May 2025 23:00:14 +0000

Day 3 of the #30DayTerraformChallenge was pure instance gratification – no more just talking about cloud infrastructure, but actually deploying it and watching code bring resources to life!

🚀 Quick Wins of the Day:

I achieved two key deployments:

✅ A 🖥️ Single Server — a basic standalone EC2 instance with no configurations.
✅ A 🌐 Web Server — an EC2 instance that auto-installs Apache and serves a custom web page using user_data. (a fully functional web server) Seeing terraform apply work its magic? Priceless! ✨

🧠 Key Differences: Single Server vs Web Server

Feature	Single Server 🖥️	Web Server 🌐
Purpose	Basic EC2 VM	Hosts a website
User Data Script	❌ No	✅ Installs Apache & HTML
HTTP Access	❌ No	✅ Yes
Visible in Browser	❌ No	✅ Yes

1. The Simple Start: Deploying a Basic EC2 Instance 👶

Every cloud journey begins somewhere, and for me, it was a fundamental EC2 instance. This represents the simplest form of compute in AWS – a virtual server spun up straight from code.

🖥️ Single Server: Basic EC2 Setup

This is a minimal EC2 instance — no web server, no automation, just a VM in the cloud.
Why deploy this? To confirm my Day 2 setup was solid and to witness the raw power of terraform apply in action for basic resource creation.

📜 Code: single-server.tf

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
}

provider "aws" {
  region = "af-south-1"
}

resource "aws_instance" "single-server" {
  ami           = "ami-0914bddde8faa93a0" # Amazon Linux 2023 AMI
  instance_type = "t3.micro"
  key_name      = "cloudykey"

  tags = {
    Name = "single-server"
  }
}

💬 Code Comments:

provider "aws": Your entry point to AWS, specifying the region (af-south-1 for Nairobi vibes! 🌍).
resource "aws_instance": The core block for creating an EC2 VM.
ami: The Amazon Machine Image – essentially the operating system pre-configured.
instance_type: Defines the CPU, memory, and networking capacity (e.g., t3.micro is usually free-tier eligible).
key_name: Links to your SSH key pair for secure remote access.
tags: Simple key-value pairs for organizing and identifying your resources in AWS.

2. Beyond Basic: Spinning Up A Web Server! 🌐

This EC2 instance runs a startup script to install Apache and serve a static HTML page.

🌐 Web Server: With Apache and HTML Page

Why deploy this? To demonstrate automating server configuration post-launch (user_data) and managing network traffic (Security Groups).

📜 Code: web-server.tf

# Terraform 0.13 and later:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
  }
}

# Configure the AWS provider
provider "aws" {
  region = "af-south-1" # Specify your desired AWS Region
}

# Create an EC2 Instance
resource "aws_instance" "web-server" {
  ami                    = "ami-0914bddde8faa93a0" # Amazon Linux 2023 AMI ID for af-south-1
  instance_type          = "t3.micro"             # Free tier eligible
  key_name               = "cloudykey"
  vpc_security_group_ids = [aws_security_group.web-server-sg.id]
  user_data = <<-EOF
              #!/bin/bash
              sudo yum update -y           # Update all installed packages
              sudo yum install -y httpd    # Install Apache Web Server
              sudo systemctl start httpd   # Start the Apache Web Server Service
              sudo systemctl enable httpd  # Configure Apache to start on every reboot

              echo "<!DOCTYPE html>
              <html>
              <head><title>We Are Live, Baby!🚀🎉🥳</title></head>
              <body style='background-color:#1e1e1e; color:#00ffcc; text-align:center; padding-top:15%; font-family:monospace;'>
              <p>Infrastructure as Code? More like <strong>Magic as Code!😂💫✨</strong></p>
              </body>
              </html>" > /var/www/html/index.html
              EOF

  tags = {
    Name = "web-server"
  }
}

# Data source to Default VPC
data "aws_vpc" "default_vpc" {
  default = true
}

resource "aws_security_group" "web-server-sg" {
  name        = "web-server-ssh-http-sg"
  description = "Allow SSH and HTTP inbound traffic for web server"
  vpc_id      = data.aws_vpc.default_vpc.id # Or hardcode your VPC ID

  ingress {
    from_port   = 22
    to_port     = 22
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"] # From ANYWHERE - Be cautious! Wide open for testing only
    description = "Allow SSH"
  }

  ingress {
    from_port   = 80
    to_port     = 80
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"] # From ANYWHERE - Be cautious! Wide open for testing only
    description = "Allow HTTP"
  }

  egress {
    from_port   = 0     # All Ports
    to_port     = 0     # All Ports
    protocol    = "-1"  # All Protocols
    cidr_blocks = ["0.0.0.0/0"] # To ANYWHERE
  }
}

💬 Code Comments & What's New:

user_data Power: This is where the real "Magic as Code" shines! It's a bash script that runs when the instance first launches. I used it to:
- ➡️ Update packages, install Apache.
- ➡️ Start/enable the Apache service.
- ➡️ Create my awesome custom HTML welcome page:"Infrastructure as Code? More like Magic as Code!😂💫✨"
aws_security_group: This acts as a virtual firewall for your server.
- 🔒 It allows Port 22 (SSH) for secure remote access.
- 🔒 It allows Port 80 (HTTP) so web browsers can connect to our page.
- 🔒 Caution: 0.0.0.0/0 means "from anywhere." Super easy for testing, but in production, you'd restrict this to known IPs for better security!
data "aws_vpc" "default_vpc": A neat way to reference your default VPC without hardcoding its ID.

🧪 The Terraform Lifecycle: From Code to Cloud (and Back!) 🔁

I truly experienced the core Terraform workflow:

➡️ terraform init: Initializes the working directory, downloading necessary provider plugins (like hashicorp/aws). It's the setup step.
➡️ terraform plan: Before applying any changes, terraform plan shows you exactly what Terraform will do. It's a crucial "dry run" to avoid surprises!
➡️ terraform apply: Brings your infrastructure to life! It executes the changes outlined in the plan, creating, updating, or deleting resources in your cloud provider.
➡️ terraform destroy: The responsible cleanup crew! This command tears down all the resources managed by your Terraform configuration. Crucial for avoiding unwanted cloud costs! 💰

💡 Brain Bytes from Day 3 🧠

'terraform apply' is Real Power!: Transforms code into live cloud infrastructure.
Layered Deployments: Start simple, build complexity.
'user_data' for Automation: Automates server setup right after launch.
Security Groups as Firewalls: Essential for controlling network access.
Full Lifecycle: Remember init -> plan -> apply -> destroy! Budgeting: Always terraform destroy when done!

What's Next? ➡️

Day 3: Mission accomplished! Code was tangible and deployed real infrastructure.
Stay tuned for more awesome automation on Day 4!

📡 Let’s Connect:

LinkedIn💼

🧱 Terra Biteʒ 2: AWS Handshake 🤝

Mercy Ndonga — Wed, 28 May 2025 10:54:49 +0000

Day 2 of my Terraform journey was all about forging a powerful alliance: Terraform and Amazon Web Services (AWS)! This is where the magic of Infrastructure as Code truly begins.

🔑 Secure Your AWS Kingdom: IAM is FREE! 🥳

Ditch the root user (it's like leaving your castle door wide open! 😱). We're all about creating a dedicated IAM (Identity and Access Management) User. Think granular permissions – keys to specific rooms, not the entire fortress. Best part? IAM is a FREE AWS service! 🎉
Here’s the quick setup:

➡️ AWS Console > IAM: Navigate and add a new user.
➡️ Programmatic Access: Select this type.
➡️ Permissions: For learning, AdministratorAccess gets us going.
➡️ 🔑 Grab Your Keys: Download that .csv with your Access key ID and Secret access key. Guard them like gold! 🔒

💻 Connecting Your Dev Machine: `aws configure` FTW!

Time to link your local VS Code (or your favorite IDE's terminal) to your AWS account:

✔️ Install AWS CLI: (If you haven't yet).
✔️ Terminal Time: Open your terminal in VS Code.
✔️ Run aws configure:
- ➡️ Enter your AWS Access Key ID.
- ➡️ Enter your AWS Secret Access Key.
- ➡️ Set your Default region name (e.g., af-south-1🌍).
- ➡️ (Optional) Choose an Output format (like json).

✨ Boom! Your local setup is now authenticated and ready for action!

✅ Verification Checkpoint

To make sure Terraform and AWS are BFFs, I did a quick check:

AWS CLI Check:
```
aws sts get-caller-identity
```

Expected Output: This should tell you about the IAM user you configured, confirming AWS CLI is working.

```json
{
  "UserId": "AIDACKCEVSQ6C2EXAMPLE",
  "Account": "123456789012",
  "Arn": "arn:aws:iam::123456789012:user/my-iam-user"
}
```

🤝 Terraform & AWS: Speaking the Same Language

Here's the cool part: Terraform uses the secure credentials you configured with aws configure to talk to AWS behind the scenes. This allows Terraform to make the necessary API calls to build, tweak, and tear down your infrastructure based on your code. Automation unlocked! 🚀

🚧 Troubleshooting Corner

Error: No valid credential sources found: Classic! Usually means your aws configure went wrong, or Terraform can't find your ~/.aws/credentials file. Double-check those aws configure steps.

💰 Pro Tip: Cloud Budgets are Your Friend! 🤝

Keep those cloud costs in check! Always remember to terraform destroy resources you're not actively learning with. Let's build knowledge, not unexpected bills! 😉
Enable MFA (Multi-Factor Authentication) on your root account (first!) and highly privileged IAM users. It's a game-changer! 🔐

💡 Brain Bytes from Day 2 🧠

Authentication is King: aws configure = AWS access. No aws configure, no Terraform fun.
Verify, verify, verify: aws sts get-caller-identity is your friend after config changes.

🎉 What's Next? The Real Building Begins!

Terraform and AWS are officially connected!☁️
Day 3: Time to actually deploy something small – maybe an EC2 instance?

📡 Connect with me:

LinkedIn 💼

`#terraform #aws #iac #cloud #devops #30dayterraformchallenge #cloudcomputing

🛠 Terra Biteʒ 1: Terraform Prep Party! 🎉

Mercy Ndonga — Tue, 27 May 2025 09:28:34 +0000

Hey there! 👋

Welcome to Terra Biteʒ 1 of my 30-Day Terraform Challenge journey! Today’s mission: set the stage for my cloud adventure with a deep dive into Infrastructure as Code (IaC) and Terraform. Let’s break it down:

🚀 Quick Wins of the Day:

✅ Grasped core IaC concepts
✅ Installed and configured my DevOps toolkit

🌩 Why Code Your Cloud? (Intro to IaC)

In traditional IT ops, infrastructure was manually set up—slow, error-prone, and inconsistent. Enter Infrastructure as Code (IaC)—a game-changer in DevOps!

🧠 IaC lets us define, deploy, and destroy cloud infrastructure using code.

No more click-ops. Just clean, trackable, automatable configurations.

🔍 Types of IaC Tools:

Ad hoc scripts: Basic automation.
Configuration mgmt tools: e.g. Ansible, Puppet.
Server templating: Immutable images.
Provisioning tools: Like Terraform! 🚀

🧱 Why IaC is a Big Deal:

Speed ⚡: Automate deploys, cut manual work
Consistency ✅: No “it works on my machine” drama.
Versioned Infrastructure 🔁: Track infrastructure like code with Git
Reusable Modules 🧩: Repeat patterns, eliminate repetitive setup.
Self-Service Infrastructure 🧑‍💻: Empower devs to build fast

🌍 Terraform 101: Your Cloud’s Architect

Terraform is the IaC tool of choice for multi-cloud infrastructure. Here’s why it rocks:

Feature	Description
Declarative	You say what you want, Terraform figures out how.
Agentless	Works directly with cloud APIs, no agents needed.
Multi-cloud	AWS, Azure, GCP? One tool to rule them all.

🔧 My Terraform "Party Pack" Setup

To get hands-on, I set up my full IaC environment:

Tool	Purpose
VS Code	Code editor of choice 🎨
Git	For version control 🔁
AWS CLI	For cloud API access ☁️
Terraform CLI	Core tool for IaC 💻

🔌 Must-Have VS Code Extensions:

🧩 Hashicorp Terraform
🧩 Hashicorp HCL
🧩 AWS Toolkit
🎨 Material Icon Theme
🌈 Indent Rainbow

🧪 Terraform Core Commands

Command	What It Does
`terraform init`	Prepares the project (downloads providers)
`terraform plan`	Dry run – see what changes would happen
`terraform apply`	Executes and provisions infra
`terraform destroy`	Destroys resources (careful!) 💣

🧁 Terra Biteʒ Recap:

Today’s Output:

✅ Terraform installed and ready

Feeling: Energized and prepped for the Terraform deep-dive ahead!
Stay tuned for Terra Biteʒ 2!

DEV Community: Mercy Ndonga

🧱 Terra Biteʒ 3: Instance Gratification ⚡️

🚀 Quick Wins of the Day:

🧠 Key Differences: Single Server vs Web Server

1. The Simple Start: Deploying a Basic EC2 Instance 👶

🖥️ Single Server: Basic EC2 Setup

💬 Code Comments:

2. Beyond Basic: Spinning Up A Web Server! 🌐

🌐 Web Server: With Apache and HTML Page

💬 Code Comments & What's New:

🧪 The Terraform Lifecycle: From Code to Cloud (and Back!) 🔁

💡 Brain Bytes from Day 3 🧠

What's Next? ➡️

📡 Let’s Connect:

🧱 Terra Biteʒ 2: AWS Handshake 🤝

🔑 Secure Your AWS Kingdom: IAM is FREE! 🥳

💻 Connecting Your Dev Machine: aws configure FTW!

✅ Verification Checkpoint

🤝 Terraform & AWS: Speaking the Same Language

🚧 Troubleshooting Corner

💰 Pro Tip: Cloud Budgets are Your Friend! 🤝

💡 Brain Bytes from Day 2 🧠

🎉 What's Next? The Real Building Begins!

📡 Connect with me:

🛠 Terra Biteʒ 1: Terraform Prep Party! 🎉

🚀 Quick Wins of the Day:

🌩 Why Code Your Cloud? (Intro to IaC)

🔍 Types of IaC Tools:

🧱 Why IaC is a Big Deal:

🌍 Terraform 101: Your Cloud’s Architect

🔧 My Terraform "Party Pack" Setup

🔌 Must-Have VS Code Extensions:

🧪 Terraform Core Commands

🧁 Terra Biteʒ Recap:

📡 Let’s Connect:

💻 Connecting Your Dev Machine: `aws configure` FTW!