We recently held a web session “5 reasons to turn off your cloud servers when they’re not in use.” Even if you weren’t able to join us, you can check out the recording below – or use the annotations below to skip ahead to the section you’re interested in.
00:51 Overview of presentation
01:18 Reason #1 – Save Money
- Compute makes up the largest share of spend for most enterprise cloud users
- AWS Example:
- $10 billion/year in revenue
- 70% is EC2 ($7 billion)
- 52% is non-production which could be turned off at night ($3.5 billion)
- A simple 12-hour on/off schedule saves $1.75 billion in instance costs
03:00 Comparison of the major ways to save money in AWS
- 03:07 Reserved instances – pay upfront for a contract for 30-40% savings. Best for production environments.
- 04:06 Spot instances – open market on spare capacity. Savings are compelling (70-90%) but risk that your instance could go away if the price goes above your bid price.
- 04:37 Autoscaling groups – scale up and down groups of all types of instances according to your environment needs.
- 05:00 Turn instances off to save money when you’re not using them.
05:29 Reason #2 – Improve Security
- There is nothing more secure than a server that is OFF (This is what security people actually dream about)
- There is nothing easier to monitor than servers that are OFF (so long as your NOC folks are NOT surprised)
06:20 Reason #3 – Reduce Environmental Impact
- Data centers consume ~2% of all electricity globally (3% of U.S.), growing at 12% YoY.1
- 80% of power is provided by fossil fuels
- Avoiding the need for new data centers reduces carbon emissions
- It also makes good business sense:
- Cloud providers like AWS improve profitability and increase carbon credits when they can oversubscribe their infrastructure.
- They can’t oversubscribe if they are over-provisioned
- Therefore, turning servers off when not in use is one sure fire way help oversubscribe
08:31 Reason #4 – Because Werner Says So
- AWS CTO Werner Vogels recently addressed an audience of AWS users, saying, “You can turn off your resources when you go home. Typical cost savings are 75%.”
08:51 Reason #5 – Peace of Mind
- Knowing you’re saving money, improving security, helping the environment and obeying Werner will help you sleep better at night … who wouldn’t?
- The question is how?
- You manually turn things off when you leave. In Offices there are automated light switches. There’s a reason, right?
- You could create scripts to do this automatically – that is not a cost-effective
09:29 ParkMyCloud – built specifically to turn off your servers when you don’t need them
- WHAT: Simple, single- purpose SaaS tool.
- HOW: Automatically schedule on/off times for idle servers.
- WHY: Optimize cloud services spending.
- ROI: Save 60% or more; 6 week payback.
10:17 ParkMyCloud product demo
- 10:28 Dashboard overview – see all your instances in one place
- 11:19 Parking recommendations
- 12:15 Parking schedule interface – create your own schedules
- 13:51 Snooze parking schedules
- 15:24 Automated policy engine – create policies to automatically handle scheduling, team assignments
- 18:16 How did you connect to AWS and find your instances?
- 19:18 How do you figure that you can save 65% on instances that you turn off nights and weekends?
- 19:52 Can you compare turning instances off to Reserved Instances?
- 22:12 Do the energy savings you described for Amazon apply to other cloud providers?
- 24:05 Why Dale doesn’t like scripting on/off times
We welcome additional questions in the comments below, and hope to see you at our next web session!