1. Home
  2. Training Library
  3. Amazon Web Services
  4. Amazon Web Services Courses
  5. Improve Planning and Cost Control With AWS Budgets

Creating a Budget Demo

Contents

keyboard_tab
Improve Planning and Cost Control with AWS Budgets
1
Introduction
PREVIEW2m 10s

The course is part of this learning path

Start course
Overview
Difficulty
Intermediate
Duration
23m
Students
57
Ratings
5/5
starstarstarstarstar
Description

This course will explain how AWS Budgets can help you manage AWS spend and improve financial planning. 

Learning Objectives

  • What the tool is and the benefit it provides
  • How to set up a Budget and configure Budgets actions 
  • How to send a Budget report 
  • And lastly, how to configure and use AWS Cost Anomaly Detection

Intended Audience

This course has been created for financial operations professionals interested in controlling AWS costs and for engineering team members who want more visibility into the cost of their environments.

Prerequisites

To get the most out of this course, you should have an understanding of the AWS Billing console and AWS Cost Explorer. Additionally, I briefly discuss establishing permissions through IAM and AWS Organizations and use examples referencing Amazon EC2.

Transcript

In this video, I’ll create a cost budget to monitor the costs in my AWS account. To do this, I’ll search for Budgets in the AWS console, and click Create Budget. 

The first thing I’ll select is the type of budget, I have four options: cost, usage, savings plans and Reserved Instances. I’ll select a cost budget.

From there, you can see my screen has been split. On one side, I’m selecting the options for my budget, and on the other side, it generated a chart from AWS Cost Explorer so I can view the historical cost data in my account. This account is fairly new, only a few months old, so it only has data from the past few months and you can see I generally stick around the $15 range monthly. 

Using this data, I can gain a solid understanding of my costs and fill out the rest of my information to create my budget. First, I’ll choose a budget name,  I’ll call it TakeMyFifteenDollars. Then I’ll select the time period. My options are daily, monthly, quarterly, and annually. I’ll choose monthly. 

Then I can choose to have this budget set to recur after my budget period of a month, or I can have it expire after a certain period of time that I choose. I want this to be ongoing, so I’ll select recurring.  

Then I select my threshold. I can either choose a fixed amount, such as $15. Or I can select a planned amount for each month in my budget period, in this case, a year. I can input these values manually, or I can let AWS calculate them based on a starting budget and a percentage of budget growth that I’m expecting.

So for example, if I own a consulting company, and I know the beginning of the year is typically tight budget wise, I can start with a low number - let’s say $100. And let’s say I know I’m going to grow at least 1% every month. AWS will use this information to fill in the data for my period of time, starting with $100 and ending with a compounded budget that accounts for my monthly 1% growth - in this case $111.57.

However, there may be times when you know your spending patterns will change over time, but you don’t know the exact percentage increase. So if you want to avoid having to update and maintain your budget yourself, you can choose the auto-adjusting option. 

This, as the name suggests, will adjust your budget automatically based on spending patterns over a time range that you specify. You can choose to base your budget on the forecast for the current month, your bill last month, your average spend over 6 months, or a custom time period. 

Since my account is new and I only have data for the past four months, I’m going to use the custom time period and select four months and click apply. Using this, it generates a budget amount for me - in this case it recommends $14 as my budget amount. 

If AWS chooses to increase this budget threshold for me, it will notify me through email that it did so. And I can always make updates and edit this budget if I need. 

Moving on to the budget scope, I can either choose to track costs from any services or filter based on specific resource attributes. With filters, you can get pretty advanced with how you configure your budgets. For example, EC2 instances for my development environment are often the most expensive part of my bill, so I might choose to add a filter to set a budget for my EC2 instances that are tagged with the tag value “dev”. 

However, since I want to monitor costs for my entire account, I’ll choose all services. As far as advanced options, you can choose how to aggregate your costs for your budget. You can choose between unblended, blended, or amortized costs. Additionally, you can also specify whether your budget includes credits, discounts, taxes and more.   

I’m going to leave these options on the default settings and click next.  From there, I can create my alert threshold where I can specify a percentage or an absolute value to trigger my alert. For example, I can choose to get notified when I reach the $10 value, or if I’ve spent 80% of my budget. Then I can choose if this is based on actual spend or forecasted. I’ll choose forecasted. If I’m forecasted to spend above 80% of my budget, it will notify me and then I can make changes before I’ve actually spent that money. 

Then, I can notify myself through email, or choose to integrate Amazon SNS or Amazon Chatbot alerts. 

I can also have multiple alert thresholds to receive additional notifications to have a better pulse on my spending at different times. I’ll leave it at one alert,  click next, ignore the Budget actions section for this video, and then I can finally click create budget. And I’m done. From there, AWS will monitor all activity in my account, and send me an email notification if I’m forecasted to spend 80% of my $15 budget.

About the Author

Alana Layton is an experienced technical trainer, technical content developer, and cloud engineer living out of Seattle, Washington. Her career has included teaching about AWS all over the world, creating AWS content that is fun, and working in consulting. She currently holds six AWS certifications. Outside of Cloud Academy, you can find her testing her knowledge in bar trivia, reading, or training for a marathon.