All Apps and Add-ons

Can the Splunk Add-on for AWS forward to a non-default indexer cluster?

scombs
Path Finder

Is it possible to forward different Splunk Add-on for AWS inputs to different indexer clusters?   We have a heavy forwarder using Splunk_TA_aws and standard defaultGroup=<clusterlabel>, indexerDiscovery, etc configured in etc/system/local/outputs.conf.  At present, all the AWS inputs are forwarded to indexes contained within the default indexer cluster.  However, we now have an AWS input which we want to forward to an index in a different indexer cluster.  Are there options within either the etc/apps/Splunk_TA_aws/local/ or other .conf files that will allow us to, say, add a second [tcpout:Cluster2] stanza into outputs.conf and then forward  events from this new AWS input to it?

Labels (1)
Tags (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

i haven’t do it with AWS TA, but I suppose that you could do it with these instructions https://docs.splunk.com/Documentation/SplunkCloud/latest/Forwarding/Routeandfilterdatad

r. Ismo

scombs
Path Finder

Thanks r.

I didn't try your solution, but another colleague got it working with the following configuration.

 

 

../etc/system/local/outputs.conf
[indexer_discovery:first_cluster_label]
master_uri = https://mm.mm.mm.mm:8089
passSymmKey = $asdfasfasdfasfasdfasdfas=
. . .
[indexer_discovery:second_cluster_label]
master_uri = https://nn.nn.nn.nn:8089
passSymmKey = $zxcvzxcvzxcvzxcvzxcvzxcv=
. . .
[tcpout:FirstClusterName]
autoLBFrequency = 30
indexerDiscovery = first_cluster_label
. . .
[tcpout:SecondClusterName]
autoLBFrequency = 30
indexerDiscovery = second_cluster_label
. . .
[tcpout]
defaultGroup = FirstClusterName
. . .


../etc/apps/Splunk_TA_aws/inputs.conf
[aws_sqs_based_s3://First_SQS_S3_Import]
# Uses defaultGroup.
. . .
[aws_sqs_based_s3://Second_SQS_S3_Import]
_TCP_ROUTING = SecondClusterName
. . .

 

 

 

 

0 Karma

isoutamo
SplunkTrust
SplunkTrust
This is exactly the same solution what I propose. It’s even better learning experience that you are solving it by yourself;-)
Happy splunking!
0 Karma
Get Updates on the Splunk Community!

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...

Splunk Observability Cloud | Enhancing Your Onboarding Experience with the ...

We understand that your initial experience with getting data into Splunk Observability Cloud is crucial as it ...