6 Hacks for AWS Cloud Cost Optimisation

6 Hacks for AWS Cloud Cost Optimisation

As it is rightly said “Reducing the overall cost is a high priority” and it is true for any organization whether big or small.

By using E2E Cloud we can lower the IT costs, compute costs, storage as well as caching costs. But what after that, after we start using AWS how can we still optimize our costs. This is the agenda in writing this blog.

While?using the AWS services?we often become careless and instances are left running or volumes are unattached or some other resources are kept idle which lead to increase in the overall bill. To avoid such situations or carelessness, AWS provides us with a service called AWS Trusted Advisor(TA) available with the business support plan. It calculates the cost which is generated due the unused or underutilized resources and recommends corrective actions.

But AWS Trusted Advisor comes under the Business Support Plan which is chargeable. The pricing of Business support is either 10% of the overall bill incurred or 100$, whichever is higher. So basically, to save some costs, you might need to shell out some money.

1. Low Utilization EC2:?The first and foremost resource to check is compute. You must check for over-provisioned instances or which have very less utilization trend. The function calculates the average CPU Utilization and Network I/O of all the instances for the past 14 days. The CPU Utilization should be less than 10% and the network I/O should be less than 5 mb for any 4 of the last 14 days. Both conditions should be true for declaring the instance in the low utilization mode. However, you have put your own values to decide about the idleness.

2. RDS Idle DB Instances: Database instances are costlier than a normal EC2 instance and their idleness will be costlier. The function checks whether all the RDS instances are getting enough DB connections or not. If the RDS don’t have the desired DB Connections in the last one week then it’s getting wasted and should be given a check.

3. Underutilized Amazon EBS Volumes: Elastic Block Store volumes which come pre-attached with an instance are usually the boot devices which are deleted once Instance is terminated. However, these EBS volumes even with stopped instance incur some charges. The function lists all the EBS volumes in all the regions and checks whether the EBS is attached to an instance or the EBS has had no IOPS in the last 1 week. The cost of EBS is based on provisioned storage and no of IOPS per month. This also varies according to the type of the volume to be used.

4. Unassociated Elastic IP Addresses: As we know the IP (version-4) are getting exhausted really fast. So we need to use the IP’s carefully until we start adopting the IPv6 class. The cost of using an elastic IP occurs when the IP is generated and it is not attached to any of the instances i.e. its left unassociated. This function gives a list of all the IP’s that are left unattached.

5. Legacy Instance Type Usage: Legacy instances are the old class of instances which were provided until the new generation instances were released. The new generation instances have a higher performance compared to the legacy ones as well as new generation instances are also cheaper than legacy ones for the same configuration. This funtion lists all the instances which are running using the legacy instances and also the class of the instance and recommends replacing them with new generation instance.

6. Idle Load Balancers: Next, we should be checking the Elastic load balancers which are lying idle. Any ELB that is created and configured will accrue charges. The function will list all the ELB’s which are either not attached to an instance or which don’t have a healthy instance or the no. of requests to the load balancer is less than 100 in the past 7 days.

The above-mentioned script should be run on a regular basis so as to avoid any unnecessary cost on the bill.

要查看或添加评论,请登录

Harshit Goyal的更多文章

社区洞察

其他会员也浏览了