Академический Документы
Профессиональный Документы
Культура Документы
Learn how to efficiently optimize your resource utilization and control your costs
NYC Cloud Computing Group
Aaron C. Newman CEO/Founder, CloudCheckr Aaron.Newman@CloudCheckr.com
Agenda:
Overview of Costs in AWS Going Reserved Going Spot Optimizing Resources Economic Denial of Sustainability Conclusion, Resource, and Questions
Co-location/ISPs as an alternative
Still buying your own equipment/building for peak capacity High margins were the norm
Cloud Costs
(Bytes of Data Transferred) * Price + (Size of Compute Resource) * (Price of Compute Resource) * (Number of Hours) + (Storage Used) * Price * (Time Stored) + (Transactions Processed) * Price
Architecting Applications
In the past, architecture was typically a large, multithreaded executable talking to a single database running on the biggest boxes you could afford. Sat idle a lot. Moving old apps into the cloud
Can you resize your resources different times of the day? Use load balancers or Multi AZ capabilities to resize
Important to design your apps to scale horizontally Design you application into components
That can be added or removed dynamically
Going Reserved
What is Reserved?
Pay up front, get a lower variable cost ROI as high as 500% over 3 years, 60% savings in cost Types of Reserved Resources Available
EC2 Instance RDS DB Instance Elasticache Node S3 Reserved Storage (for GovCloud) Utilization light, medium, heavy Commitments 1 or 3 year
Types
Heavy Reserved Instances even if you dont use it youre charge Match reserved instances carefully!
OS Type, Availability Zone, Size (VPC vs. Classic, Tenancy only matter for guaranteed availability) AWS tools do not show you if an instance is properly mapped
Consolidated Billing
Reserved Pricing is applied across AWS accounts AWS Tools do not show you how your reserved instances are applied
Going Spot
Spot is almost always cheaper But you need to consider < 99% availability
Spot prices spike frequently
Spot Pricing is typically 10-20% of On-Demand But can easily spike HIGHER than On-Demand
Spot Strategies
Most people dont understand spot pricing, afraid to use it
As more people understand and use it, pricing will be driven up
From GigaOm: A sudden spike in the price of m2.2xlarge servers (normally $.44/hour) drove the price briefly up to $999/hour, causing a site-wise outage. If you follow this strategy, use a variety of instance sizes, Availability Zones, and even regions to minimize the risk
Optimizing Resources
Overview
Keep track of what you are using
Find and eliminate idle instances Find and reduce under-utilized resources Unused EBS drives, ELB, multiple snapshots of same EBS drive
Horizontally scale
Find smallest instance type that can handle your transactions Find your bottle necks (network, disk I/O, CPU util, memory util)
But you need to compare Resource Type, Pricing Type (ondemand/spot/reserved), Region, AZ, etc for your circumstance
How much of your S3 storage can you convert to RRS? Glacier Pricing about 1 cent per gigabyte
Pricing difference from S3 decreases as the price goes up Takes up to 4 hours to retrieve files, and cost to retrieve
How much of your S3 storage can you convert to RRS? Glacier Pricing about 1 cent per gigabyte
Pricing difference from S3 decreases as the price goes up Takes up to 4 hours to retrieve files, and cost to retrieve
EDoS Attacks
Variation of Distributed Denial of Service Attack
Goal is not to overload and crash an application Instead to cause the server hosting costs to overwhelm the victims budget
the infrastructure allows scaling of service beyond the economic means of the vendor to pay their cloud-based service bills
-http://rationalsecurity.typepad.com
http://www.reviewmylife.co.uk/blog/2011/05/19/a mazon-cloudfront-and-s3-maximum-cost/
Use pre-paid credit cards or credit card with appropriate credit limit
Not sure if this limits your liability legally
Solutions?
Amazon limits/caps have been in the works since 2006
Each year Amazon talks about intention of releasing the feature
5 Strategies To Optimize
Keep a close handle on what you are running in the cloud Measure what you are spending Calculate Return On Investment Minimize what you dont need Protect yourself from EDoS
Still see some of the slower moving Corporate types claiming production work loads cant be run on the cloud
While their competitors leveraging the cloud eat their lunch
Resources
Further reading: How AWS Pricing Works
http://media.amazonwebservices.com/AWS_Pricing_Overview.pdf
Questions?
Questions on:
Cloud Computing Resource Utilization Optimizing Your Costs CloudCheckr