Splunk® App for AWS (Legacy)

Release Notes

Acrobat logo Download manual as PDF


On July 15, 2022, the Splunk App for AWS will reach its end of life (EOL). After this date, Splunk will no longer maintain or develop this product. Splunk App for AWS is used for both IT monitoring and security use cases because it provides dashboards for both ITOps and security teams. The IT monitoring functionality in Splunk App for AWS is migrating to a content pack in Data Integrations called the Content Pack for Amazon Web Services Dashboards and Reports. The security use case functionality in Splunk App for AWS is migrating to the new Splunk App for AWS Security Dashboards. For more about migration options, see this community post.
This documentation does not apply to the most recent version of Splunk® App for AWS (Legacy). For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

The Splunk App for AWS Release Notes

These release notes apply to the Splunk App for AWS version 5.2.0.

For compatibility information, see Hardware and software requirements for the Splunk App for AWS.

New features

New feature or enhancement Description
AWS Cost and Usage Reports (CUR) for billing data The Splunk App for AWS supports AWS CUR to analyze billing data for your AWS account.


You can select to populate these billing dashboards and panels with AWS Cost and Usage Reports (CUR):

  • Budget Planner dashboard
  • Historical Monthly Bills dashboard
  • Historical Detailed Bills dashboard
  • Capacity Planner dashboard
  • Reserved Instance Planner dashboard
  • Reserved Instance Inventory (RI Utilization by Family in Last Month panel)
  • Topology dashboard (Billing layer)
  • Reserved Instance Planner Detail dashboard

If you do not have access to CUR, you can continue using Detailed Billing Reports (DBR) to monitor billing data.

When you set up a CUR input and start populating billing dashboards with CUR data, you can disable DBR inputs from the Splunk Add-on for Amazon Web Services. When you start populating billing dashboards with CUR data, the app no longer uses DBR data. If you want to view DBR data again, switch the billing report type.

To start monitoring CUR data in the Splunk App for AWS, see Specify the type of AWS billing data to monitor.

New knowledge objects The new knowledge objects support AWS CUR to analyze billing data for your AWS account.


There are two new saved searches:

  • Billing CUR: Billing Reports AssemblyId Generator
  • Billing CUR: Topology Billing Metric Generator

For more information about the saved searches, see Saved searches for the Splunk App for AWS. There are two new data models:

  • Detailed Billing CUR
  • Instance Hour CUR

For more information about data models, see Data models for the Splunk App for AWS. There is one new macro:

  • aws-billing-index-cur

For more information about macros, see Macros for the Splunk App for AWS.

Fixed issues

Date resolved Issue number Description
2019-05-29 AWSAPP-2032 The EC2 Insights Dashboard does not populate even when the required sourcetypes are available.
2019-05-27 AWSAPP-2127 A terminated resource displays in the Topology view.
2019-03-26 AWSAPP-2056 The Capacity Planner does not display data if the app is installed on Splunk Enterprise version 7.2.x.

For fixed issues relevant to accounts, inputs configuration, and knowledge management, see the Fixed issues for the Splunk Add-on for Amazon Web Services.

Known issues

Date filed Issue number Description
2021-01-19 AWSAPP-2602 "Config rules" dashboard dedup results in missing information
2019-10-03 AWSAPP-2206 A help link takes you to the wrong version of the app.
2019-08-25 AWSAPP-2160 Some accounts in the Splunk Add-on for Amazon Web Services don't populate in the app.
2019-08-21 AWSAPP-2156 There's a Capacity Planner: Data mismatch between Dashboard panels and the AWS Console.
2019-07-11 AWSAPP-2153 A warning message is visible on dashboards even after you disable it from the Configure dashboard.
2019-05-15 AWSAPP-2119 Capacity Planner (CUR): Value mismatch between panel data of Billing Legacy and Billing CUR.
2019-05-10 AWSAPP-2112 Historical Monthly Bills: Value mismatch in "Cost by Service" panel
2019-05-07 AWSAPP-2107 Billing CUR: Account Name is not visible in any of the dashboards or panels that use Billing (Cost and Usage Report) data.

For known issues relevant to accounts, inputs configuration, and knowledge management, see also Known issues for the Splunk Add-on for Amazon Web Services.

See also

To get started with the app, see the Installation and Configuration Manual.

For upgrade requirements, see Upgrade the Splunk App for AWS.

Last modified on 22 January, 2021
  NEXT
Credits for the Splunk App for AWS

This documentation applies to the following versions of Splunk® App for AWS (Legacy): 5.2.0

Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters