While Amazon Web Services typically offers a pay-as-you-go approach for its products, the company’s Relational Database Service (RDS) has been an outlier. Unlike Elastic Compute Cloud (EC2) instances, which can be paused and relaunched as needed, the ability to directly stop and start RDS instances has never been available… until now.
In a blog post published earlier this month, AWS announced that its users can now stop and start RDS instances of MySQL, MariaDB, PostgreSQL, Oracle, and SQL Server. Since this new feature may result in significant savings for many businesses, the following article will take a closer look at what it entails. We’ll also discuss how CloudRanger can help automate your RDS instances, saving your business time and money in the process.
Why Your Company Should Stop And Start RDS Instances
For those unfamiliar with why this new feature is worth exploring, it comes down to money. If your company is running an RDS instance, it is being billed for the entire duration. That’s not exactly a problem if the instance in question is constantly being utilized. But what about instances that go through long periods of inactivity, such as those being used by developers in a non-production environment?
Previously, the only way to avoid being charged for an inactive instance was to delete it and later restore it from a snapshot when it was needed. But this workaround was far from efficient, and many businesses simply paid to run their RDS instances 24/7 even though they weren’t always in use. Luckily, now that AWS allows users to stop and start RDS instances, businesses will no longer have to pay for those periods of inactivity.
However, keep in mind that while you will no longer have to pay for unwanted database instance hours, you will still be on the hook for provisioned storage, manual snapshots, and automated backup storage. Also keep in mind that when you stop an instance, it will only remained paused for seven days before it is automatically restarted, at which time you will once again begin to accrue fees.
Stop And Start RDS Instances On An Automated Schedule
The cost-saving benefits of this new stop/start option are clear. But for businesses running multiple RDS instances, utilizing the feature could prove to be a tedious, time-consuming process. And while scheduling RDS instances in advance is now an option, users who are not IT infrastructure and DevOps professionals may have a hard time automating the process. Just as with EC2 scheduling, automating RDS instances requires a certain level of technical/scripting know-how, making it an unrealistic option for many would-be users.
Luckily, CloudRanger’s simple, intuitive interface allows users to easily stop and start RDS instances on a predetermined schedule, and without the need for scripting. This makes it possible for users without a high-level of technical know how to utilize the feature.
The newly-updated CloudRanger offers a simple AWS cloud management system for scheduling critical, repetitive tasks without the need for in-house coding. Our easy-to-use interface will help save your organization both time and money. Even IT professionals who are well-versed in scripting will benefit from CloudRanger’s simplified automation process, which will allow them to focus on more important matters.
Try CloudRanger For Free
Whether you are a small business, a medium business, or an enterprise user of Amazon Web Services, CloudRanger has features that will meet your specific needs. Our AWS cloud management system is easy to install, which means your business can be up and running with CloudRanger in no time. And best of all, you can even try CloudRanger for free for 14 days. So why not experience all the money-saving features and time-saving benefits CloudRanger has to offer?