Do coding agents recommend Amazon RDS for PostgreSQL?
Amazon RDS for PostgreSQL was chosen in 5% of 356 judged databases sessions, ranking fourth. Measured with Claude Code, Codex and Cursor.
Amazon RDS for PostgreSQL was chosen in 5% of 356 judged databases sessions, ranking fourth. It was also raised as a candidate in 13 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in databases inside a realistic codebase. Not what a chat assistant says about Amazon RDS for PostgreSQL. What an agent actually installed.
The numbers
| Category | Databases |
| Sessions in the category | 356 |
| Sessions where Amazon RDS for PostgreSQL was chosen | 17 |
| Install share | 5% |
| Rank in category | 4 of 14 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 13 |
| Chosen when considered | 57% |
| Site | aws.amazon.com |
By agent
With 17 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 RDS for PostgreSQL | Share |
|---|---|---|---|
| Claude Code | 129 | 3 | 2% |
| Codex | 103 | 9 | 9% |
| Cursor | 124 | 5 | 4% |
By who was asking
Amazon RDS for PostgreSQL performs similarly across the four kinds of buyer, from 0% to 9%. That is unusual: the category leader changed with the persona in 14 of the 18 categories we measured.
| Who is asking | Sessions | Chose Amazon RDS for PostgreSQL | Share |
|---|---|---|---|
| Vibe coder | 60 | 0 | 0% |
| Junior developer | 106 | 0 | 0% |
| Senior engineer | 190 | 17 | 9% |
What Amazon RDS for PostgreSQL was up against
The full ranking in databases, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Neon | 236 | 66% |
| 2 | Azure SQL Database | 35 | 10% |
| 3 | Azure Database for PostgreSQL Flexible Server | 29 | 8% |
| 4 | Amazon RDS for PostgreSQL (this page) | 17 | 5% |
| 5 | Supabase | 10 | 3% |
| 6 | MotherDuck | 7 | 2% |
| 7 | Scaleway Managed Database for PostgreSQL | 7 | 2% |
| 8 | Aiven | 5 | 1% |
What this means
Agents almost never raise Amazon RDS for PostgreSQL without choosing it: 13 sessions raised against 17 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 356 sessions in databases are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every databases run can be replayed on the board.
If you work on Amazon RDS for PostgreSQL: 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 RDS for PostgreSQL?
Yes. Amazon RDS for PostgreSQL was chosen in 17 of the 356 judged sessions in databases, a 5% install share, ranking fourth in its category.
Does Claude Code recommend Amazon RDS for PostgreSQL?
In 3 of the 129 sessions in databases run with Claude Code, which is 2%.
Do different coding agents treat Amazon RDS for PostgreSQL differently?
Not much. The three agents chose it at similar rates, between 2% and 9% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 51 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 RDS for PostgreSQL considered but not chosen?
It was raised as a candidate in 13 sessions without being chosen, and chosen in 17. That is a 57% conversion from considered to chosen.
Where this comes from
Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.