Skip to main content

How BYOC Works

The Ververica Cloud: Bring Your Own Cloud deployment enables you to run Apache Flink workloads in your own Kubernetes environment (such as Amazon EKS), while centrally managing and monitoring those workloads through the Ververica Cloud Control Plane.

The key components of the BYOC framework are:

  • Ververica Cloud Control Plane: The centralized service that handles user interactions, job orchestration, and monitoring.
  • Ververica Agent (Pyxis): A specialized controller deployed in your Kubernetes cluster. It maintains a secure, outbound-only connection to Ververica Cloud and orchestrates Workspace Agents.
  • Workspace Agent: A dedicated agent within each workspace. It manages lifecycle operations (create, update, delete) for Flink jobs and monitors their status.
  • Flink Jobs: The actual stream processing or batch jobs running on Kubernetes infrastructure. These jobs access data sources, sinks, or other resources within your own cloud environment.
  • Data Stores: This includes systems like Amazon S3, Kafka, relational databases, or other services reachable from your Kubernetes cluster. Connectivity may be established via direct access, VPC peering, or private links.

In this architecture, you install Ververica Agent (also referred to as “Pyxis”) on your Kubernetes cluster to communicate with Ververica Cloud. The diagram and description below illustrate how the various components interact.

image