Do coding agents recommend Amazon EventBridge?
Amazon EventBridge was chosen in 3% of 288 judged message queues sessions, ranking ninth. Measured with Claude Code, Codex and Cursor.
Amazon EventBridge was chosen in 3% of 288 judged message queues sessions, ranking ninth. It was also raised as a candidate in 81 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in message queues inside a realistic codebase. Not what a chat assistant says about Amazon EventBridge. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about message queues in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Message queues |
| Sessions in the category | 288 |
| Sessions where Amazon EventBridge was chosen | 10 |
| Install share | 3% |
| Rank in category | 9 of 25 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 81 |
| Chosen when considered | 11% |
| Site | aws.amazon.com |
By agent
With 10 wins spread across three agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Amazon EventBridge | Share |
|---|---|---|---|
| Claude Code | 96 | 5 | 5% |
| Codex | 96 | 0 | 0% |
| Cursor | 96 | 5 | 5% |
By who was asking
Amazon EventBridge performs similarly across the four kinds of buyer, from 0% to 14%. That is unusual: the category leader changed with the persona in 23 of the 28 categories we measured.
| Who is asking | Sessions | Chose Amazon EventBridge | Share |
|---|---|---|---|
| Vibe coder | 48 | 0 | 0% |
| Junior developer | 120 | 0 | 0% |
| Senior engineer | 48 | 0 | 0% |
| Enterprise team | 72 | 10 | 14% |
What Amazon EventBridge was up against
The full ranking in message queues, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 49 | 17% |
| 2 | Apache Kafka | 39 | 14% |
| 3 | Amazon SQS | 27 | 9% |
| 4 | Service Bus | 24 | 8% |
| 5 | Laravel Queues | 20 | 7% |
| 6 | Amazon Kinesis | 19 | 7% |
| 7 | Cloudflare Queues | 19 | 7% |
| 8 | Cloud Tasks | 15 | 5% |
What this means
This is an integration problem, not a presence problem. Agents raised Amazon EventBridge in 81 sessions and chose it in 10, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 288 sessions in message queues are part of a published set of 7,852, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every message queues run can be replayed on the board.
If you work on Amazon EventBridge: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Amazon EventBridge?
Yes. Amazon EventBridge was chosen in 10 of the 288 judged sessions in message queues, a 3% install share, ranking ninth in its category.
Does Claude Code recommend Amazon EventBridge?
In 5 of the 96 sessions in message queues run with Claude Code, which is 5%.
Do different coding agents treat Amazon EventBridge differently?
Not much. The three agents chose it at similar rates, between 0% and 5% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 90 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Amazon EventBridge considered but not chosen?
It was raised as a candidate in 81 sessions without being chosen, and chosen in 10. That is a 11% conversion from considered to chosen.
Where this comes from
Armature ran 7,852 judged sessions with Claude Code, Codex and Cursor inside 90 realistic codebases, and published every run. The numbers on this page come from that work.