RDS is just a per-hour price, so a t3.micro depending on region and DB engine is about 20/month for it to be running, plus any storage. If it's multi-AZ it will be more. Your bill should provide a breakdown. Answer from inphinitfx on reddit.com
🌐
Reddit
reddit.com › r/aws › how to find out what exactly is causing the cost for my rds instance
r/aws on Reddit: How to find out what exactly is causing the cost for my RDS instance
November 3, 2022 -

Hello,

I am running a db.t3.micro rds for my discord bot, and the average monthly costs are $20. It seems a bit much, as there is max maybe a couple of interactions per hour with the bot and, therefore, the rds instance.

Is there a good way to check what exactly is causing the cost?

I also see that the db.Transactions.xact_commit.avg value is constantly on 2.7~ even when there are no interactions with the bot for multiple hours.

🌐
Reddit
reddit.com › r/aws › aws rds pricing help.
r/aws on Reddit: AWS rds pricing help.
October 4, 2023 -

Can someone shed some light on how RDS pricing works?

There seems to be 3 components here - the instance, storage and iops. Instance and storage are fixed and you can calculate for a month.

But what about iops? IIUC I'll be charged every time I read/write to the tables with increased cost if I hit a spike in traffic or run some queries on very big tables?

https://aws.amazon.com/ebs/pricing/

This link says gp3 has 3000 iops free. How do I estimate my iops?

Then there seems to be a separate charge for throughput? 125MB/s and then an additional charge per MB/s-month. Not sure how to calculate this. What happens if I had a sudden spike where I went to 500 MB/s for an hour. How would that get converted to MB/s-month.

All this seems like a recipe to get hit by an unexpected large bill. Would it be better to go with a managed db on lightsail which has a fixed monthly cost?

Thanks.

🌐
Reddit
reddit.com › r/aws › why is rds so incredibly expensive
r/aws on Reddit: Why is RDS so incredibly expensive
May 23, 2022 -

I created an RDS postgres database with the lowest settings - literally free tier on everything, but apparently I don't qualify for that anymore.

I was never able to figure out how to create a table, put data into it, or connect to it.

However, I was charged $10 a day for a few days, so I killed it and won't be going back. I've had multiple similar experiences with AWS and I never get an explanation for the charged from AWS.

Is there any explanation for this? I use heroku and firebase and never have nearly as much difficulty using those and I've never had a billing issue or random charges.

Update:Here is a detail for the billing. How did this happen?

Update 2:
After feedback here that the costs came from the storage type, I went back and looked at the creation process to see what happened. In selecting the "Easy Create" process for a postgres RDS database, the more expensive storage type was the "default". That's pretty upsetting to me and I really wish that there was something that told you the project cost prior to activation, but at least I figured out what happened. I'm gonna recreate and see if I can't get it cheaper.

Thanks for the help.

🌐
Reddit
reddit.com › r/aws › why is postgres rds instance more expensive than sql server (license included) rds instance?
r/aws on Reddit: Why is Postgres RDS instance more expensive than SQL Server (license included) RDS instance?
September 5, 2025 -

Question is in the Title. Only reason I'm considering Postgres is because of the "licensing costs" associated with SQL Server. Then I see this. What's up?

Postgres instance would be $86.51 USD:

db.t4g.micro

vCPU: 2

Memory: 1 GiB

SQL Server equivalent instance would be (license included): $67.71 USD

db.t3.micro

vCPU: 2

Memory: 1 GiB

Edit:

For those who asked for more information to better understand my perspective

  1. Go to https://aws.amazon.com/rds/pricing/?p=ft&c=db&refid=e21cc09f-34cd-4d7e-a012-ad97353eb4b4 and go to the "Pricing by Amazon RDS engines" section.

  2. Select either "Amazon RDS for PostgreSQL Pricing" or "Amazon RDS for SQL Server Pricing"

  3. Navigate to the "AWS Pricing Calculator" and click "Create your custom estimate now." Select the instance types that I have mentioned above without changing any of the filler info.

🌐
Reddit
reddit.com › r/dataengineering › need help understanding rds pricing and options
r/dataengineering on Reddit: Need help understanding RDS Pricing and options
February 17, 2024 -

Context - I am not a Data Engineer or an Infrastructure person. I do understand the basics when someone is talking about On-Demand vs Reserved instances and such. I am well versed with the anything that comes with working with databases once it is already in place. I am trying to understand the cost for AWS RDS option for Postgres. I am very confused with the terminology that comes along with their instance selection and pricing calculator selection.

Current requirement - I am expecting around 300,00 - 3,000,000 million records of data. It might grow to about 30,000,000 (being overly optimistic) over next 2-3 years. Records I have mentioned would be across entire DB, including multiple schemas and tables.

Question - Is there even a need for a cloud solution like AWS or GCP? If so could someone point me in the right direction to get started? Especially understanding the pricing structure?

🌐
Reddit
reddit.com › r/aws › how do i see why my rds costs went up?
r/aws on Reddit: How do I see why my RDS costs went up?
April 4, 2024 -

I have an RDS instance that supports a years old EC2 service and had had an extremely stable cost. This month, it went up $300 which is over 100%.

So I try and dig in on the billing stats and there is nothing that I can see that can explain it.

Is there any way to figure out what changed or is my only option to move the service out of aws?

🌐
Reddit
reddit.com › r/aws › rds pricing 2 cores vs 4 cores is almost 10 times the cost. what gives?
r/aws on Reddit: RDS pricing 2 cores vs 4 cores is almost 10 times the cost. What gives?
April 21, 2023 -

Hello, I'm a senior developer and just landed on an ongoing project recently. I'm quite new to AWS.

I had to upgrade an RDS instance in production a week or 2 ago. CPU was running at 95% all the time and our backend was bored and basically sleeping waiting for the database to answer. My only option to remove the bottleneck ASAP was to upgrade to 4 cores and to my shock it costs nearly 10 times more. (db.t3.small to db.t3.xlarge)

We're using mysql community and that did the trick to resolve our issue in production.

Am I missing something? Should I configure 2 db.t3.small instances instead?

Thanks.

Top answer
1 of 6
25
The price difference shouldn't have been a surprise. The db.t3.xlarge is listed as 8x as much per hour vs a db.t3.small. The number of cores is just one metric. An xlarge has 8 times the memory vs. a small. And the xlarge can "burst" its CPUs usage 4x as much as the small instance. Some things to check: Are the db queries optimized? E.g., maybe there are missing indexes, slow queries, bad schema design, mix of oltp & olap loads, etc., causing poor performance Can the application be shaded to use multiple smaller databases? There are many tradeoffs between price, performance, reliability, application & operational complexity, etc. Can the application use techniques such as caching to reduce the db load? Can the application instances be split to use different write vs. read instances (replicas)? (see also: CQRS ) And generally you'll want to load test with different instance types to see which one fits your needs the best. (But be sure to test under realistic conditions, especially if there are frequent traffic spikes and/or high expected traffic growth).
2 of 6
15
Yes, you are forgetting something. T instance family provide burstable performance, you must understand what that means before pick a T instance here . In a nutshell, if the instance is performing above the CPU baseline AWS will “remove” performance from the CPU. If the CPU is already at 95% for a long time, it’s likely that all the CPU credits are gone, check this doc to learn how to monitor it. Last but not least, don’t take from granted T instances are always cheaper, if your workload needs consistent performance above the T instance baseline evaluate M or R instance type.
Find elsewhere
🌐
Reddit
reddit.com › r/aws › confused about rds pricing
r/aws on Reddit: Confused about RDS pricing
November 6, 2016 -

Hello all. I am currently using free tier for RDS, I plan on using EC2 as well as an RDS for mysql. The application is a simple springboot app (which will run on EC2, something small) and then the database will need to run on mysql which may grow rather large over time.

I have looked at EC2 and the pricing on that is pretty straightforward. take hourly cost, multiply by hours in a month, and thats the monthly cost.

The price on RDS is a bit more confusing though. It has a usage cost just like EC2, but then im wondering what exactly you pay for the actual storage itself. 20GB could not cost the same as 200GB could it?

Is there another cost that is added onto the actual server cost that handles storage capacity?

🌐
Reddit
reddit.com › r/aws › $200 bill for rds with like 1000 queries?
r/aws on Reddit: $200 bill for RDS with like 1000 queries?
February 4, 2021 -

I signed up for AWS hoping to use the free tier, and today I got a bill on $200 for RDS, so I was pretty surprised. The specification reads:

$0.20 per RDS million I/O requests (Aurora) - 2,926,527.000 IOs

USD 0.29 per RDS db.r5.large Single-AZ instance hour (or partial hour) running Aurora MySQL - 538.799 Hrs

And I don't understand at all where this is coming from. I have a node app that I'm developing and doing some queries with the mysql2 module and pooling and have at a maximum done 1000 queries.

Can someone please explain? I realized that I may have forgotten to end() the connections that I'm doing in the app, can it be tied to that mistake?

🌐
Reddit
reddit.com › r/aws › rds costs have ballooned: how to monitor i/o requests?
r/aws on Reddit: RDS costs have ballooned: how to monitor I/O requests?
April 21, 2024 -

I've been using Amazon RDS for many years; but all of a sudden, my costs have ballooned into hundreds of dollars. From 118mn I/O requests in February, March saw 897mn and April is so far on over 1,500mn.

I've not changed any significant code, and my website is not seeing significant additional traffic to account for this.

How can I monitor I/O requests? I don't see a method of doing this from the RDS dashboard?

I rebooted (by applying a maintenance patch) yesterday, and the only change I can detect is a significant decrease in swap usage - it was maxing out, and is now much, much lower. Does swap usage result in increased I/O requests?

I only have the one Aurora MySQL box. Am I best to enable an RDS proxy on this ($23 a month), or would that have any real effect?

...later, if you're wanting to monitor I/O requests, you want to be monitoring these three in Cloudwatch. As you can see, there's been quite the hockeystick.

An I/O request is a badly-optimised request, or if you've just got too many requests going on for some reason. I looked into it, and found that some database-heavy pages were being scraped by some of the big search engines. Using WAF, I've capped those pages at 100 page impressions per ten minutes for every visitor - which humans are unlikely to hit, but scrapers will hit relatively quickly. The result is here - returning these down to zero.

🌐
Reddit
reddit.com › r/aws › how to minimize cost in an rds database environment?
r/aws on Reddit: How to minimize cost in an RDS Database environment?
November 13, 2025 -

I have a web application with 20GB of provisional data on an RDS database. It's a load balanced environment.

I'm looking for ideas to keep costs down, because as I look at my first monthly bill it's a lot higher than I thought it'd be.

$0.0225 per load balancer hour -- don't know how I can get rid of this or keep it down. I noticed through 12 days it charged me for 617 hours (which is 25 days), but I think it's because I had an old environment that I hadn't closed down and the load balancer was still running.

$0.005 per in-use public IPV4 address hour. This is the one I think I should be able to drive down, but I'm not sure how to start doing that without breaking something. AWS through 12 days is charging me 2,098 hours, which is 87 days, which over 12 days suggest I have 7 IPV4 addresses. This seems excessive for what I'm doing.

There are some other charges as well: $0.0104 per Elastic Cloud Compute On Demand Linux t3.micro instance hours ... $0.08 per GB-month of gp3 provisioned storage (EBS US East) ... $0.016 per RDS db.t4g.micro Single-AZ Instance Hour running PostgreSQL ... $0.115 per GB-Month of provisioned gb2 Storage running PostgreSQL ... As I look at the hours or GB-Mo consumed for all of these, it doesn't seem I'll be able to eliminate these costs, although I am confused why I'm getting charged for both RDS provisional storage and EBS provisional storage, but I chalk that up to my own personal ignorance of how EWS works.

Does anyone have recommendations of where I can check or possibly reduce the number of IPV4 addresses I'm using? Is there maybe another better hosting platform than AWS that I should investigate somewhere that will reduce my costs?

If you can't tell I'm a newb and appreciate any insight and patience with my potentially dumb questions... Thank you!

🌐
Reddit
reddit.com › r/aws › aws rds vs ec2 self hosted pricing
r/aws on Reddit: AWS RDS vs EC2 self hosted pricing
October 1, 2020 -

I'm trying to understand if I'm doing the right comparison.

CPUs RAM GB Storage GB Storage Type Price/month
RDS MariaDB 2 4 30 gp2 53.09$
RDS MariaDB 2 4 30 io1 153.39$
EC2+EBS 2 4 30 gp2 27.53$
EC2+EBS 2 4 30 io1/2 28.28$

Of course, I do understand that RDS manage for you backups, patches, failure recovery, it's easier to set up a multiAZ deployment etc.

I just need to evaluate if the extra work is worth the effort or not, so I'd like to understand if my calculations are correct.

Also I don't understand why RDS io1 is 6 times more expensive...

Are there other factors, like performance?

🌐
Reddit
reddit.com › r/aws › regarding rds cost. how to calculate?
r/aws on Reddit: Regarding RDS Cost. How to calculate?
September 24, 2024 -

Can anyone please share how to check the AWS extended support cost details for the RDS instances. Currently the RDS is having engine Aurora sql and the while using AWS Price Calculator what should i select in configuration part. And after that how should I get the pricing for the updated version of RDS .

Thanks in advance :)

🌐
Reddit
reddit.com › r/aws › cost effective rds
r/aws on Reddit: Cost Effective RDS
May 3, 2018 -

RDS seems to be the majority of my side project bill. I get the importance of managed DBs and the opportunity cost of something like maintenance, ingress, snapshots, etc. Right now I'm basically shutting down my instance when im not working on my project, which isnt a long term solution, but I'm curious about what's the most cost effective DB setup other than un-managed on EC2?

I've looked into Aurora Serverless but it seems a bastion node is required in the VPC for tunneling? That's another $6-8 for a tX.micro and my goal is to be cheap in the near term.

I've also toyed with a mysql container in compose, but I've never been a fan of using a DB in a container.

Lightsail seems fine I guess, but it seems like there's no CI available?

🌐
Bytebase
bytebase.com › blog › understanding-aws-rds-pricing
Understanding AWS RDS Pricing (2025)
Amazon Relational Database Service (RDS) offers a fully managed database solution that simplifies setup, operation, and scaling of relational databases in the cloud. While it's easy and relative cheap to get started, the bill can accumulate pretty fast as this heated Reddit Postgres RDS is too expensive post suggests.
🌐
Reddit
reddit.com › r/devops › postgres rds is too expensive -
r/devops on Reddit: Postgres RDS is too expensive -
October 14, 2024 -

- I run engineering for an Indian company serving Indian customers.

- We run a multi az rds postgres on a db.m6g.12xl instance with 10tb of storage in ap-south-1

- This is costing us 12k USD per month

- We are constantly spending time optimising application performance since IOPs is a challenge

Now my question is, is anyone running postgres on data centers - I feel like the SSD storage of 100 TB with replication in multiple data centers with similar hardware would still be less expensive to us than this while giving a lot more performance. There will be some upfront investment needed but over an year it should pay for itself.

The database is both read and write heavy.

- I would like to hear stories (both good and bad) of being off the cloud and running things on your own.

- Are there alternatives to RDS postgres while giving me cost and performance benefits.

I am someone who has only worked on cloud in the last 12 years - I wonder if it makes sense to be off the cloud.

Top answer
1 of 5
167
If you’ve never managed bare metal, especially in a hybrid cloud/on-prem fashion, now is not the time. It would be better to get off RDS and run a Postgres ec2 cluster.
2 of 5
119
You can cut the cost in half by disabling the multi-AZ thing, because redundancy means redundant machines so twice the cost. In the end, that's a 48 vCPU 192GB of RAM box, and 10TB of SSDs, go look anywhere else and it won't be that much cheaper. Calculate how much it would cost you to build just two such machines, and put them in a datacenter. Plus the employee cost to maintain it over time, spare parts, backup storage. It's mostly upfront costs, it will be cheaper in the longer run but it might still take many months before you even break even. And then you also have to account for the machine's lifecycle: in AWS, you can just upgrade it to a 16xl if you need to, in minutes. With a real machine, when you're past the hardware lifecycle, you have to invest upfront again to upgrade it. If it breaks, someone has to physically go there and service it, and hope you have replacement parts around. In AWS, they'd transparently move you to another host and be back up in minutes. You'll also have to tune it for your hardware yourself as you no longer will have the AWS presets pretuned. You don't exactly just throw a 10GB NIC in a server and just like that you're processing 10GB of traffic: you'll probably have to configure jumbo frames and bigger rx/tx queues, etc. As others have pointed out, the bandwidth costs are probably gonna be high if you pass that over the Internet, so you'll probably also want to move all of your workloads there so traffic is local, so you also have to factor in a bunch more servers as well, and a good switch, and storage. If you want a cloud-like experience you might install something like OpenStack, and suddenly you're managing a Ceph cluster too. It's not that bad, I used to manage on-prem clusters but you know, beware of the details and gotchas. You're on your own: your own networking, your own operating systems, your own provisioning systems, your own storage solutions, your own backups, your own everything. You can't just make a VPC or a security group with metal servers, you have to configure all of that. You can't just order a new server and it boots up on its own with an AMI template.