Jayanth Katta | Technology, Life, Health & Learning

Today felt different. Until now, Terraform was just creating resources. But today, I learned how Terraform remembers what it creates, and how to manage that memory safely using a remote backend. Why Remote State Matters When Terraform runs, it keeps track of infrastructure in a state file. If that file stays on a local machine: It’s not shareable It’s not safe It can easily get corrupted or lost Moving state to Amazon S3 solves this. Teams can collaborate State is stored securely Changes are tracked with versioning Locking prevents conflicts What I Built Today I configured Terraform to: Store state in an S3 bucket Enable encryption Use native state locking (no DynamoDB required) Create a new S3 bucket using Terraform Step 1: Created S3 Bucket for State I manually created an S3 bucket and enabled versioning. Step 2: Configured Remote Backend I updated my Terraform configuration to use S3 as backend: backend "s3" { bucket =...

  Introduction Day 3 felt like the first real interaction with AWS. Not just writing Terraform code,  but actually creating something in the cloud. A small step, a simple S3 bucket, but it carried an important lesson: before infrastructure, comes authentication. Understanding the Basics Before Terraform can create anything in AWS, it needs permission. This is handled using AWS credentials. I configured mine using: aws configure Once set, Terraform can securely communicate with AWS APIs. What is S3? Amazon S3 (Simple Storage Service) is an object storage service. It allows you to store files like: Images Backups Logs Application data One key rule: S3 bucket names must be globally unique across AWS. Terraform Code Here’s the simple configuration I used: provider "aws" { region = "us-east-1" } resource "aws_s3_bucket" "my_bucket" { bucket = "jay-day3-s3-bucket-123456" tags = { Name = "Day3B...

  Introduction On Day 2 of my 30-Day AWS Terraform Challenge, I moved from understanding concepts to actually running Terraform against AWS. This day focused on Terraform Providers, versioning, and why controlling versions is critical when working with Infrastructure as Code. More importantly, I successfully created real AWS resources using Terraform. AWS Configuration Before running Terraform, I configured AWS CLI to allow my local environment to connect to my AWS account. First, I installed AWS CLI and verified it. Then I configured credentials as below.  This confirmed that my local machine was successfully authenticated with AWS. What are Terraform Providers Terraform providers act as a bridge between Terraform and external systems like AWS. Terraform itself does not directly create resources. Instead, it uses providers such as the AWS provider to communicate with cloud APIs. For AWS, the provider used is hashicorp/aws . Terraform Core vs Provider Version O...

Introduction I recently started the 30 Days AWS Terraform Challenge to strengthen my understanding of Infrastructure as Code and cloud automation. Day 1 focused on the fundamentals. It may sound basic, but it sets the foundation for everything that follows. The shift from manual provisioning to automated infrastructure is not just a technical improvement. It is a mindset change. What is Terraform and Infrastructure as Code Terraform, developed by HashiCorp , is a tool that allows us to define cloud infrastructure using code. Infrastructure as Code means we describe resources such as virtual machines, storage, and networks in configuration files instead of creating them manually through a console. This approach makes infrastructure: Repeatable Consistent Version-controlled Easy to scale Instead of remembering steps, we define the desired state and let Terraform handle the execution. Problems with Manual Infrastructure Before Infrastructure as Code, most systems were...

The other day, I was looking at a pair of sunglasses. Same model, same lenses, same performance, yet two very different prices: $244 and $162 . That’s when something clicked. Price isn’t what we think it is. The Illusion of Price We grow up believing a simple rule: higher price means better product, lower price means compromise. But the real world doesn’t work like that. Most of the time, price has little to do with the product itself. It’s about positioning. Brands don’t just sell utility. They sell perception, trust, and convenience, and all of that gets baked into the price tag. What You’re Really Paying For By the time a product reaches you, it carries far more than its manufacturing cost. It includes production, branding, marketing, retail margins, logistics, and customer service. What you pay isn’t just for the object; it’s for the entire system behind it. The price is a story. The cost is the truth. Same Product, Different Buyers Two people can buy the exact same product and pa...

  When people talk about money, they usually talk in numbers . “How much will it be worth?” “Will it reach six figures?” “Is that enough?” But numbers without context can be misleading. What actually matters is purchasing power ,   what that money can do when the time comes. This post isn’t about chasing quick returns or timing markets. It’s about inflation , investing , and why time is the most powerful tool parents have when planning for their children. The Quiet Problem With Inflation Inflation doesn’t announce itself loudly. It doesn’t show up as a sudden loss. Instead, it quietly reduces what money can buy year after year. Something that costs $1,000 today may cost $1,700 or more in 20 years  , not because it’s better, but because each dollar is worth a little less. This is why simply saving money isn’t enough anymore. Even “doing nothing” has a cost. Why Cash Loses Without Risk If money sits still: The number stays the same Prices keep rising Purchasing power falls...