Private Networking for the Real-Time Context Engine in Confluent Cloud
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 enabling the feature. With private networking enabled, topics enabled with the Real-Time Context Engine might be accessible across environments and private network boundaries within your organization. This is a temporary limitation.
You can connect to the Real-Time Context Engine endpoint by using the following networking options:
The following table shows the endpoint patterns for different networking and cluster type combinations.
Networking |
DNS |
Cluster Type |
Endpoint |
|---|---|---|---|
PrivateLink |
Private |
Enterprise (PrivateLink Gateway) |
|
PrivateLink |
Private |
Dedicated |
|
PrivateLink |
Public |
Dedicated |
|
VPC Peering / Transit Gateway with /16 CIDR |
Public |
Dedicated |
|
VPC Peering / Transit Gateway with /27 CIDRs |
Public |
Dedicated |
|
Replace the following placeholders:
<region>: The AWS region of your cluster, for exampleus-west-2.<network_id>: Your Confluent Cloud network ID, for examplen-12345.<domain_id>: The ID portion of your network’s DNS domain, after the literaldomprefix 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 isdomzpyodm2g.us-west-2.aws.confluent.cloud, the<domain_id>iszpyodm2g.