AWS CloudWatch — Logs Insights, CW Agent and Container Insights — CI/CD, GitOps, DevSecOps & Observability

AWS CloudWatch is the native observability service for AWS workloads, providing metrics, logs, and alarms that integrate tightly with all AWS services without requiring additional infrastructure setup. For EKS workloads, CloudWatch Container Insights provides automatic collection of pod and node metrics through the CloudWatch Agent DaemonSet, giving teams visibility into their Kubernetes workloads using only AWS-managed services. CloudWatch Logs Insights provides a serverless query engine for analysing log data without managing Elasticsearch clusters or configuring Loki.

CloudWatch is the pragmatic choice for organisations that want to minimise operational overhead by using managed services rather than self-hosting Prometheus and Loki, or for teams that need to correlate EKS application metrics with AWS service metrics—RDS query latency, SQS queue depth, ElastiCache hit rate—in a single platform. Its limitations compared to Prometheus—higher per-metric cost at scale, less flexible PromQL-equivalent query language—mean that many organisations run CloudWatch for AWS service monitoring and Prometheus for application-level monitoring side by side.

Analogy🏏Cricket

Think of it like cricket: Imagine the BCCI's team management system for an international tour with matches in three different countries simultaneously. Rather than a coordinator manually managing each match day's logistics, the system reads the official tour schedule document and automatically dispatches the right squad, equipment, and support staff to each venue. When the tour schedule changes—a match is rescheduled, a squad member is replaced—the system detects the change and updates the arrangements automatically. Just as the tour management system uses the official document as the source of truth and orchestrates multiple concurrent deployments to multiple venues, ArgoCD uses the Git repository as the source of truth and orchestrates multiple concurrent Application syncs to multiple clusters. Just as the system provides a dashboard showing which venues are 'ready', 'delayed', or 'degraded', ArgoCD provides a dashboard showing which Applications are Synced, OutOfSync, or Degraded. This reveals why ArgoCD is valued at scale: managing dozens of applications across multiple clusters manually is operationally equivalent to coordinating an international cricket tour by phone.