Users of Amazon’s database service have been clamoring for a solution to shutting down RDS instances with an automatic schedule ever since 2009, when the PaaS service was first released. Once Amazon announced the ability to power off and on RDS instances earlier this year, AWS users started planning out ways to schedule these instances using scripts or home-grown tools. However, users of ParkMyCloud were happy to find out that support for RDS scheduling was immediately available in the platform. If you were planning on writing your own scripts for RDS parking, let’s take a look at some of the additional features that ParkMyCloud could provide for you.
Schedule EC2 and ASG in addition to RDS
Very few AWS users are utilizing RDS databases without simultaneously running EC2 instances as compute resources. This means that writing your own scheduling scripts for shutting down RDS instances would involve scheduling EC2 instances as well.
ParkMyCloud has support for parking EC2 resources, RDS databases, and Auto Scaling Groups all from the same interface, so it’s easy to apply on/off schedules to all of your cloud resources.
Logical Groups to tie instances together
Let’s say you have a QA environment with a couple of RDS databases and multiple EC2 instances running a specific version of your software. With custom scripts, you have to implement logic that will shut down and start up all of those instances together, and potentially in a specific order. ParkMyCloud allows users to create Logical Groups, which shows up as one logical entity in the interface but is scheduling multiple instances behind it. You can also set start or stop delays within the Logical Group to customize the order, so if databases need to be started first and stopped last, then you can set that level of granularity.
Govern user access to databases
If your AWS account includes RDS databases that relate to dev, QA, staging, production, test, and UAT, then you’ll want to allow different users to access different databases based on their role or current project. Implementing user governance in your own scripts can be a huge hassle, but ParkMyCloud makes it easy to split your user base into teams. Users can be part of multiple teams if necessary, but by default they will only see the RDS databases that are in the teams they have access to.
High visibility into all AWS accounts and regions
Scripting your own schedules can be a challenge with a single region or account, but once you’re using RDS databases from around the world or across AWS accounts, you’re in for a challenge. ParkMyCloud pulls all resources from all accounts and all AWS regions into one pane of glass, so it’s easy to apply schedules and keep an eye on all your RDS databases.
RDS DevOps automation
It can be a challenge to integrate your own custom scripts with your devops processes. With ParkMyCloud, you have multiple options for automation. With the Policy Engine, RDS instances can have schedules applied automatically based on tags, names, or locations. Also, the ParkMyCloud API makes it easy to override schedules and toggle instances from your Slack channels, CI/CD tools, load-testing apps, and any other automated processes that might need a database instance powered on for a brief time.
Shutting down RDS instances is a huge money-saver. Anyone who is looking to implement their own enterprise-grade AWS RDS start/stop scheduler is going to run into many challenges along the way. Luckily, ParkMyCloud is on top of things and has implemented RDS parking alongside the other robust feature set that you already used for cost savings. Sign up for a free trial today to supercharge your RDS database scheduling!