{"id":493,"date":"2020-10-06T16:28:26","date_gmt":"2020-10-06T09:28:26","guid":{"rendered":"https:\/\/vticloud-test.tk\/?p=493"},"modified":"2021-09-20T09:33:01","modified_gmt":"2021-09-20T02:33:01","slug":"10-goi-y-giup-ban-toi-uu-chi-phi-tren-aws","status":"publish","type":"post","link":"https:\/\/vticloud.io\/en\/10-goi-y-giup-ban-toi-uu-chi-phi-tren-aws\/","title":{"rendered":"10 things you can do today on AWS cost optimization"},"content":{"rendered":"

<\/p>\n

This post is contributed by Shankar Ramachandran, SA Specialist, Cost Optimization<\/em><\/span><\/p>\n

Introduction to AWS cost optimization<\/span><\/h2>\n

AWS\u2019s breadth of services and pricing options offer the flexibility to effectively manage your costs and still keep the performance and capacity per your business requirement. While the fundamental process of cost optimization on AWS remains the same \u2013 monitor your AWS costs and usage, analyze the data to find savings, take action to realize the savings; in this blog, I will take a more tactical approach of reducing cost with changes in user demand.<\/span><\/p>\n

Before you start\u00a0<\/span><\/strong><\/span><\/p>\n

Before taking any actions to reduce cost, find out the costs of AWS services, you are consuming. The AWS Free Tier<\/a>\u00a0provides customers the ability to explore and try out AWS services free of charge up to specified limits for each service. Use the steps in this\u00a0video<\/a>\u00a0to check if you are exceeding the free tier limit.<\/span><\/p>\n

Next, use\u00a0AWS Cost Explorer<\/a> to view and analyze your AWS costs and usage. This tool provides default reports that help you visualize cost and usage at a high level (e.g., AWS \u00a0accounts, AWS service) or at the resource level (e.g., EC2 instance ID). Start by identifying the top accounts where your costs incur using the \u201cMonthly costs by linked account report.\u201d Next, identify the top services that contribute to the costs within those accounts. You can do this by using the \u201cMonthly costs by service report.\u201d Use the hourly and resource level granularity and tags to filter and identify the top resources incurring costs.<\/span><\/p>\n

\"\"<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Cost Explorer resource level granularity<\/span><\/p>\n

Now, you should have an understanding of your AWS costs and usage. Next, let\u2019s walk through 10 tactical things you can do today using existing AWS tools and services to reduce your AWS costs.<\/span><\/p>\n

1. Identify Amazon EC2 instances with low-utilization and reduce cost by stopping or rightsizing<\/span><\/h3>\n

Use\u00a0AWS Cost Explorer Resource Optimization<\/a>\u00a0to get a report of EC2 instances that are either idle or have low utilization. You can reduce costs by either stopping or downsizing these instances. Use\u00a0AWS Instance Scheduler t<\/a>o automatically stop instances. Use\u00a0AWS Operations Conductor<\/a>\u00a0to automatically resize the EC2 instances (based on the recommendations report from Cost Explorer).<\/span><\/p>\n

\"\"<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Cost Explorer rightsizing recommendations<\/span><\/p>\n

Use\u00a0AWS Compute Optimizer<\/a> to look at instance type recommendations beyond downsizing within an instance family. It gives downsizing recommendations within or across instance families, upsizing recommendations to remove performance bottlenecks and recommendations for EC2 instances that are parts of an Auto Scaling group.<\/span><\/p>\n

2. Identify Amazon EBS volumes with low-utilization and reduce cost by snapshotting then deleting them<\/span><\/h3>\n

EBS volumes that have very low activity (less than 1 IOPS per day) over a period of 7 days indicate that they are probably not in use. Identify these volumes using the Trusted Advisor Underutilized Amazon\u00a0EBS Volumes Check<\/a>. To reduce costs, first snapshot the volume (in case you need it later), then delete these volumes. You can automate the creation of snapshots using the\u00a0Amazon Data Lifecycle Manager<\/a>. Follow the steps\u00a0here<\/a>\u00a0to delete EBS volumes.<\/span><\/p>\n

3. Analyze Amazon S3 usage and reduce cost by leveraging lower-cost storage tiers<\/span><\/h3>\n

Use\u00a0S3 Analytics<\/a>\u00a0to analyze storage access patterns on the object data set for 30 days or longer. It makes recommendations on where you can leverage\u00a0S3 Infrequently Accessed<\/a> (S3 IA) to reduce costs. You can automate moving these objects into lower-cost storage tier using\u00a0Life Cycle Policies<\/a>. Alternately, you can also use\u00a0S3 Intelligent-Tiering<\/a>, which automatically analyzes and moves your objects to the appropriate storage tier.<\/span><\/p>\n

4. Identify Amazon RDS, Amazon Redshift instances with low utilization and reduce cost by stopping (RDS) and pausing (Redshift)<\/span><\/h3>\n

Use\u00a0the Trusted Advisor Amazon\u00a0RDS Idle DB instances check<\/a> to identify DB instances that have not had any connection over the last 7 days. To reduce costs, stop these DB instances using the automation steps described in\u00a0this<\/a>\u00a0blog post. For Redshift, use the Trusted Advisor Underutilized\u00a0Redshift clusters check<\/a>, to identify clusters which have had no connections for the last 7 days, and less than 5% cluster-wide average CPU utilization for 99% of the last 7 days. To reduce costs, pause these clusters using the steps in this<\/a>\u00a0blog.<\/span><\/p>\n

\"\"<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Pause underutilized Redshift clusters<\/span><\/p>\n

5. Analyze Amazon DynamoDB usage and reduce cost by leveraging Autoscaling or On-demand<\/span><\/h3>\n

Analyze your DynamoDB\u00a0usage by monitoring 2 metrics, ConsumedReadCapacityUnits and\u00a0ConsumedWriteCapacityUnits, in CloudWatch. To automatically scale (in and out) your DynamoDB table, use the AutoScaling feature. Using the steps\u00a0here<\/a>, you can enable AutoScaling on your existing tables. Alternatively, you can also use the on-demand option. This option allows you to pay-per-request for reading and writes requests so that you only pay for what you use, making it easy to balance costs and performance.<\/span><\/p>\n

 <\/p>\n

\"\"<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0DynamoDB read\/write capacity mode<\/span><\/p>\n

 <\/p>\n

6. Review networking and reduce costs by deleting idle load balancers<\/span><\/h3>\n

Use the Trusted Advisor Idle\u00a0Load Balancers check<\/a>\u00a0to get a report of load balancers that have RequestCount of less than 100 over the past 7 days. Then, use the steps\u00a0here<\/a>\u00a0to delete these load balancers to reduce costs. Additionally, use the steps provided in\u00a0this<\/a>\u00a0blog, review your data transfer costs using Cost Explorer.<\/span><\/p>\n

\"\"<\/span><\/p>\n

Cost Explorer filters for EC2 Data Transfer<\/span><\/p>\n

If data transfer from EC2 to the public internet shows up as a significant cost, consider using Amazon CloudFront. Any image, video, or static web content can be cached at AWS edge locations worldwide, using the Amazon CloudFront Content Delivery Network (CDN). CloudFront eliminates the need to over-provision capacity in order to serve potential spikes in traffic.<\/span><\/p>\n

7. AWS Cost Optimization with Amazon EC2 Spot Instances\u00a0<\/span><\/h3>\n

If your workload is fault-tolerant, use Spot instances to reduce costs by up to 90%. Typical workload examples include\u00a0big data, containerized workloads, CI\/CD, web servers, high-performance computing (HPC), and other test & development workloads. Using\u00a0EC2 Auto Scaling\u00a0you can launch both On-Demand and Spot instances to meet a target capacity. Auto Scaling automatically takes care of requesting for Spot instances and attempts to maintain the target capacity even if your Spot instances are interrupted. You can learn more about Spot by watching this 2019 re:Invent session:<\/span><\/p>\n