Performing a perfect Start or Stop RDS Instances is an art. If you’re a CFO trying to control costs or a DevOps personnel working on optimizing resource allocation, you know that DB instances are billed. And the billing is incurred for just running the DB instances, irrespective of whether there is any activity on the server or not. When you are in a development/ non-production environment, every penny saved goes a long way. Isn’t it?
Unlike EC2 instances and EBS volumes in an AWS cloud environment, DB instances are always cumbersome to reign in. Moreover, the EC2 instances and EBS volumes were long taken care off but DB instances were not.
Did you ever wish you could control usage of your relational database on your cloud? Did you ever wish to Start or Stop RDS Instances at your will? Or did you ever wish to save the RDS operational costs accrued during weekdays when the office lights go off or on weekends?
Your wish is our command!
With years of expertise in AWS cloud, we understand that you always wished for a magical tool that could take care of these DB instances like a pro.
Our Botmetric, a noteworthy SaaS-based cloud management suite, has made it possible with one of its newest features on its Cloud Automation module. This new feature — a market debutant — allows you to stop an RDS DB at your desired time and start it at your prescribed schedule. This capability, which is not available on AWS, is currently applicable to DB start/stop. However, it is applicable to EC2-VPC platform for non-production environments.
Benefits of Pre-Defining Start or Stop RDS Instances: Savings, and more Savings
Pay for only what you use: The easy-to-schedule start or stop feature will help you pay for just the cost accrued per hour and only for the running RDS instances. More than that, you will have the capability to use your DB instance only for working hours, thus saving you as much as 60% of cost (60 vs. 168 hours).
The cost you incur is minimal: Cost accrued from creating intermediate snapshots as well as the cost of data transfer, to and from AWS S3 for restoring the RDS, will be minimal
Start or Stop RDS Instances on Botmetric: It’s as easy as 1-2-3
Botmetric lets you schedule the time of start and stop customized by local time zones and the size of cron jobs. Refer the image below.
To initiate the scheduling of RDS instances on Botmetric, you will need to key in just a few pivotal information.
- Define AWS Region: Specify the AWS region RDS instances currently residing under Enter Job Attributes
- Define Time Zones: Specify the preferred time zones and eliminate the struggle with UTC time conversions for your AWS regions — a glitch that you have to deal with if you use the AWS console to do your tasks
- Define Schedule Time: Specify detailed scheduled details in Enter Job Schedules, as per your desire. Under the scheduling section, you have the freedom to schedule the start and stop instances at your will. No fuss. No fiddling. Hit the go button and your job is ready to deploy at the scheduled time
P.S.: Botmetric recommends you to take database size into account before setting up your DB instances when creating the CRON job. Here’s why: The time to restore your DB instance is dependent on the size of the DB.
Botmetric not only brings agility in managing RDS instances but also helps in trimming the RDS operational cost for unused instances. Stay on top of the things. Take a 14-day trial of our Botmetric to explore this new feature and expedite RDS operations in a split second.
Botmetric, listed on AWS Marketplace, can run rigorous Cloud Audits, provide the best cost optimization opportunities, and automate cloud tasks. Together, these features complement your Amazon Cloud infrastructure and facilitate you to be ahead of the game with AWS investment.
Latest posts by Tarun G (see all)
- Save more in Elasticache RI with Botmetric - August 7, 2017
- Ultimate Comparison of AWS EC2 T2.Large Vs. M4.Large for Media Industry - May 30, 2017
- Embrace Continuous Security and Ensure CIS Compliance for Your AWS, Always - May 9, 2017