BARCELONA. 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

Transcription

1 BARCELONA 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

2 Optimizing Cost and Efficiency on AWS Inigo Soto Practice Manager, AWS Professional Services 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

3 A Couple Assumptions 1. You re using AWS 2. You like it!!

4 But maybe you are spending more than you planned

5 Or you d just like to spend less

6 Cost Optimization Is Going From: To: Paying for what you use Paying for what you need

7 What should you do?

8 We ll Talk Through Some Frameworks Tools Best Practices

9 And Some examples from other customers like you

10 Cost Optimization Strategies: Policies and Processes

11 1. Limit Resource Provisioning

12 By Controlling Who Can Provision Resources

13 2. Understand What is Deployed and What it Costs

14 By Employing Tags Jane_Doe Key (Attribute): 127 Unicode characters Value (Detail/Description): 255 Unicode characters Tags per resource: 10 tags

15 And Using The Different Types of Tags Appropriately Resource Tags Provide the ability to organize and search within and across resources Filterable and Searchable Do not appear in Detail Billing Report Only available on certain services or limited to components within a service (e.g. S3 bucket but not objects) Cost Allocation Tags Provide the ability to map AWS charges to organizational attributes for accounting purposes Information presented in Detailed Billing Report and Cost Explorer (must be explicitly selected)

16 Tag Key Examples Cost Center Business Unit Dept./ Group Product / Application Owner Endpoint Support Contact Environ. Backup Tier Shutdown Time

17 Customer Example Large Financial Services No tags? No instance Customer

18 3. Proactively Monitor Your Account Billing Usage

19 By Using Detailed Billing Reports and Enabling Billing Alerts

20 And Configuring Simple

21 Or Advanced Alarms in CloudWatch

22 Alongside Cost Explorer

23 Or Using an AWS Partner Tool

24 Customer Example Kellogg CloudWatch helps our people make better decisions around the capacity they need, so that they can avoid waste We were never able to do that with our on-premises infrastructure. AWS breaks down usage and cost to such a granular level that we can identify which costs come from which department, like a toll model.

25 Best Practice: Manage How Resources are Provisioned and Monitored Only allow specific groups or teams to deploy (certain) AWS resources Create different environment (e.g. Dev/Test vs. Production) with different policies for each Require tags in order to instantiate resources Monitor and send alerts or shut down instances improperly tagged Use CloudWatch to send alerts when billing thresholds are met Analyze your spend using AWS or Partner tools

26 Cost Optimization Strategies: Architecture and Design

27 4. Design for Elasticity Rather Than Deploy for Peak

28 By Picking the Right Instance Type Instance Type vcpu Mem (GiB) Monthly Cost (OD)* Ideal use case m3.medium $48.24 Always available, balanced m4.large 2 8 $90.72 Latest generation, always available, balanced c4.large 2 8 $79.20 Always available, compute r3.large 2 15 $ Always available, memory g2.xlarge 8 15 $ Always available, GPU d2.xlarge $ Always available, storage t2.medium 2 4 $37.44 Bursty workloads * Assumes Amazon Linux Instances in US-East at 720 hours per month

29 And Determine if Bursting Works For You t2.medium 2vCPU, 4 GiB RAM Baseline performance: 40% (of a single core) Bursts beyond this based on CPU credits Less than $40 per month Use Cases: Web servers, dev, small databases Additional Details:

30 Customer Example Nomura Research For Nomura Research, the t2 instance provides enough performance for a development environment, remote desktop of evaluation environment requiring occasional CPU bursting

31 Customer Example Kaplan We quickly converted a hefty percentage of our systems to run under this EC2 Instance type, and have seen major cost reductions without affecting performance whatsoever. For all instances built for Kaplan moving forward, the T2 is going to be the preferred option unless measured or load-tested computing needs demand otherwise.

32 Using Autoscaling. Trigger autoscaling policy Automatic resizing of compute clusters based on demand Feature Control Integrated to Amazon CloudWatch Instance types Details Define minimum and maximum instance pool sizes and when scaling and cool down occurs. Use metrics gathered by CloudWatch to drive scaling. Run Auto Scaling for On-Demand and Spot Instances. AWS autoscaling create-autoscaling-group Auto Scaling-group-name MyGroup Launch-configuration-name MyConfig Min size 4 Max size 200 Availability Zones us-west-2c

33 And Adjusting for Utilization and Granularity More smaller instances vs. less larger instances 36 $0.252/hr $ / mo* 55 $0.126/hr $ / mo* *Assumes Linux instances in US-East at 30 days per month

34 Customer Example Large Aerospace Customer Challenge Workloads arrive asynchronously and require isolation Solution Use Amazon SQS and Autoscaling Groups to launch / terminate instances

35 5. Identify Idle Resources and Turn Off Unused Instances

36 Using Trusted Advisor

37 Or Amazon CloudWatch to Monitor, Collect and Track Metrics Amazon CloudWatch

38 Or (Again) Using an AWS Partner Tool

39 Customer Example Samsung We are using AWS Trusted Advisor to improve cost efficiency and to audit the configurations of service platforms

40 Best Practice: Match Your Usage and Capacity Start Choose an instance that best meets your basic requirements Start with memory & then choose closest virtual cores Tune Use CloudWatch and Trusted Advisor to assess Change instance size up or down based upon monitoring Expand Run multiple instances in multiple Availability Zones Use Autoscaling to scale in and out based on demand and usage (e.g. spikes) Look for peak IOPS storage requirements

41 6. Architect Your Workload with Cost in Mind

42 Select Reserved Instances for Steady State Workloads Commitment Level 1 Year 3 Year AWS Services Offering RIs Amazon EC2 Amazon RDS Amazon DynamoDB Amazon Redshift Amazon ElastiCache * Dependent on specific AWS Service, size/type and Region

43 Or Spot Instances for Non-Stateful (Time Insensitive or Fault Tolerant) Workloads Minimum Commitment Commit to 1 hour Tradeoff Potential for interruption * Compared to On Demand price based on specific EC2 instance type, region and availability zone

44 Or A Combination of All Three 1. Start by using RIs for known/steady-state workloads 2. Set-up multiple autoscaling groups 3. Autoscale first using Spot first 4. If Spot instances are unavailable (or priced too high), use On-Demand /Spot On Demand Spot Reserved Instance

45 And When You Have Excess RIs Use the Amazon EC2 Reserved Instance Marketplace

46 Customer Example Novartis Goal: Screen 10 million compounds against a common cancer target in < 1 week Set Up: 10,600 AWS Instances (39 drug design years in 9 hours) Result: 3 promising compounds Cost: $4,232

47 Leverage The Right Storage Classes On-premises Data Center Amazon S3 Infrequent Access Block File Archive Backup Disaster Recovery 99.9% (read) availability vs % Same durability Gateway Appliance/ AWS Storage Gateway Up to 60% savings Great for storing logs, backups Amazon Glacier AWS Cloud Same durability as S3 3 to 5 hours restore time Up to 75% savings Amazon EBS Amazon EFS (Preview) Amazon S3 Amazon Glacier Great for archiving, long-term backups and old data

48 Alongside AWS Managed or Application Services Amazon Relational Database Service (RDS) Amazon DynamoDB Elastic Load Balancing (ELB) Amazon Simple Queue Service (SQS) Amazon Simple Service (SES) Amazon Kinesis Amazon ElastiCache Amazon Redshift Amazon Route 53 Amazon Simple Notification Service (SNS) Amazon Lambda Amazon Elastic MapReduce (EMR)

49 To Offload Your Architecture + Standard Setup Optimized 4 x Medium Instances $193 AWS Data Transfer 1 TB $92 Total = $285 1 x Medium Instance $48 CloudFront Data 1 TB $87 CloudFront Requests (10M) $7.5 50% 6X Cheaper Faster Total = $142.5

50 Customer Example Infospace Chooses the right instance types (using Cloudwatch) Uses Reserved Instances (reduced monthly costs by 28%) Monitors and turns off unused instances (own tool Junkyard Dog) Offloads architecture by moving to Cloudfront Leverages App services: ELB, SNS, SES Uses Trusted Advisor Moves Data warehouse to Redshift

51 Cost Optimization Strategies: Technology Updates

52 7. Be Cognizant of Technology Lifecycle Updates

53 Including New Instance Types/Families (e.g. m4s) New Technologies (e.g. Amazon RDS for Aurora, AWS Service Catalog) New Prices

54 And Remember to Use Consolidated Billing Receive a single bill for all charges incurred across all linked accounts Share RI discounts Combine tiering benefits / Volume discounts View & manage linked accounts Add additional accounts

55 Best Practice: Pull all Levers Available When Architecting Your Solution Utilize On-Demand, Reserved and Spot Instances Use the Amazon EC2 RI Marketplace when you have excess Ris Use the appropriate storage class based on your requirements (not on what you use today) Use micro services where possible in your architecture Review your architecture when new services or technologies are announced Use consolidated billing to take advantage of tiered pricing

56 Cost Optimization Strategies Putting It All Together

57 Cost optimization framework recap Limit Resource Provisioning Understand What is Deployed and What it Costs Proactively Monitor Your Account Billing Usage Design for Elasticity Rather Than Deploy for Peak Identify Idle Resources and Turn Off Unused Instances Architect Your Workloads with Cost in Mind Be Cognizant of Technology Lifecycle Updates

58 BARCELONA