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.
Download topic as PDF
Fixed issues for the Splunk App for AWS
For fixed issues relevant to accounts, input configuration, and knowledge management, see also Fixed issues for the Splunk Add-on for Amazon Web Services.
Date resolved | Defect number | Description |
2016-02-26 | AWSAPP-675 | Historical Billing - "Cost by Account" and "Month over Month Comparison" are not accurate. |
2016-02-24 | AWSAPP-409 | Dashboards are not organized correctly. |
2016-02-24 | AWSAPP-680 | Authentication error when configuring a new account implies incorrect credentials when problem could be insufficient permissions. |
2016-02-23 | AWSAPP-677 | Using time filter in sub search causes incorrect TotalCost calculation |
2016-02-19 | AWSAPP-670 | Alerts are not listed on app's Alerts page. |
2016-02-17 | AWSAPP-643 | Estimated billing macro does not work when timezone < 0. |
Last modified on 26 February, 2016
PREVIOUS Upgrade guide for the Splunk App for AWS |
NEXT Known issues for the Splunk App for AWS |
This documentation applies to the following versions of Splunk® App for AWS (Legacy): 4.1.1
Feedback submitted, thanks!