Private Cloud (BYOC)
Getting started with HoneyHive in your cloud environment.
Customers with high privacy & security requirements defer to hosting HoneyHive in their own infra.
We primarily support 2 ways to do custom cloud deployments
- BYOC to deploy HoneyHive’s Kubernetes cluster in a pre-configured Cloud account (AWS, GCP, Azure)
- BYOVPC to deploy HoneyHive’s Kubernetes cluster in a pre-configured VPC
Please refer to our Platform Architecture to understand the different components of HoneyHive.
Supported Kubernetes providers
Our private cloud offering is currently available for the following Kubernetes providers:
- AWS EKS
- GCP GKE
- Azure AKS
- RKE
- OpenShift
We are also open to adding support for other Kubernetes providers if necessary.
Getting started via Private Cloud
We support automated BYOC deployments for all 3 major cloud providers - AWS, GCP & Azure.
The steps below are a high-level overview of the process to install HoneyHive’s BYOC. In case you are interested in this deployment model, please reach out to us at support@honeyhive.ai to get started.
Expected time to get started: 1-4 weeks (depending on customizations)
A network architecture and data flow review call
We will present our Terraform, Network Architecture & Data Flow diagram for the BYOC deployment to your Cloud Security team.
The objective of this call is to ensure
- Our network architecture is compliant with your network security policies
- The data flow, encryption policies, and retention policies are compliant with your data security policies
- Make sure we have access to all the resources we need to deploy HoneyHive
Expected time: 1-2 hours
A HELM chart review call
We present our HELM charts and CRDs for the BYOC deployment to your Cloud Infrastructure team.
The objective of this call is to ensure
- Our HELM charts are compliant with your kubernetes namespace & RBAC policies
- Our CRDs are compliant with your internal policies
- We have adequate machine resources to deploy HoneyHive
Expected time: 1-2 hours
Wait for customizations
We apply any customizations to the Terraform, HELM charts and CRDs to ensure they are compliant with your policies.
In the case of BYOVPC, we will also configure the VPC peering connection for the new account.
Expected time: 1-4 weeks (depending on the complexity of the customizations)
Deploy HoneyHive's Kubernetes cluster
We deploy HoneyHive’s Kubernetes cluster in your Cloud account.
We will share the cluster details and maintanence scripts with you alongside.
Expected time: 2-4 hours
Configure the VPC peering connection
Configure the VPC peering connection for the new account.
Expected time: 1-2 hours
Integrate SAML
We integrate SAML with your HoneyHive deployment to ensure your users can login to HoneyHive using your SAML identity provider.
Expected time: 2-4 hours
Congratulations, now you have a private HoneyHive deployment with restricted network access in your cloud.
Self-Hosting Maintenence
Once deployed, we abide by a standard 24x5 SLA support policy. You can find more details on our Incident Response Policy in our trust center
In order to expedite support, we provide you with automated troubleshooting and upgrade scripts which you can run at your own convenience.