Skip to main content

Blog category

DevOps & CI/CD

Articles in this topic
52
4 min

From One FIS Experiment to a Resilience Program (2026): AWS Fault Injection Service, Stop Conditions, and GameDays That Actually Change Behavior

Running one AWS FIS experiment in a demo account is not chaos engineering. It is a screenshot. A program ties experiments to SLOs, scopes blast radius with tags, halts on CloudWatch alarm stop conditions, schedules via EventBridge, and closes the loop by re-testing the fix. FIS now ships AZ Power Interruption and cross-Region connectivity scenarios in its Scenario Library. This post covers the L0 to L3 maturity matrix, a GameDay runbook, and a stop-condition-wired experiment skeleton.

Manoj V.
4 min

GitOps on Amazon EKS (2026): Argo CD vs Flux, App-of-Apps, and the Decisions That Actually Bite

AWS Prescriptive Guidance says Argo CD and Flux both handle most GitOps scenarios capably, so picking one is a fit decision. The decisions that actually cause incidents are the ones underneath: plaintext secrets in the GitOps repo, CI running kubectl apply and reintroducing drift, no App-of-Apps so onboarding is click-ops, and repo topology you can't change later. This post has the Argo CD vs Flux matrix, an App-of-Apps example, and the five traps independent of tool.

Manoj V.
8 min

Observability Beyond CloudWatch (2026): When to Add Application Signals, ADOT, Managed Prometheus, and Grafana — and When Not To

The reflex to bolt Amazon Managed Prometheus + Grafana onto every workload is how observability bills quietly double. CloudWatch Application Signals now gives you an auto-discovered service map, SLOs, and traces with near-zero setup; AMP only earns its keep when you are PromQL-native or drowning in high-cardinality metrics, where ingestion (not retention) is the cost driver. The post covers the decision matrix, an ADOT dual-export config, and the three levers that actually cut the AMP bill.

Manoj V.