Hi @ajac
My understanding is that SmartStore implements SSE‑C by generating a per‑object data‑encryption key (DEK) using the customer‑managed CMK. The Smartstore service never stores the plaintext key; the key is only supplied by the client on each read/write request, encrypted by KMS, this protection model is same as SSE‑C (the client controls the keys), but the actual key payload is managed by KMS.
Customer Managed Keys (CMK) is available in Splunk Cloud AWS / Google Cloud environments but not Azure (see https://help.splunk.com/en/splunk-cloud-platform/get-started/service-terms-and-policies/10.0.2503/in...)
Check out the https://help.splunk.com/en/splunk-cloud-platform/administer/manage-users-and-security/9.3.2408/manag... EMEK page for more information on this but to answer your question, yes, you can manage the key yourself and share access to it through AWS IAM Policies so that Splunk Cloud can consume it.
Its worth discussing this with your Splunk account team if you need further lower level detail as they may be able to share more under your NDA agreement etc.
🌟 Did this answer help you? If so, please consider:
- Adding karma to show it was useful
- Marking it as the solution if it resolved your issue
- Commenting if you need any clarification
Your feedback encourages the volunteers in this community to continue contributing
