Cost Efficiency

How to Configure the Auto Scaling EC2 Cloud Instance Termination Policy

AutoscalingAWS Auto Scaling adds or removes the EC2 instances automatically based on a pre-configured condition. When a new EC2 instance is launched automatically it will be added to the Auto Scaling group. Auto Scaling allows the user to add a policy to decide on the termination of an instance. Before Auto Scaling terminates the EC2 instance, it first checks the availability zones. It will find the availability zone with the highest number of instances and delete the instance from there. If all the availability zones have the same number of instances, Auto Scaling selects any random zone. Once the availability zone is defined, Auto Scaling uses the termination policy to identify the instance to be deleted.

By default, Auto Scaling will delete the oldest instance from the selected availability zone. If more than one instance was launched simultaneously based on the scaling policy, Auto Scaling will take the instance that is closest to next instance hour. The above mentioned policy can result in cost savings. If more than one instance has the same time, Auto Scaling selects any random instance.

The present guide demonstrates how to configure and test the above mentioned termination policy for Auto Scaling. Since AWS does not provide the management console for Auto Scaling, all the tasks would be performed by CLI.

Newvem Launches Analytics for Windows Azure Cloud

Newvem analytics for AzureWe are thrilled to announce the launch of Newvem Cloud Operations Optimization for Windows Azure. This latest offering empowers Windows Azure users with straight forward visibility into their cloud inventory and usage, enabling better decision making, minimalizing operational exposures, and aligning cloud operations with business objectives.

Built for the Enterprise

Azure offers a natural extension to enterprise IT operations by allowing them to relieve IT resources and prevent bottlenecks.  With this powerful solution, enterprises can respond quickly to market needs with Microsoft’s enterprise-grade reliability. Public Cloud adoption in the enterprise centers on the developers need to provision servers to address the enterprises IT needs as well as meet new demands.

5 Key Essentials of Cloud Workloads Migration

Cloud Workload TypesThe benefits of migrating workloads between different cloud providers or between private and public clouds can only truly be redeemed with an understanding of the cloud business model and cloud workload management. It seems that cloud adoption has reached the phase where advanced cloud users are creating their own hybrid solutions or migrating between clouds while striving to achieve interoperability values within their systems. This article aims to answer some of the questions that arise when managing cloud workloads.

How to Clean-up Unused AWS EBS Volumes and Snapshots

Clean EBS and SnapshotsIn this post, I will show you how to clean up unused Amazon EBS Volumes and Snapshots.

This is worth doing as quite a collection can build up over time and Amazon Web Services has limits on the number of volumes and snapshots you can store; these limits can be increased, but you have to make a Request to Increase the Amazon EBS Volume Limit.

What are EBS Volumes?

Volumes behave like raw, unformatted block devices, with user supplied device names and a block device interface. You can create a file system on top of Amazon EBS volumes, or use them in any other way you would use a block device (like a hard drive).

Presentation: Newvem’s Cloud Utilization Heat Maps

UHM_SlideshareNewvem’s Utilization Heat Map enables you to visualize your 30-day cloud usage by hour, region, business activity, and more in a single glance.

Did you know that more than 15% of clouds are underutilized? That’s more than $30M of the $200M in EC2 spend that Newvem has analyzed over the past year! Such a waste but it can be easily remedied with Cloud Utilization Heat Maps!

How-to Estimate Your AWS EBS Volume’s Snapshot Costs - Part 2

EBS Snapshot costs feature imageIn part one I described the AWS EBS snapshot mechanism. In this part I will drill deeper on how to calculate the EBS snapshot cost. I  will show how to be able to do a rough estimation or even to perform an accurate cost analysis using monitoring tools.

Rough estimation

In order to estimate how large your EBS snapshots will be, you need to know how much your volumes are changing. One way would be to guesstimate,we can use a simple thumb rule that is often used in- backup planning: A typical data volume of a production server changes about 3% a day. Let’s try and calculate the cost. Assuming a 1TB EBS volume, that is 70% full at first. We take snapshots and keep them for 30 days. So, the first full will be taking 700GB (70% of 1TB). For the incremental snapshots we can multiply 30 (days) by 30GB (3% of 1TB) and we reach 900GB. Add them together and we reach about 1.6TB of total snapshot storage. AWS compresses the snapshots when they are stored in S3.

Netflix on Cost-Aware AWS Cloud Architectures

AWS Cost Aware by NetflixCloud computing comes with amazing financial benefits for the organization…assuming it’s done right. In this presentation, Adrian Cockcroft of Netflix explains how a rapid innovation cycle encourages faster returns and a more economic cloud. He posits that lowering the cost of failure will create a more innovative organization and culture – but how?

How to Detect and Shutdown an Unused AWS EC2 Instance

Amazon CloudWatch is used to monitor several AWS products. Cloudwatch provides various metrics to monitor the user’s instance, the resources as well as the AWS billing. Cloudwatch can send a notification about a particular event. The user can create alerts to send the notifications. CloudWatch monitors the CPU usage and sends a notification if the usage exceeds the specified threshold. AWS CloudWatch also offers a unique feature to stop or terminate an instance when the CloudWatch alarm is triggered.

The present guide demonstrates how to stop an instance if the EC2 instance is not in use. The alarm will be configured to stop the instance when the CPU usage is less than 5% for more than 2 hours. The below mentioned steps are only for an EBS backed instance. For an instance store backed AMI instance, the user can configure the terminate action only.

Estimating your Amazon EBS Snapshots Cost - Part 1: Block Level Incremental Snapshots

When using Amazon EBS snapshots for your EC2 backup solution, you worry about stuff like automating EBS snapshots. To rely on EBS snapshots as a backup solution, however, you may want to be able to estimate the cost of storing the snapshots. Currently, the exact size of EBS snapshots is not available. In part 1 of this 2 part series, we will try to better understand how EBS snapshots work.

How to Subscribe to an AWS EC2 Spot Instance Auto Feed

An AWS spot instance helps to reduce the running cost of the EC2 instance.  The user bids for a spot instance request specifying the maximum price that the user is willing to pay per hour per instance. Once the spot instance request is fulfilled, the instance will continue to run until it is manually terminated or the spot price increases above the maximum bid price. The user is not charged as per the max price; instead the user will be charged at the current spot price in that availability zone. To know the charges for spot instances, Amazon EC2 provides access to a data feed, which details the user’s spot instance usage and pricing every hour.

The present guide demonstrates how to subscribe or delete the spot instances price data feed.

Hitchhiker's Guide to The Cloud

Newvem's eBook for Cloud Operations