Hello Experts,
We have one non prod DB cluster in aurora postgres. We are seeing the daily cost for the RDS instance is appearing as ~$300 even we perform no activity on that database. Is there any way to further dig down and see what all queries or functions inside the database is actually contributing to these ~300$ amount?
We were initially thinking if the database backup is costing so much as the database size is ~15TB and we have 7 days backup retention set. But the cost explorer showing the cost under service "backup" as ~$2 only per day. And what should be the backup retention should we set, as it seems its occupying full DB snap each day in the storage and setting the retention for longer period (~35days for e.g.) is going to cost us more?
Difference between RDS and Aurora, when hosting Java application with PostgreSQL database.
Here i have my estimated pricing for using RDS. I suppose this is a separate server for actually hosting the database (hence the price) I found this alternative Aurora, which seemed a little bit better in regards to pricing.
This is much cheaper and also allows for almost the same amount of data (and up 1 million requests).
Can anyone explain to me the major differences in regards to these two services?
Hello, PM for Amazon RDS and Aurora here.
We recommend Amazon Aurora Serverless for bursty workloads that spike up/down frequently. Think an e-commerce website which gets a lot of traffic on weekends and nothing on weekdays. Our customers love not having to scale the database to account for the surge or drop in traffic.
Amazon RDS and "regular" Amazon Aurora are for workloads that need sustained throughput. Think a search website which gets traffic throughout the day/week etc.
Hope that helps!
Aurora is more than just serverless. Serverless is good for bursting or dynamic workloads. Regular aurora gives you managed updates, scaling, separate data and compute plane, etc. It is way more managed than RDS
Videos
Hello,
We are seeing the bill section its showing the aurora postgres cost per month as ~$6000 for a r7g 8xl standard instance with DB size of ~5TB. Then going to the "storage I/O" section, its showing ~$5000 is attributed to the ~22 billion I/O requests.
So in such scenario ,
1)should we opt for I/O optimized aurora instance rather standard instance as because its noted in document that if we really have >~25% of the cost because of I/O, then we should move to I/O optimized instance?
2)Approx. how much we would be able to save if we move from standard to I/O optimized instance in above situation?
3)Also is this the correct location to see the breakup of the cost for the RDS service or any other way to see and analyze the cost usage per each component of aurora postgres?
Hello All,
For provisioning Aurora postgres database for one of our existing OLTP system, in which there will be multiple applications running and those applications will be migrated slowly and will run in full capacity in an year from now. This will be a heavily used OLTP system which will consume customer transactions 24 by 7 and can grow up to ~80TB+ in size and peak read and write IOPS can go 150K+ and 10K+ respectively(based on existing oltp system statistics).I agree it wont be apple to apple comparison, but the existing OLTP system stats which runs on Oracle Exadata , its ~96 Core each node in the two node database with 200+GB memory in each node.
Now when checking AWS pricing calculator to have some guess estimate of how much cost we are going to bear for provisioning an aurora postgres instance below is what i found. The key contributor are as below..
https://calculator.aws/#/createCalculator/AuroraPostgreSQL
Compute Instance cost:- (Considering our workload criticality we were thinking of r6g or r7g)
r6g 4xl- 16 cpu , 128 GB memory , Standard instance costs $1515 per month and IO optimized instance costs $1970 per month.
r6g 8xl- 32 cpu , 256 GB memory , Standard instance costs $3031 per month and IO optimized instance costs $3941 per month.
r7g 4xl -16 cpu , 128 GB memory , Standard instance costs $1614 per month and IO optimized instance costs $2098 per month.
r7g 8xl- 32 cpu , 256 GB memory , Standard instance costs $3228 per month and IO optimized instance costs $4196 per month.
Storage cost:-
for "standard" instance, storage space 80TB+, considering 150K IOPS during peak hours and 10K IOPS during off peak hours and having ~1hrs daily as peak hours i.e. 30hrs peak IOPS in a month the cost comes to ~$13400.
for "I/O Optimized" instance, storage space 80TB+ and the cost comes to ~$18432/month and it doesn't depend on IOPS number.
Backup storage cost:-
As i see , even the automated backup is incremental but each of the daily snap is almost showing full size of the database. So here in our case for 80TB database, if we keep backup retention for ~15 days and considering 1 day backup retention is free , it would be (80)*(15-1)= 920TB. And its coming as ~$19783!! Is this cost figure accurate?
There are other services like performance insights , RDS proxy etc., but those cost appears to be lot lesser as compared to above mentioned services.
These costs looks to be really high and I have few questions here,
-
Is the above compute instance cost estimation is based on ~100% CPU utilization and in reality, as we wont use 100% cpu all the time so the cost is going to be lesser?
-
The storage cost seems to be really high, so should be worry about this, as because currently at the initial phase we may be having ~10TB of storage needed and as the day progresses we will accumulate ~80TB+ of data here at the end of the year? And should we be really go for standard instance of IO optimized one?
-
I got some information in some blogs stating the IO optimized instance is suitable if we are spending 2/3rd of the cost in the IO. So i was wondering, how to know the percentage we are spending for IO in our case once we move to AWS aurora, so as to choose IO optimized instance over standard one?
4)Backup storage cost appears to be really high, i.e. we are seeing for having ~15 days of retention. So want to understand of the figure is accurate or i am miss interpreting anything here?
Our production database needs some maintenance because it was neglected for a while. Some dba friends I know keep telling me to migrate to Postgres compatible Aurora. Others tell me it is too expensive.
When I did some quick estimates in the aws calculator, the cost seems unrealistically low.
Is there some tool that would give me a better idea of how much it would realistically cost?
-
Recent AWS ads in the console:
Amazon Aurora is a MySQL- and PostgreSQL-compatible enterprise-class database, starting at <$1/day.
After month-long support tag, I was told I "misinterpreted" the statement. The correct interpretation of that statement was that I could get a Aurora MySQL-compatible database for <$1/day, or an Aurora PostgreSQL-compatible database for no less than $7/day (or $2.50/day with 3yr upfront reservation).
2. The pricing section for Aurora PostgreSQL (https://aws.amazon.com/rds/aurora/pricing/) has "Serverless Pricing". Except...that Severless Pricing isn't available for Aurora PostgreSQL. This is the Aurora PostgreSQL-specific pricing section, and it's talking about pricing that simply isn't even available.
3. In the pattern of basically all Aurora docs/announcements, AWS recently announced "Amazon Aurora Backtrack – Turn Back Time" (https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-turn-back-time/). Except if you the post all the way to the bottom, you find at the very end that is "Amazon Aurora MySQL Backtrack". I guess that title isn't as exciting?
4. AFAIK it's not documented anywhere, but major version upgrades for Aurora PostgreSQL are impossible. 100% impossible. Try creating from snapshots, setting up replicas, whatever....it is 100% not possible to do a non-minor upgrade of Aurora PostgreSQL ever. You have to kludge together your own text import/export process between clusters, migration scripts, etc. which takes literally days on any decent data set. I hope you like the version of PostgreSQL you start with, because that's the one you're keeping.
---
Anyone have the inside scoop? Is Aurora PostgreSQL actually used by anybody? Is it ever not going to be a misleading and poorly supported product? Or should I go back to non-hyped vanilla PostgreSQL RDS?
I've been exploring AWS Aurora for my database needs, and while the service seems promising, I'm a bit confused about its pricing structure.
Is it true that, even if your Aurora DB instance is idle and not receiving any requests, there's still a minimum of 0.5 ACU 'in usage', which contributes to the billing. This information is not really visible in the AWS Pricing examples.
If anybody is using Aurora DB do you recommend it and how much do you pay for which cluster?
- 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.
Hey there,
Sorry if I lack any technical jargon for this question, I'm still pretty novice to AWS.Right now I have a desktop application that has a leaderboard function. For this I decided with would be best to go down the RDS path. I know pretty little about connecting and running databases, so I opted to go with the serverless route, and wanted to access the database using the Aurora API/ lambda.
I saw AWS deprecated mySQL for serverless 1.0, and since serverless 2.0 does not support the aurora API, I went with the postgres option, as I could still use the API.
I think this is the first mistake, as it seems the minimum ACUs for the postgres option is double of the mySQL. But either way my database has a min and max of 2 ACUs which is probably far more than my application needs. I would estimate max, my user pool will be about 50k and its just storing simple leaderboard numbers.
After one month of running the database, my monthly bill came out to ~230 dollars, which is just a lot especially since I have not even launched this product yet.My main cost was in just running the database :
$0.08 per Aurora Capacity Unit hour running Amazon Aurora PostgreSQL Serverless
2,840.991 ACU-Hr
$227.28
So does anyone have any advice on where to start in reducing the cost ? Should I move off postgres?Would running the EC2 and manually managing the database be cheaper? Would no longer using the API be cheaper ? Any help appreciated
Edit : Wow I just realized while posting this my ACU numbers did not add up and it turns out I was running a second database all month with nothing in it. So thats half the cost atleast lol. But still my questions apply
Which one would you pick for production workloads and why? I am asking the question from the perspective of performance, cost, support for Postgres extensions - which makes Postgres so powerful. Would like to get perspectives from folks who are currently using/have used them in production.
There are quite a few differences and which you pick depends on your specific use case. Here's an article from AWS giving an overview: https://aws.amazon.com/blogs/database/is-amazon-rds-for-postgresql-or-amazon-aurora-postgresql-a-better-choice-for-me/
Aurora is superior if you need to scale up and scale down without downtime. Just resize your replica then fail over to it.
Building a multi-tenant service. We're expecting ~100s of gb of embeddings per tenant.
I've never used Aurora so wanted to see peoples thoughts on price/performance of vector searches.