Amazon RDS Reviews

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 Amazon RDS to store and manage data securely. It helps me retrieve information and gain insights from the data that comes in for my business or specific applications.

In one of our applications, customer interactions, such as subscriptions, transactions, and data from filled forms, are stored in Amazon RDS. This enables us to maintain a backup and aids in disaster recovery. Storing this data in the product allows us to analyze and gain insights into the details that come through the application when customers log in.

During our proof of concept, I had the opportunity to utilize the service alongside the vendor we were testing. Its most valuable feature is the scalability of the storage. It is easy to learn. 

I like using Amazon RDS because it offers quick operations for me. However, there are times when understanding how to use some of the services can be challenging, even with documentation. If I could add a feature, I'd improve navigation for related services. 

I have been using the product for a few years, 

Amazon RDS is a stable product with minimal bugs.

The product's scalability is good. It is used by over 1000 users in my company. 

I have contacted the tool's support. 

Positive

I find the tool's installation easy.

The solution is expensive. 

I rate Amazon RDS an eight out of ten. 

Amazon RDS is a good database.

Amazon RDS is very easy to use.

Amazon RDS should have a more user-friendly graphical user interface and include better database management options.

I have been using Amazon RDS for three years.

Amazon RDS is a stable solution.

I rate Amazon RDS a nine out of ten for stability.

Around 100 people are using Amazon RDS in our organization.

I rate Amazon RDS an eight out of ten for scalability.

Before Amazon RDS, I used Oracle and SQL Server. I switched to Amazon RDS to use the cloud.

The solution's initial setup is easy.

The solution was deployed through a consultant, and it took a few minutes to deploy it.

The solution's license was included in the payment of the cloud. On a scale from one to ten, where ten is the most expensive, and one is the cheapest, I rate the solution's pricing a seven out of ten.

Amazon RDS is a cloud based solution.

I recommend Amazon RDS to other users. I advise users to enforce the DBA to be part of any database cloud. Sometimes, people think managing the database is easy because the cloud is easy. However, that is not always the case.

Overall, I rate Amazon RDS an eight out of ten.

We use the solution to migrate products from on-premises to AWS environment.

The solution's most valuable feature is the provisioning of products. We don't have to worry about storage approval or hardware availability using this feature. It is the most accessible feature in RDS.

They should add a feature for manual SQL patching in RDS. Also, the auto-patching features have their limitations. We can't set a particular day or date of the month for auto-maintenance.

We have been using the solution for two years.

I have never come across any issues regarding the solution's stability. The database uptime works fine.

Scalability is one of the solution's best features.

The solution's customer service is excellent.

Positive

The solution's initial setup is straightforward.

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

If they have to segregate the databases into different RDS databases, it will cost almost the same or even more than any on-premises migration.

I rate the solution as an eight because it quickly provisions the resources. It covers all the security and governance parameters as well.

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.

I use this solution because I am trying to develop a fintech application.

It takes off a load in setting up the VM, infrastructure, software and user accounts that go with databases.

I appreciate how Amazon RDS allows me to choose the kind of database I want. The IT is easy to set up, which is the best. It makes it easy to deploy quickly. I initially tried setting up a database on a local machine and realized that several requirements were needed. I needed to do a lot of infrastructure management.

Sometimes the interface has many moving parts, which is a concern. For example, the cloud is a virtual network instead of having a dedicated VPC that handles databases, and they have it connected to the VPC that handles the main Amazon infrastructure.

If I had one that was indicated, it would make things easier because there are specific things I need when connecting to ensure accessibility. There is no need for multiple settings, considering a database cannot survive independently. Amazon RDS needs a connection to be a client, so they should tune it a bit more. In addition, uploading and having it done within a short period is challenging.

I have used this solution for the past seven months, and we use the latest version. It is deployed on the cloud, public AWS.

It has good availability, and so far, we haven't had any issues with it.

We haven't reached the point where we need to scale up for performance or storage. But I don't think manually scaling the discs is easy to do, so it should be able to scale on its own. In addition, the instances can manage the traffic, and there's an option for setting each total scale. So depending on how production goes, we may scale it. We have three people using the solution, including myself. So we need only one person to maintain.

We haven't contacted technical support because we haven't encountered any issues.

I completed the deployment myself. We're using local databases on a local host to test and deploy it.

We do not have any return on investment because we are still testing.

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.

I rate this solution a seven out of ten. Regarding advice, learning from other good consoles and having the basics before approaching them is essential.

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.

We primarily have many tools, including Jira, that are currently using RDS. It's mainly used by developers.

The provisioning is much faster. You don't have to prepare hardware or install software. You just need to create an instance and you have a database.

The RDS is a community version, so there are many common features that are basic. It's not an enterprise version, but all the features are very good overall.

A lot of the features are disabled by default. The solution should enable more features. I understand this could cause challenges to management for many clients using RDS, however.

I've been using the solution for less than a year, but some people on my team have been using it longer.

The stability os really good. I like it.

We haven't expanded on the solution, so I'm unsure about if it would scale well or not. We have a bunch of teams using the solution in the company, but they're small.

We haven't contacted technical support.

We are currently using a lot of other solutions as well. We have Oracle, we have PP2, and MySQL. We have a secret server as well.

The initial setup is straightforward. Deployment took about ten minutes.

We handled the deployment ourselves.

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.

We didn't evaluate other solutions before choosing RDS. Since we're using everything else that is Amazon, it seemed like an obvious choice.

We're currently expanding multiple versions of the solution. We use the cloud deployment model and most clients are also in the AWS environment.

I'd advise others to pay attention to the sizing, You don't want to over or under-size.

I'd rate the solution eight out of ten.