Use Private Networking with Tableflow in Confluent Cloud

You can use Tableflow on Confluent Cloud clusters that are deployed in private networks, ensuring that no data is transmitted over the public internet.

Private networks on AWS

You can use Tableflow on Confluent Cloud clusters that are located in any of the following private network options.

The traffic between Tableflow and your S3 storage is transmitted securely through Gateway VPC Endpoints, ensuring that data remains within the AWS private network and does not traverse the public internet.

AWS Glue Catalog integration is enabled through Interface VPC Endpoints, ensuring that metadata communication occurs securely within private networks without exposure to the public internet.

Limitations

  • The Apache Iceberg™ REST Catalog is not supported in private networking-enabled clusters, so you must use external catalog integrations like AWS Glue Data Catalog.
  • You can’t use Confluent-managed storage in Private Network-enabled clusters.
  • The catalog integrations, like Snowflake Open Catalog/Apache Polaris, are not supported via private networking.

Related content

Note

This website includes content developed at the Apache Software Foundation under the terms of the Apache License v2.