Configure Config inputs for the Splunk Add-on for AWS
Configure the Splunk Add-on for AWS to ingest Config inputs.
Best practices for configuring inputs
- Configure SQS-based S3 inputs to collect AWS data.
- Configure an AWS Config input for the Splunk Add-on for Amazon Web Services on your data collection node through Splunk Web. This data source is only available in a subset of AWS regions, which does not include China. See the AWS documentation for a full list of supported regions.
- Configure a single enabled Config modular input for each unique SQS. Multiple enabled modular inputs can cause conflicts when trying to delete SQS messages or S3 records that another modular input is attempting to access and parse.
- Disable or delete testing configs before releasing your configuration in production.
Configure AWS services for the Config input
The Splunk Add-on for AWS collects events from a Simple Queue Service (SQS) that subscribes to the Simple Notification Service (SNS) notification events from AWS Config. Configure AWS Config to produce SNS notifications, and then create the SQS that the add-on can access. For more information about AWS Config, see the AWS Config documentation.
- Enable AWS Config by following the AWS Config setup guide.
- Specify a new S3 bucket to save the data and an SNS Topic to which Splunk software will stream Config notifications. Do not use an existing bucket or SNS.
- Verify that you have successfully completed the setup process. If you used the AWS console, the Resource Lookup page displays.
- Create a new SQS.
- Subscribe the SQS exclusively to the SNS Topic that you created in Step 2.
- Grant IAM permissions to access the S3 bucket and SQS to the AWS account that the add-on uses to connect to your AWS environment.
Configure a Config input using Splunk Web
To configure inputs using Splunk Web, click Splunk Add-on for AWS in the left navigation bar on Splunk Web home, then click Create New Input > Config > Config. Fill out the fields as described in the table:
|Field in Splunk Web||Description|
|AWS Account||The AWS account or EC2 IAM role the Splunk platform uses to access your Config data. In Splunk Web, select an account from the drop-down list.|
|AWS Region||The AWS region that contains the log notification SQS queue. Enter the region ID. See the AWS documentation for more information.|
|SQS queue name||The name of the queue to which AWS sends new Config notifications. Select a queue from the drop-down list, or enter the queue name manually. The queue name is the final segment of the full queue URL. For example, if your SQS queue URL is |
|Source type||A source type for the events. Enter a value only if you want to override the default of |
Note that the Splunk platform indexes AWS Config events using three variations of this source type:
|Index||The index name where the Splunk platform puts the Config data. The default is main.|
|Interval||The number of seconds to wait before the Splunk platform runs the command again. Default is 30 seconds.|
Configure a Config input using configuration files
To configure inputs manually in
inputs.conf, create a stanza using the following template and add it to
$SPLUNK_HOME/etc/apps/Splunk_TA_aws/local/inputs.conf. If the file or path does not exist, create it.
[aws_config://<name>] aws_account = <value> aws_region = <value> sqs_queue = <value> interval = <value> sourcetype = <value> index = <value>
Some of these settings have default values that can be found in
[aws_config] aws_account = sourcetype = aws:config queueSize = 128KB persistentQueueSize = 24MB interval = 30
The values above correspond to the default values in Splunk Web as well as some internal values that are not exposed in Splunk Web for configuration. If you choose to copy this stanza to
/local and use it as a starting point to configure your
inputs.conf manually, change the stanza title from
aws_config://<name> and add the additional parameters that you need.
Configure inputs for the Splunk Add-on for AWS
Configure Config Rules inputs for the Splunk Add-on for AWS
This documentation applies to the following versions of Splunk® Supported Add-ons: released