Menu

1 / 2

Eyes, Not Hands: Adding AWS DevOps Agent, Bedrock AgentCore and Kiro to a GitOps Platform on EKS

DEV Community: aws·Alejandro Velez·about 4 hours ago
#DObaAmWx
#devtoaws#devto#dev#agent#gitops
Reading 0:00
15s threshold

__ Level 300 — Advanced | Amazon EKS, Argo CD, AWS DevOps Agent, Amazon Bedrock AgentCore, Kiro CLI, Amazon EventBridge

🎯 The Challenge

Scenario

Suppose you are the Platform Engineering lead of an enterprise that already runs Kubernetes the GitOps way: an Amazon EKS hub cluster with Argo CD manages a fleet of spoke clusters , and every team onboards its workloads through a single values file in Git. It works. Deployments are boring, in a good way.

Operations are not. On-call engineers keep getting paged for the same kind of incidents: a bad config is merged, pods start crash-looping, and someone spends 40 minutes reading logs and events before realizing the fix is "revert that commit". Then leadership asks the question every platform team is hearing:

"Can AI agents take the first part of on-call?"

Your mission: add agentic investigation and remediation to the existing platform , under these constraints:

✅ No agent gets write access to production.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.