With the present COVID -19 difficult situation, I am sure that almost all businesses\u00a0will be thinking of cutting down their costs, and CFO\u2019s will be looking for all possible cost reduction options. Generally, it\u2019s easy to think about reducing the unwanted human resource investments, come on! The present financial crisis is not suitable for thinking that way, Let’s think sensible, and stand shoulder to shoulder to support each other.<\/p>\n
So, where do the business leaders and CFO\u2019s should check first? Of course, it is your cloud infrastructure spending!<\/p>\n
A study done by Gartner, Inc forecasts the growth of worldwide public cloud services from a total of $227.8 billion in 2019 to a whopping $266.4 billion of 2020.<\/p>\n
We all know\u00a0AWS (Amazon Web Services) is the undisputed leader in the industry with about 47% of the market share. This consists of Small and Medium business using a single EC2 instance to Enterprises using multi region workloads who spends several thousand dollars per year.<\/p>\n
We all might see different mails from various public cloud providers about the tools they provide to check the optimal usage and suggestion on cost reductions, but might not have taken it too seriously. The IMF chief recently announced this pandemic will unleash worst recession. So why don’t we optimize our spendings?<\/p>\n
Since\u00a0Urolime<\/a>\u00a0being an AWS Partner company, and supporting customers for the last 9 years for AWS consulting and cost optimization, we now get numerous requests from AWS customers optimizing their cloud spend. In this, I would like to share a few best practices that would be worth considering:<\/p>\n 1. EC2 Instances<\/strong><\/p>\n One of the common cost optimization best practices by AWS, the purpose of it is to match the instance size to their necessary workloads. Most of the time, customers don\u2019t really know what is the best instance type to use, so they start with biggest\u00a0in thought that we never want to run out of CPU or RAM.<\/p>\n 2. Purchasing Reserved Instances\u00a0(RIs)<\/strong><\/p>\n I believe every AWS customer would have heard about RIs. This is one of the easiest ways to reduce your cost in AWS, at the same time if you do not know how optimally this needs to be planned and utilized, it will increase your AWS cost.<\/p>\n 3. Scheduling on\/off times<\/strong><\/p>\n I still our team writing scripts to automate this with AWS CLI in the past to make it a one click solution for the development team, but now everything is available from the dashboard. This is one of the best ways to reduce your AWS cost by scheduling start\/stop of your non-production environments such as development, staging, QA etc. This could save you 60% – 70% of running this non-production instances.<\/p>\n 4. Upgrade instances to the latest generation<\/strong><\/p>\n Amazon Web Services releases new generation of instances, so often, and thus tend to have improved performance and functionality compared to their predecessors. The option here is either upgrade existing instances to the latest generation, or downsize existing instances with borderline utilization metrics in order to benefit from the same level of performance at lower cost.<\/p>\n 5. Delete unattached EBS volumes<\/strong><\/p>\n If you are an AWS customer for quite a long time, I am sure that you tried creating and deleting EC2 instances multiple times. The general mistake found here is we forget to select\u00a0\u201cdelete on termination\u201d box when the instance was launched. If the box wasn\u2019t checked, the EBS volume still exists\u00a0and it will be charged until you delete it.<\/p>\n 6. Delete orphaned snapshots, always have a retention policy<\/strong><\/p>\n Most of the customers just want to make sure the backup is happening, without a proper plan or retention policy. If you have one, and maintain the retention it is simply great! Otherwise the number will grow, and so your monthly bill.\u00a0Usually, you just require the most recent snapshot to restore data if something goes wrong, and although\u00a0snapshots don\u2019t cost very much individually, you could save thousands of dollars by deleting those which is no longer required.<\/p>\n 7. Terminate zombie assets<\/strong><\/p>\n You need to keep an eye on unused assets and do frequent clean up. The common unused assets we usually find in new customer environments are ELB, ALB, Elastic IPs, Snapshots, Unattached EBS volumes, NAT gateways etc.<\/p>\n 8. Move infrequently-accessed data to lower cost tiers<\/strong><\/p>\n Based on the data access frequency from AWS S3 buckets, you need to decide which tier is suitable for your use case.\u00a0The savings generated from storing infrequently accessed, non-critical data in a lower cost tier can be substantial.\u00a0Determining which storage tier is most suitable for data depends on factors such as how often data is accessed and how quickly a business would need to retrieve data in the event of a disaster.<\/p>\n The six tiers of storage:<\/p>\n 9. Use Spot Instances<\/strong><\/p>\n Amazon EC2 Spot Instances allow you to access spare Amazon EC2 computing capacity. Since Spot Instances are available with up to 90% discount when compared to On-Demand pricing, you can significantly reduce the cost of running your applications, grow your application\u2019s compute capacity and throughput for the same budget, and enable new types of cloud computing applications.<\/p>\n 10. Monitor, track and your service offerings<\/strong><\/p>\n You can use Amazon CloudWatch to collect and track metrics, monitor log files, set alarms, and automatically react to changes in your AWS resources. You can also use Amazon CloudWatch to gain system-wide visibility into resource utilization, application performance, and operational health.<\/p>\n With Trusted Advisor you can provision your resources following the best practices to improve system performance and reliability, increase security, and look for opportunities to save money. You can also turn off non-production instances and use Amazon CloudWatch and Autoscaling to match increases or reductions in demand.<\/p>\n 11. Analyze your costs and usage using cost explorer<\/strong><\/p>\n AWS Cost Explorer<\/a>\u00a0gives you the ability to analyze your costs and usage. Using a set of default reports, you can quickly get started with identifying your underlying cost drivers and usage trends. From there, you can slice and dice your data along numerous dimensions to dive deeper into your costs.<\/p>\n One powerful,\u00a0cost\u00a0management<\/a>\u00a0feature available in Cost Explorer is to filter and group your Cost Explorer data according to your resource tags. Tagging gives you the ability to create resource groups that that match your business structures, making it easier to map your resources and workloads to the appropriate cost center.<\/p>\n It is also suggested to look at your existing infrastructure architecture and make sure it’s highly available and scalable. With horizontal scalability, you can cut down the number of running instances, rather let AWS handle the extra traffic with its auto scalability feature for you.<\/p>\n We, at\u00a0Urolime<\/a>\u00a0always experienced a significant cost reduction of 25% to 35% in most of the customer environments after cost optimization. And let me remind you, cost optimization is a continuous process, you always need to monitor and identified unused or underutilized resources. There are a lot of ways to automate this process. Optimize your AWS spendings today!<\/p>\n If you need some help, feel free to\u00a0contact us<\/a>\u00a0any time! Stay healthy and stay safe!<\/p>\nThe 11 AWS cost optimization best practices<\/strong><\/h3>\n
\n