AWS announces EBS snapshot price reduction,PIOPS increase

AWS announces EBS snapshot price reduction, PIOPS increase

AWS recently announced the price reduction of their EBS volume snapshots and the increase of available Provisioned IOPS (PIOPS) per GiB for all volumes. Even better, all price reductions are retroactive as far back as August 1st, 2016.

Read the post:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

[Playbook] AWS Cost Allocation Using Tags and Linked Accounts

AWS Cost Allocation Using Tags and Linked Accounts

By separating your resources into multiple linked accounts and then assigning tags to your resources, you can precisely track where your AWS spending is going. In this guide, you’ll learn the fundamentals of AWS tags and linked accounts, and how to apply them to your organization. We’ll cover:

– How to properly separate and tag your resources
– When to use tags vs. linked accounts
– Reporting out costs by resource
– And more!

Download the Guide:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

AWS cost allocation: best practices and what to avoid [Webinar]

AWS cost allocation: Best practices and what to avoid
Date: Wednesday, August 24
Time: 11:00 am PT / 2:00 pm ET

Register for the webinar:

Proper AWS cost allocation allows you to find the value and waste in your AWS spending. In this webinar, you’ll learn the right strategies and tools to segment, report and control your company’s AWS costs across multiple applications, departments, environments, teams, and at the AWS resource level. Topics include:

– Understanding AWS spending via tagging and linked accounts
– Customizing and automating cost allocation reports
– Using resource-level analytics to identify cost drivers
– Improving spend visualization by identifying and eliminating
untagged resources

We’ll also field your questions about cost allocation best practices
and strategies at the end of the session.

Register now:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

Finding your most expensive AWS resources (and what to do about them)

Finding your most expensive AWS resources (and what to do about them)

With hundreds or thousands of AWS resources running, it can be challenging to wrangle all cost and usage data to find out which resources are costing your org the most. Learn how having the right analytical tools in place can help users keep an eye on high-cost resources and start the conversations around optimizing AWS usage.

Read the post:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

Four tags that every cloud instance should have

Four tags that every cloud instance should have

For as long as we’ve been a source of cloud cost management strategies and tips, we’ve preached the gospel of tags. They’re a vital tool for enabling cost allocation, chargeback, and in-depth understanding of how the cloud is being leveraged across your company. These are four tags that every cloud instance should have:

#1: Environment
Knowing how your usage breaks out across dev, test, qa and prod provides insight into your spending across environments (should you really be spending that much on test?) and can be vital for optimizing your spending.

Example tags:

environment=dev
environment=prod

#2: Role
The ability to quickly identify what an instance is being used for can go a long way. Should this instance really be running as frequently as it has been? Should we be spending as much as we are to keep this instance running?

Example tags:

role=webserver
role=customerdatabase

#3: Creator/Owner
A little accountability goes a long way. Encourage (or mandate) employees to tag any instance that they spin up with their own name, and efficiency might just magically increase. And if it doesn’t_ you can point fingers with confidence.

Example tags:
owner=steven
creator=luna

#4: Name
The name tag is set by default when an instance is launched, for good reason. The ability to uniquely identify any given instance allows you to allocate spending all the way down to specific instances, associate bandwidth to a tagged resource, and let you use concatenated tags.

Example tags:
name=the_id_of_the_instance_a_volume_is_attached_to
name=the_name_of_the_instance_a_volume_is_attached_to

When we say that these are four tags that every instance should have, we really do mean every instance. Tags are only useful if they’re applied consistently — otherwise, they’ll only provide a partial representation of your spending.

Want to see which instances you still need to tag? Check out our Untagged Instances Report by signing up for a free 14-day trial of Cloudability (Start the trial:
Unsubscribe

Wednesday’s webinar: AWS cost allocation

AWS cost allocation: Best practices and what to avoid
Date: Wednesday, August 24
Time: 11:00 am PT / 2:00 pm ET

Register for the webinar:

Proper AWS cost allocation allows you to find the value and waste in your AWS spending. In this webinar, you’ll learn the right strategies and tools to segment, report and control your company’s AWS costs across multiple applications, departments, environments, teams, and at the AWS resource level. Topics include:

– Understanding AWS spending via tagging and linked accounts
– Customizing and automating cost allocation reports
– Using resource-level analytics to identify cost drivers
– Improving spend visualization by identifying and eliminating
untagged resources

We’ll also field your questions about cost allocation best practices and strategies at the end of the session.

Register now:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

It’s not too late to register for tomorrow’s webinar

AWS cost allocation: Best practices and what to avoid
Date: Wednesday, August 24
Time: 11:00 am PT / 2:00 pm ET

Register for the webinar:

Proper AWS cost allocation allows you to find the value and waste in your AWS spending. In this webinar, you’ll learn the right strategies and tools to segment, report and control your company’s AWS costs across multiple applications, departments, environments, teams, and at the AWS resource level. Topics include:

– Understanding AWS spending via tagging and linked accounts
– Customizing and automating cost allocation reports
– Using resource-level analytics to identify cost drivers
– Improving spend visualization by identifying and eliminating
untagged resources

We’ll also field your questions about cost allocation best practices and strategies at the end of the session.

Register now:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe:

OpenDNS/Cisco builds a culture of AWS cloud cost management

OpenDNS/Cisco builds a culture of cloud cost management

Organizations large and small start to notice their cloud costs spike once apps and business starts humming. Learn how OpenDNS sought to get more out of their AWS Reserved Instances spending by using Cloudability to build a stronger culture of cloud cost management.Read the post:

Twitter:
Facebook:
LinkedIn:

Cloudability
718 SW Alder St.
Portland, OR 97205

Unsubscribe: