Skip to main content

Deployment Guide: Ververica Cloud: Bring Your Own Cloud

info

Ververica recommends reviewing About BYOC before deploying Ververica Cloud: Bring Your Own Cloud. It covers several important factors for you to consider, including:

  • Is this the right option for your needs?
  • What are the core components of the BYOC framework
  • What is the security model and how can it help with a Zero Trust design?
  • What are the operational responsibilities for BYOC?

This guide walks you through deploying Ververica Cloud: Bring Your Own Cloud on an Amazon EKS cluster. By the end of the guide, you will have a Ververica Agent installed and running on your cluster and be able to create new BYOC workspaces that use your own AWS environment.

How to Use This Guide​

  1. Architecture Overview

    • Get a high-level understanding of how the BYOC Agent (Pyxis) communicates with Ververica Cloud.
    • See how Workspace Agents are created and how Flink jobs are managed inside your own Kubernetes environment.

  2. Prerequisites

    • Infrastructure Requirements: Ensure your EKS cluster meets the minimum version, capacity, and operating system requirements.
    • IMDS Access: Verify IMDSv1 is available on your worker nodes.
    • Network Requirements: Whitelist (allow outbound traffic) to agent.ververica.cloud, app.ververica.cloud, registry.ververica.cloud, and cdn.ververica.cloud.
    • IAM Setup: Make sure you have the correct IAM roles, permissions, and S3 bucket configurations, if not using the CloudFormation script.

  3. Create AWS Resources

    • Configure IAM roles, policies, and an S3 bucket for Flink artifacts using either an automated CloudFormation script or a manual setup.
    • Enable Kubernetes OIDC (IRSA) to manage the Ververica Agent.

  4. Install and Configure the Ververica Agent

    • Link your Ververica account with AWS Marketplace and subscribe to the BYOC product.
    • Install the Ververica Agent (Pyxis) using Helm and verify its registration in the Ververica Portal.
    • Create a new BYOC workspace, and uninstall the Agent if needed.

Once these steps are complete, you can run your Flink workloads in your own AWS environment while maintaining central control and visibility via Ververica Cloud.

On this page