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.
Known issues for the Splunk App for AWS
| Date filed | Issue number | Description |
|---|---|---|
| 2017-03-07 | AWSAPP-1729 | Topology - Playback stopped working due to reaching session storage limits in case of too many changes. |
| 2017-02-08 | AWSAPP-1670 | When there are very few billing items under one account, the calculated total cost of one-time payments is not accurate. |
| 2017-02-06 | AWSAPP-1668 | The behavior of Party.js collecting hostnames is unnecessary and should be stopped. |
| 2017-01-31 | AWSAPP-1664 | Detailed monthly billing data is inaccurate across different time zones. |
| 2016-01-13 | AWSAPP-568 | AWS lookups aren't populated when the add-on is on a separate instance than the app. |
| 2015-12-08 | AWSAPP-479 | The calculation for reserved instance count is incorrect |
For known issues relevant to accounts, input configuration, and knowledge management, see also Known issues for the Splunk Add-on for Amazon Web Services.
Last modified on 19 January, 2018
| Fixed issues for the Splunk App for AWS | Credits for the Splunk App for AWS |
This documentation applies to the following versions of Splunk® App for AWS (Legacy): 5.0.1
Download manual
Feedback submitted, thanks!