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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...