← All insightsObservability

Monitoring and observability for Amazon Web Services

Nir Geier, CodeWizard · 8 January 2026 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of Amazon Web Services and turn them into alerts that mean something.

AWS is a broad public cloud spanning compute (EC2, ECS, EKS, Lambda), storage (S3, EBS), networking (VPC) and hundreds of managed services - best operated declaratively with IaC and least-privilege IAM.

What to watch

  • Use SSO for humans and OIDC roles for CI - no static keys
  • Write least-privilege IAM and manage everything via IaC
  • Turn on CloudTrail, GuardDuty and budget alerts
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
aws sts get-caller-identity
aws s3 ls
aws eks update-kubeconfig --name prod --region eu-west-1

Keep it healthy

  • Scan IaC (tfsec/Checkov) for open buckets and wide security groups
  • Enforce MFA, rotate credentials, and enable org-wide guardrails (SCPs)

Want senior help putting Amazon Web Services to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult