Amazon RDS Reviews

If you're operating within the Amazon universe of cloud computing, it's almost a no-brainer to utilize [Amazon Relational Database Service (RDS)]. RDS is well suited for probably a majority of applications that are candidates to host on a cloud computing platform as it reduces overall management and complexity of your system.

However, if you're doing a lot of data exporting/importing using tools that write to/read from the disk on the server, you may have challenges integrating RDS, as you have no access to the underlying host.

Amazon Relational Database Service is a simple, reliable and scalable solution to implementing Databases in a cloud environment. It provides convenient access to databases with high availability and security features. It integrates well with other Amazon Web Services tools, and can be used inside private clouds as well as publicly. It serves well as a foundation of any online service.

We have not needed a great deal of support with Amazon Relational Database Service, but as a service I've seen good things in terms of responsiveness, comprehension and helpfulness from the RDS support team when we have had to interact with them. They usually know the answers or get them quickly, and provide us with guidance even for features they don't provide yet.

If you don't want to have to deal with some aspects of daily DBA, Amazon Relational Database Service (RDS) is the right solution for you.

• Automatic backup
• Optimized instances
• Lots of database options
• Set up lots of stuff inside the database
• Backup to S3
• Integration with other services
• High availability replication
• Many of the options available in other vendors, but much easier and faster

I needed to use support sometimes. And AWS support is really, very good. From documentation to live support (chat/e-mail/etc.), it all really helps. And if you have some question, the support helps, from auditing stuff to adding parameters, or even with optimization. They try always to help more than we need, and this, to me, is very good. It's like a spare DBA waiting to help you.

RDS is well suited for application environments where the developers don't have time to worry about the database. If the application requires a DB that is "fire and forget," RDS can be a rock solid implementation. This is particularly true for teams that may not have DBA resources or don't have a team member with extensive database admin skills. With some basic understanding, teams can stand up a DB in RDS and move on to the task of developing and maintaining the applications that use the DB.

RDS may be less appropriate for high performance applications where every level of the systems needs to be finely tuned. On the one hand, a novice developer may be able to get the required performance by scaling up to a large instance size while a proficient DBA could get the same performance from a finely tuned database running on an EC2 instance where access to the OS is available.

Pricing might also be a factor against RDS for teams that have limited budgets. Again, higher performing DB instances might be priced slightly more than the same DB running on a stand-alone server.

I have only had good experiences in working with AWS support. I will admit that my experience comes from the benefit of having a premium tier of support but even working with free-tier accounts I have not had problems getting help with AWS products when needed. And most often, the docs do a pretty good job of explaining how to operate a service so a quick spin through the docs has been useful in solving problems.

Amazon Relational Database Service is well-suited if the project requires high factor time to market. It is a good approach to enable full-fledged services in a quick manner using IaC deployment methods.

Documentation and the community are sufficient to deal with many small instances (PostgreSQL, MySQL).

A growing organization that was already stretched financially and infrastructure wise, was looking for ways to further test and build out product environments for evaluation were looking for quick, easier ways to spin up new environments. Amazon Relational Database Service could certainly be used for long term use, but for this nimble use/business case, it was a great option.

The product is fairly straight forward to use, and staff as well as knowledge base is pretty good for getting answers you may need. The product is a great, flexible alternative to adding to one's own in-house infrastructure. It's especially useful for environments that you aren't sure about the overall long term need. Amazon Relational Database Service is great for environments that once you determine the long term need, can be maintained by Amazon.

For a general-purpose workload, RDS is a perfect fit and works really well and takes care of a lot of stuff for you (replication, security, monitoring, scaling, storage, publishing logs to CloudWatch). If you have a read-intensive load though, you should probably think of switching to a NoSQL database service like DocumentDB or DynamoDB.

AWS has always been very prompt in responding to support tickets and follow-up questions. With RDS too, we never felt that the support that AWS provided was not good enough.

I definitely can recommend RDS to my colleagues, it has helped us a lot to solve issues. We don't have to worry about networking configuration as doing this with Amazon Relational Database Service is fast, easy and secure. We can create instances in a few steps, we have an API that allows us to do via code, not only in the console.

I have never used the customer service of Amazon. But the great advantage of AWS is the community support, you can get a lot of help in any internet forum, so this is really good. So if you feel that isn't in your budget remember you can count on the internet.

RDS has the ability to handle infrastructure management in a secure manner, creating a highly available and scaleable database system for great use in production, stage, and development environments. AWS handles all backup and restoration giving your developers less to worry about with infrastructure worries and more time to develop code and produce quality code. In our use case, we required a fully configurable and easily maintainable and scriptable database and RDS completely fit that bill with ability to be scripted via terraform.

Support for overall AWS services is a 10. We had one issue with creating a dev / stage / prod database within Aurora and a quick call with Amazon allowed us to figure out the issues we were having and it was determined it was how we were creating our initial setup of the databases.

Using Amazon Relational Database Service you have almost everything that is needed in a database environment. High availability, backup and recovery processes are already in place, with load balancing, updates and so on. For sure your demands for a DBA will be smaller than if you had an on-premises environment since most of the job is performed by AWS. Just have on mind that you will have to expand your knowledge to cover some specific aspects of a cloud database environment.

I had some situations where I expected more from the RDS support team. Basically, you can't trust RDS 100% (like any other product). You need to monitor it yourself, check backups, maybe extract those database logs from AWS and store in a local resource.

My agency took on a client that required a mobile game build from scratch that had e-commerce baked into the final product. We needed to keep the user information safe and organized on both a game perspective but also from a financial perspective. Amazon Rational Database Service does all of that. They monitor the database so we don’t have to spend time and resources doing so.

As I said earlier, ARDS checked off all of the requirement boxes. And when we needed assistance with any problems we ran into, their support staff was there to help. Simple problems can be fixed quickly. Larger problems might require spending money to get consulting hours on the project so experts can help course correct.

Any production database needs could benefit from Amazon Relation Database Service. You can pick any engine you want, and it is entirely managed for you. It is especially good for small teams who do not have or cannot afford a database administrator. It has been useful in that way for us.

Amazon support is always top-notch. You get immediate feedback on whatever you are working through and given several resources on how to resolve them. Additionally, they are able to do some things for us, meaning we don't need to have a database administrator around at all time to implement their suggestions.

We use AWS RDS service for multiple applications as a back-end for MySQL Databases. It is well suited for all companies, including small to enterprise. It does not suit if your application has only a static website or fewer backed services.

We have the AWS Enterprise support plan, and the response time was great in less than 1 hour. The AWS engineering team understands the issue and solves.

Amazon Relational Database Service (Amazon RDS) is great for any relational database installation. If you are starting a new project you might even benefit from their Free Tier for the first year of using the service. But what really helps me is that it allows anyone to set up a production environment, and helps you manage backups and failover so your customers won't be caught unaware when there is an outage.

It is very well suited as a small data store for lightweight micro-services where there is no need for a complex table structure and database objects. It is not very well suited for applications which perform analytics on a large volume of data in a short span of time and, hence, require a very high throughput.

If you have the rest of your infrastructure in AWS, it is easiest to use Relational Database Service for your databases rather than build out your own servers in EC2. The server maintenance, clusters, etc. are all done for you, and you have technical support you can call rather than having to troubleshoot everything yourself.
If you have non-Microsoft databases, you have the ability to set up read replicas so your database writes are not slowed down.

All AWS support teams have been very helpful in giving setup advice, troubleshooting, etc.

Amazon Relational Database Service is well suited for environments where fully managed relational databases are required or desired. With Amazon RDS you can know that your database instance is being monitored, updated, and backed up, and is in good hands. It's great to be able to sleep well at night.

All of my RDS support experiences have been very positive. I've gotten help whenever we've done a major upgrade to an RDS instance and want some hand-holding.

Amazon RDS is the best suitable solution if you want to store sensitive data in the cloud with high availability and scalability of the database. Cost is a major concern. If your organization is financially small, then only you have to search for another solution.

Great for anyone just getting started with hosted RDS, and looks to have the price advantage as well. Leveraging other AWS services are very helpful, so as not to have to learn different configurations/tools to adjust RDS vs EC2, etc.

Amazon Relational Database is easy to Set up, Use and debug. Automatic patch is very good. Amazon Relational Database provides good security and it's configured very well. The timely backup is also too good in reality. Multi-tasking can be improved and the amount of data storage in one file needs to improve.

Amazon Relational Database Service is great when you need a Database solution that can work for you very fast. It is also a great solution when you need a system that can scale to handle very large amounts of data. You can get set up with a complex, large database eco-system in minutes/hours, and have the best security and backups scheduled. The alternative to doing this would typically be hiring one or more very experienced database professionals for not just the implementation, but also on staff to handle the periodic maintenance necessary.

RDS is well suited if:

1. You have a modest budget. If I were completely bootstrapped and not married to AWS, I might look elsewhere.
2. You need a speedy, secure transactional, do-it-all database.
3. You need the ability to scale seamlessly.

Best for simple to moderately complex database solutions that will keep running with minimal oversight. Bad for complex database solutions that the sysadmin wants to keep a detailed eye on and wants access to all the available tools of an RDS system. Data will be safe under the RDS umbrella if you implement it right, which is something that can be learned in a 2 hour class on AWS.

If you want to run a database in the cloud, RDS is definitely the way to go. I have not come across any scenarios that would indicate a better option.

RDS removes the headache of maintaining and monitoring database instances, we do not have to worry about replication, backup and restore, updating the database etc as it's fully managed by AWS. So if you want to focus more on building the actual software rather than worrying about the infrastructure, RDS is a highly recommended.