> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectivity-management/ztna/edge-routers.md). # Edge Routers Learn how to create, manage, and monitor your Edge Routers on the Digibee Integration Platform. An **Edge Router** is a connection point between your network and the Digibee Integration Platform. Each Edge Router belongs to a **group**, which you use to organize and segregate Edge Router communication. For example, a group named `prod-onpremise` might consist only of Edge Routers in the Prod environment that are hosted on an on-premise infrastructure. A group can have an unlimited number of Edge Routers, and each route associates with the Edge Routers across the group it belongs to. {% hint style="info" %} Only users with the connectivity-manager role can create and manage ZTNA connections. Check out all the [ZTNA roles and permissions](/documentation/platform-administration/administration/new-access-control/access-control-roles.md#system-roles). {% endhint %} ## **Creating an Edge Router** 1. Click the Digibee logo in the upper left corner, then click **Connectivity**. 2. The page opens in the **Edge Router** tab. 3. Click **Add Edge Router**. A new modal opens. 4. Fill in the fields: * **Name**: a name for your new connection. * **Group**: create a new group name, or select an existing group to associate with this Edge Router. 5. Click **Create** to continue, or **Cancel** to go back. 6. A new window opens with a key for your Edge Router. Copy it and register it in your Edge Router. You have 48 hours before the key expires. {% hint style="info" %} If you created your Routes and Edge Routers before groups existed, your existing connections were automatically migrated: Edge Routers previously tied to the Prod environment are now part of the `prod` group, and so on. You can keep the default groups or create new ones and reorganize your Edge Routers and Routes. {% endhint %} ### **Naming groups** Use lowercase letters and avoid spaces. Use hyphens or underscores to separate words — for example, `prod-gcp` or `test-devs`. A group only exists while it's associated with at least one Edge Router — if you remove the last Edge Router from a group, the group is automatically deleted. ### **Inverse Flow group** When you create an Inverse Route, an Edge Router is automatically created on the Digibee side and assigned to a group called **Inverse**, which cannot be modified. ## **Changing an Edge Router's group** 1. Click the **Edit** icon of the selected Edge Router. 2. Enter a new group name, or select an existing group. 3. Click **Save**. {% hint style="warning" %} Changing an Edge Router's group does not change the environment of the routes associated with it. Environment is a property of the **route** (Network Mapping), not of the Edge Router — see [Network Mapping](/documentation/connectivity-management/ztna/network-mapping-routes.md). {% endhint %} ## **Generating and registering keys** Each key is valid for 48 hours. After that, generate a new one. You can also regenerate a key before it expires. 1. On the **Edge Router** tab, check the **Registered** column: * **Yes** — key is registered and functioning. * **Pending** — key generated, not yet registered (48h to do so). * **Expired** — key has expired; generate a new one. 2. Click the **Key** icon next to the Edge Router. 3. Click **Register new key** to generate a new key, or **Close** to cancel. 4. Copy the registration key and close the window. 5. In a terminal on the Edge Router, run: ``` sudo router-registration --force ``` ## **Viewing associated Network Mappings** 1. On the **Edge Router** tab, click **View** (eye icon) next to the Edge Router. 2. The side sheet displays all Network Mappings associated with that Edge Router, based on the Edge Router's group and each route's environment. ## **Deleting an Edge Router** {% hint style="warning" %} Edge Routers are linked to specific Network Mappings (routes). Deleting an Edge Router breaks any Network Mapping that depends solely on it. {% endhint %} 1. On the **Edge Router** tab, click the **Delete** icon next to the Edge Router. 2. A pop-up window opens to confirm the action. Click **Delete** to proceed, or **Cancel** to return to the previous screen. If you try to delete an Edge Router that's the sole link for a Network Mapping, the platform warns you that the action creates an orphaned Network Mapping, which can disrupt your connections. If you're certain about the deletion, click **Delete** again to proceed. This confirmation step helps prevent unintentional network disruptions. --- # 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.digibee.com/documentation/connectivity-management/ztna/edge-routers.md?ask=&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.