The AWS Cost sensor monitors the costs of an Amazon Web Services (AWS) account by reading its data from the AWS Cost Explorer API.

The sensor can show the following:

  • Monthly and yearly costs
  • Forecasts for monthly and yearly costs
  • Unblended and net unblended costs, monthly and yearly
  • Forecast for unblended and net unblended costs, monthly and yearly
  • Amortized and net amortized costs, monthly and yearly
  • Forecast for amortized and net amortized costs, monthly and yearly
AWS Cost Sensor

AWS Cost Sensor


  • icon-betaThis sensor is in beta status. The operating methods and the available settings can change at any time. Do not expect that all functions work properly, or that this sensor works as expected at all. Be aware that this sensor can be removed from PRTG at any time.
  • Requires the AWS Cost Explorer to be activated in your AWS account.
  • Requires IAM User and Role Access to Billing Information enabled in your AWS account.
  • Requires Credentials for AWS in the settings of the parent device or group.
  • Requires permissions for the API Key.
  • After sensor setup, the first data is available after 24 hours. Forecast data is available after a few days.
  • The minimum scanning interval for this sensor is 6 hours.
  • Amazon charges you for each API call that the sensor sends to the Amazon servers.
  • You can only set up this sensor on a local probe device.
  • You can only set up this sensor for one AWS account per PRTG installation.
  • Knowledge Base: Where do I find Amazon documentation related to the AWS Cost sensor?

Requirement: Permissions for the API Key

The API Key needs the following permissions:

  • "ce:GetCostAndUsage",
  • "ce:GetCostForecast",
  • "ce:GetDimensionValues",
  • "ce:GetCostAndUsageWithResources",
  • "ce:GetUsageForecast"

Add Sensor

The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the setting fields that are required for creating the sensor. Therefore, you do not see all setting fields in this dialog. You can change (nearly) all settings in the sensor's Settings tab later.

Sensor Settings

Click the Settings tab of a sensor to change its settings.

icon-i-round-blueUsually, a sensor connects to the IP Address or DNS Name of the parent device on which you created the sensor. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings. See below for details on available settings.

Basic Sensor Settings

Sensor Name

Enter a meaningful name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

Parent Tags

Shows tags that this sensor inherits from its parent device, group, and probe. This setting is shown for your information only and cannot be changed here.


Enter one or more tags, separated by spaces or commas. You can use tags to group sensors and use tag–filtered views later on. Tags are not case sensitive. We recommend that you use the default value.

There are default tags that are automatically predefined in a sensor's settings when you add a sensor. See section Default Tags below.

You can add additional tags to the sensor if you like. Other tags are automatically inherited from objects further up in the device tree. These are visible above as Parent Tags.

icon-i-round-blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).


Select a priority for the sensor. This setting determines where the sensor is placed in sensor lists. A sensor with a top priority is at the top of a list. Choose from one star (low priority) to five stars (top priority).

AWS Cost Specific

Additional Cost Types

PRTG creates two default channels for blended monthly and yearly costs. If you enable this option, you can select additional cost types for which PRTG creates additional channels.

Select Additional Cost Types

This field is only visible if you select Enabled as Additional Cost Types setting above. Select additional cost types. PRTG creates two overview channels (monthly and yearly) for every additional cost type that you select.

Additional Forecast Types

PRTG does not automatically create additional forecast channels. If you enable this option, you can select additional forecast types to create additional forecast channels.

Select Additional Forecast Types

This field is only visible if you select Enabled as Additional Types for Costs setting above. Select additional forecast types. PRTG creates two overview channels (monthly and yearly) for every additional forecast type that you select. Every selected forecast type creates additional fees. Deselect a forecast type if you no longer want the according channels to create additional fees. You can still see the channels, but they do not receive data anymore.

Debug Options

Sensor Result

Define what PRTG does with the sensor results:

  • Discard sensor result: Do not store the sensor result.
  • Write sensor result to disk (file name: Result of Sensor [ID].txt): Store the last result received from the sensor to the \Logs\sensors subfolder of the PRTG data directory on the probe system (master node, if in a cluster). File names: Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This is for debugging purposes. PRTG overwrites these files with each scanning interval.

icon-prtg-on-demandThis option is not available when the sensor runs on the hosted probe of a PRTG hosted by Paessler instance.

Sensor Display

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

icon-i-round-blueYou can set a different primary channel later by clicking the pin symbol of a channel on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    icon-i-round-blueThis option cannot be used in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This field is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Edit Channels

To change display settings, spike filtering, and limits, switch to the sensor's Overview tab and click the gear icon of a specific channel. For detailed information, see section Sensor Channel Settings.

Notification Triggers

Click the Notification Triggers tab to change notification triggers. For detailed information, see section Sensor Notification Triggers Settings.


For more general information about settings, see section Object Settings.

Sensor Settings Overview

For information about sensor settings, see the following sections: