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
Known issues for the Splunk App for AWS
Date filed | Issue number | Description |
---|---|---|
2017-08-23 | AWSAPP-1904 | Not able to add the AWS account, ERROR : Unexpected Error occurs. Unexpected error "" from python handler: "timed out". See splunkd.log for more details. |
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-12-26 | AWSAPP-1590, ADDON-12905 | unsupported regions get listed in TA after creating Description from APP |
2016-12-12 | AWSAPP-1565 | Timezone issue: Historical Monthly Bills searches for events outside specified time range |
2016-12-12 | AWSAPP-1566 | AWS AssumeRole not supported in the current release |
2016-11-22 | AWSAPP-1513 | VPC Flow Logs Summary Generator: Potential performance bottleneck in Src IP command.prestats in the event of large data variations |
2016-11-22 | AWSAPP-1515 | Data models currently do not support role-based access control |
2016-11-21 | AWSAPP-1511 | In Splunk Light, the app icon and list are not displayed under the Configure menu |
2016-11-20 | AWSAPP-1505 | Billing Topology Billing Metrics Generator should use data model summary index rather than raw events |
2016-11-10 | AWSAPP-1472 | In Splunk Light, Insights dashboards are not supported but Insights menus are still available in the search page |
2016-11-08 | AWSAPP-1463 | Undesirable performance in the search for Cloudtrail user activity data to feed the dashboard |
2016-10-13 | AWSAPP-1317 | Topology dashboard rendering is slow when there are a large number of resources to display |
2016-08-10 | AWSAPP-1083 | Monthly billing data takes a long time to load when the amount of data is huge |
2016-05-10 | AWSAPP-921 | When user-defined custom tags in AWS are identical to pre-defined filters in the Splunk App for AWS, the Group By filer produces duplicate values |
2016-05-10 | AWSAPP-924 | Becuase the tags filter does not support display names, special characters are replaced with underscores (_), and names are truncated at 32 characters |
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 13 August, 2022
PREVIOUS Fixed issues for the Splunk App for AWS |
NEXT Credits for the Splunk App for AWS |
This documentation applies to the following versions of Splunk® App for AWS (Legacy): 5.0.0
Feedback submitted, thanks!