Amazon RDS Reviews

We have on-prem servers and our database is hosted in the cloud on Amazon RDS. Everything is automated there, like setting up backups and replication. We have around 40 persons using RDS.

Amazon RDS gives us the ability to select as many tools, replicas, regions, and zones as we want.

I've used Amazon RDS for six or seven years.

RDS is stable. A cloud solution is always stable, and RDS servers are solid.

Amazon RDS is highly scalable. It is much simpler to scale up compared to an on-premise solution where you need to buy new hardware and migrate all the data. Ifwe need more capacity, there is a symbol that you can click on to upgrade your hardware. 

If you want one more server in a different region, you can spin it up and everything is done on the cloud. You can just select what you need and go, whether you're going to downgrade or upgrade to system type TX for whatever configuration you want.

Amazon support is good, but we've only communicated with them via email so far. We email support when we have questions, and they've always come up with the proper solution.

Before Amazon, we had MySQL and PostgreSQL, but it's not like we switched We still have on-premise solutions and some things in the cloud. Most of our stuff is still on-prem. It depends on if it's a critical application that is heavily used, so you don't have downtime.

Installation is straightforward. You choose your database for RDS, like MySQL, Oracle, PostgreSQL, MongoDB, etc., and select the distance type. It takes a maximum of five minutes time to select and set up the system. Our servers can be up and running in 10 to 15 minutes, and data migration took about an hour.

We have several in-house teams with separate databases, so they usually take care of it for us. I worked on some databases. We have a different method for RDS. One stacked, so we build our own scripts and publish them in the stack.

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.

I rate Amazon RDS nine out of 10. I recommend it. Cost is the only issue. RDS is one of the best choices if you need scalability and reliability, but you're not worried about the cost.

Some of the features will not be there. For example, some on-premises things we want to set up will not be supported there. There are some challenges there that they are fixing. 

When I was working for at my previous organization, we wanted to bring stability to all our MySQL databases. As a DBA, at first, it was scary as I thought I would be out of a job, however, the RDS managed DB allowed me to focus more on optimization and less on administration. (both hardware and software). 

When I was working at another organization we had a large amount of MySQL on-prem to manage. It required lots of time to set them up, monitoring, and maintain them. RDS really allowed us to remove all the painful administration parts. 

Less time was spent maintaining MySQL. Having to configure each server and spinning up a new MySQL in RDS takes 10 to 15min. It's a huge time-saving in maintenance. 

By using RDS, AWS takes care of the maintenance of the hardware and software updates. Being able to scale quickly or downsize with no impact is also great.

All of your databases are nicely organized under 1 interface; you have quick access to some monitors and Cloudwatch can be used to set up alerts based on thresholds and notify you. 

Today, with Terraform, you can automate the full process of creating RDS servers, deprecating them, changing their size, adding a replica, etc.

Create Replicas. Being able to create a replica with just a few clicks is great. Setting replication before would require backup, restore, and synching replication. 

Backups. The fact that you can take a snapshot of the database without impacting the server is great. In comparison, large backups could lock tables or take too long. Alternatively, you would have to use tools such as xtraDB backup. That requires lots of code and maintenance.

Change Size. Being able to change the size of an RDS MySQL instance is amazing. There's no need to provision new machines, setup replication, etc. It's all done for you.

The solution needs RDS Mysql support for both MySQL 8 and MariaDB. 

The Performance Monitor they have is a little clanky, at least in regards to the UI. 

I wish they had designed a better MySQL Monitoring solution. I personally like SolarWinds DPA.

The performance is not always as good as MySQL running on its own EC2 instance. I have done some benchmarks before between EC2 instances and RDS and EC2 were better.

Being unable to select Out-file is annoying. They do support select Out-files into S3 but only on Aurora. It would be nice if they had implemented that feature in RDS MySQL.

I've been using AWS RDS for more than 8 years. 

MySQL RDS is very stable. I cannot say that running MySQL on-premise or on EC2 instances is less stable than RDS MySQL. However, when there are hardware issues, if you have RDS MySQL standby "on", you'll appreciate the fail-over solution. 

MySQL RDS can scale very well. I have been using it in critical Production services.

AWS Customer Support is pretty good. Their response time is usually adequate. They offer different support options and provide different support media (for example, phone, web, and email).

I was using MySQL on-prem. I decided to switch due to the amount of time required to maintain on-premises databases.

The initial setup is fairly straightforward. There is some tuning that needs to be done with RDS. The default settings are not always adequate.

We handled the implementation in-house.

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.

I did not evaluate other options. I did evaluate Aurora, however, for the project requirements, it was not needed.

RDS MySQL (and Postgres) are great managed database services. AWS provides a large range of database instance sizes from micro to very large machines. RDS can scale, and creating Replicas is very easy to accomplish. 

If you're unsure if you should start using RDS or not, I suggest you consult with a MySQL RDS DBA or Data Architect who has used RDS for several years before making a decision.

I use the solution in my company as a database.

I use the solution for database setup and management, along with other factors like HA, durability, security, performance, automated backup, and maintenance.

Amazon RDS serves as a managed database service that supports database engines, improving areas involving MySQL cycle and PostgreSQL. The tool obviously handles the working of the database as a provider of managed services. The product also offers backup and recovery.

The product's high price is an area of concern where improvements are required.

I have been using Amazon RDS for less than a year. I am a user of the tool.

Around 4,000 people in my company use the product.

If I face any problems with the product, I contact the solution's support team. I look online to see if I can resolve the problem by myself, and if I don't get any answers to my issues, then I contact the product's support team. The product's support team is very good.

I use AWS Identity and Access Management (IAM).

The product's installation phase is easy.

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

I attend training sessions via calls with Amazon to learn about Amazon RDS.

If you have many sites for your company, using Amazon RDS can help with the database area. If you have any problem with the database, you can choose Amazon RDS.

I like the product very much.

I rate the tool a ten out of ten.

I use the solution to store the data of the applications we run on AWS Lambda.

The solution is scalable and can be configured with AWS Secrets Manager. So our password is secure. Also, due to Amazon RDS Multi-AZ, other nodes are available for us if we face a problem in a particular zone. This functionality makes the solution resilient.

If we do not keep track of our costs, we might face some problems.

I have been using the solution for more than three years.

The solution is quite stable. We haven't seen any issues in the last three years. Since we are using Amazon RDS Multi-AZ, other nodes are available on the machine, even if the solution is down. I rate the stability an eight out of ten.

I rate the scalability a seven out of ten. Multiple teams in our organization are using the solution.

We get a timely response from the support team when we raise issues.

The initial setup is quite easy. If we know the configuration, we can run the system, and our database will be ready in 10 to 15 minutes.

If we use the product wisely, we can optimize the cost. The cost depends on the kind of instance we use.

The solution helps us to provide a serverless database. There are multiple servers available in case someone has a high workload. We must understand whether our application is a read-heavy application or a write-heavy application. Accordingly, we must choose the right instance. Overall, I rate the solution an eight out of ten.

I use the tool to find out latency. 

The tool is very easy to use and configure. 

I would like to see improvements in the tool's automatic restart. 

I have been using the solution for two to three months. 

The tool is stable. 

The tool's support is nice. 

Positive

The tool's initial setup is straightforward. 

I would rate the tool's pricing an eight out of ten. 

I would rate the solution a seven out of ten. 

Our primary use case for this solution is relational data services.

The Amazon RDS features I found most valuable are snapshots and automatic backups.

In the next release, it would be great to see RDS provide connection pooling out of the box.

I have been using this solution for eight years.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best. It has never crashed on us.

My impression is that Amazon RDS is quite a scalable solution. If there are any issues, it's usually on the application side of things.

My impression is that deployment is quite straightforward. It took just one person in our company to deploy it.

Overall, I would rate this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

The dashboard and performance are the most valuable features of Amazon RDS.

In terms of what needs to be improved, I am unable to provide appropriate feedback because we are still familiarizing ourselves with the solution. 

Some of the documents that I have seen also state that Amazon previously supported MS SQL, which is great, but we are going into the database areas of PostgreSQL and MySQL. 

With my limited experience, I have noticed that documentation management could be improved. It could be better.

I have been working with Amazon RDS for three months.

We are using the latest version.

Amazon RDS is stable. I have not had any issues with the stability of this solution.

We are just now experimenting with scalability.

We have two engineers using this solution in our organization.

We are not receiving direct support from them, AWS. But from the previous company, we got one of the API services for this one, which was fine. But because of the account, we stopped the service, taking the service. We are still maintaining the solution on our end.

I would rate the technical support a three or four out of five.

EC2 and Lambda functions are two of Amazon's other services. 

There is another service that I have used. I have used Amazon services.

Our team and CTO are also looking into it. They were suggesting that Amazon was the best.

The initial setup was easy for me. In the beginning, I began with research and development. I didn't have any issues, it comes naturally to me.

I deployed this solution myself.

It took me, two or three hours to complete because I had to go through the documentation and check those areas.

I am not aware of the licensing costs.

I would recommend this solution to others who are interested in using it.

I would rate Amazon RDS a seven out of ten.

I work with Amazon RDS for our credit card business operations.

Amazon RDS fulfills PCI requirements, which is a valuable feature for us.

Amazon cannot guarantee the stability of some extensions, and there is a need for different extensions to meet PCI requirements.

I have been working with Amazon RDS for five years.

I would rate the stability of Amazon RDS as the best on a scale from one to ten.

The scalability is the best, and I have no issues with the ability to scale.

I rely on reading documentation to manage the database. The documentation is quite good.

Positive

I have used both Amazon RDS and Oracle, and I prefer Amazon. I prefer Amazon over Oracle as Amazon offers better features for our needs.

The initial setup process is simple.

I rate the price for Amazon as eight on a scale from one to ten. It's a reasonably high price for us.

Overall, I would rate Amazon RDS an eight out of ten. I would recommend Amazon RDS to other users.