AWS Console Guide

This page provides a complete guide to using the AWS section of the Bill Watch Console. You’ll find a breakdown of each tab and field involved in creating and managing AWS Watches, along with descriptions of monitoring dimensions, metrics, and watch list details. Use this guide to understand how Bill Watch tracks AWS usage and detects anomalies effectively.

What Is Amazon Web Services (AWS)?

Describe what AWS is in simple, clear terms. Include a brief overview of its core services, its importance in cloud infrastructure, and why many organizations rely on it.

 

The Challenge in AWS Cost Monitoring

Explain the difficulties users often face when trying to understand and track their AWS costs—such as data fragmentation, sudden cost spikes, limited native tools, or lack of anomaly detection.

 

How Bill Watch Solves the Problem

Summarize how Bill Watch addresses the cost monitoring challenges in AWS. Highlight features like Watch configuration, anomaly detection, customizable rules, and actionable notifications.

 

 

Overview of AWS Watch Fields and Options

Below is a brief introduction to the fields and options you will encounter when creating an AWS Watch in Bill Watch. Each entry corresponds to an element or parameter you must configure; understanding these definitions will help you complete the setup accurately and know how each component affects monitoring behavior and reporting.

• ID

• User ID

• Workspace ID

• Credential ID

• Account ID

• Topic ID

• Log Group ID

• Name

• Active

• Show API Call

• Show New Cost

• Max API Call Total

• Max API Call Per Operation

• Description

• Active

• Credential ID (Link to Credential Console Guide)

• Topic ID (Link to Notification Sender Console Guide)

• Log Group ID (Link to Log Console Guide)

• Name

• Description

• Show API Call

• Show New Cost

• Max API Call Total

• Max API Call Per Operation

• (Refer to the Create Rule section on the Rule Console Guide page for full rule definition)

• Lookback Periods (multi-select)

• By Region

• By Service

• By Instance Type

• By Usage Type

• By Availability Zone (Az)

• By Platform

• By Purchase Type

• By Tenancy

• By Operation

• By Record Type

Note: When combining two dimensions (e.g., Region and Platform), AWS may trigger additional API calls, increasing monitoring cost.

• All

• Unblended Cost

• Blended Cost

• Amortized Cost

• Net Amortized Cost

• Net Unblended Cost

• Last Run At

• Last Run Status

  • NotStarted

  • Processing

  • Scheduled

  • Deactive

  • Failed

  • Successed

• Last Run Anomaly Found

• Last Run Message

• Next Run At

• Created At

• Updated At