ParkMyCloud allows you to apply parking schedules (essentially on/off times) to compute instances that aren’t currently in use to save money. Great! So how do you figure out what you can park?
The past few months have been whirlwind of activity. On September 8, we launched ParkMyCloud. A few weeks later, the application debuted at AWS re:Invent and the reception went quite well.
When we talked with prospective customers at AWS re:Invent, they confirmed that there’s a need for the ability to schedule EC2 instance on/off times (or “park” those instances). In fact, several companies we spoke with have created their own homegrown scripting solutions for AWS EC2 instance parking to control AWS spend.
We had a lot of great conversations at the booth, where everyone seemed to immediately “get” ParkMyCloud and its value – the ability to schedule on/off times for EC2 instances to save time and money – almost instantly. We heard feedback like:
When last we left Bob – the wasteful and careless IT infrastructure guy who leaves his home AC blasting away while he’s at work, his car running all night, and the water on in the bathroom after he leaves – he was squandering thousands of dollars a month because there was no easy way to automatically turn off his non-production AWS instances when they’re not being used by his company’s developers and testers.
5 Things We Learned in our First 30 Days Providing Software as a Service (And, What’s Next for ParkMyCloud)
Well, here we are about 30 days after ParkMyCloud’s launch. I thought I would take a few moments to reflect on how it’s going and what we have learned in this month providing software as a service. As I type this, I am 38K feet above the ground on my way to AWS re:Invent, my 3rd year attending this event. It even sold out this year. In fact demand was great we even had random folks hitting us on firstname.lastname@example.org asking if we had extra tickets to sell, like a sold out music or sporting event – go figure, this AWS thing is pretty hot, eh?