Reducing Your AWS Spend by 40%: Best Practices Mark Lavi, Technology June 2016

Transcription

1 Reducing Your AWS Spend by 40%: Best Practices Mark Lavi, Technology June

2 Agenda 1. Growth in cloud spend 2. AWS cost control challenges 3. Controlling cloud costs 4. How much can you save? 5. Calm cost control on AWS 6. Summary and Q&A

3 Growth in cloud is real!

4 AWS Cost Control Challenges Lack of Visibility Transferring real-world budgets Application Architecture Issues

5 Lack of Visibility Teams provision resources by hand and never turn them off, never release associated resources (elastic IPs, volumes, keys, etc.) No meta data or naming convention enforcement: Ownership of resources is unknown Tracking and allocation of resources using spreadsheets Resource overview requires credentials to each cloud provider account

6 Transferring real-world budgets Tool fragmentation prevents global project, team, or department controls; people consume as much as they want. Management would like to predict and enforce cloud spend so that budgets can be planned by project, team, or department Multiple clouds and hybrid infrastructure prevent consistent charge back model

7 Transferring real-world controls How do we enable global notification and approval policies for any: Business property: team, budget, provider account, etc. Application life cycle event: deployment, maintenance, upgrade, restart, etc.

8 Application Architecture Issues Static capacity planning reflects a traditional approach to compute, storage, and network consumption Sizing resources for the high water mark results in most capacity remaining underutilized and represents waste You pay for your consumption and waste!

9 Application Architecture Issues Traditional architectures represent friction on engineering delivery: time to market for new features and time to fix problems are critical. Slow results cause customers to choose to go elsewhere! Despite elastic scale, resources can remain underutilized.

10 Controlling Cloud Costs Application Expiration Governance / Compliance Team Budgets Elastic Scale and Containerization

11 Application Expiration Restrict application deployments to teams Configure application deployments to expire Configure policies for team notification and approval Expiration can control unchecked deployments, encouraging evolution to ephemeral infrastructure, enforced by Calm Simply re-deploying each day and expiring 8 business hours later would equal 66% savings compared to perpetual deployments

12 Governance/Compliance Who did What, Where, and When? Streaming Logs Audit Trails 12

13 Team Budgets Teams, user roles, and budgets can govern deployments Show dashboard overview of a team's spend Budgets can control unchecked deployments Encourages evolution to managed and ephemeral deployments

14 Elastic Scaling & Containerization Dynamic, elastic capacity in the cloud can be sized based upon closing the loop via CPU use, external KPIs, etc. to scale up or scale down a population of application tiers Containers represent an infrastructure refinement from bare metal servers and VMs, allowing higher application density per host Containers enable architectural best practices: immutable infrastructure and microservices

15 How much money can you save? Team Budgeting Elastic Scaling Containerization Automatic Application Expiration

16 Team Budgets: Savings Budgets can control unchecked deployments, encouraging evolution to ephemeral infrastructure Set and forget per period example budget: can trigger a notification at 85% spend the team cannot exceed US$30K deployment costs 16

17 Elastic Scale: Savings Using a typical sinusoidal model for each local region: weekday vs. weekend cycle: 30% off is typical business hour versus off-business hours on weekdays: 50% off is typical We can achieve 40+% savings (resolution dependent)! ((50% * 5 days/week * 4 weeks * 2/3 day) +(70%* 2 days/week * 4 weeks)) / (30 days/month) = ( )/30 = 40.86% savings 17

18 Containerization: Savings Assuming a two-tiered application e.g.: web tier + business logic tier We can co-locate both application tiers on each container host. By scheduling both tiers per container host, we achieve 50% savings. 18

19 Application Expiration: Savings Expiration can control unchecked deployments, encouraging evolution to ephemeral infrastructure Simply re-deploying each day and expiring 8 business hours later would equal 66% savings compared to perpetual deployments Even more if we count weekends off! 19

20 Using Calm to Save on Cloud Governance and Compliance Results: fixed budget constraints Elasticity and Containerization Results: 40%+ and 50% savings Application Expiration Results: 66% savings

21 Calm Demo Role Based Access Control of a hybrid blueprint deployment (with containers and VMs) under a team budget using Calm!

22 Native AWS Cost Savings AWS provides many facilities which we did not cover: 1. Prepaid reserved and spot instances: requires planning and management 2. CloudTrails and CloudWatch for auditing and monitoring, SNS for notifications 3. Autoscale groups: requires AMI and deploy optimization All of our prior recommendations are cloud independent!

23 Summary Usage of Cloud is continuing to increase You can save up to 40% using cost-control solutions Save money before it is spent

24 Thank you, Questions? Get Calm: free 50 node license. Be Calm. Go Home Early. Slides: 24