Optimizing EC2 usage on AWS
-
Upload
cloudability -
Category
Software
-
view
323 -
download
0
Transcript of Optimizing EC2 usage on AWS
@cloudability
@cloudability
Optimizing EC2 Usage on AWS
May 17, 2016
๏ @cloudability
Introduction
Today’s Topics
Mike McCullough Technical Account Manager
TODAY’S SPEAKER
1. Wait, how does the cloud work again?
2. Finding and trimming the waste
3. Reducing hourly cost
4. Q&A
@cloudability
About Us
Cloud Cost Management
$2B+ in tracked AWS costs
@cloudability
Our SolutionsHow It Works
1 2 3
4 5
Spend Monitoring Spending visibility via custom dashboards, budget alerts, and daily email digests.
Cost Allocation Segment your cloud costs with detailed reports by tag, service, usage type, etc..
Usage Optimization Spot under-utilized resources w/ instance level usage metrics.
RI Portfolio Optimization Get recommendations to buy, modify and sell the right RIs. Then see their impact on your spending.
Company-Wide Governance Organizational group views/filtering/rollups, multi-user access.
0
45
90
135
180D
ev/T
est
POC
App
#1
App
#3
App
#2
Exec team starts really caring
Load
test
A Story of Growth
๏ @cloudability
The BasicsFinding Waste
๏ EC2 Instances run by the hour
๏ Different compute capabilities cost different amounts
๏ Misalignment in either /both can be very costly
๏ @cloudability
The PiecesFinding Waste
๏ Multiple major business units
๏ Lots of products or cost centers
๏ Dedicated and shared AWS resources
๏ Distributed teams using AWS
๏ @cloudability
Stage I: Cost visibility for all (emails, alerts, dashboards)
Stage II: Allocating costs to departments (tags, linked accounts)
Stage III: Using only what you need (underutilized, unneeded)
Stage IV: Lowering Cost Per Hour (new families, Reserved Instances)
Stage V: Tying spending to the bottom line (unit cost)
The Five Stages of Cloud EfficiencyCloudability
๏ @cloudability
Finding Waste
You’ve got a sense that you could be spending less …and you’re probably right.
๏ Not using what you’re paying for๏ Buying instances that are too large๏ Not turning off things at night๏ Paying more than you should
The Problem You’re Solving
@cloudability
Reducing Usage
Underutilized EC2 Hours
๏ @cloudability
168 hours in a week
๏ @cloudability
108 nights & weekends
@cloudability
Finding Waste
Widgets and Dashboards
@cloudability
Finding Waste
Utilization Analytics - Day of Week and Hourly
๏ @cloudability
How to turn off non-prod on nights/weekends
1. Confirm idle instance times2. Assign instance schedules with tags3. Run a crontab scheduler like “Valet”
- For more Google “Cloudability Valet”
@cloudability
Reducing Usage
Underutilized EC2 Instances
๏ @cloudability
Finding Waste
You’ve got a sense that you could be spending less …and you’re probably right.
๏ Not using what you’re paying for๏ Buying instances that are too large๏ Not turning off things at night๏ Paying more than you should
The Problem You’re Solving
@cloudability
Finding Waste
Utilization Analytics - Legacy Instance Usage
๏ @cloudability
Reducing Usage
Key metrics to look at:
๏ CPU Utilization๏ Bandwidth๏ Disk I/O๏ Days and Hours Running๏ Estimated Cost๏ Current State
Finding Underutilized EC2 Instances
๏ @cloudability
Finding Waste
You’ve got a sense that you could be spending less …and you’re probably right.
๏ Not using what you’re paying for๏ Buying instances that are too large๏ Not turning off things at night๏ Paying more than you should
The Problem You’re Solving
@cloudability
Reducing Rate
Reserved Instances
@cloudability
Reducing Rate
Reserved Instances
@cloudability
Reducing Rate
Reserved Instances
@cloudability
Reducing Rate
Reserved Instances
@cloudability
Reducing Rate
Reserved Instances
@cloudability
Reducing Rate
Reserved Instances - the Injected Line Item
๏ @cloudability
Finding Waste
You’ve got a sense that you could be spending less …and you’re probably right.
๏ Not using what you’re paying for๏ Buying instances that are too large๏ Not turning off things at night๏ Paying more than you should
The Problem You’re Solving
๏ @cloudability
Going Further
- Turn off instances that are not being used- Autoscale resources down when load decreases- Turn off dev/test/stage resources at night - Rightsize the instance size/type to the load- Migrate from old instance families to new ones (e.g., m1 to m3)
- Consider moving older S3 resources to Glacier- Employ a ‘stopinator’ or Janitor Monkey- Use Spot Instances for asynchronous workloads
Many ways to increase efficiency…
@cloudability
Thank you!Try Cloudability free
Learn more
Want a demo?
cloudability.com
blog.cloudability.com