Amazon RDS Reviews

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.

We have a lot of benefits moving to managed services, including Amazon RDS. It is a great service, and we have a lot of cases needing Amazon RDS. So, it is a great product.

We have some cases where our customers are looking for more performance or simplifying their DR. So, in this way, we have some cases where the customers moved from EC2 using enterprise license to Amazon RDS with less cost or with included standardization. So, we have cases of moving from EC2 to RDS to simplify the management and also simplify the DR strategy.

The most valuable feature is how simple it is to implement the solution's multiple phases, and also and also have the DR strategy on Amazon. For me, I think it is a great feature how simple it is to increase the performance of instances running on Amazon RDS.

For me, I think that it will be great to have the option to have more SQL or have a deployment allowing for configuring it with a Microsoft SQL server.

Currently, speaking of Microsoft SQL on RDS, you don't have a full option to be able to use it directly on RDS. So, it needs improvement. It will be good to have more solutions with a simple deployment. So being in one region, you should have the option to deploy the solution in another region.

I have been using Amazon RDS for three years. Also, I am using the solution's latest version.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten.

I haven't used the support, but as a partner, I rate the support a ten out of ten since we have a lot of technicians, like solution architects and so on. So the support is great. And we also have feedback from the customers regarding the tech support manager and the support they received. So, overall it is great.

Positive

The initial deployment of RDS was straightforward since our teams have experience.

I have seen a return on investment using the solution.

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.

I would recommend the solution to others. I rate the overall solution a ten out of ten.

Amazon RDS helps with information regarding the customer's business performance.

The solution has helped us have valuable metrics on our customer's business.

The most valuable feature of Amazon RDS is its performance.

The solution could improve the administration tools.

I have been using Amazon RDS for approximately three years.

The stability of Amazon RDS is good.

We do not have plans to increase the usage of the solution.

I have not used the support from the vendor.

The initial setup was straightforward.

We have seen an ROI using the solution.

Amazon RDS is less expensive than other solutions.

I rate Amazon RDS a nine out of ten.

Amazon RDS is custom development. 

Some databases that we would like to use are lightweight and simple to integrate with the application.

Amazon RDS is lightweight and flexible.

It's a secure solution.

The security features could be improved.

I have been working with Amazon RDS for three years.

It is part of the cloud migration solution.

Amazon RDS is quite stable.

Amazon RDS is a scalable solution.

RDS is a single instance. However, the actual users are approximately 500 people, both direct and indirect.

We have stopped using it.

I have not contacted technical support.

In the past, I used Amazon SimpleDB, Amazon EMR, and Amazon Redshift, but I no longer use them.

The initial setup is satisfactory.

It took two weeks to complete the installation.

We have three engineers, one lead, and one manager to maintain this solution.

With the help of our in-house staff, we completed the installation on our own.

Licensing fees are paid on an annual basis.

I would rate Amazon RDS a ten out of ten because it is lightweight, and the flexibility.

The primary use case is when you have to host your application on the Amazon cloud and your application uses database. Amazon RDS supports the following database engines: Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle Database, and SQL Server database. Amazon provides AWS Database Migration Service to migrate your existing databases to the Amazon cloud. It automates many aspects of database management viz hardware provisioning, database set up, database patching, and backups, which frees your database administrator to focus on important tasks. It also saves on the DB licencing costs.

It makes it easy to administer the database. It helps to scale your database by providing Read Replicas, which reduce transaction time. It is highly available and durable which helps in disaster recovery and management. 

It is also secure. You can build your own VPC and host the database inside it, which will produce robust security. You still need to follow the principles of security as highlighted by Amazon. 

Most useful is its availability to support multiple databases, such as Aurora, MySQL, Oracle, SQL Server, MariaDB, and PostgresSQL. Your application can use multiple databases as required. Combine that with the Automated CI/CD tools, this makes it easy to implement the microservices architecture, which is the need of the hour for web based applications. The capability provided by the RDS to automate a portion of the RDBMS tasks, such as backups and performance tunings for multiple database engines, helps to save on DBA time and cost.

The Amazon RDS engine could provide features for additional databases, such as Db2. It could also provide support for other databases, such as NoSQL databases, DynamoDB, and Apache Cassandra. They could all stay under one hood.

Another improvement that Amazon could do is to market their product so that more customers can use it. With Microsoft having its own cloud Azure hosting SQL Server databases and Oracle coming up with its own cloud, there appears to be more competition. As more customers move to Amazon cloud, it will increase the utilization of the RDS, then more customers will be able to harness the power of Amazon Relational Database Service (RDS).

I have been using this solution since 2015 on my consulting projects with a variety of clients.

This Solution is very stable, as many customers have witnessed. Responsibility to set up the Amazon VPC, servers, and RDS does take work. This requires a solid AWS (infrastructure): Administrators and networking team. They need to work with the AWS team, following the stringent security guidelines that will help to build stability for the solution. 

Amazon Web Services is built for scalability. RDS is designed with scalability in mind.

It is available. You need to negotiate and engage their services.

Earlier, we were using traditional on-prem databases. The need to switch to Amazon RDS has been due to a variety of factors. One such factor is the need to move the existing applications in our data center with variable demand utilization and pre-installed servers and databases to applications migrated to Amazon Web Services cloud. Along with migrating applications on servers, we also need to migrate databases. With the added power of supporting multiple database engines as well as automating many functions of DBAs and releasing the DBAs to focus on essential tasks, this has made it easier to switch to Amazon RDS.

The initial setup will be complex. You and your team need to understand the complexities of setting up IAM, security groups, AMIs, VPCs, autoscaling/loadbalancing, and RDS, then plan for multiple availability zones for disaster and recovery. You also need to set up an infrastructure admin and infrastructure support team who will work closely with the AWS team. You do not want your entire development to get involved with setting up the infrastructure. Your administrators and infrastructure team need to set it up, then guide the development team on how to utilize the infrastructure.

The initial vendor team could help to set up the infrastructure, team organization, etc. Then, your in-house team can carry out the administration and support work as well as the day-to-day tasks, such as providing access, helping developers make changes, uploading to the infrastructure, performing the migration, deployment, etc. The vendor team needs to have certified, experienced consultants to set up the infrastructure.

Work with Amazon Pre-Sales team and have them present their products to your organization. They will help you to arrive at building a business case, PoCs, SLAs, contracts, etc. You will also need to set up a product support team along with the migration, deployment, and core AWS Infrastructure Administrator teams who will be essential to the success of the project.

This is where the product stands apart. You do not need to set up thousands of servers, hundreds of database, and hundreds of DBAs. You need to set up a minimal infrastructure. There is no need to pay upfront the cost of an entire data center. It is pay as-you-go. Therefore, you realize the benefits and scale up/down as needed. Amazon will provide the required capacity. This will help you to realize the ROI quickly, which helps you to keep on growing.

This has helped reduce the cost at the same time increasing the agility of the organization. Some thing which would have costed millions of dollars and nine DBAs could easily be replaced by Amazon RDS.

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

The main reason to migrate to the cloud comes from moving the underutilized. Variable demand applications moving to the cloud benefit from a cost savings as well as when they move from data center maintenance to building the core business capabilities. The application migration and database migration to AWS also provides an added advantage.

For new/existing customers building new products, such as Ola, Uber, or Swiggy, instead of building their own data center first and launching the product which involves massive costs, AWS offers a better quality solution if they are unsure about whether their product will succeed in the market. They can build the product, start making money, and utilize the pay-as-you-go model. Then, they can scale the product depending on demand utilization. That appears to be the best business case for Amazon Web Services.

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.

I use Amazon RDS for my access control system, which manages permissions for users to enter places like universities, workspaces, and club team areas. Amazon RDS stores user data and keeps access permissions current, ensuring the system is reliable and responsive for user security and convenience.

The most valuable features of Amazon RDS are its scalability, reliability, and intelligence.

The only thing that needs improvement would be the pricing of the solution. Otherwise, it works very well as it is.

I have been using Amazon RDS for three years.

I would rate the stability a ten out of ten. I haven't had any issues with it so far.

Scalability is one of Amazon RDS's strongest points. I would rate it a nine out of ten.

In 2019, we had a paid subscription for AWS technical support, not specifically for Amazon RDS. We reached out to them when we were conducting stress testing on our system and noticed a significant performance drop, but we couldn't identify the cause. AWS support was helpful. They opened a ticket, communicated with us, and worked with us to pinpoint the problem. Eventually, they helped us resolve the issue, which was valuable for our project.

I have previously used another DBaaS solution apart from AWS, which was Google Cloud Platform (GCP). In GCP, we used a PostgreSQL database. One standout feature of GCP that I appreciated was its robust monitoring tools, which were helpful for analyzing performance and identifying issues. While I can't speak in depth about AWS's monitoring capabilities, based on my experience, GCP's tools were quite beneficial in this regard.

Setting up Amazon RDS is quite simple. First, you create an instance by specifying details like its name, storage preferences, and security settings. You can also choose to set up backups. After clicking "create," your RDS instance is ready within minutes. You receive connection parameters, which you use in your application to connect to the database. From there, you can start creating tables and storing data. It's a straightforward process that doesn't require much technical complexity. The deployment of Amazon RDS instance was very quick configuration took only a few minutes. It is an easy and cost-effective process, with a setup fee of around $31. Getting the connection parameters and establishing the connection to the database was seamless and efficient. Overall, it was a smooth and positive experience. 
Amazon RDS requires some maintenance, but it is not complicated. You might need to update the database configuration from time to time, which can be done by modifying your RDS instance. You can also schedule regular backups and updates provided by AWS. These changes can be controlled by you, so it is an organized process that ensures your database stays in good shape without much hassle. We have approximately 10,000 users of the solution at our company.

Amazon RDS is quite expensive.

My advice for those starting with AWS products is to closely monitor your usage and expenses. With on-demand and pay-as-you-go services, it is easy to keep using resources without realizing the costs adding up. So, keep a close eye on your bills to control expenses, as pricing might seem small but can accumulate quickly. This is important for cost management in general, and it applies to AWS services too. Overall, I would rate Amazon RDS a nine out of ten.