Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

Third Party Sub-processors

On this page

SingleStore Helios is deployed in the cloud provider of your choice. SingleStore does not directly host or process customer data. When you select to deploy in AWS, Azure, or GCP all data ingested into SingleStore Helios is hosted and processed by the third-party sub-processor (cloud provider) you choose and is stored within the geographic region of the deployment.

Since SingleStore does not directly host or store customer data outside of the sub-processor selected, if you have an existing arrangement with one or more cloud providers, you can migrate to SingleStore Helios without adding additional sub-processors to your existing legal or compliance processes.

Infrastructure and Data Sub-processors

Sub-processor

Purpose

Link

Amazon Web Services

Hosting services and storage

Amazon Web Services (AWS) Sub-processors

Azure

Hosting services and storage

Service Trust Portal

Google Cloud Platform

Hosting services and storage

Google Cloud Platform Subprocessors | Google Cloud

Below are the sub-processors used for support and communication (not customer data)

Zendesk

Customer support portal

Google Inc.

Email Support/documentation

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In