Splunk® App for AWS (Legacy)

Release Notes

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.

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-05-09 AWSAPP-910
 Lookup file unauthorized_errorCode.csv is outdated, causing incorrect unauthorized event counts in Security Overview and IAM Activity dashboards
2016-05-04 AWSAPP-888
 Monthly Billing report is not handled properly due to timezone issue.
2016-05-02 AWSAPP-878
 KVStore usage is growing to a noticeable size
2016-04-25 AWSAPP-827
 BotoClientError: When using SigV4, you must specify a 'host' parameter.
2016-04-24 AWSAPP-817
 SPL used to extract tags is not optimized for best performance.
2016-04-20 AWSAPP-800
 Performance issue: Long load time and difficult to choose specified item for in Folder/File name field in Create Page of S3 input
2016-04-08 AWSAPP-769
 Historical detailed billing shows inaccurate total
2016-03-24 AWSAPP-735
 Metadata doesn't support customized index
2016-03-08 AWSAPP-701
 App should warn user if some of the S3 billing files in the target bucket will not be ingested
2016-03-07 AWSAPP-699
 Wildcard option should be removed if user specifies customized option in CloudWatch input
2016-03-06 AWSAPP-698
 Historical detailed billing data in China Region cannot be displayed because data does not have a field named 'BlendedCost'
2016-03-03 AWSAPP-695
 Can't select dimensions by storage type when creating a CloudWatch input for S3
2016-02-29 AWSAPP-688
 App writes an incorrect data input file with multiple bucket names specified
2016-02-23 AWSAPP-678
 Performance issue for Historical Billing - "Cost by Account" and "Month over Month Comparison"
2016-02-19 AWSAPP-673
 Create account should be disabled in Metadata configure page to avoid confusion
2016-01-22 AWSAPP-608
 UI blocks user from creating multiple billing inputs with same account against same bucket
2015-12-24 AWSAPP-527
 AWS doesn't provide detail sourceIPAddress so that Notable CloudTrail Activity by Origin panel cannot display
Last modified on 24 May, 2016
Upgrade guide for the Splunk App for AWS   Known issues for the Splunk App for AWS

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

Acrobat logo Download manual
Acrobat logo Download this page

Was this topic useful?







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