Internal fleet-scale Java 8/11→17 upgrades — >4,500 dev-years saved, $260M.
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Pipeline
- Agent count
- 1
- Platform
- Amazon Q Developer
- Runs on
- Amazon Q Developer
- Industries
- cloud-infrastructuree-commerce
- Task kinds
- code-migration
- Trust tier
- Self-Reported
- Proof entries
- 1
Topology & roster
Pipeline agent. A single transformation agent per application run: analyze source → generate upgraded code → test → execute on human approval. Deployed at internal Amazon fleet scale (many parallel per-app runs).
System wiring
Node details
Typical Pipeline layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Stage 1 agent
BuilderStage 1 agent
- Tool
- Stage 1 agent
- Autonomy
- Runs autonomously
- hands off to → Stage 2 agent
- directs ← Human operator
BuilderStage 2 agent
- Tool
- Stage 2 agent
- Autonomy
- Runs autonomously
- hands off to → QA reviewer
- hands off to ← Stage 1 agent
QAQA reviewer
- Tool
- QA reviewer
- Autonomy
- Runs autonomously
- delivers to → Output artifact
- hands off to ← Stage 2 agent
ResourceOutput artifact
- Tool
- Output artifact
- Autonomy
- Runs autonomously
- delivers to ← QA reviewer
How a typical Pipeline team handles a task
Typical Pipeline layout — schematic, not verified wiring
Task arrives
Human operator directs Stage 1 agent.
The builders execute
Stage 1 agent and Stage 2 agent build the work.
Independent review gates the work
QA reviewer reviews the work. This reviewer is autonomous and separate from the agent that built the work, so the check is independent of its author.
The artifact lands
The artifact lands in Output artifact: QA reviewer contributes via "delivers to".
Human holds the last word
Human operator holds final approval.
Replicate a typical Pipeline setup
Typical Pipeline layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- BuilderStage 1 agent
- BuilderStage 2 agent
- QAQA reviewer
- ResourceOutput artifact
Setup order
- 1.Provision the substrate: Output artifact.
- 2.Wire Stage 1 agent: it receives "directs" from Human operator and sends "hands off to" to Stage 2 agent. Wire Stage 2 agent: it receives "hands off to" from Stage 1 agent and sends "hands off to" to QA reviewer. Wire QA reviewer: it receives "hands off to" from Stage 2 agent.
- 3.Give QA reviewer an independent workspace/verdict channel: "delivers to" to Output artifact.
- 4.Declare the human gate: Human operator holds final approval.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
'$260 million dollars in annual cost savings' from performance improvements (host reduction); described by AWS as a conservative estimate. Source: AWS DevOps blog, 2024-08-01. [self_reported]
'>4,500 years of development work' saved across 'tens of thousands' of production Java 8/11→17 upgrades (The Register separately specifies 30,000 apps — attributed to The Register only, not an Amazon figure). Methodology described by AWS as conservative (time estimated via dependency-migration counts). Internal, unaudited company estimate. Source: AWS DevOps blog, 2024-08-01; Amazon press release, 2024-12-03. [self_reported]
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
A conservative, explicitly-disclosed measurement methodology (dependency counts for time, host-removal for cost) plus a human-approval gate before execution lets Amazon scale the transformation agent across tens of thousands of applications without an unaudited or unreviewed production change ever landing.
Amazon Q Developer's code-transformation agent, deployed internally across Amazon's own application fleet as a dogfooding case ahead of/alongside the external product offering.
Human-approved execution: the agent proposes the upgrade and runs tests, but a human approves before the change is executed in production.
Proof (1)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactAug 1, 2024self-reported
Amazon Q Developer reaches $260M internal savings milestone
>4,500 developer-years saved, $260M annual cost savings across tens of thousands of internal Java 8/11→17 migrations; AWS labels its own methodology conservative.
https://aws.amazon.com/blogs/devops/amazon-q-developer-just-reached-a-260-million-dollar-milestone/
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in