All Apps and Add-ons

Inspector input in Splunk Add-on for AWS in GovCloud

tgrogan_dc
New Member

Does anyone have a workaround for getting the "This service not available in your account" message when attempting to add an AWS Inspector input in AWS GovCloud?

I know this service was not previously available, and am presuming this error is being generated from within the Splunk Add-on code and not as a result of an actual REST query. Inspector is now available in GovCloud and an endpoint is available, which I've attempted unsuccessfully to add to the endpoints.json file.

The service is available from the CLI but even when the same keys are added to the Add-on and that account is selected in the input configuration screen, the error still comes up.

Any help is greatly appreciated.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...