Amazon RDS

Amazon RDS

Top Rated
About TrustRadius Scoring
Score 9.0 out of 100
Top Rated
Amazon Relational Database Service (RDS)


Recent Reviews

RDS helped me a lot!

10 out of 10
November 29, 2021
I have used it for both PostgreSQL and MySQL databases. It was a way to host our database services when we were utilising the AWS …
Continue reading

Database for all environments

9 out of 10
May 02, 2021
It is used for hosting databases for a web application that has multiple environments and customers. The deployment for environments is …
Continue reading

RDS--database as a service

9 out of 10
March 05, 2021
Amazon Relational Database Service (RDS) is being used by the entire organization (benefits), but managed, when needed, by the IT …
Continue reading

Reviewer Sentiment

Positive ()
Negative ()
Learn how we calculate reviewer sentiment


TrustRadius Award Top Rated 2022
TrustRadius Award Top Rated 2020
TrustRadius Award Top Rated 2019
TrustRadius Award Top Rated 2018

Popular Features

View all 6 features

Database scalability (16)


Automated backups (16)


Automatic software patching (16)


Monitoring and metrics (16)


Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Amazon RDS, and make your voice heard!


View all pricing

Amazon RDS for PostgreSQL

$0.24 ($0.48)

per hour, R5 Large (R5 Extra Large)

Amazon RDS for MariaDB

$0.25 ($0.50)

per hour, R5 Large (R5 Extra Large)

Amazon RDS for MySQL

$0.29 ($0.58)

per hour, R5 Large (R5 Extra Large)

Entry-level set up fee?

  • Setup fee optionalOptional
For the latest information on pricing, visit…


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Features Scorecard



Product Details

What is Amazon RDS?

Amazon Relational Database Service (RDS) allows users to set up, operate, and scale a database in the cloud. The vendor states it provides cost-efficient and resizable capacity while automating time-consuming administration tasks such as hardware provisioning, setup, patching, and backups. This frees users to focus on applications so they can give them the fast performance, high availability, security, and compatibility they need.

Amazon RDS is available on several database instance types - optimized for memory, performance or I/O - and provides you with six familiar database engines to choose from including Amazon Aurora, MySQL, PostgreSQL, MariaDB, Oracle Database, and SQL Server.

Amazon RDS Screenshots

A look inside the RDS console.

Amazon RDS Videos

What's new in Amazon RDS!
Dive deep into RDS new features.

Amazon RDS Integrations

Amazon RDS Competitors

Amazon RDS Technical Details

Deployment TypesSaaS
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesNAMER, APAC, LATAM, EMEA
Supported LanguagesEnglish, French, Korean, Chinese, Japanese


View all alternatives

Frequently Asked Questions

What is Amazon RDS?

Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.

What is Amazon RDS's best feature?

Reviewers rate Database scalability highest, with a score of 9.6.

Who uses Amazon RDS?

The most common users of Amazon RDS are from Small Businesses (1-50 employees) and the Computer Software industry.

Reviews and Ratings




(1-25 of 51)
Companies can't remove reviews or game the system. Here's why
Ravi Khunt | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Previously we were using other SQL databases like MySQL or MSSQL on the same server where the application was hosted. As time passed and the size of the database increased, the performance of the application decreased, because of constantly increasing database size. Then we came to know Amazon Relational Database Service (RDS) provides the best possible solution to resolve database size and performance issues, no matter how much data in your database contains.
  • Scalability
  • Security
  • Automatic Backup
  • High Availability
  • As of now all features are up to the mark.
  • May be support of more SQL databases.
  • May be option for custom memory frequency for same size.
Amazon Relational Database Service (RDS) provides great features that may resolve your different issues. It supports multiple SQL database types at your convenience. If you want to separate the hosting of your Application and Database, then this is one of the best options to select. It provides Automatic backup in case of your database crashes. But for obvious, if you strict want to keep the database and application on the same server, then this may not the option for you.
Tom Blazek | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
I use RDS because we are migrating from MySQL on-prem to the cloud. This will result in less work and maintenance for us in the long run. We have moved almost all our on-prem workloads and are pretty happy so far. The interface for AWS is a bit hard to learn but we are getting used it to.
  • Easy to scale
  • Simple to setup
  • Lots of online examples
  • Not always easy to understand the access controls
  • Interface could be more modern
  • Not always easy to understand the actual cost
RDS is well suited for people who are too busy to host or manage Linux servers themselves. If you are growing rapidly it's much easier to spin up more servers in AWS or to increase capacity on your RDS instance. I don't think its cheaper, but its definitely less work and hopefully less worry about your data
Ramneet Kaur | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We used Postgres AWS RDS Solution for our database need. First, we used to have traditional excel storage but since data is increasing with immense speed. We decided to upskill our team and start looking for solutions and ended up with AWS RDS. It takes some skills to write SQL queries but it is the best approach we could ever see. We are delighted to use this service.
  • Postgres help us to do many SQL queries for crud operations.
  • With the public endpoint, it is easy to provide the endpoint to other cloud providers and we can perform database migration.
  • Databases Versions are not updated as they are updated in the industry.
If we have a need for a database then Amazon RDS is best in the market. We can start from small and then move to big data storage. If people are using an on premises database then also they can easily move to RDS.
November 29, 2021

RDS helped me a lot!

Score 10 out of 10
Vetted Review
Verified User
Review Source
I have used it for both PostgreSQL and MySQL databases. It was a way to host our database services when we were utilising the AWS services. So we had one for the staging-development environment and one for production. It was fast and functional so we were happy working with it. It is managed by AWS so we don't need to take care of updates. It's helpful to set a maintenance window. It has also snapshots that helps to keep our data safe.
  • Updates (patching).
  • Backups.
  • Scaling.
  • Handling Load and serving.
  • Performance Monitor should be better and show more metrics.
  • A super admin who can tune up some mysql innodb values.
  • Migration Tool.
I have used it for PostgreSQL and MySQL and it worked perfectly fine for both. They were different applications but there was no significant high load. Running a single instance was fine. I would like to run a cluster and see how will it be but have not tested it yet. So far I would recommend it for a single point of failure DB.
Score 10 out of 10
Vetted Review
Verified User
Review Source
I use AWS RDS for my application database in [the] Production, Test, and Dev environment. This service is very useful as it gives many [features] such as Scaling, administration, backup, availability[,] and many more. if you start using AWS RDS then no more database installation is required, it [provides] plug and play feature which lets you to use it with any application by just declaring DB credentials.
  • Scaling
  • Database management like admin process
  • Availability
  • Backup ease
  • Easy to install and use.
  • Allow to create more than 30 Databases on RDS instance[.]
  • Increasing maximum size of storage more than 4TB[.]
  • Does not support SQL server analysis, Integration, reporting, Data quality services.
Whether your organization is [an] early startup or large company AWS RDS fits in most of the cases such as 1. Easy to start, setup, used by [a] few or large developers team. 2. You can easily scale DB [instances] when your business required scaling as a startup or pay only for [users] to optimize cost as [a] large organization. 3. If your application requires SQL Server, Oracle, or Maria DB then you should use AWS RDS instance. 4. Your application requires better availability and security of data you can use AWS RDS instance. When AWS RDS is not recommended: 1. You need automatic scaling or capacity flexibility as request load gradually increases, better to use Amazon Aurora DB in this case.
Score 9 out of 10
Vetted Review
Verified User
Review Source
We mainly use AWS in our org and are transitioning everything to VPC. One of the use cases was to have an RDBMS that supports several databases such as MySQL, Postgres, and the likes. AMAZON RDS checked all the boxes and made it easier for us to manage everything on AWS.
  • Supports MySQL, PostgreSQL.
  • Useful if you want to leverage Aurora.
  • Highly scalable.
  • Supports dynamic scaling.
  • Scale down is a bit buggy.
Easy to create and configure. Front-end configuration makes it easier for non DBAs to maintain and manage databases on Amazon RDS. Well integrated with AWS' fine-grained and role-based security. Highly scalable and supports dynamic scaling which takes away the overhead of constantly monitoring databases for space/memory issues.
Sunny Hemnani | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
1. We are providing product management services and using RDS as a database for them 2. The benefit is that AWS manages the database instances, and we don't have to keep separate servers for them. 3. Helps us keep database backups and images of those schemas very efficiently. 4. The dashboard shows the running load & queries on the database.
  • Supports many types of databases like MySQL, PostgreSQL, Aurora, etc.
  • RDS console makes it very easy to maintain all the different instances of relational database services.
  • Provides performance insights for all the database instances.
  • Cost is very high as compared to other cloud service providers.
  • Snapshots are also very expensive to maintain.
When your application is hosted on the Amazon Web Services cloud & we need a managed database, Amazon RDS is the go-to solution for such a scenario. When there are budget restrictions, Amazon RDS is not cheap & difficult to scale at a low budget.
Score 9 out of 10
Vetted Review
Verified User
Review Source
We are using it to create database instances for dev and using Aurora for making our effort of managing database, backup with zero effect. It helps us to scale our application in all regions.
  • Scaling.
  • Give options to create backup.
  • Easy setup.
  • Different way to login securely from username/password to IAM.
  • Making AWS Aurora accessible from localhost.
Good for scaling your application in multiple regions, storage issue fix as with config it can grow, easy to set up from console or using AWS CLI.
Abdullah Khawer | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Review Source
Amazon Relational Database Service (RDS) is being used as the centralized database to store the data required by the application. AWS RDS is used as the main database. Automated backups, high availability, reader and writer, auto-scaling, all of these are being used in the Production environment to fully get the benefit of using this managed AWS service.
  • Backups.
  • Resource monitoring.
  • Auto-scaling.
  • Trigger AWS Lambda within AWS RDS database.
  • Serverless using Aurora.
  • Run SQL Queries from AWS Console on AWS RDS (Non Aurora) databases.
  • Ability to take SQL backups automatically instead of taking the whole snapshot.
  • Access and searching logs.
Amazon Relational Database Service (RDS) is well suited where you need a managed database. It is also good using Aurora when you want a serverless version that is a bit faster and more managed by AWS. It is a good choice of a database due to the different flavours available like MariaDB, MySQL, Oracle DB, etc. It is good when you want features like automatic backups, automatic upgrades, auto-scaling, high availability, etc. It is a good choice for the production environment. It is not a good choice for those databases where you need more access on the system level or looking for deep access to logs or for a database that is not available on AWS RDS like AS400, etc.
Score 9 out of 10
Vetted Review
Verified User
Review Source
It is used for hosting databases for a web application that has multiple environments and customers. The deployment for environments is automated and an appropriate RDS instance is created for each environment in the process. RDS is being used both by software developers in the development environment and by testers & support in others. RDS solves the problem of having a database solution in a scalable web application with a large user base.
  • Automation, database instances are created with scripts.
  • Low maintenance, no need for developers to worry about additional machines.
  • Many database options.
  • Versions of databases are limited.
  • Amazon drops support of older database versions, you are forced to upgrade even though your application wouldn't need it.
  • There is no actual machine you can connect to with SSH, only with database clients.
It is a very good solution for web applications. RDS is scalable and has supported many databases so it can provide a database solution regardless of how many users you expect for your application and you can choose which database to use based on your application's needs. Works well for all environments (QA, PROD, etc.) and deployment can be automated with scripts so it will cause work only once.
Rahul Chhajed | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We have been using Amazon RDS as our production database. Even with all our products we have been using RDS. RDS is a highly managed database and easy to setup other things like monitoring and auto scaling of database. A managed database reduces a lot of the headache of managing, maintaining, and other tasks related to database.
  • Setting up and managing a new RDS is just a matter of few clicks.
  • Maintaining different version of backup is just like a matter of turning on and off.
  • Automatic minor update of database.
  • Best restore:- You can even restore to 1 second before time.
  • RDS has everything that can be configured, but when you need efficient configuration we need little bit more knowledge about Dev Ops things.
  • Although restoration is available, when you need to do it it's pretty tricky. A new instance will be created and you will face some downtime.
  • Understanding which configuration and pricing would be suitable for startups as well [as] enterprise needs more reading and research.
RDS is well suited for faster deployments and when you don't have a dedicated Database Administrator to manage your database environment. With RDS it will be so easy to manage your production and development environment [with] a few clicks and a little bit of research. Both enterprise and startups can use RDS with a reasonable pricing plan. If you [are] already using some other cloud platform, then the migration is pretty simple to RDS also.
Score 10 out of 10
Vetted Review
Verified User
Review Source
As we have many customers in different countries we are creating one [Amazon Relational Database Service (RDS)] instance for each country and then splitting it by usage. Nowadays, all our data it's being created and stored in RDS and moved to Redshift afterward. The main purpose to have it on RDS is trustability and easy maintenance once we can connect from a client directly to our instance.
  • Scalable - If you need more space or more processing, it's really easy to choose another instance.
  • Reliable - One of the main benefit it's reliability once the availability it's close to 100%
  • Integration - Everything can be connected to RDS
  • Honestly, I think RDS enough for my all purposes.
If you want to store your data in the cloud you must check [Amazon Relational Database Service (RDS)] once it's perfect in terms of integration, it's really nice to store your live data (from web applications mainly), the performance is also cool and you can use many of the advantages like scalability, reliability, performance.
Michael Jenkins | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Amazon RDS is our default solution for running databases in the cloud. RDS provides the data layer for our web applications that require data persistence. RDS is widely used by application development teams throughout the company. RDS allows us to rapidly deploy databases, operate them in a manner that is generally hands off, and with extended features like Amazon Aurora, take advantage of capabilities like automatic backups, multi-AZ read replicas, and simple failovers.
  • For engineers with experience managing databases, setup is simple. And for the uninitiated, the RDS console interface becomes intuitive with some practice.
  • Not having the maintain the underlying infrastructure is a great benefit of using RDS. Patching and backups can be scheduled from the console and from then on are pretty much automated.
  • Right-sizing the DB instance to perform optimally with an application can be a very simple procedure. If a DB instance is not struggling to keep up, the instance size can be scaled up with just a few clicks.
  • Baseline configurations are generally sane for most RDS instances. This allows novice developers and engineers to get the most out of the service without being a complete database administrator.
  • Experienced DBAs may find RDS limiting in some areas. There is no direct access to the underlying servers so OS level tweaks may be out of bounds.
  • Getting logs from a database can be a challenge. Other services may need to be turned on (CloudWatch, for example) to get access logging, etc.
  • While rudimentary logging is included with RDS, users must pay a premium to get more in depth logs (in particular, fine grained logging in terms of events per minute). This is not a bad thing, since you get what you pay for, but some users find it annoying to have to pay extra for metrics with higher fidelity.
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.
  • Online training
  • in-person training
  • no training
Score 9 out of 10
Vetted Review
Verified User
Review Source
Amazon Relational Database Service (RDS) is being used by the entire organization (benefits), but managed, when needed, by the IT department. The main problem that it solved was management (backup, daily operations, scaling, etc.), plus the RDS benefits that are related to management (updates, maintenance windows, easier and faster setup to help the administrators).
  • Management
  • Security
  • Backup
  • Daily activities
  • Monitoring
  • Integration with active directory that is not AWS-managed
  • Sometimes you change something in configuration and don't know if the instance will reboot
  • Some stuff on the main version of the database is not available yet in RDS version
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.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Amazon [Relational Database Services (RDS)] is deployed as a primary datastore for a number of applications within our infrastructure. It allows us to offload the typical Database Server Maintenance/Configuration and even System Management to Amazon, which ultimately reduces the cost of our System Administration overhead. Amazon makes it very easy to customize the configuration for each RDS deployment with a number of database engines, as well as set up automatic fail over, automated backups, and the ability to resize your database deployment seamlessly, should your application requirements call for additional resources.
  • Removes the burden of host OS maintenance
  • Simple configuration and management
  • Automatic, easy to restore, backups
  • You don't have os-level or hardware-level access to the system, so all your performance tuning needs to be done within your application or within the parameters of the database engine that amazon allows you to customize.
  • Customizations/Extensions to the database engines are impossible, as you don't have OS-level access.
  • Migrating in/out of RDS with zero down time can be relatively challenging from a configuration and execution perspective, depending on your infrastructure.
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.
Score 8 out of 10
Vetted Review
Review Source
The project required many small instances across different regions and departments of our organization.
  • scalable
  • automated backups
  • managed services
  • additional price for managed services
  • not flexible pricing model based on storage and CPU
  • very basic monitoring metrics
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).
Diego Turcios Lara | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
Instead of having our database servers in house, we decided to use the cloud for managing the servers. Our costs have come down with this and it's so easy to spin up a new database instance. Besides this, as we use several AWS technology we can control it with other services such as CloudWatch or Lambda.
  • Easy to use.
  • Not expensive.
  • Flexible.
  • Parameter groups are sometimes confusing at the moment of editing.
  • Just supports certain amount of databases.
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.
Mike Narumiya | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Amazon Relational Database Service is used for spinning up test scenarios or alpha test of products. In addition, it's utilized for creating environments that may or may not be used in the long term. Excellent product for its flexibility, and lack of need for long term capital expenditures or commitments. Easy to utilize and purchase. It's a very friendly platform to use in agile environments, or in organizations that are in either an early startup mode, or rapid growth/expansion phase.
  • Ease of use.
  • Flexibility without excessive commitment.
  • Slightly pricier than some options.
  • Name brand of Amazon is good in some industries, less positive in others.
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.
Score 10 out of 10
Vetted Review
Verified User
Review Source
I have used the Amazon Relational Database Service on behalf of a customer that was creating a mobile game that had elements of e-commerce. We needed something that was scalable, easy to implement, only charged us for the resources that we used, and had excellent customer service as this was a new project for our agency. ARDS checked every box.
  • Database server monitoring.
  • Security.
  • Admin tools were confusing.
  • Trial and error based learning.
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.
Matthew King | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
RDS is being used in a ton of different ways, however it shines best for use in conjunction with Elasticsearch and providing the endpoint a writable position that we don't have to manage. Being multizone it allows for it to always be up and working; also since backups are automatic, it takes off that overhead of our engineering team.
  • Automatic backups
  • Multi-zone
  • Completely managed service
  • One thing I'd love to have is the ability to run actual SQL commands on it from the command line with typical SQL workbench type tools.
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.
Alok Patwal | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use AWS RDS to manage our MySQL and PostgreSQL databases without having to worry about issues like replication error, hardware failure or logs(general, slow, error) analysis. It is being used primarily by the database team but indirectly a lot of teams use RDS. Since RDS manages a lot of tasks for us, it frees us to focus on the business side of things.
  • Create snapshots on schedule or whenever required: RDS gives you the freedom to take manual snapshots at will or configure a backup policy wherein you can specify the time when the backup would be taken and the number of such automated backups to retain. You can restore a backup very easily whenever required with a few clicks.
  • Monitoring: RDS comes with a lot of metrics like CPU utilization, free storage, freeable memory and read/write latency that you can create alarms on to make sure you can quickly resolve an issue.
  • Failover: If you have a multi-AZ RDS set-up, failover is done automatically when the primary instance fails. This minimizes downtime
  • Point-in-time-restore: With RDS, you can sort of time travel, creating a new instance and restoring the database state to a point in time in the past.
  • Logs: The general, slow, error and audit logs can be published to CloudWatch for better analysis with a few clicks.
  • There should be a proper listing of all parameter groups alongside the instances that they are attached to. This would help to see which instances would be affected if a parameter group is changed.
  • RDS should allow SUPER privilege to the master user. A few advanced tasks(like getting a physical backup using MySQL Enterprise Backup) fail because SUPER privilege is not available for the master user.
  • A few parameters are not modifiable in the parameter groups and the access to the server filesystem is not given. This should not be the case because as an advanced user, you might want to understand things a little deeper.
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.
Score 10 out of 10
Vetted Review
Verified User
Review Source
Amazon Web Services Relational Database Service (RDS) is being used as our production data store running MySQL. We use it to store user information, click information, billing information. Additionally, we have a separate instance running PostgreSQL and storing some of our proprietary objects used to emit streams for our core business model.
  • Managed - RDS is entirely managed for us
  • Scalable - It is incredibly easy to scale an RDS instance
  • Support - AWS support is top-notch
  • Since RDS is managed, you are never truly a superuser, you just have admin privileges.
  • Lack of direct access to MySQL files and whatnot.
  • Downtime is scheduled on their schedule rather than yours.
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.
Erlon Sousa Pinheiro | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
At my current organization, we are using Amazon Relational Databases as our first option databases, supporting our DevOps environment. Currently, our monitoring system (based on Zabbix) and our configuration management system (based on Puppet) are using it as the main database. In our team, all databases are being based on AWS RDS PostgreSQL so far.
  • AWS products on average, excel at high availability. RDS is a good example of that.
  • Easy scaling. Just a few clicks.
  • Load balancing in a transparent way.
  • Sometimes you can't install specific items like modules.
  • You are not able to use different DB versions from those provided by AWS.
  • AWS keeps DB logs for a short time. If you have a problem and need to check something beyond the retention period, you can't.
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.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use AWS RDS service for multiple applications as a backend for MySQL Databases. It helped us in updating MySQL versions, backups, and snapshots. We don't have to spend time managing and maintaining infrastructure, and we spent the most time on business. We can choose or readjust capacity based on demands and also automatic backups stored on S3 bucket.
  • Automatic updates.
  • We can scale the resources.
  • 99% availability.
  • It needs some basic aws console experience to set up RDS.
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.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Amazon Relational Database Service is used to host databases accessed by web applications that are on servers hosted within AWS EC2. There is also a database hosted in RDS used by end-user desktop applications.
  • As with all AWS services, it is fast and easy to get set up.
  • It integrates well with the rest of your infrastructure hosted within AWS.
  • The point in time backup/restore options work well.
  • There are use cases where you have to delete and recreate your entire database instance just to change one thing.
  • SQL Server backup and restore to file is not a simple GUI-driven process.
  • Read replicas are not offered for Microsoft SQL databases.
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.