Hi, I was excited to see edge processor has been made available in Splunk enterprise on-prem - this will be super handy for one of our installations where cloud isn't an option. In spiking a PoC however, I noticed that the S3 destinations are _only_ able to speak to AWS - there is no way to use a custom endpoint URL, so no way to send to our own S3-compatible object store.  I had a good look at the deployed config and API calls, and there is no endpoint configured anywhere there, so it appears to be baked into the code.  Am I right about that? We're using Splunk enterprise because cloud services aren't possible for this deployment - naturally that includes AWS as well as Splunk cloud, so suddenly edge became a whole lot less useful for us. Does anyone know if this limitation is by design, and will it be changed in the near future? I suspect this is actually a pretty big limitation for a lot of on-prem edge users and quite a surprising omission.  I'm keen to find out what the deal is! ... View more