What users hate about Amazon Relational Database Service (RDS)
405 complaints extracted from 405 reviews of Amazon Relational Database Service (RDS) between 2014-05 and 2026-01, average rating 4.47/5, grouped into the problems users report most. Each problem links to the market it belongs to and to startup ideas built on it.
The problems Amazon Relational Database Service (RDS) users report
Unpredictable and hard-to-justify database costs — 34 complaints about Amazon Relational Database Service (RDS); 51 complaints across 6 products · market pageUsers across managed relational database services consistently describe costs as high, opaque, and difficult to estimate in advance. Several specifically note they're 'billed for the whole time it is up' without understanding what they're paying for, that 'pricing is complex and costly,' and that the jump between tiers catches them off guard. Students, NGOs, and small teams say they can't afford it at all, while engineers say they lose money to misconfigured settings they didn't know to watch.
No automated database performance tuning — 23 complaints about Amazon Relational Database Service (RDS); 30 complaints across 4 products · market pageUsers across Aurora, RDS, Ignite, and ApexSQL keep hitting the same wall: performance degrades unexpectedly and there is no system that catches it early or adjusts automatically. Complaints range from 'CPU spikes on 1000tps' and 'slow query detection missing' to 'no automated performance tuning' appearing nearly a dozen times verbatim. The monitoring that does exist — like Enhanced Monitoring — is described as 'entirely non-functional under heavier workloads', and users are left manually guessing whether the instance is undersized, misconfigured, or just having a bad day.
RDS costs spiral without warning — 23 complaints about Amazon Relational Database Service (RDS); 23 complaints across 1 product · market pageUsers consistently find RDS more expensive than expected, and the surprises compound: they're charged for snapshots after aborting instances, billed for stopped instances, and the default configuration silently enables scalable options without clearly stating the cost implications. One user put it plainly — 'RDS obscures certain configuration settings and defaults to a scalable server without clearly stating the payment options, leading to unexpected costs.' Another notes the per-hour billing model is painful for individual developers and small teams who don't run workloads continuously.
Unplanned downtime from routine DB operations — 20 complaints about Amazon Relational Database Service (RDS); 23 complaints across 3 products · market pageEngineers running managed databases on Aiven, Aurora, and RDS consistently hit forced downtime for things that feel like they should be routine: scaling instance types, patching, engine upgrades, subnet changes. The complaints are specific — 'the downtime that occurs when changing the instance type size needs to run much faster', 'it's not always clear from the console if changes may create downtime', 'scaling operation required downtime, zero data loss not guaranteed'. The problem isn't that downtime is infinite; it's that it's unpredictable, underdocumented, and hits production without warning.
No visibility inside managed RDS instances — 19 complaints about Amazon Relational Database Service (RDS); 20 complaints across 2 products · market pageRDS and Aurora users have zero access to the underlying OS, file system, or terminal — by design. This means when something goes wrong, they can't SSH in, can't inspect logs in real time, can't install diagnostic agents, and can't analyze the MySQL data directory or system-level resource contention. Users describe it as 'inability to see what's happening inside' during incidents, with logs that must be downloaded and analyzed offline rather than in a usable console.
Database management UIs built for engineers, unusable by everyone else — 16 complaints about Amazon Relational Database Service (RDS); 27 complaints across 8 products · market pageUsers across every major relational database product — Aurora, RDS, Aiven, Ignite, Phoenix — describe the same experience: consoles that are 'extremely NOT user friendly even for a tech savvy professional', management GUIs that are 'clunky', interfaces where 'multiple clicks are needed' for basic operations, and no way to visually interact with tables or build architecture diagrams. There is no night mode. There is no mobile interface. Parameters cannot be configured without hunting through menus. The consistent thread is that these UIs were designed to expose every capability to a database engineer, not to help a developer, analyst, or small-team CTO actually get work done without frustration.
RDS setup and migration complexity — 16 complaints about Amazon Relational Database Service (RDS); 16 complaints across 1 product · market pageUsers consistently struggle with the multi-step, multi-service setup process for RDS, describing it as 'very confusing' with too much switching between services. Migration pain is especially acute — both moving from on-prem to RDS (where existing monitoring integrations like New Relic break and table-level visibility disappears) and moving between RDS engine flavors like MySQL to Postgres (a workflow users say flat-out doesn't exist in a managed way). Security configuration compounds everything: multiple users independently flagged that security group setup for RDS is 'tricky' and that it's 'too easy to expose RDS into wrong security groups.'
Lost control in managed database environments — 13 complaints about Amazon Relational Database Service (RDS); 16 complaints across 3 products · market pageDBAs and developers using managed PostgreSQL and RDS services keep hitting invisible walls: no superuser access, default configurations they can't override without manual workarounds, and no UI visibility into basic properties like port numbers or current parameter values. As one user put it, 'all the configuration comes with default parameters requiring manual modification to override' — and another noted that entire categories of DBA work that rely on OS-level or system-level access simply cannot be done. The frustration isn't that managed services exist; it's that the handoff between what the cloud provider manages and what the DBA still owns is poorly defined, poorly tooled, and changes unpredictably.
No OS or root access on managed RDS — 13 complaints about Amazon Relational Database Service (RDS); 14 complaints across 2 products · market pageTeams running databases on Amazon Aurora and RDS repeatedly hit a wall: they can't get root or sysadmin access, can't touch the underlying OS, and can't install plugins or run admin-level utilities. Complaints range from 'administrator access to the server (sudo su) is not possible' to 'certain admin level utilities are not supported' to being forced into 'hacky workarounds' because a missing privilege blocked the SA from creating objects.
Database docs too hard to learn from — 9 complaints about Amazon Relational Database Service (RDS); 22 complaints across 7 products · market pageUsers across multiple relational database products repeatedly hit the same wall: documentation exists but is written for people who already know the system. Complaints include 'lack of tutorials for beginners', docs that are 'not very easy to understand', and users having to leave the product entirely and 'search on Google' just to locate basic features. The problem isn't missing docs — it's that what's there assumes prior expertise, skips hands-on examples, and leaves newcomers stuck at configuration and setup.
In their words
“Steep learning curve on the aws environment”2.5/5 · 2018-11-29
“The lack of detailed documentation about how to optimise your code for the RDS service.”2.5/5 · 2018-11-28 · RDS setup and migration complexity
“The service has administrative restrictions that prevent its application to some large vendor products, requiring extensive DBA tasks.”2.5/5 · 2018-11-27 · Lost control in managed database environments
“We do not have all the option in RDS within free tier.”3/5 · 2023-05-23 · No visibility inside managed RDS instances
“The restrictions to the master database limit access to some system-wide offerings until later.”3/5 · 2018-11-27 · Lost control in managed database environments
“Expensive, pricing can be hard to estimate”3/5 · 2018-04-25 · Unpredictable and hard-to-justify database costs