Hello, As suggested in my previous answer, no changes are required on your end, untill explicity requested from your network team. Here are the steps for you to follow: Changes needed on AWS end 1. You, as the SIEM admin and owner of the tool, will consult your sysops network team, putting the requirement in front of them about exposing your application URL to public. (Basically the team which manages the networking part of your organization) 2. Based on your requirements, they'll decide the best way to expose the URL public. (will either be VPC peering, or Privatelinks over ALB etc, based upon the architecture of your organization). Please note, none of these changes are to be made by you. Network team will do it. 3. Once the step up will be done. You'll get a private URL, which you can share with your customers to use Splunk over the internet. Changes needed on Splunk end: 1. Depends upon the requirements of the network team and the architecture of your organization. Whatever path they choose to expose the Splunk's URL to public, they'll give you specific instructions to perform on Splunk server, if required. Till then, all you need to do is contact them and have them do the work for you. Summary: Please contant your sysops network team and put the request to them about exposing a URL for splunk in public with your decided name for it. They are the ones, who will fulfill your requirement. Since this requires changes on VPC and ALB. Hope this helps 🙂
... View more
