I Amazon Elastic Kubernetes Service (Amazon EKS) gives teams a scalable, Kubernetes-native way to run applications without managing the underlying infrastructure. For many organizations, moving applications to Amazon EKS is a clear next step in modernizing their environments. Before any application moves, though, someone has to answer a basic question: is it ready? That means reading through the application’s code, mapping its dependencies, spotting anything that would block the move, and estimating the work involved. Doing this by hand is slow and hard to keep consistent.
The time per application varies widely with its complexity, and different reviewers often reach different conclusions. It’s also easy to overlook things that only surface later, such as hardcoded configurations, stateful dependencies, or storage patterns that don’t map cleanly onto Kubernetes. When you’re assessing tens or hundreds of applications running on virtual machines or other container orchestration platforms, a consistent, automated review scales in a way that manual effort can’t.
It can handle the repetitive reading and pattern-matching quickly, so reviewers spend less time on boilerplate and more on the judgment calls that actually need a human. In this post, we show you how to build a migration assessment agent using Amazon Bedrock AgentCore , a platform to build, connect, and optimize agents at scale with any framework or model. The agent is built with the Strands Agents SDK , an open source toolkit for building AI agents in a few lines of code.
The agent reads an application’s source code and container artifacts from source platforms such as OpenShift, Azure, on-premises or self-managed Kubernetes and produces a readiness score, a list of blockers ranked by severity, and a migration plan with architecture recommendations for Amazon EKS. AWS provides a broad set of migration services, and open source tools can assess readiness too. This solution complements them by adding AI-powered, application-level code analysis: This agent goes a step further than infrastructure inventory: it reads the application’s source code.