I’m a fan of automation – as a CEO, I think you should do everything possible to simplify your day-to-day, whether that means you overhaul your calendar system or automate tasks in AWS.
Amazon themselves is great at this. I’m sure you are well aware of Amazon’s quest for automation in their warehouses (robots) and distribution (drones) to reduce costs and deliver packages faster. (That’s a great goal, by the way – I am an Amazon Prime customer – love it.) If you’re interested in Amazon’s robots, check out this article from Business Insider. And as the use of drones to deliver product becomes reality, Amazon has created a service – check out Amazon Prime Air if you haven’t already.
So let’s look at another branch of Amazon – Amazon Web Services (AWS). AWS is a large distributor of cloud, which in and of itself is actually a utility that can be used on demand to provide compute, database, and storage services to small and large companies alike. It’s just like the way utility companies provide electricity, water and heat to homes and business. Over time, features and services have been built and sold to optimize these traditional utilities in order to simplify mundane tasks via automation and achieve ROI by saving more money than cost. Here are a few examples:
- Nest to detect, learn, and automate programmable thermostats to save on heating and cooling
- In-office motion sensors to detect movement to turn lights off/on
- Motion sensors on faucets and hand dryers to eliminate water and electric waste
- Gadgets on showers, toilets, etc. to reduce water consumption and waste
The point is, all of these utilities need to be optimized with 3rd party technologies to automate and reduce waste, and to optimize spend. At home, you’re the CFO (or maybe your spouse is 🙂) but you don’t want to spend more than you need to, and you will buy technology to automate mundane tasks and save yourself money if there is a tangible ROI.
Amazon is doing this with robots and drones – neither of which they built. So why not use 3rd party technology to automate for AWS, Azure, and Google Compute. Remember that the public cloud is a utility, and utilities have waste. In public cloud, what can we look at that’s mundane, that can be automated and where you can save dollars on cloud waste?
I have a simple one – automate tasks in AWS by turning servers off and on. Did you know that on average, 66% of what you spend on the public cloud is on compute (servers), and 45% of that is on non-production systems like development, test, and QA – servers that’s don’t need to run 7×24. That’s $6B in waste per year.
Even better than Nest, which you can install and set up in 30 minutes, ParkMyCloud can be setup and configured in 15 minutes or less. The next day, we will tell you how much you saved in the previous 24 hours by simply automating the mundane task of turning idles servers on/off with schedules.
There’s a reason Amazon is so successful – they automate mundane tasks in a simple, efficient way, follow their lead – automate today!
Dear Evan Spiegel, Bobby Murphy, and whoever manages Snap’s cloud infrastructure,
We have a proposition for you. We can save you $80 million on your cloud bills.
See, when you filed for IPO a few weeks back, one snippet of information that caught our eye was your use of public cloud – specifically your $400-million-annual four-year public cloud deal with Google Cloud Platform. We never doubted that your cloud infrastructure would be huge, see. After all, saw Netflix’s cloud spend rise to some $800 million a year in 2016 after they completed a near-total migration to AWS. These huge infrastructures are the most important to optimize – particularly as you grow.
As cloud waste reduction engineers here at ParkMyCloud, we are passionate about automating that optimization – and doing so quickly and simply. Obviously, in your case, you will continue to scale your infrastructure to deal with the exponential customer growth and daily peaks in usage (and by the way, my kids love Snapchat and I had to get an unlimited data plan – thanks!). Based on our analysis, we know that the largest item on public cloud customers’ monthly bills is compute instances/VMs (typically about 70% of a cloud bill). Research has shown that industry-wide, the amount of non-production in this infrastructure is about 44%. These non-production instances are the number one place to start hunting for optimization opportunities.
Your rate of innovation is certainly impressive and we see that you spent some $185MM last year on R&D. We would be willing to bet that although your teams are incredible, that in the haste to deliver better and better product, your cloud waste is likely enormous. Based on what we have seen in similar set-ups, we think we can save close to half this spend by simply automating the turning off of your cloud instances when not being used.
Here’s what we propose: you need to put parking schedules in place on your non-production instances. Snap, you need to ensure that your public cloud resources are only used when needed and turned off when not. Based on this alone we typically see our customers saving upwards of 65% off their compute spend. If you add additional optimization approaches that address industry rates of over-provisioning of compute instances (55%) and large scale inventory waste (15%) i.e. spend on resources that are no longer required savings grow even further, you will save even more on non-production (dev, test, QA etc.) workloads.
So when we see huge monthly spend numbers like yours, what gets us excited is thinking about how just how big your savings could be. And the truly wonderful thing with these type of savings is that everyone’s a winner – the DevOps team wins as they help the enterprise deliver more for less, the shareholders benefit from reduced Op-Ex and increased profits. (You probably don’t care, but your cloud providers will also benefit as they can better utilize their own datacenters.)
So Evan Spiegel, Bobby Murphy, and the rest of the team – shoot us a note. We are happy to talk whenever you are.
Jay Chapel & the ParkMyCloud Team
A recent report from 451 Research analyst William Fellows caught our eye – Now hiring: Cloud financial administrators. The report – which you can download here on our website – discusses a trending new role in enterprises as they seek to keep cloud costs in check.
Why would you need a cloud financial administrator?
The complexity of the cloud infrastructure space, plus the increasing costs in public cloud as enterprises grow, leaves many enterprises unprepared to manage the financial aspects of their cloud usage. IT, Operations, and Development managers and directors already have too much on their plates to add the entire responsibility category of managing cloud finances – and therefore, some are turning to creating a new role solely for this purpose.
Here at ParkMyCloud, we’ve had similar observations. Just take a look at our case studies to see stories of DevOps Engineers, Operations Engineers, and Directors of Infrastructure Services who were unprepared to take on the additional burden of cost optimization single-handedly. Or so they thought.
Is it worth the expense?
As mentioned in the report, the salary of any cost-savings hire should, of course, be lower than the amount that person saves the organization. If your enterprise’s cloud infrastructure is extensive enough to cover a CFA’s salary, it may seem like a cost-effective decision.
However, this can be done in a simpler and more cost-effective manner by introducing cost-optimization tools. The key is to ensure that they are simple to use, and won’t take much time for users to implement and maintain.
Our customers have found ParkMyCloud to fit this need. It takes just minutes to set up and provides savings in the hundreds of thousands and more.
So do you need a cloud financial administrator? Well, it’s up to you. But we don’t think so.
Since mid-2016, ParkMyCloud has served as a co-organizer with BlackSky for our local AWS user group. Each month, we gather 50-100 AWS users in the Northern Virginia and Washington DC area to learn, share technical knowledge, and have a good time.
There are tons of AWS meetups throughout the country and the world. If there’s one near you, we’d highly recommend checking it out. If there’s not, consider starting one up! Comment below or reach out through the meetup page if you want some pointers on how to do that.
Here are three reasons you should attend an AWS user group:
Different user groups and meetups will organize the “learning” portion in different ways. For our local group, we tend to have two to three different presentations on AWS technologies and use cases. For example, our recent talks have covered continuous compliance, backends for IoT modules, and various security topics. The great thing is that as a user group, anyone is eligible to present and share what they’ve learned in AWS – so you can contribute, too.
From these presentations and from talking with peers, not only will you get new ideas – you’ll find that some of the problems you thought you were facing alone are actually common challenges. Meeting up with other users gives you a chance to commiserate and to learn that these problems are solvable – some much needed encouragement!
Additionally, if AWS participates in your local user group, you have the opportunity to get insights into new or upcoming products and more.
Maybe you think “networking” is best left to the sales and marketing folks. I’d urge you to think twice. Every time our group meets, I see people making connections – about job openings and business opportunities, sure. But there’s also the joy of being able to talk shop with someone who understands – sharing tips, tricks, and cool stuff you’ve been doing. See the above note on commiseration, too.
Generally, a sponsor will provide food – and if you’re lucky, beer – for the event, in exchange for the opportunity to address the group. Who can say no to free food? (And don’t discount the sponsors from the “learning” portion either – they’ve identified the group as a good audience for a reason! )
By the way, for those based in or traveling through the DC area, we’d love to see you at our next AWS user group event! See the meetup page for attendee information, and information for speaking or sponsoring at the event.
If you read any cloud or tech blogs, you’ve probably seen the latest financials that show that Microsoft Azure is growing – and that it’s currently the fastest-growing cloud provider. However, this growth means an ever-increasing amount of wasted spend on Microsoft Azure resources.
Overall, Azure’s growth is exciting for customers who have bought into the Microsoft stack — more momentum means quickly evolving product lines, balanced prices, and improving cloud services.
However, dominant competitor Amazon Web Services (AWS) has had more time to feel and subsequently address growing pains. That means that AWS users have more options available to them to address certain concerns that come with using public cloud. For example, managing costs.
Managing Costs: a Major Concern Among Cloud Users
How much are Azure users worrying about managing their cloud costs? According to RightScale’s 2017 State of the Cloud report, managing costs is a huge, top-of-mind challenge. While it’s a top-3 concern for all cloud users, for mature cloud users, managing costs is the number one concern.
The primary goal of cost management efforts is to optimize costs – in other words, to eliminate wasted spend. Most cloud customers would agree that they have some amount of spend wasted, whether that’s from leaving resources on when not needed, oversized resources, orphaned storage volumes, etc. However, estimating the amount of wasted spend is a problem.
RightScale found that customers consistently underestimate how much they are wasting:
So when we’re looking at Microsoft Azure specifically – how much spend is wasted?
Wasted Spend on Microsoft Azure
We’ve talked about overall cloud waste before. So let’s apply those numbers to Azure specifically.
And that’s only a portion of the waste – it doesn’t even address oversized resources, orphaned volume storage, etc. Many of these problems are well-addressed in AWS, but the Azure support market is still catching up.
The good news is, this $0.9 billion portion of wasted spend is easy enough to solve. All Microsoft Azure users need to do is schedule the “lights to turn off” when they’re not home – in other words, schedule non-production resources to turn off when no one is using them. Try it now with ParkMyCloud!