Skip to main content
Version: User Guides (BYOC)

BYOC Overview
Private Preview

Bring Your Own Cloud (BYOC) is a deployment option for organizations to host applications and data in their own cloud accounts instead of using Zilliz Cloud's infrastructure. This solution is ideal for organizations with specific security requirements or regulatory compliance needs that require maintaining full data control sovereignty.

Why use Zilliz BYOC

Zilliz BYOC delivers a unique fully managed deployment option that lets you keep complete control over your data while eliminating operational overhead with the following benefits:

  • Operations

    • You can create BYOC projects and deploy the infrastructure on the Zilliz Cloud console.

    • You can use the well-tuned metrics and alert settings for monitoring your BYOC clusters in projects.

  • Scalability

    • You can always scale your BYOC projects by purchasing more licenses.

    • Clusters in BYOC projects are also scalable with manual and automatic scaling mechanisms.

  • Data management & security

    • Role-based access control (RBAC) at the organization, project, and cluster levels.

    • All data is securely stored and processed within your cloud accounts.

How it works

BYOC involves deploying Milvus alongside Zilliz-managed backend services, such as the upgrade workflow, resource scheduler, open API service, and web console, within your cloud environment, typically inside your own Virtual Private Cloud (VPC). This setup ensures that your data is stored and processed within your own infrastructure.

PCAOw33vKhCLHubzOiCciDDMnGg

According to the architecture outlined above, you need to provide a VPC, an S3 bucket, and the minimum permissions for Zilliz Cloud to start an EKS cluster and deploy the necessary components, such as the Milvus Operator, Import/Backup tools, the monitoring stack, including Grafana and Prometheus, and a Milvus instance on your behalf.

Additionally, Zilliz Cloud establishes two separate planes for communication with the components deployed in your VPC, and they are

  • Control Plane

    The control plane facilitates communication between Zilliz Cloud and the components deployed in your VPC for scheduling resources, upgrading Milvus instances, and providing access to the Zilliz Cloud console and control-plane open API services.

  • Data Plane

    The data plane allows communication between your applications/services and the Milvus instance deployed in your VPC, specifically for data storage and retrieval.

📘Notes

Zilliz BYOC is currently available in Private Preview. For access and implementation details, please contact Zilliz Cloud support.

Security assurance

Zilliz Cloud ensures secure communication across network boundaries through comprehensive encryption and strict access controls.

Network security

  • Internal Traffic: Full TCP/UDP communication within the cluster security group.

  • External Traffic: Encrypted outbound-only TCP connections on port 443 enable:

    • Connectivity to the Zilliz control plane.

    • Access to data sources and image repositories.

  • Same Security Group: TCP/UDP connections allowed for intra-cluster communication.

Access control

  • Secure VPN and, just-in-time, certificate-based authentication for Zilliz engineers.

  • Every access requires approvals and is logged for audits.

  • The control plane monitors and collects metrics through the outbound-only TCP connections.

These robust measures protect data integrity and confidentiality, ensuring secure and reliable operations in the cloud.

Encryption in transit

Client establish HTTPS or gRPC connections to the Zilliz Cluster. HTTPS/gRPC connections use the TLS 1.2 (or better) protocol with AES-256 (256-bit Advanced Encryption Standard ) to encrypt user data in transit.

Encryption at rest

The data plane of Zilliz Cloud encrypts the stored data on AWS S3 using the AES-256 (256-bit Advanced Encryption Standard ) encryption algorithm.

Cost management

Zilliz BYOC uses licenses to place charges on the services you consume. You still bear infrastructure expenses from cloud service providers and additional responsibilities like private networking.

The following figure shows the costs compared between Zilliz BYOC and SaaS subscriptions.

AJzswn6lAhsEl5bC4flcXAA4n6f