All Apps and Add-ons

add-on for AWS: how to change the STS endpoint when adding an account in private subnet?

hyugma
Explorer

Hi Experts,

Question: Anyone know how to change the STS endpoint to private VPCe Interface address when adding an account to ADD-ON for AWS during setup?  

I am trying to deploy Splunk on a VM in private subnet (no route to the internet) in a VPC in AWS, and to index data on S3 (and more later). Currently, I have set up VPC endpoint (interface) for S3 and STS, and confirmed those 2 endpoints are accessible from the VM via an account from awscli.

When I tried to add an account in add-on Account setup, add-on actually tried to talk STS through public STS which the private network does not have route to. 
I would like to change add-on configuration to have the addon talk to private STS VPCe address to complete the setup/adding an account.

If there is another way to have splunk run in a private subnet, I would like to know about it.

Any comment would be appreciated..
Thank you! 

Labels (2)
0 Karma
1 Solution

hyugma
Explorer
0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...