---
title: "#amazonwebservices articles | Hashnode"
description: "Explore 25 articles tagged #amazonwebservices on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/amazonwebservices"
---

Tag

# #amazonwebservices

25 posts · 0 followers

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 19](https://hashnode.com/posts/cloudtrail-explained-knowing-what-actually-happened/6ad5ba8faae187351c18e304)

### [CloudTrail Explained: Knowing What Actually Happened](https://jayesh-sojitra.hashnode.dev/cloudtrail-explained-knowing-what-actually-happened?utm_source=hashnode&utm_medium=feed)

When 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](https://jayesh-sojitra.hashnode.dev/cloudtrail-explained-knowing-what-actually-happened?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 13](https://hashnode.com/posts/week-3-recap-networking-delivery-and-reliability/6acdfdf570aa8db2832be2f5)

### [Week 3 Recap: Networking, Delivery, and Reliability](https://jayesh-sojitra.hashnode.dev/week-3-recap-networking-delivery-and-reliability?utm_source=hashnode&utm_medium=feed)

Week 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](https://jayesh-sojitra.hashnode.dev/week-3-recap-networking-delivery-and-reliability?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 13](https://hashnode.com/posts/multi-az-vs-multi-region-what-each-actually-protects-against/6acdfc73fb5da3df24ac0040)

### [Multi-AZ vs Multi-Region: What Each Actually Protects Against](https://jayesh-sojitra.hashnode.dev/multi-az-vs-multi-region-what-each-actually-protects-against?utm_source=hashnode&utm_medium=feed)

"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](https://jayesh-sojitra.hashnode.dev/multi-az-vs-multi-region-what-each-actually-protects-against?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 11](https://hashnode.com/posts/5-aws-mistakes-that-cost-teams-real-money/6acb9725c867ec60dfcb1ea8)

### [5 AWS Mistakes That Cost Teams Real Money](https://jayesh-sojitra.hashnode.dev/5-aws-mistakes-that-cost-teams-real-money?utm_source=hashnode&utm_medium=feed)

Most 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](https://jayesh-sojitra.hashnode.dev/5-aws-mistakes-that-cost-teams-real-money?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 11](https://hashnode.com/posts/what-production-support-on-aws-actually-looks-like/6acb98a47d73c30842d890f4)

### [What Production Support on AWS Actually Looks Like](https://jayesh-sojitra.hashnode.dev/what-production-support-on-aws-actually-looks-like?utm_source=hashnode&utm_medium=feed)

Production 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.dev](https://jayesh-sojitra.hashnode.dev/what-production-support-on-aws-actually-looks-like?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/what-production-support-on-aws-actually-looks-like/6acb98a47d73c30842d890f4)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 9](https://hashnode.com/posts/route-53-explained-dns-basics-for-aws/6ac8e433617147b6abf07ef3)

### [Route 53 Explained: DNS Basics for AWS](https://jayesh-sojitra.hashnode.dev/route-53-explained-dns-basics-for-aws?utm_source=hashnode&utm_medium=feed)

When 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](https://jayesh-sojitra.hashnode.dev/route-53-explained-dns-basics-for-aws?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 8](https://hashnode.com/posts/week-2-recap-databases-scaling-and-cost/6ac79864f2439e48845099cd)

### [Week 2 Recap: Databases, Scaling, and Cost](https://jayesh-sojitra.hashnode.dev/week-2-recap-databases-scaling-and-cost?utm_source=hashnode&utm_medium=feed)

Week 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](https://jayesh-sojitra.hashnode.dev/week-2-recap-databases-scaling-and-cost?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 5](https://hashnode.com/posts/building-a-monitoring-setup-that-actually-catches-issues/6ac3a6759c80a4fbc60a0cc5)

### [Building a Monitoring Setup That Actually Catches Issues](https://jayesh-sojitra.hashnode.dev/building-a-monitoring-setup-that-actually-catches-issues?utm_source=hashnode&utm_medium=feed)

Having 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](https://jayesh-sojitra.hashnode.dev/building-a-monitoring-setup-that-actually-catches-issues?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 4](https://hashnode.com/posts/auto-scaling-groups-explained-with-a-real-example/6ac1ac874f301e1dc1622cf6)

### [Auto Scaling Groups Explained With a Real Example](https://jayesh-sojitra.hashnode.dev/auto-scaling-groups-explained-with-a-real-example?utm_source=hashnode&utm_medium=feed)

Auto 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](https://jayesh-sojitra.hashnode.dev/auto-scaling-groups-explained-with-a-real-example?utm_source=hashnode&utm_medium=feed)

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra) · [Oct 2](https://hashnode.com/posts/cloudwatch-explained-metrics-logs-and-alarms/6abfb64ba36107fefaa1b1f8)

### [CloudWatch Explained: Metrics, Logs, and Alarms](https://jayesh-sojitra.hashnode.dev/cloudwatch-explained-metrics-logs-and-alarms?utm_source=hashnode&utm_medium=feed)

Most 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](https://jayesh-sojitra.hashnode.dev/cloudwatch-explained-metrics-logs-and-alarms?utm_source=hashnode&utm_medium=feed)
