<a id="rtce-private-networking"></a>

# 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:

- [VPC Peering](../../networking/peering/aws-peering.md#cloud-networking-peering-aws)
- [AWS PrivateLink](../../networking/aws-privatelink-overview.md#cloud-networking-aws-privatelink-overview)
- [AWS Transit Gateway](../../networking/aws-transit-gateway.md#aws-transit-gateway)

The following table shows the endpoint patterns for different
networking and cluster type combinations.

| Networking                                   | DNS     | Cluster Type                     | Endpoint                                            |
|----------------------------------------------|---------|----------------------------------|-----------------------------------------------------|
| PrivateLink                                  | Private | Enterprise (PrivateLink Gateway) | `mcp.<region>.aws.private.confluent.cloud`          |
| PrivateLink                                  | Private | Dedicated                        | `mcp.dom<domain_id>.<region>.aws.confluent.cloud`   |
| PrivateLink                                  | Public  | Dedicated                        | `mcp-<network_id>.<region>.aws.glb.confluent.cloud` |
| VPC Peering / Transit Gateway with /16 CIDR  | Public  | Dedicated                        | `mcp-<network_id>.<region>.aws.confluent.cloud`     |
| VPC Peering / Transit Gateway with /27 CIDRs | Public  | Dedicated                        | `mcp-<network_id>.<region>.aws.glb.confluent.cloud` |

Replace the following placeholders:

- `<region>`: The AWS region of your cluster, for example
  `us-west-2`.
- `<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
  `domzpyodm2g.us-west-2.aws.confluent.cloud`, the `<domain_id>`
  is `zpyodm2g`.

## Related content

- [Overview](overview.md#real-time-context-engine) - Feature overview
  and supported cluster types.
- [Get Started](get-started.md#rtce-get-started) - Enable the
  Real-Time Context Engine and run your first query.
- [Support and Limitations](limitations.md#rtce-limitations) - Supported
  environments, data types, and query limitations.

#### NOTE
This website includes content developed at the [Apache Software Foundation](https://www.apache.org/)
under the terms of the [Apache License v2](https://www.apache.org/licenses/LICENSE-2.0.html).