+
-
+
diff --git a/src/pages/manage/networks/use-cases/by-resource-type/accessing-entire-domains-within-networks.mdx b/src/pages/manage/networks/use-cases/by-resource-type/accessing-entire-domains-within-networks.mdx index 2e49f79c8..c3ae8e0d4 100644 --- a/src/pages/manage/networks/use-cases/by-resource-type/accessing-entire-domains-within-networks.mdx +++ b/src/pages/manage/networks/use-cases/by-resource-type/accessing-entire-domains-within-networks.mdx @@ -74,23 +74,21 @@ In `Advanced Settings`: ### Add a wildcard domain resource -Click `Add Resource` to create the wildcard domain resource. +Click `Add Resource` to open the resource modal.  -Configure the resource: +In the **Resource** tab, configure the resource: - **Name**: `Development Wildcard Domain` - **Address**: `*.dev.example.com` -- **Assigned Groups**: Select or create a group (e.g., `Development Domain`) -- Click `Add Resource` +- Expand **Additional Options** and under **Resource Groups**, select or create a group (e.g., `Development Domain`) +- Click **Continue** to proceed to the **Access Control** tab  ### Create an access policy -Click `Create Policy` to grant developers access to `*.dev.example.com`. - - +In the **Access Control** tab, click **Add Policy** to grant developers access to `*.dev.example.com`. Configure the policy: - **Protocol**: `ALL` @@ -103,6 +101,8 @@ Click `Continue` to optionally add posture checks, then `Continue` again. Enter  +Click **Add Resource** to save the resource with its policy. + ### Add the base domain resource Wildcard domains (`*.dev.example.com`) only match subdomains, not the base domain itself. To also allow access to `dev.example.com`, add it as a separate resource. @@ -111,11 +111,11 @@ Wildcard domains (`*.dev.example.com`) only match subdomains, not the base domai  -2. Configure the resource: +2. In the **Resource** tab, configure the resource: - **Name**: `Development Regular Domain` - **Address**: `dev.example.com` - - **Assigned Groups**: `Development Domain` (same group as the wildcard) - - Click `Add Resource` + - Expand **Additional Options** and under **Resource Groups**, select `Development Domain` (same group as the wildcard) + - Click **Continue** to proceed to the **Access Control** tab, then click **Add Resource**  @@ -153,15 +153,15 @@ Add routing peers (single or group for high availability):  -Add the wildcard domain resource for `*.ai.example.com`: +Add the wildcard domain resource for `*.ai.example.com`. In the **Resource** tab, enter the name and address, then expand **Additional Options** to assign a resource group (e.g., `AI Domain`). Click **Continue** to go to the **Access Control** tab:  -Create an access policy for the `Data Scientists` group: +In the **Access Control** tab, click **Add Policy** and create an access policy for the `Data Scientists` group:  -Add the base domain `ai.example.com` as a separate resource. The completed network: +Click **Add Resource** to save. Then add the base domain `ai.example.com` as a separate resource using the same resource group. The completed network:  @@ -169,7 +169,7 @@ Add the base domain `ai.example.com` as a separate resource. The completed netwo You can add individual subdomain resources for more granular access control. For example, to add a specific AI model subdomain: -Click `Add Resource`, enter the subdomain name and address, and assign it to the appropriate group: +Click `Add Resource`, enter the subdomain name and address in the **Resource** tab, expand **Additional Options** to assign it to the appropriate resource group, then click **Continue** and **Add Resource**:  diff --git a/src/pages/manage/networks/use-cases/by-resource-type/accessing-restricted-domain-resources.mdx b/src/pages/manage/networks/use-cases/by-resource-type/accessing-restricted-domain-resources.mdx index f40098488..e880aa63f 100644 --- a/src/pages/manage/networks/use-cases/by-resource-type/accessing-restricted-domain-resources.mdx +++ b/src/pages/manage/networks/use-cases/by-resource-type/accessing-restricted-domain-resources.mdx @@ -47,23 +47,21 @@ In `Advanced Settings`: ### Add the accounting subdomain resource -Click `Add Resource` to add the accounting website. +Click `Add Resource` to open the resource modal.  -Configure the resource: +In the **Resource** tab, configure the resource: - **Name**: `Accounting restricted subdomain` - **Address**: `accounting.example.com` -- **Assigned Groups**: Select or create a group (e.g., `Accounting Subdomain`) -- Click `Add Resource` +- Expand **Additional Options** and under **Resource Groups**, select or create a group (e.g., `Accounting Subdomain`) +- Click **Continue** to proceed to the **Access Control** tab  ### Create an access policy for the finance team -Click `Create Policy` to define access for the finance team. - - +In the **Access Control** tab, click **Add Policy** to define access for the finance team. Configure the policy: - **Protocol**: `TCP` @@ -77,37 +75,41 @@ Click `Continue` to optionally add posture checks, then `Continue` again. Enter  +Click **Add Resource** to save the resource with its policy. + ### Add the top-level domain resource for support The support team needs SSH access to the backend at `example.com`. Add a new resource: 1. In the `AWS EU Network` screen, click `Add Resource` -2. Configure: +2. In the **Resource** tab, configure: - **Name**: `Restricted Website TLD` - **Address**: `example.com` - - **Assigned Groups**: Select or create a group (e.g., `Webserver`) + - Expand **Additional Options** and under **Resource Groups**, select or create a group (e.g., `Webserver`) +3. Click **Continue** to proceed to the **Access Control** tab  ### Create an access policy for the support team -Create a policy for SSH access: +In the **Access Control** tab, click **Add Policy** to create a policy for SSH access: -1. Click `Add Policy` next to the `Restricted Website TLD` resource -2. Configure: +1. Configure: - **Protocol**: `TCP` - **Source**: `Support` - **Destination**: `Webserver` - **Ports**: `22` -3. Click `Continue` +2. Click `Continue`  -4. Optionally add posture checks, then click `Continue` -5. Enter a policy name (e.g., `Restricted Website TLD Policy`) +3. Optionally add posture checks, then click `Continue` +4. Enter a policy name (e.g., `Restricted Website TLD Policy`) and click `Add Policy`  +Click **Add Resource** to save the resource with its policy. + ## Verify the configuration The completed network shows both resources with their access policies: diff --git a/src/pages/manage/networks/use-cases/by-resource-type/routing-traffic-to-multiple-resources.mdx b/src/pages/manage/networks/use-cases/by-resource-type/routing-traffic-to-multiple-resources.mdx index d057fa30a..1382c97d8 100644 --- a/src/pages/manage/networks/use-cases/by-resource-type/routing-traffic-to-multiple-resources.mdx +++ b/src/pages/manage/networks/use-cases/by-resource-type/routing-traffic-to-multiple-resources.mdx @@ -40,19 +40,21 @@ Click `Continue`, then accept the defaults and click `Add Routing Peer`: ### Add the network resource -Click `Add Resource` and enter `Office network` as the name with IP range `172.16.0.0/15` as the address: +Click `Add Resource` to open the resource modal. In the **Resource** tab: +1. Enter `Office network` as the name +2. Enter `172.16.0.0/15` as the address +3. Expand **Additional Options** and assign the resource group `office-network` — this group will be used in the access policy for the DevOps team +4. Click **Continue** to proceed to the **Access Control** tab
@@ -64,17 +66,21 @@ Click `Continue` twice, then click `Add Policy`:
@@ -82,9 +88,9 @@ Add the second DNS server resource:
### Create an access policy for DNS servers
-Create a policy that grants the `All users` group access to the `office-dns-servers` resource group on UDP port 53 only.
+Now that both DNS servers share the `office-dns-servers` resource group, create a single policy for both. From the network view, click **Add Policy** next to one of the DNS server resources.
-Click `Create Policy` and configure the fields:
+Create a policy that grants the `All users` group access to the `office-dns-servers` resource group on UDP port 53 only:
diff --git a/src/pages/manage/networks/use-cases/by-scenario/access-home-devices.mdx b/src/pages/manage/networks/use-cases/by-scenario/access-home-devices.mdx
index 2502d6819..e741c4e13 100644
--- a/src/pages/manage/networks/use-cases/by-scenario/access-home-devices.mdx
+++ b/src/pages/manage/networks/use-cases/by-scenario/access-home-devices.mdx
@@ -66,10 +66,10 @@ Look for your local subnet, typically something like `192.168.1.0/24` or `192.16
## Step 5: Add Your Home Subnet as a Resource
1. In your new network, click **Add Resource**
-2. Enter a name like "Home Subnet"
+2. In the **Resource** tab, enter a name like "Home Subnet"
3. Enter your home subnet (e.g., `192.168.1.0/24`)
-4. Create a group called `home-lan` for the destination
-5. Click **Add Resource**
+4. Expand **Additional Options** and under **Resource Groups**, create a group called `home-lan`
+5. Click **Continue** to proceed to the **Access Control** tab
@@ -81,11 +81,12 @@ For more granular access, add specific device IPs instead of the entire subnet.
## Step 6: Create an Access Policy
-1. After adding your resource, click **Create Policy**
+1. In the **Access Control** tab, click **Add Policy**
2. Set **Source** to "Home Users"
3. Set **Destination** to `home-lan`
4. Set **Protocol** to All
5. Name it "Home LAN Access" and click **Add Policy**
+6. Click **Add Resource** to save the resource with its policy
diff --git a/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx b/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
index 0c32037bc..42cf55a60 100644
--- a/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
+++ b/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
@@ -45,10 +45,10 @@ Look for your local subnet, typically something like `10.100.0.0/24`.
## Step 3: Add Your Database as a Resource
1. In your new network, click **Add Resource**
-2. Enter a name like "Database Servers"
+2. In the **Resource** tab, enter a name like "Database Servers"
3. Enter your database subnet or specific IP (e.g., `10.100.0.0/24` or `10.100.0.50/32`)
-4. Create a group called `on-prem-databases` for the destination
-5. Click **Add Resource**
+4. Expand **Additional Options** and under **Resource Groups**, create a group called `on-prem-databases`
+5. Click **Continue** to proceed to the **Access Control** tab
@@ -60,12 +60,13 @@ For more granular access, add specific database IPs instead of the entire subnet
## Step 4: Create an Access Policy
-1. After adding your resource, click **Create Policy**
+1. In the **Access Control** tab, click **Add Policy**
2. Set **Source** to "`cloud-workloads`" (you'll create this group in the next step)
3. Set **Destination** to `on-prem-databases`
4. Set **Protocol** to TCP
5. Set **Ports** to the database ports (e.g., `5432` for PostgreSQL, `3306` for MySQL)
6. Name it "Cloud to Database Access" and click **Add Policy**
+7. Click **Add Resource** to save the resource with its policy
diff --git a/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx b/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
index 4f40976d8..4dc8bdfd1 100644
--- a/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
+++ b/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
@@ -66,10 +66,10 @@ Look for your local subnet, typically something like `10.0.0.0/24` or `192.168.1
## Step 5: Add Your Office Subnet as a Resource
1. In your new network, click **Add Resource**
-2. Enter a name like "Office Subnet"
+2. In the **Resource** tab, enter a name like "Office Subnet"
3. Enter your office subnet (e.g., `10.0.0.0/24`)
-4. Create a group called `office-lan` for the destination
-5. Click **Add Resource**
+4. Expand **Additional Options** and under **Resource Groups**, create a group called `office-lan`
+5. Click **Continue** to proceed to the **Access Control** tab
@@ -81,11 +81,12 @@ For more granular access, add specific server IPs instead of the entire subnet.
## Step 6: Create an Access Policy
-1. After adding your resource, click **Create Policy**
+1. In the **Access Control** tab, click **Add Policy**
2. Set **Source** to "`remote-workers`"
3. Set **Destination** to `office-lan`
4. Set **Protocol** based on needs (TCP for most apps, All for full access)
5. Name it "Remote Worker Office Access" and click **Add Policy**
+6. Click **Add Resource** to save the resource with its policy
