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
| Date resolved | Issue number | Description |
|---|---|---|
| 2016-06-23 | AWSAPP-1002 | Config page is showing unexpected error if the underlying CloudWatch configuration is incorrect |
| 2016-06-16 | AWSAPP-1004 | Configuration endpoint for govcloud is inaccessible |
| 2016-06-16 | AWSAPP-1015 | Out of N reserved instances is always 0 in EC2 Instances Dashboard |
| 2016-06-16 | AWSAPP-1014 | SQS list is empty in CloudTrail configure even it has been setup in AWS side |
| 2016-06-07 | AWSAPP-957 | Historical detailed billing data does not include items without an Operation field, so totals do not include one-time costs |
| 2016-05-26 | AWSAPP-968 | Log groups are truncated in AWS VPC Flow Log configuration |
For fixed issues relevant to accounts, input configuration, and knowledge management, see the Fixed issues for the Splunk Add-on for Amazon Web Services.
Last modified on 31 August, 2017
| 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.1
Download manual
Feedback submitted, thanks!