> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/create-a-layer-2-connection.md).

# Create a Layer 2 Connection

The following steps are applicable to connections with two access points of IDCs or public clouds based on Layer 2 SDN backbone network.

If you need a Layer 2 network connection - the [**private connect**](/welcome/cloud-networking/overview/concepts.md#private-connect), you can follow the steps as shown below.

## Prerequisites

* You have [**signed up an account**](/welcome/platform/account-management/create-an-account.md) with your email and sign in to [**zenConsole**](https://console.zenlayer.com/).
* If you need to connect to your cloud services, your public cloud provider should be one of the following: Amazon Web Services (AWS), Tencent Cloud, Google Cloud, Alibaba Cloud, Huawei Cloud, Microsoft Azure, Oracle Cloud, and BytePlus. See [**Public Cloud**](/welcome/cloud-networking/get-started/create-a-layer-2-connection/select-a-public-cloud-as-access-point.md) for details.

## Procedures

On the upper left corner of zenConsole, go to **Products** > **Cloud Networking** > **Private Connect L2** > [**Create Private Connect**](https://console.zenlayer.com/sdn/network/create/ptp).\
The overall steps of creating a private connect is shown below. For detailed operations, please refer to the links of specific chapters.

<div align="left"><figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-fa2d5d9dd6238e3d7b1da934e67886e83780adbd%2Fimage.png?alt=media" alt="" width="563"><figcaption><p>Create a Layer 2 Private Connect</p></figcaption></figure></div>

### 1. Label Your Private Connect

Click <img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-a6d760e3932f19ec2b1d98c4c2d682431c99348a%2Fimage.png?alt=media" alt="" data-size="line"> to modify the label name of your private connect. You can also click **Add Description** to give the private connect a note.

### 2. Add Access Points

Select two access points as the source end and the destination end of your private connect.\
You may have the following options:

* [**Data Center**](/welcome/cloud-networking/get-started/create-a-layer-2-connection/select-a-data-center-as-access-point.md)
* [**Public Cloud**](/welcome/cloud-networking/get-started/create-a-layer-2-connection/select-a-public-cloud-as-access-point.md)

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">A Layer 2 private connect cannot connect Tencent Cloud and Google Cloud to each other.</mark>
* <mark style="color:blue;">For Alibaba Cloud and BytePlus, the two access points of a private connect cannot both be the same cloud.</mark>
  {% endhint %}

### 3. Configure Bandwidth Cap

[**Configure the bandwidth cap**](/welcome/cloud-networking/get-started/create-a-layer-2-connection/configure-network-information.md) between two access points of your Layer 2 private connect.

### 4. Confirm Order and Pay for It

## What to Do Next

More operations offline or on the public cloud console.

### For the Public Cloud Point

[**Validate your cloud connect**](/welcome/cloud-networking/get-started/validate-connection-in-public-cloud.md) on the corresponding console of your public cloud provider.

### For the Data Center Point

Contact Zenlayer Support or your data center operator to establish a cross connect offline.

## Result

After your cross connect is established offline and your cloud connect is validated on the public cloud console, the states of corresponding points will change into **Active** and you will receive a notification email.

Once the states of both ends are **Active**, your private connect state will become **Active**.

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">Billing for private connect starts as soon as the private connect is provisioned successfully. It does not wait for the source and destination end points to become active.</mark>
* <mark style="color:blue;">Billing for your port will start:</mark>
  * <mark style="color:blue;">when the port is active.</mark>
  * <mark style="color:blue;">15 days after you submit the order – whether or not your cross connect has been established.</mark>
* <mark style="color:blue;">Billing for your cloud connect will start:</mark>\ <mark style="color:blue;">Once you have validated your cloud connect on the public cloud console.</mark>
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/create-a-layer-2-connection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.