Switch language한국어
Back to the list

Optimizing EKS operations with Agents: Reduce MTTR using AWS DevOps Agent + K8s Operator | Amazon Web Services

TL;DR AI

Key summary

2 min read
  1. AWS DevOps Agent was announced in preview announced in preview in December 2025 to analyze incidents by connecting code repos, observability tools, CI/CD and runbooks.

  2. DevOps Agent Operator detects Pod failures and sends context to DevOps Agent a Kubernetes Operator that detects Pod failures in-cluster and forwards context to DevOps Agent via webhook.

  3. DevOps Agent requires webhook trigger and contextual data to start investigations requires an external webhook trigger and sufficient context (manifest, logs, events, node info) to start an investigation.

  4. Generic Webhook is supported and secured with HMAC-SHA256 used by DevOps Agent Operator and secured with HMAC-SHA256; HMAC secret cannot be re-retrieved after creation.

  5. EKS Pod Identity associates Kubernetes Service Accounts with IAM roles for pod AWS access can associate a Kubernetes Service Account with an IAM role so pods access AWS services with least privilege.

Read the original