What is your experience regarding pricing and costs for Amazon RDS?

I would rate the pricing between six and seven. The cost is manageable because you can see the expense associated with each instance and utilize tools for tagging and cost control. However, a common issue is the tendency to forget about running instances no longer needed, which can lead to unexpected charges.

I don't know if the solution is cheap or expensive in comparison with competitors since AWS is the only cloud provider I tried so far. I connected some Azure Blob Storage to the instance running the Redshift instance. AWS is becoming pretty expensive because cheap or absolutely free services have become paid services. Amazon RDS is not an expensive product, but Amazon's ecosystem is becoming increasingly expensive.

The product is expensive. If Cisco needs two servers, Amazon uses four.

The solution is expensive.

The cost is a critical factor, especially if you are not inclined to spend a significant amount, Amazon is the preferable choice. The substantial initial credit and cost-effectiveness make Amazon an attractive option.

Amazon RDS is cheaper compared to other tools.

Amazon RDS is an expensive solution.

The cost varies depending on our use and our database engine. RDS is the database, and AWS manages it for us. It is cheaper to host on a cloud machine ourselves. RDS increases the cost because it manages the database. It’s really, really good. The solution is fairly priced.

The solution's price is good.

The solution is expensive.

The pricing of RDS is a little bit high compared to Microsoft. But we know that it is related to Microsoft licenses. However, it is a good price compared to other solutions.

Amazon RDS is less expensive than other solutions.

The solution's pricing needs improvement. I rate it as a six.

I have found the price to be a little bit too expensive.

I do not have specific details about the pricing, but we use the solution on demand. I rate the pricing a six out of ten, with one being the most expensive and ten being the cheapest. We have to pay extra for monitoring services.

Across most of the database services, it had been a little expensive. It's not only Amazon. If you look at other cloud solution providers, they have to reconsider bringing the prices down. Some clients might not be able to reap their ROI the way that the pricing has been structured for RDS services. It was quite expensive.

RDS costs can get complicated, that's for sure! 

I write this guide on how to analyze your RDS costs on the Developer's Guide to AWS costs: RDS Cost Guide. Probably the hardest part about RDS is understanding the different possible cost drivers: hourly instance costs, reservations, data transfer costs, backup storage, provisioned storage, etc.  Once you understand the AWS cost and usage report, it is pretty simple to pull it all together!

I am not aware of the licensing costs.

On pricing, I would rate RDS six out of 10 because if you don't know how to optimize and use your tool properly, the cost might hurt you. It would've been great if they had some cost alerts. You can usually manage using CloudWatch, but a simple notification that your costs just went up sharply or you overspent would help. I know there are videos and instructions on AWS. I'm not saying it's not there. But when the technology is new to you, it's hard to know what went wrong. And certainly, if you're not looking at your bill, you will be shocked by the amount. We had one or two bad instances or hiccups, but now we have everything under control. The licensing is fine for us, but it may be a challenge for new users.

Amazon RDS is a little costly, but it also reduces the number of full-time employees needed. We require fewer system admins or DBS because RDS reduces our workload. It's pay as you go. Once you are using it, you will get support. You don't need to buy a yearly license to get support. If we deployed our server there, we would get support from them.

Licensing fees are paid on an annual basis.

Cost always depends on usage

Make sure you provision your MySQL RDS properly. Don't over or under-provision. Perform some benchmarks before migrating. Migrating to a new system is costly. You don't want to have your data migrated only to realize it performs much worse than before.

It is less expensive than SQL Server. We pay based on the usage on a monthly basis.

The price could be better.

While, with all services of Amazon, there is a starter option that is given for free, this starter offer is not enough for the development or the deployment of products. Each time you pass these limits, you have to pay and it's completely unpredictable. The pricing can get very expensive. You pay a standard price, which is low, for a fixed reservation. However, if you exceed your limit, instantly, then the bill is increased tremendously. That's a drawback for the system. You have to provision very carefully and to make sure that you do not exceed the limit. That said, after careful provisioning, it is a very cheap option. If you are successful at cloud provisioning, you won't need to pay much. You do have to pay extra for technical support, even if you are on the free service tier.

By using a combination of Reserve Instances and On-Demand pricing, you can reduce the cost.

Good amount of cost reduction in cloud but we need to have well defined monitoring rules to save cost even after hosted in cloud. You can scale-up and scale-down with minimal duration compare to on-prem DB Servers. Which add more cost benefits. We can BYOL (Bring Your Own License), if you already purchased for Microsoft SQL Server or for Oracle and use that during RDS launch. If you need to reduce licensing cost in database , we can migrate to 3 open source databases in AWS RDS : MySQL, PostgreSQL, and MariaDB

We use the community version of the solution. I believe we only pay for the storage, but I'm not sure how it works exactly.