# Network Management

EMQX Cloud provides network management at two levels: the **project level** and the **deployment level**.

## Project-Level Network Management

Each project includes a **Network Management** section accessible from the project’s left menu. It displays the networks associated with deployments in that project.

When you create an EMQX Broker or EMQX Tables deployment, a network is automatically created for it. A Broker and a Tables deployment can share the same network only when they are in the same cloud platform and region, and you explicitly select the existing network under **Network Association** when creating the second deployment. If you do not select a network during creation, a separate network is created. When both deployments share a network, private connectivity is available between them.

The network list shows the following information for each network:

| Column | Description |
| --- | --- |
| **Network Name** | The name of the network. Click to view details, including the VPC ID, CIDR, and associated deployments. |
| **Status** | The current status of the network. |
| **Cloud Platform** | The cloud provider where the network is hosted. |
| **Region** | The region where the network is located. |
| **Deployments** | The number of deployments associated with this network. |
| **Actions** | A **+** icon for creating a new deployment in this network. |

Each network can hold at most one EMQX Broker and one EMQX Tables deployment. The **+** icon in the **Actions** column lets you create a paired deployment directly. The new deployment's network is pre-selected to this network. If the network already has both a Broker and a Tables deployment, the **+** icon is disabled.

When both deployments share a network, the Broker can reach EMQX Tables over a private connection. If they are in different regions or networks, private connectivity is not available, and you must enable the **NAT Gateway** on the Broker deployment to connect to EMQX Tables over the public internet.

## Deployment-Level Network Management

::: tip Note

Deployment-level Network Management is only available with the EMQX Dedicated and Dedicated Flex edition.

:::

Each Dedicated and Dedicated Flex deployment also has a **Network Management** section in its own left menu. This provides additional options for managing network access, optimizing routing, and securing connectivity. For detailed instructions on configuring and using each feature, click the following links:

- **[VPC Peering Connection](./vpc_peering.md)**: Establishing secure, direct network connections between your EMQX VPC and your application’s VPC within the same or different regions.
- **[PrivateLink](./privatelink.md)**: Connecting to EMQX services securely over a private AWS or Azure network.
- **[Internal Endpoint](../vas/internal-endpoint.md)**: Distributing incoming traffic across multiple EMQX instances within the VPC peering network.
- **[NAT Gateway](../vas/nat-gateway.md)**: Enabling your EMQX instances to communicate with external services while keeping internal resources private.