Bit of an old post but I had this exact error, spent way too long troubleshooting it, and was saddened when this post didnt have an accepted solution. The problem is, the s3 vpc endpoint you are using DOES NOT match the supported format Splunk expects.  Then, when it tries to do hostname validation (s3 VPC endpoint) against the expected format, it fails and throws this ugly error. you said: "As part of the Splunk AWS Add-on naming convention for private endpoints, the Private Endpoint URL for the S3 bucket must be https://vpce-<endpoint_id>-<unique_id>.s3.<region>.vpce.amazonaws.com" This isnt true, as the docs explain.  You actually need to use: Thus, the format for S3 is actually https://bucket.vpce-<endpoint_id>-<unique_id>.s3.<region>.vpce.amazonaws.com.  I didnt read the documentation closely enough and wasted a lot of time.. so I hope this helps someone.   ... View more

@buddhaeyes1Its not as inuitive as the classic way of linking searches.. but you actually need to link to a URL.  Then you need to URL encode the search.  For example, if I wanted to search the windows index whenever I click on a table value, I would add: This is also documented on the answers here: https://community.splunk.com/t5/Dashboards-Visualizations/Cloud-Dashboard-Studio-What-is-the-correct-way-to-Link-to-custom/m-p/580479 ... View more

As others have pointed out, the openssl library can of course be used.  But, if you wanted to specifically hit the openssl binary from Splunk:     /opt/splunk/bin/splunk cmd openssl x509 -enddate -noout -in <PATH TO CERTIFICATE>     ... View more