The beauty of Amazon Web Services is they’re easy to set up and run. The problem with those services is they’re easy to set up and run. Now Amazon is offering companies a better way — with a little prep work — to track those costs.

6091370824_f55d937089_z (3)

Amazon is making it easier for companies to track and price out the cloud services they’re deploying with a new cost allocation process.

The fact that Amazon Web Services are so inexpensive and easy to spin up is both a blessing and a curse for companies. A blessing because internal developers can try out new stuff fast and cheap; a curse because it leads to cloud sprawl where companies find it difficult to track and monitor cloud usage and the costs of which — let’s face it — add up. Even cheap services cost money. A post on the Amazon Web Services blog outlines how corporate users can tag those services to make billing less of an, um, adventure.

It does still require some manual input. The Amazon resources you use have to be tagged  as one of the following:

  • S3 buckets
  • EC2 Instances
  • EBS volumes
  • Reserved Instances
  • Spot Instance requests
  • VPN connections
  • Amazon RDS DB Instances
  • AWS CloudFormation Stacks

The tags — 10 of which can be applied for each resource — are then entered via the AWS Management Console, the service APIs, the command line or Auto Scaling.

For many big AWS users, this is a good thing. Because there are so many services offered by the hour, it is easy to leave something running unnecessarily. “For us, the underlying mechanism is very valuable because it means we can do a ‘one-stop-shopping’ for our clients and re-bill them for a combination of the AWS charges plus our support and engineering charges,” said Bob Shear, president of Greystone Solutions, a Boston company that sets up ecommerce sites for customers.

A variety of third parties including Rightscale, Cloudability, CloudynNewvem and UptimeCloud already offer services to help customers better track their cloud spending. And Rightscale just announced its PlanforCloud service for forecasting purposes.

Amazon clearly sees a need to offer a better cost tracking service of its own.

Feature photo courtesy of Flickr user Will Merydith

You’re subscribed! If you like, you can update your settings

  1. Barb,

    It would be very helpful to your non-insider readership, to explain (briefly) what exactly each of those 8 or 10 Amazon resources actually *do*.

    The labels are pretty opaque for any other than the IT Illuminati.

    1. you are right about that. Apologies. next time i’ll explain better….

    2. A quick overview of the AWS services:

      S3 buckets – Redundant data storage infrastructure
      EC2 Instances – Computing capacity
      EBS volumes – Block level storage volumes
      Reserved Instances – Upfront payments for EC2
      Spot Instance requests – Bid on unused Amazon EC2 capacity
      VPN connections – Hardware Virtual Private Network
      Amazon RDS DB Instances – Relational Database Service
      AWS CloudFormation Stacks – AWS management framework for AWS resources.

      Check out blog.cloudyn.com for more info regarding reserve instances, RDS, EBS, EC2 and S3 control and optimization

      1. thanks cloudyn… i should have done that my own self!

Comments have been disabled for this post