Amazon Relational Database Service (Amazon RDS) is a database-as-a-service (DBaaS) from Amazon Web Services.
N/A
Amazon S3
Score 8.7 out of 10
N/A
Amazon S3 is a cloud-based object storage service from Amazon Web Services. It's key features are storage management and monitoring, access management and security, data querying, and data transfer.
N/A
Pricing
Amazon Relational Database Service (RDS)
Amazon S3 (Simple Storage Service)
Editions & Modules
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)
Amazon RDS for Oracle
$0.482 ($0.964)
per hour, R5 Large (R5 Extra Large)
Amazon RDS for SQL Server
$1.02 ($1.52)
per hour, R5 Large (R5 Extra Large)
No answers on this topic
Offerings
Pricing Offerings
Amazon RDS
Amazon S3
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Relational Database Service (RDS)
Amazon S3 (Simple Storage Service)
Features
Amazon Relational Database Service (RDS)
Amazon S3 (Simple Storage Service)
Data Center Backup
Comparison of Data Center Backup features of Product A and Product B
Amazon Relational Database Service (RDS)
-
Ratings
Amazon S3 (Simple Storage Service)
9.0
Ratings
8% above category average
Universal recovery
00 Ratings
9.00 Ratings
Instant recovery
00 Ratings
7.90 Ratings
Recovery verification
00 Ratings
8.00 Ratings
Business application protection
00 Ratings
8.60 Ratings
Multiple backup destinations
00 Ratings
9.40 Ratings
Incremental backup identification
00 Ratings
9.30 Ratings
Backup to the cloud
00 Ratings
9.40 Ratings
Deduplication and file compression
00 Ratings
8.70 Ratings
Snapshots
00 Ratings
9.50 Ratings
Flexible deployment
00 Ratings
9.20 Ratings
Management dashboard
00 Ratings
8.10 Ratings
Platform support
00 Ratings
8.70 Ratings
Retention options
00 Ratings
10.00 Ratings
Encryption
00 Ratings
9.80 Ratings
Enterprise Backup
Comparison of Enterprise Backup features of Product A and Product B
If your application needs a relational data store and uses other AWS services, AWS RDS is a no-brainer. It offers all the traditional database features, makes it a snap to set up, creates cross-region replication, has advanced security, built-in monitoring, and much more at a very good price. You can also set up streaming to a data lake using various other AWS services on your RDS.
For archiving old data that is infrequently accessed it is perfect. You can choose to let it go into cold/glacier storage which saves even further costs but at the expense of accessibility. I like that you can set access rules to automatically move it to the next storage tier after a certain amount of time that it has not been accessed. I also use it a lot with PHP via the API. We have some custom in-house applications that have a fair amount of data uploaded into them. S3 has been a perfect solution to store these files, taking the load off web servers and never having issues with running out of storage.
Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch
Reliable and secure way to store objects in cloud: Storing any type of file(text, pdf, doc, csv, etc) is very easy with S3. Fetching this stored content as and when you require is also pretty easy and can be done using both the console and AWS CLI. Appropriate permissions can be set up for buckets using IAM roles/policies.
Versioning in buckets: S3 gives you a very handy feature to store multiple versions of objects stored in a bucket.
Lifecycle policies: You can set up lifecycle policies in S3 that can move your older objects to IA or Glacier. This setup is very easy and can be done within minutes for a bucket.
Replication: The cross-region replication that S3 provides is wonderful. Beware of the inter-regional data transfer costs though.
It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
There should be tools to analyze cost and minimize it according to the usage.
The biggest problem is to rename the bucket. There is no direct way to do it. One need to copy entire content to the different bucket with intended bucket name and then remove the old bucket. Sometimes it creates issues.
There is no direct way to upload .zip file and extract it to inside the bucket.
While uploading large files, sometimes you will find a drop of upload speed. I observe it so many times and while checking my internet speed, I find it absolutely perfect. So there must have something wrong on the AWS side.
We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.
I've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).
The UI could have some improvements (better filters) and there is a lack of some useful functionality, such as renaming an existing bucket: the latter is much needed in the context of rapidly evolving companies. Overall though, Amazon S3 (Simple Storage Service) is easy to use and to onboard people and tools to, thanks to its various APIs and flexibility.
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.
It depends on your tier within Amazon on how great of support you get. For us we have a dedicated Point of Contact that is great in taking in what we need and discussing it with the S3 team. The best thing is features we need or suggest have a good chance of landing on their roadmap.
Amazon Relational Database Service (RDS) stands out among similar products due to its seamless integration with other AWS services, automated backups, and multi-AZ deployments for high availability. Its support for various database engines, such as MySQL, PostgreSQL, and Oracle, provides flexibility. Additionally, RDS offers managed security features, including encryption and IAM integration, enhancing data protection. The pay-as-you-go pricing model makes it cost-effective. Overall, Amazon RDS excels in ease of use, scalability, and a comprehensive feature set, making it a top choice for organizations seeking a reliable and scalable managed relational database service in the cloud.
S3 is the most mature simple storage service on the web. It has direct competitors from Google and Azure, as well as a bunch of other competitors that focus on different aspects. For example, Backblaze specializes on file backups, and while s3 can also be used for that, Backblaze provides a better price point in exchange for more focused functionality. S3 really shines in that it performs simple things astonishingly well, while also being flexible enough to stretch itself to other situations (data lakes, file mounts, backup/restores systems, web hosting, etc.).
Allows us to store large amounts of raw traffic from data providers to allow us to view data our systems received at particular times, in order to reconstruct inputs in case of errors
Is capable of storing very large amounts of data cheaply without material impact to our business