Membro Do Conselho Consultivo at a computer software company with 5,001-10,000 employees
Real User
Top 10
Oct 27, 2025
I have used DB2. I also deal with databases, specifically with Amazon EC2. I have heard about Amazon AppStream and Amazon Kendra, but I have never used them. I used Amazon Transcribe just a little bit before. I used Amazon Transcribe only for experiments, only to learn about it. I used all the AWS AI tools only for learning matters. I learned about Amazon Transcribe because it was an AWS feature. I was trying to learn what kind of solutions AWS has about AI in general. Other than EC2, the only AWS products I have experience with are virtual machines, EC2, storage, S3, database, and Amazon RDS on Outposts, the basic use. In terms of use cases for Amazon RDS on Outposts, I use it for personal use, and I am a postgraduate teacher, and I recommend it to my students to use in their scholarship matters. They usually deal with web applications, some e-commerce, and basic registry applications, and they use Amazon RDS on Outposts as a storage database. The automated backups help a lot with my database management. Amazon RDS on Outposts positively impacted my organization by being very useful to migrate, freeing the technical team to think about other matters instead of focusing just on backups and provisioning the database. The team was freed up to do other things, which saved a lot of time for them. The initial setup of Amazon RDS on Outposts was very easy—almost straightforward. It was deployed in the cloud. I used AWS as the cloud provider for Amazon RDS on Outposts. The Amazon RDS on Outposts I used was located on AWS. It was not through the marketplace; it was the basic Amazon RDS on Outposts provided by AWS. I rate Amazon RDS on Outposts an eight out of ten.
Recommending the solution to other users depends on the use case, customer, and the customer's business profile. Suppose a customer is at a tipping point where their spend rate on IT is considerable, and they're in the cloud. I would ask them if they have any thoughts about going to on-prem because that can help reduce costs and make costs more consistent. The solution works very well with EC2, one of the main services that consumes RDS. It works well within the AWS system. I don't believe you specifically use Amazon RDS for others outside of AWS. Overall, I rate the solution ten out of ten.
Architect - Database Administration at Mitra Innovation
Real User
Top 5
Jun 6, 2024
I would say that the product is not integrated with any on-premises environment. For the use cases for which my company manages the product, I would say that the drawbacks I have seen in the solution are associated with SQL servers and Amazon RDS since, after a certain level of CPU utilization, the systems get unexpectedly impacted by it. Nowadays, my company is proactively monitoring setups and is allowed to make sure that the product doesn't reach a certain level of CPU utilization, which may cause the systems to suffer. There are four teams in my company that manage the product, and if its CPU utilization level reaches a certain threshold, we make sure that application usage is not kept at a minimal level insert scenarios. When my company used to use the on-premises version of the tool, we never encountered such issues. Even though there was some slowness, we did not encounter any issues with the company's product. In my company, when we were using Amazon RDS with SQL Server, it had a bit of an impact. The tool's partition features work seamlessly because I have been using the partitioning functionality. My company introduced the partitioning feature about three months ago for table partitioning, and I see that such features are working robustly on the on-premises version. Snapshot backups have become very easy for our company and it is a very good feature with which we can easily spin up additional databases we require. My company did not have a huge set of data to migrate, and so we did not have much of an issue with the migration process. My company is a service provider organization who does all the risk analysis. My company did not have any issues with whatever we tested and because of it, the migrations were okay. I would say Amazon RDS is a good solution and easy to implement since you don't need to spend a lot of time on it, as it is a very straightforward tool. The suggestion I would like to provide is that you need to script everything so that you don't fall into a lot of issues. Suppose you can script all the steps that you are doing. When it comes to the parameters, Amazon RDS gives users a set of Amazon's default parameters. If anybody is facing any issues, look at the default parameters, which you can always configure, and create a parameter group. I rate the tool an eight out of ten.
Amazon RDS on Outposts extends AWS cloud benefits to on-premises setups, offering seamless database management with low latency. It's tailored for users requiring consistent infrastructure technologies both on-premises and in the cloud. Designed to provide managed database services using the familiar AWS ecosystem, Amazon RDS on Outposts supports popular databases such as MySQL, PostgreSQL, and SQL Server. It delivers the same AWS APIs, functionalities, and tools for a unified experience....
I have used DB2. I also deal with databases, specifically with Amazon EC2. I have heard about Amazon AppStream and Amazon Kendra, but I have never used them. I used Amazon Transcribe just a little bit before. I used Amazon Transcribe only for experiments, only to learn about it. I used all the AWS AI tools only for learning matters. I learned about Amazon Transcribe because it was an AWS feature. I was trying to learn what kind of solutions AWS has about AI in general. Other than EC2, the only AWS products I have experience with are virtual machines, EC2, storage, S3, database, and Amazon RDS on Outposts, the basic use. In terms of use cases for Amazon RDS on Outposts, I use it for personal use, and I am a postgraduate teacher, and I recommend it to my students to use in their scholarship matters. They usually deal with web applications, some e-commerce, and basic registry applications, and they use Amazon RDS on Outposts as a storage database. The automated backups help a lot with my database management. Amazon RDS on Outposts positively impacted my organization by being very useful to migrate, freeing the technical team to think about other matters instead of focusing just on backups and provisioning the database. The team was freed up to do other things, which saved a lot of time for them. The initial setup of Amazon RDS on Outposts was very easy—almost straightforward. It was deployed in the cloud. I used AWS as the cloud provider for Amazon RDS on Outposts. The Amazon RDS on Outposts I used was located on AWS. It was not through the marketplace; it was the basic Amazon RDS on Outposts provided by AWS. I rate Amazon RDS on Outposts an eight out of ten.
Overall, I rate Amazon RDS eight out of ten.
The integration of the solution with our on-premises infrastructure is very simple. Overall, I rate the solution an eight out of ten.
Recommending the solution to other users depends on the use case, customer, and the customer's business profile. Suppose a customer is at a tipping point where their spend rate on IT is considerable, and they're in the cloud. I would ask them if they have any thoughts about going to on-prem because that can help reduce costs and make costs more consistent. The solution works very well with EC2, one of the main services that consumes RDS. It works well within the AWS system. I don't believe you specifically use Amazon RDS for others outside of AWS. Overall, I rate the solution ten out of ten.
I would say that the product is not integrated with any on-premises environment. For the use cases for which my company manages the product, I would say that the drawbacks I have seen in the solution are associated with SQL servers and Amazon RDS since, after a certain level of CPU utilization, the systems get unexpectedly impacted by it. Nowadays, my company is proactively monitoring setups and is allowed to make sure that the product doesn't reach a certain level of CPU utilization, which may cause the systems to suffer. There are four teams in my company that manage the product, and if its CPU utilization level reaches a certain threshold, we make sure that application usage is not kept at a minimal level insert scenarios. When my company used to use the on-premises version of the tool, we never encountered such issues. Even though there was some slowness, we did not encounter any issues with the company's product. In my company, when we were using Amazon RDS with SQL Server, it had a bit of an impact. The tool's partition features work seamlessly because I have been using the partitioning functionality. My company introduced the partitioning feature about three months ago for table partitioning, and I see that such features are working robustly on the on-premises version. Snapshot backups have become very easy for our company and it is a very good feature with which we can easily spin up additional databases we require. My company did not have a huge set of data to migrate, and so we did not have much of an issue with the migration process. My company is a service provider organization who does all the risk analysis. My company did not have any issues with whatever we tested and because of it, the migrations were okay. I would say Amazon RDS is a good solution and easy to implement since you don't need to spend a lot of time on it, as it is a very straightforward tool. The suggestion I would like to provide is that you need to script everything so that you don't fall into a lot of issues. Suppose you can script all the steps that you are doing. When it comes to the parameters, Amazon RDS gives users a set of Amazon's default parameters. If anybody is facing any issues, look at the default parameters, which you can always configure, and create a parameter group. I rate the tool an eight out of ten.