Cost optimization - Don't overspend on AWS
•Download as PPTX, PDF•
6 likes•2,384 views
Levers and best practices for cost optimization when running applications on the AWS cloud.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cost optimization - Don't overspend on AWS
Similar to Cost optimization - Don't overspend on AWS (20)
Recently uploaded
Recently uploaded (20)
Cost optimization - Don't overspend on AWS
- 1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Sandeep Cashyap, Head Business Development, Bangalore AWS Startup Day Cost Optimization: Don’t Overspend
- 2. AWS Global Infrastructure 16 Regions – 44 Availability Zones – 90 Edge Locations Region & Number of Availability Zones AWS GovCloud (2) EU Ireland (3) US West Frankfurt (2) Oregon (3) London (2) Northern California (3) Asia Pacific US East Singapore (2) N. Virginia (5), Ohio (3) Sydney (3), Tokyo (3), Seoul (2), Mumbai (2) Canada Central (2) China Beijing (2) South America São Paulo (3) Announced Regions Paris, China, Sweden,Bahrain, Hong Kong US Govcloud(US-East)
- 3. Account Support Support Managed Services Professional Services Partner Ecosystem Training & Certification Solution Architects Account Management Security & PricingReport s Technical Acct. Mgmt Marketplace Business Applications DevOps Tools Business Intelligence Security Networking Database & Storage SaaS Subscription s Operating Systems Mobile Build, Test, Monitor Apps Push NotificationsBuild, Deploy, Manage APIsDevice Testing Identity Enterprise Application s Document Sharing Email & Calendaring Hosted Desktops Application Streaming Backup Game Developme nt 3D Game Engine Multi-player Backends Mgmt. Tools Monitoring Auditing Service Catalog Server Mgmt Configuratio n Tracking Optimization Resource Templates Automation Analytics Query Large Data Sets Elasticsearch Business Analytics Hadoop/Spar k Real-time Data Streaming Orchestratio n Workflows Managed Search Managed ETL Artificial Intelligence Voice & Text Chatbots Machine Learning Text-to- Speech Image Analysis IoT Rules Engine Local Compute Sync Device Shadows Device Gateway Registry Hybrid Devices & Edge Systems Data Integration Integrated Networking Resource Managemen t VMware on AWS Identity Federation Migration Application Discovery Application Migration Database Migration Server Migration Data Migration Infrastructure Regions Availability Zones Points of Presence Compute Containers Event-driven Computing Virtual Machines Simple Servers Auto Scaling Batch Web Applications Storage Object Storage Archive Block Storage Managed File Storage Exabyte- scale Data Transport Database MariaDB Data Warehousin g NoSQLAurora MySQL Oracle SQL ServerPostgreSQL Application Services Transcoding Step Functions Messaging Security Certificate Managemen t Web App. Firewall Identity & Access Key Storage & Mgmt DDoS Protection Application Analysis Active Directory Dev Tools Private Git Repositories Continuous Delivery Build, Test, and Debug Deployment Networking Isolated Resources Dedicated Connections Load Balancing Scalable DNS Global CDN The AWS Platform
- 4. What sets AWS apart? Building and managing cloud since 2006 90+ services to support any cloud workload; rapid customer driven releases 16 regions, 44 availability zones, 90 edge locations Thousands of partners; 3,800+ Marketplace products Experience: 1M+ customers Service Breadth & Depth; pace of innovation Global Footprint Ecosystem Fine-grained controlSecurity Fully integrated in AWSArtificial Intelligence Gartner Magic quadrant recognizing AWS for 7th year Enterprise leader
- 5. Introduction to Cloud Economics
- 6. Different sides of Cloud Economics Cloud Economics TCO & Business Value Cost Optimization
- 7. Continually lowering prices for customers is in our DNA – 62 Done Till Date Reduced Prices More Customers More AWS Usage More Infrastructure Economies of Scale Lower Infrastructure Costs Ecosystem Global Footprint New Features New Services Infrastructure Innovation We pass the savings along to our customers in the form of low prices and continuous reductions
- 9. With the AWS cloud, you only pay for what you use.
- 10. So you’re feeling pretty good.
- 11. Until your CFO shows up with the bill
- 12. Cost optimization is… going from… to… pay for what you provision pay for what you need
- 13. Where can you optimise? Technical perspective
- 14. “Harder”Easier Rightsizing before migration Rightsizing after migration Instance on-off to meet dev- test-staging work hours Reserved Instances Spot instances Match usage to storage class You can optimise in many areas … Instance scaling to meet external demand Architecting for cost after migration Deleting unused resources Containers to maximize utilisation Consolidated billing Automation and time saving via Cloud Formation Planning/ Architecting for cost before migration
- 15. “Harder”Easier Rightsizing before migration Instance on-off to meet dev- test-staging work hours Spot instances Match usage to storage class So how much do these activities save? Instance scaling to meet external demand Architecting for cost after migration Deleting unused resources Containers to maximize utilisation Consolidate billing Planning/ Architecting for cost before migration ~7% 50% + 100 % ~40 % 80% + ~70 % ~80 % ~80 % 80% + ~50 % Rightsizing after migration Reserved Instances Automation and time saving via Cloud Formation ~35 % ?% 50% +
- 16. The Five Pillars of Cost Optimization Right-Sizing Your Instances Pick the Right Pricing Model Increase Elasticity Measuring & Monitoring Match usage to storage class
- 17. Pillar 1: Right-Sizing Right-sizing • Selecting the cheapest instance available while meeting performance requirements • Looking at CPU, RAM, storage, and network utilization to identify potential instances that can be downsized • Leveraging Amazon CloudWatch metrics and setting up custom RAM metrics Rule of thumb: Right size, then reserve. (But if you need to save fast, you can still reserve first)
- 18. Pillar 2: Increase Elasticity Turn off non-production instances • Look for dev/test, nonproduction instances that are running always-on and turn them off. • Lambda + CloudWatch = Automated Scheduling* Autoscale production • Use Auto Scaling to scale up and down based on demand and usage (for example, demand spikes). * https://aws.amazon.com/premiumsupport/knowledge-center/start-stop-lambda-cloudwatch/
- 19. Released 1st June 2017: Amazon RDS start-stop • For MySQL, MariaDB, PostgreSQL, Oracle and SQL Server • While your database instance is stopped, you are charged for provisioned storage, manual snapshots and automated backup storage, but not for database instance hours. • Can stop for 7 days at a time • Available to database instances running in a Single-AZ deployment which are not part of a Read Replica (both source and replica) configuration • See Amazon RDS Pricing for regional availability.
- 20. Tagging is crucial to elasticity and rightsizing bit.ly/co17_tag
- 21. Cost Explorer
- 22. Pillar 3: Leveraging the Right Pricing Model Reserved Instances Spot Instances On-Demand
- 23. On-Demand Pay for compute capacity by the hour with no long-term commitments For spiky workloads, or to define needs Reserved Make a 1 or 3 Year Commitment and receive a significant discount over on- demand For committed or baseline utilization Spot Bid for unused capacity, charged at a Spot Price which fluctuates based on supply and demand For fault tolerant, time- insensitive or transient workloads EC2 Purchasing Options
- 24. Reserved Instances for Always-On Workloads Commitment level 1 year 3 year AWS services offering RIs Amazon EC2 Amazon RDS Amazon Redshift Amazon ElastiCache Amazon DynamoDB (not quite RI) Amazon CloudFront (not quite RI)
- 25. Payback on RIs is pretty good * Customers only committing for payback period as it’s like a “free” instance after payback period compared to on-demand • 1 year (approx. 7-8 months payback) • 3 year (approx. 12-18 months payback)
- 26. Reserved Instance Payment Options The No Upfront option provides a discount compared to On-Demand (up to 55% off) and does not require an upfront payment. • Low hourly rate for the RI for every hour in the term regardless of usage The Partial Upfront option balances the payments of an RI between upfront and hourly and provides a higher discount (up to 76%) compared to the No Upfront option. • Lower hourly rate for every hour in the term regardless of usage With the All Upfront option you benefit from the highest discount compared to On- Demand (up to 77% off) • Full upfront payment with no additional usage fees for the hours used via the RI during the term
- 27. Understanding the different RI types 1 year 3 years Standard Regional (with Size Flex) Regional (with Size Flex) AZ-Specific (with capacity reservation) AZ-Specific (with capacity reservation) Convertible Regional (with Size Flex) AZ-Specific (with capacity reservation) Note: can easily switch between Regional and AZ-Specific at no cost Shaded items affect pricing
- 28. Standard Reserved Instances • A Standard RI offers you the most amount of discount when you commit to a 1 year or 3 year term • 3 Year RIs offer a higher discount as compared to a 1 Year RI • You can purchase a Standard RI by specifying the instance type (e.g. m4.xlarge), OS (e.g. Windows), Tenancy (e.g. Default) and AZ (optional) • Instance size flexibility (large, small etc) within a family (M4)
- 29. Convertible Reserved Instances With a Convertible RI, you can modify your existing reservation across: Instance families Instance sizes Operating Systems Tenancy
- 30. Understanding Convertible Reserved Instances You are committing to: 3 years (no change on conversion) Region EC2 on AWS Spend (convert to equal or greater $)
- 31. Impact of May 2017 Reserved Instance Price Drop As AWS scales, we share the savings with our customers. Since 2006 we have dropped our prices over 62 times.
- 32. No-upfront discount is now much closer to partial upfront discount New! Available for newer instances m4.large, Linux/Unix, Singapore, Shared
- 33. Instance Size flexibility now launched for RDS
- 34. • Build it into your auto scaling groups • Batch • Transcoding • EMR • and more… Can be used for production * Compared to On Demand price based on specific EC2 instance type, region, and Availability Zone Spot provides incredible savings for the right workloads (stateless applications)
- 35. Spot price vs On-Demand 72% saving from a few lines of code
- 36. Strike a Balance Finding balance between pricing options Reserved Instances On Demand Spot
- 37. Pillar 4: Leveraging the Right Storage Class Block Storage Object Storage
- 38. Use appropriately sized EBS, Modify if needed with zero downtime Note: decreasing volume size is possible, but requires a different process
- 39. Object Storage Classes on Amazon S3 Active data Archive dataInfrequently accessed data Standard Hot Standard - Infrequent Access Warm Amazon Glacier Cold
- 40. Running the Numbers: S3 or S3-IA Comparing 1 PB of object storage* 1PB Monthly S3 S3-IA Savings % $24,117 $14,116 41% Rule of thumb: Breakeven = 105% Retrieved per Month Content Accessed per Month 10% $24,117 $18,350 24%50%1PB Monthly $24,117 $23,593 2%100%1PB Monthly * Based on US-East Prices
- 41. Mechanisms for self-sustained optimisation Management Perspective Pillar 5: Measuring and Monitoring
- 42. “Good intentions never work, you need good mechanisms to make anything happen” – Jeff Bezos What do we mean by mechanisms?
- 43. Setup Mechanisms for Optimisation $ Leadership Support Cloud Center of Excellence Reporting & Tooling Measures and Targets of Success Tagging & Enforcement of Tagging Stakeholders from the Business Ongoing Education Governance and Controls
- 44. Control who can provision resources
- 45. AWS Organizations allows definition of policies by Organisational Unit https://aws.amazon.com/organizations/
- 46. Measures and Targets of Optimisation: Guiding metrics • % instances turned off daily • % of instances rightsized • % always-on resources covered by RIs • % RI utilization • % Spot usage • % of resources tagged These help you know you’re headlining in the right direction
- 47. AWS Cost Explorer is an excellent starting point
- 48. Cost Explorer – Track your RI Utilization
- 49. AWS Budgets Update – Track Cloud Costs and Usage You can create up to 20,000 budgets per payer account You get notified if the budget criteria you set are reached
- 50. AWS Trusted Advisor can point you towards inefficiencies
- 51. AWS Cost and Usage Report (CUR) > Redshift / Athena > Quicksight can implement custom reporting logic Cost and Usage Report in S3 Redshift or Athena + SQL https://aws.amazon.com/blogs/aws/new-upload- aws-cost-usage-reports-to-redshift-and-quicksight/ Quicksight
- 52. Governance and Controls • What’s your cost review process? • How do you control visibility based on organizational unit and level? • What happens when costs increase unexpectedly? • Who gets to switch on resources? • What happens to resources that are not tagged? • What happens when a business unit nears or exceeds budget? re:Invent 2015 (ISM309) Efficient Innovation: High-Velocity Cost Management at Netflix https://bit.ly/co17_video4
- 53. Partners can help you accelerate your initial Reporting & Tooling maturity
- 54. Cost Optimisation Video Resources (found on YouTube) • re:Invent 2015 | (ISM402) Cost Optimisation at Scale https://bit.ly/co17_video1 • re:Invent 2016 | (ARC310) Cost Optimising Your Architecture: Practical Design Steps For Savings https://bit.ly/co17_video2 • re:Invent 2014 | (ARC201) Cloud-Native Cost Optimisation https://bit.ly/co17_video3 • AWS Summit Series 2016 | Chicago - Cost Optimization at Scale https://bit.ly/co17_video5
- 55. Next Steps 1. Enforce Tagging 2. Check Trusted Advisor Reports 3. Enabling CUR,DBR and cloud watch metrics 4. Working closely with Amazon team 5. Education – Training and well architected framework 6. Keep saving cost
- 56. Thank you!
- 57. Q&A
Editor's Notes
- AWS serves hundreds of thousands of customers in more than 190 countries. Amazon CloudFront and Amazon Route 53 services are offered at AWS Edge Locations
- AWS has developed the broadest collection of services (more than 90) available from any cloud provider. Foundation services across compute, storage, security, and networking offer customers flexibility in their architecture. We have a full spectrum of options to meet most price-to-performance scenarios. We offer the capability for both managed and unmanaged database options. The offerings for Analytics and Application Services enable advanced data processing and workloads. Our management tools offer a lot of insight and flexibility to let you manage your AWS resources through either our tools or the management tools you’re already familiar with. Recent expansion into enterprise applications has been entirely driven by customer feedback on where they’d like us to deliver value.
- TALKING POINTS Customers have selected AWS for years because we have proven ourselves committed to customer success. We believe we stand apart in the market because of seven factors: Security, Service Breadth and Depth, Experience, Global Footprint, Artificial Intelligence , Partner Ecosystem and Enterprise Leadership recognized by Gartner
- TCO Business value Cost optimisation
- We’re operating in a new IT consumption model, where IT can be consumed on demand. With this utility pricing model, everyone pays for what is used. It’s like your water bill. If your faucet is running… you’re paying your water bill at the end of the month based on what you used. But what happens if you leave that faucet running? Or have a teenager that likes long showers? Or have a leaky pipe? Cost optimization is about focusing on what is needed and identifying ways that we can turn the corner between “usage” and “need” to ensure we’re as lean and efficient as possible
- Now Lets have a look at where you can optimise from a technical hands-on perspective
- There are many ways in which you can save on AWS. Firstly there are some easier options to save such as: [Click] Consolidated billing – which is linking your accounts to a single payer account to help trigger volume discounts and maximize Reserved instances benefits Rightsizing before migration or stating your instances – it’s easy to Deleting unused resources – the equivalent of finding a $50 dollar bill on the ground and picking it up (tagging helps significantly with this) And Matching usage to storage class – S3 now has S3 analytics which identifies by bucket and tag, what is not used frequently and policies can be applied to automatically move files to infrequent access, which costs less. Slightly more complex ways include: [Click] Planning/ Architecting for cost before migration – here mature customers will design using Serverless services first, then consider containerization if that’s not possible, and then finally EC2 as a last resourt Turning instances off outside of working hours – typically 70% time in a week is non-working time. Many dev, test, staging applications can be turned off. Tagging enables this which we will cover later today. And using reserved instances – reserved instances provide discount for commitment, and are commonly used for EC2. However they also exist for RDS, Redshift, Elasticache and DynamoDB which many customers run 24-7 always on. And finally some more harder ways to save [Click] Spot instances – I’ve seen companies operate 70% of their production workload in Spot with architecture that performs as well as on-demand Scaling instances to meet external demand – websites are a perfect example of this where in busy seasons you want to ramp up and ramp down and not pay for those resources in quiet periods Rightsizing after migration saves significant cost and is supported by tooling mentioned later in this talk, Architecting for cost after migration, or breaking apart monolith applications into micro-services or taking a SaaS approach to applications where you only pay for what you use. Using containerization to maximize utilization (or squeezing more into less) And the immensely powerful CloudFormation allowing hardware to be automated, resulting in immense cost savings from a staff-time perspective. For example, Bristol Myers Squibb developed Automation using CloudFormation scripts to spin up entire secure medical analysis environments, saving 98% computation time relative to on-premise, saving analyst staff time, at a low cost, in a repeatable fashion With all of this, what is considered difficult melts away with the appropriate training, knowledge, and tools.
- So how much do these activities save? [Click] Short answer? a lot! For example, architecting for cost and using pay for use services like Lambda or DynamoDB can easily save over 80% of your application cost. Deleting unused resources such as idle EC2, instantly saves 100% of the resource cost I’ve seen customers with thousands of dollars of incomplete S3 transfers sitting there, unused ELBs, and years worth of backup volumes that are not needed.
- We see infra for Dev and Test team single timezone Really easy turn off when bed Easier still if non prod separate account In a moment we’ll look at tools large customers use
- Amazon RDS for MySQL, MariaDB, PostgreSQL, Oracle and SQL Server now allows you to easily stop and start your database instances. This makes it easy and affordable to use databases for development and test purposes, where the database is not required to be running all of the time. Stopping and starting a database instance requires just a few clicks in the AWS Management Console, or a single call using the AWS API or AWS Command Line Interface, and takes just a few minutes. While your database instance is stopped, you are charged for provisioned storage, manual snapshots and automated backup storage within your specified retention window, but not for database instance hours. While a database instance is stopped, Amazon RDS does not delete any of your automatic backups or transaction logs. This means you can do a point-in-time restore to any point within your specified automated backup retention window, even after an instance is started. Starting an instance restores it to the same configuration as it had when stopped, including its endpoint, DB parameter group, security group, and option group membership. You can stop an instance for up to 7 days at a time. After 7 days, it will be automatically started. For more details on stopping and starting a database instance, please refer to Stopping and Starting a DB Instance in the Amazon RDS User Guide. The stop/start feature is available for database instances running in a Single-AZ deployment which are not part of a Read Replica (both source and replica) configuration. Please see Amazon RDS Pricing for regional availability.
- Customers can primarily choose from 3 different purchasing options for EC2 – On Demand, RIs and Spot. On Demand is a pay as you go model with no commitments. You can increase or decrease your compute capacity depending on the demands of your application and only pay the specified hourly rate for the instances you use. This is suitable for customers that have unpredictable workloads or for applications that are being developed & tested on EC2 for the first time. RIs – This is where we’ll spend most of our time today. RIs offer a significant discount (upto 75%) over On Demand in exchange for a 1 year or 3 year commitment, and also provide an optional capacity reservation. RIs are best suited for customers that have steady state or predictable usage. Spot – AWS offers you the ability to bid on spare EC2 capacity for up to 90% discount off On Demand prices. Customers who have workloads that have flexible start and end times or who have urgent computing needs for large amounts of capacity can benefit from this model.
- There are three payment options for Reserved Instances, each with a different upfront amount – No Upfront—You are billed a discounted hourly rate for every hour within the term, regardless of usage, and no upfront payment is required. 2. Partial Upfront—A portion of the cost must be paid upfront and the remaining hours in the term are billed at a discounted hourly rate, regardless of usage. 3. All Upfront—Full payment is made at the start of the term, with no other costs incurred for the remainder of the term, regardless of hours used. The All Upfront payment option provides the highest discount.
- There are two types of RIs – Standard RIs and Convertible RIs. A Standard RI offers you the most amount of discount, when you commit to a 1 year or 3 year term. 3 year Standard RIs offer a higher discount than their 1 year counterparts. You can purchase a Standard RI using the AWS CLI, APIs or the AWS management console. At the time of purchase, you need to specify the instance type, OS, Tenancy and AZ.
- Convertible RIs offer you the flexibility to change the attributes of your RI configuration, while still receiving a significant discount (usually around 45% off On Demand prices). The Convertible RI is useful for customers who can commit for a three-year term in exchange for a significant discount on their overall EC2 usage, but are uncertain about their instance needs in the future. When you purchase a Convertible RI, you can modify the RI across instance families, sizes, OS types or tenancy.
- Spot Instances provide the ability for customers to purchase compute capacity with no upfront commitment and at hourly rates usually lower than the On-Demand rate, often as much as 90% cheaper - for those wondering what is a 90% discount? It is about 1c per core hour. Ask yourself what could your best people do, or how well could your application perform with a 10,000 core data center that costs just $100 per hour.. What applications should be considered for spot? Applications that have flexible start and end times Experiments that can only be conducted at very low compute prices (Brookhaven and Fermi – analyzing the origins of our universe). Or business that need extremely low infrastructure costs to achieve profitability such as Adtech. Users with urgent computing needs or large amounts of additional capacity
- If you think about the typical lifecycle of data, newly created active data is access very frequently. In our example take a new video clip you share with your friends and family. People will be consuming this new data actively, this new video will be played back frequently, shared and commented on very frequently. As this video becomes older, a smaller number of people will engage, it will be LESS FREQUENTLY accessed. S3 Standard-IA is a new LOW COST storage class on Amazon S3 we launched just a few weeks ago. Designed for data that is access infrequently called “Standard-Infrequent-Access”. This new storage class offers the same great durability and Performance of Amazon S3 Standard Storage class with a slightly lower availability… ideal for workloads that are “COLDER” and “less frequently accessed”. If you don’t want to think about your data access patterns but just want to high durability, availability and performance for Amazon S3 you can simply select S3 Standard. For data that is less-frequently accessed, you can leverage Amazon S3 Standard-IA to save on cost while still benefiting from the great durability and performance as S3 Standard. At some point in time your data will be ready to be archived because no one if actively interacting with your data and you need to archive that away for record keeping etc. In addition to transitioning your data to S-IA as its characteristics change, you can also leverage Amazon S3 Standard-IA for new data that fits the bill for Infrequently accessed data. For example you can leverage the S-IA storage class to stored detailed applications logs that you analyst in-frequently and save on storage cost.
- If you’re not responsible for the hands-on actioning of cost savings, there are mechanisms that you can set up so that your organisation doesn’t need to go through an effort intensive cost optimisation blitz every 6 months.
- First of all, what do we mean by mechanisms? Jeff once said, “Good intentions never work, you need good mechanisms to make anything happen” As much as teams want to save on AWS, you need mechanisms to drive action
- Once we have gathered the party, we can start setting up the remaining mechanisms These include: Tagging & Enforcement of Tagging Measures and Targets of Success Reporting & Tooling Governance and Controls And Ongoing Education
- For resource provisioning, there are several options. One is using AWS service catalogue with IAM roles and permissions requiring approval to access more expensive resources for example.
- AWS Organizations can help you define policies by Organizational Unit. For example, allowing the Finance team to only access S3 buckets for billing files. The link at the bottom provides further detail on AWS organisations
- So what should we measure? When starting out, go for measures that won’t give anyone a heart attack (e.g. non-financials) Financial measures such as current and potential savings by team invites contention and possibly defensive behavior. Try to use financial measures when you know teams are ready and have bought-in to the calculation method. Without measures teams I’ve seen teams claim to be optimized via anecdotal cases, but you have no real view of overall optimisation.
- Out of the box, from a reporting standpoint, AWS provides Cost Explorer which is an excellent starting point. It allows you to answer questions such as where is my data transfer spend coming from? How much did I spend on backup storage last month? And You can also save views for later by clicking save report.
- AWS Trusted Advisor can point you towards inefficiencies. Note that some of the savings will not be realizable, but you can treat it as a compass that points to potential savings.
- In-house developed reporting can be as simple as feeding the Cost and Usage Report into Redshift or Athena and visualizing in a reporting tool such as Quicksight. The link at the bottom provides a guide on how to set this up. Or simply google, cost and usage report redshift and quicksight
- When we talk about governance and controls, we ask questions such as: What’s your cost review process? How do you control visibility based on organizational unit and level? What happens when costs increase unexpectedly? Who gets to switch on resources? What happens to resources that are not tagged? What happens when a business unit nears or exceeds budget? The video link provided gives you a view of what advanced governance and cost management looks like at Netflix I encourage you to have a look. Because these questions are highly individual to each business, and it’s nearly impossible to plan in advance what to do. Therefore an agile and clearly communicated approach to governance that involves relevant stakeholders will set you up for successs.
- 3rd party options also provide a lot of depth and functionality in cost optimization and cost management reporting and tooling. They allow you to have instant access to thousands of hours of development time otherwise spent in building your own reporting and tooling, and makes a lot of financial sense for some customers to use. Some of these provide advanced function like reserved instance cost and benefits allocation by account and tag. And extend past cost control into security and automation.
- Here are some High quality talks that will help guide best practice and inspire your teams to take action. Each of these are less than an hour long and watching these will put you well ahead of the curve with regards to Cost Optimisation knowledge. If you’re willing to invest a little more time, there is also a course on A Cloud Guru on cost management.