AWS puts a number on agent displacement: IaC authoring from 3-4 weeks to minutes

AWS Professional Services has published the architecture for a four-agent cloud migration framework and, unusually, attached a number to it: infrastructure as code development fell from 3 to 4 weeks per application to minutes across a portfolio of more than 300 applications, on the basis of internal project tracking data ^[1]. For anyone costing a data center exit, that is a specific claim about which task an agent removes rather than a claim about productivity in general, which makes it worth reading closely before it gets requoted as a program-wide figure.

The setting is a large enterprise data center exit: over 300 applications against a fixed fiscal year deadline ^[3]. AWS names three recurring bottlenecks. Manual discovery of on-premises architecture, inventory, dependencies and intake questionnaires consumes weeks per application ^[4]. Writing IaC from scratch for each workload typically takes 3 to 4 weeks per application ^[2]. Post-migration, teams fall back on manual monitoring and reactive response, with operational drag that compounds ^[5].

The IaC line is the one carrying the business case, and the arithmetic is why. At 3 to 4 weeks each across 300 applications, the baseline is 900 to 1,200 engineer-weeks, or roughly 17 to 23 engineer-years of sequential work ^[12]. AWS phrases the same thing as "years of engineering effort" ^[2].

The build is conventional in shape. The agents use the Strands Agents SDK and run on Amazon Bedrock AgentCore ^[6]. There are four: an Intake Agent for discovery and target state architecture with dependency mappings; an IaC Agent that generates code adhering to your security best practices and standards; a Migration Intelligence and Governance Agent doing portfolio reporting and well-architected assessments across Jira, Confluence and Webex; and an SRE Agent for proactive monitoring and automated remediation ^[7]. They are split into a migration journey covering discovery through deployment and an operations journey covering post-migration monitoring ^[8]. AWS Database Migration Service handles generative AI-assisted schema conversion and automated cutover ^[9].

Two limits on the headline. First, only one of the three named bottlenecks has a stated before-and-after; discovery and operations are described as problems without post-agent figures ^[13]. Second, the metric is scoped to IaC development time, so it does not speak to what happens to generated code afterwards, including review, security sign-off and exception handling ^[14]. AWS itself frames the design as shifting repetitive work to agents while humans retain decision authority ^[11], which implies those review steps remain.

Treat the figure as self-reported and single-program. Internal project tracking data is the only stated basis ^[1].

What to watch: whether an equivalent number appears for intake, where the pre-agent cost is also stated in weeks per application ^[4]; whether the 3 to 4 week baseline included conformance to internal security standards, since the IaC Agent is specified to generate code that adheres to them ^[7]; and how much of this is reusable. The prerequisites list an AWS account with access to Bedrock AgentCore and Bedrock foundation models, familiarity with the Strands Agents SDK and Model Context Protocol server patterns, and your own IaC tooling ^[10]. That is a rebuild, not a download.