Category

Cost Efficiency Insights

Reserved Instances utilization

Introduction

Newvem continuously tracks and identifies your AWS EC2 resource utilization patterns on a per-instance basis, as well as on a per-instance-type basis. We also take into consideration what Reserved Instances you have purchased and the corresponding available reservations. Based on the analysis of this data, we identify how effectively you’ve been using your purchased Reserved Instances.

Newvem’s analysis of your AWS EC2 utilization patterns identifies the sustained usage of EC2 instances per instance-type in an availability zone. Such patterns reflect the baseline of utilization of that instance type in the select availability zone. If the user has Reserved Instances available, Newvem’s analysis take them into consideration, and determine whether the reservation is paying off.

Reserved Instances usage opportunity

Newvem continuously tracks and identifies your AWS EC2 resource utilization patterns on a per-instance basis, as well as on a per-instance-type basis. Based on these, we identify when purchasing Reserved Instances might improve your spending efficiency.

Newvem’s analysis of your AWS EC2 utilization patterns identifies the sustained usage of EC2 instances per instance-type in an availability zone. Such patterns reflect the baseline of utilization of that instance type in the select availability zone: if the user historically maintains a minimal number of instances of a given type, running in a given availability zone, for specific periods of time, in some cases it becomes more spend efficient to purchase a Reserved Instance of that instance-type in that availability zone.

The underlying utilization pattern is the fundamental usage pattern that justifies the purchase of Reserved Instances. Other considerations come into the equation when it comes to determine what type of EC2 Reserved Instances one should purchase for aligning the corresponding spending pattern with the underlying business needs.

Unused EBS volumes found

EBS Volumes are always charged for their provisioned storage, regardless of being attached to an EC2 instance. Therefore, when it comes to volumes that are not attached to an instance, the best practice is to keep only those volumes that will be needed in the future. Keeping volumes you don’t plan to use in the future, or those you just forgot, may contribute to unexpectedly high bills.

Furthermore, those volumes left on the side can become old data, that may be inadvertently misused in the future.

Newvem tracks the usage of your EBS Volumes and identifies those that haven’t been attached to any instance for a significant period. We suggest you consider discarding such volumes if you do not plan to use them.

Elastic IPs not in use

In AWS, users are charged for allocated Elastic IPs that are not associated to a running instance nor to a network interface (VPC). Therefore, the best practice is to keep only those IP addresses that will be needed in the future. Allocated Elastic IPs you don’t plan to use in the future, or those you just forgot to release, may contribute to unexpectedly high bills.

Newvem tracks the usage of your allocated Elastic IPs and identifies those that haven’t been in use for a significant period. We suggest you consider releasing those allocated IP addresses if you do not plan to use them.

Compute Utilization Efficiency (CPU Load)

Newvem continually monitoring your servers CPU load and notifies you on high loads. High-load lead to a major down time risk, you might need to consider changing the instance type or implement a different scaling method. We consider an arbitrary of 80% CPU load and above as an high load and suggest that you scale up or scale out your compute instances (i.e. move your workload to larger servers or use additional servers).

 

Keywords: compute utilization efficiency, CPU Load, Newvem

Compute Footprint Utilization (Idle)

The nature of cloud elasticity enables flexibility in choosing and provisioning instances that perfectly suit the demand at any time. With many instances deployed across multiple environments it is sometimes difficult to keep track of all the instances that you are using, leaving behind active instances that have been idle for a long time.

Oversized Servers Found (IO)

Newvem analytics provides comprehensive visibility to your EC2 footprint with drill downs from a consolidated view to a detailed resource status report. Newvem continuously analyzes EC2 instance utilization patterns and provides a down-to-the-hour picture of your AWS EC2 consumption and usage. Use it for Free!

Newvem monitors cloud servers that are active, but found that their IO has been mostly idle for a considerable amount of time. This means that you are using oversized servers, which is not cost efficient. We suggest to consider resizing these servers (i.e. move your workload to smaller, lower cost servers to reduce your compute costs). Instead of starting a new instance and configuring it from scratch, one may be able to simply resize the existing instance by moving it to a more suitable hardware configuration.

Stopped Servers Found

In order to help control and perform organized and efficient cloud operations, Newvem monitors the number of servers that have been stopped for more than one week. We suggest terminating stopped servers, and when the need arises again, activate new servers from an AMI. Finding that this server is important, you can generate a new “Golden AMI” accordingly and then terminate it. On the other hand, if you find the server to be redundant and you terminate it, you actually save storage costs and control sprawling.

Excessive Number of EBS Volume Snapshots

Newvem checks for the sprawling of EBS volume snapshots, which results in an excessive number of snapshots. As this decreases the overall efficiency of the backup process, and is also not cost-efficient, we suggest to remove the unnecessary snapshots and define a retention policy. To do so, check your Newvem EBS snapshots report to find the EBS volume that holds multiple snapshots and remove the unnecessary snapshots, refine retention policy, and generate an automatic procedure.

Abnormal Compute Cost Growth Pattern

Newvem monitors changes in the growth cost pattern of your compute resources. We have identified an abnormal change in your overall growth rate in the time range . We suggest to keep tracking costs over for few days, and check that the cost growth is aligned with your expectations and budget. If necessary, adjust your footprint accordingly.

Hitchhiker's Guide to The Cloud

Newvem's eBook for Cloud Operations