JJayesh Sojitra·Oct 19CloudTrail Explained: Knowing What Actually HappenedWhen something changes in your AWS account and nobody admits to touching it, CloudTrail is how you find out who did what, and when. The catch is that it only helps if you set it up before you need it.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 13Week 3 Recap: Networking, Delivery, and ReliabilityWeek 3 is done. Six posts, and almost every one came down to a single small detail that decides whether the setup works: a TTL, a cache key, an alert, a tested failover.3 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 13Multi-AZ vs Multi-Region: What Each Actually Protects Against"We're highly available" can mean very different things. Multi-AZ and Multi-Region protect against different failures, at very different cost and complexity.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 11 5 AWS Mistakes That Cost Teams Real MoneyMost expensive AWS surprises aren't exotic. They're five ordinary mistakes that look harmless in the console and show up weeks later on the bill.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 11 What Production Support on AWS Actually Looks LikeProduction support isn't dramatic debugging. It's a repeatable order of questions you ask when something's wrong, and most incidents turn out to have ordinary causes.4 min read·jayesh-sojitra.hashnode.dev1A
JJayesh Sojitra·Oct 9Route 53 Explained: DNS Basics for AWSWhen a site "goes down" and the servers are perfectly healthy, the culprit is often DNS. Here's what Route 53 actually does, and the settings that bite people.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 8Week 2 Recap: Databases, Scaling, and CostWeek 2 is done. Seven posts, and one question kept coming back in different forms: what are you actually paying for, and is it doing the job you think it is?3 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 5Building a Monitoring Setup That Actually Catches IssuesHaving CloudWatch configured and having a monitoring setup that actually catches issues before users do are two genuinely different things. Here's what closes that gap, from real production support experience.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 4Auto Scaling Groups Explained With a Real ExampleAuto Scaling isn't "add more servers when busy." It's a specific set of decisions — what triggers it, what the limits are, and how fast it reacts — that most teams configure once and never revisit.4 min read·jayesh-sojitra.hashnode.dev
JJayesh Sojitra·Oct 2CloudWatch Explained: Metrics, Logs, and AlarmsMost teams have CloudWatch running and still find out about outages from users, not alarms. The gap is usually a misunderstanding of what each CloudWatch piece actually does.4 min read·jayesh-sojitra.hashnode.dev