Private Networking for Lightning Tables in Confluent Cloud

You can query a Lightning Table over a private network through an HTTP API or with the Java Database Connectivity (JDBC) driver. You can also query it with a Model Context Protocol (MCP) client through the Real-Time Context Engine MCP endpoint.

To connect, use the associated private endpoint instead of the public endpoint. You can’t run queries in the Confluent Cloud Console or with the Confluent CLI over a private network.

Private networking for the API

You can query a Lightning Table through the API by using the following private networking options on AWS:

  • Private Network Interface (PNI)

  • Multi-environment PrivateLink Attachment through an ingress PrivateLink Gateway

  • The original PrivateLink Attachment, which the ingress PrivateLink Gateway replaced

For more information about these options, see Use Private Network Interface on Confluent Cloud and Use AWS PrivateLink for Serverless Products on Confluent Cloud.

If you use PNI, Confluent Cloud creates the endpoint in your environment after you set up a PNI gateway and access point. You don’t configure a domain name. For the port, security group, and DNS considerations that apply to all services over PNI, see Access services over PNI.

The following table shows the private API endpoint for each networking option.

Networking option

Endpoint

PNI

sql-<access_point_id>.<region>.aws.accesspoint.glb.confluent.cloud

Ingress PrivateLink Gateway

sql-<access_point_id>.<region>.aws.accesspoint.glb.confluent.cloud

Original PrivateLink Attachment

sql.<region>.aws.private.confluent.cloud

Replace the following placeholders:

  • <access_point_id>: The ID of your access point, without the hyphen. The Cloud Console shows the access point ID on the networking page for your environment. For example, if the access point ID is ap-abc123xyz, use apabc123xyz.

  • <region>: The AWS region of your cluster, for example us-west-2.

For example, for an access point with the ID ap-abc123xyz in the us-west-2 region, the endpoint is sql-apabc123xyz.us-west-2.aws.accesspoint.glb.confluent.cloud.

The JDBC driver connects through the same private API endpoints. For more information, see Query a Lightning Table with JDBC in Confluent Cloud.

Private networking for MCP

An MCP client queries a Lightning Table through the Real-Time Context Engine. The Real-Time Context Engine supports private networking on AWS.

Warning

Cross-environment and cross-network access

Review your private network topology and environment isolation model before you use MCP over a private network. With private networking enabled, Lightning Tables that you query with MCP might be accessible across environments and private network boundaries within your organization.

You can connect to the Real-Time Context Engine endpoint by using the following networking options:

The following table shows the endpoint patterns for each combination of networking option and cluster type.

Networking option

DNS

Cluster type

Endpoint

AWS PrivateLink

Private

Enterprise (PrivateLink Gateway)

mcp.<region>.aws.private.confluent.cloud

AWS PrivateLink

Private

Dedicated

mcp.dom<domain_id>.<region>.aws.confluent.cloud

AWS PrivateLink

Public

Dedicated

mcp-<network_id>.<region>.aws.glb.confluent.cloud

VPC peering or Transit Gateway with /16 CIDR

Public

Dedicated

mcp-<network_id>.<region>.aws.confluent.cloud

VPC peering or Transit Gateway with /27 CIDRs

Public

Dedicated

mcp-<network_id>.<region>.aws.glb.confluent.cloud

PNI

Public

Enterprise, Freight

mcp-<access_point_id>.<region>.aws.accesspoint.glb.confluent.cloud

Replace the following placeholders:

  • <region>: The AWS region of your cluster, for example us-west-2.

  • <access_point_id>: The ID of your PNI access point, without the hyphen. For example, if the access point ID is ap-abc123xyz, use apabc123xyz.

  • <network_id>: Your Confluent Cloud network ID, for example n-12345.

  • <domain_id>: The ID portion of your network’s DNS domain, after the literal dom prefix and before the first dot (.). Find the DNS domain value under Networking > Details for your Confluent Cloud network in the Confluent Cloud Console. For example, if the DNS domain is domabc123de.us-west-2.aws.confluent.cloud, the <domain_id> is abc123de.