Zscaler App Connector - Create

To create a Zscaler App Connector, follow the steps below in order. Prepare the required service values before starting: a ZPA provision key (ZPA license), the VM AS number, a login user and both user and root passwords. Choose the exact software image and one of the supported flavors.

• Select project
• Deployment configuration
• Virtual Edge configuration
• Interfaces configuration
• Service specific parameters
• Validation

Step 1 - Select project

Select the project in which you want to deploy your virtual Edge:

Select your project.

Step 2 - Deployment configuration

2.1 Name your Virtual Edge (This name will be displayed on the Virtual Network Edge dashboard)

Set Virtual Edge name.

2.2 Select the implementation mode: Single or Dual

Select implementation mode.

Virtual device configuration

2.3 Fill the Virtual Device name (This name will be used as hostname for the virtual device).

2.4 Select the Orange POP which correspond to the location of POP.

Fill Virtual Device Name, Region and POP.

For Dual or Cluster Topology

For Dual topology, different POP can be chosen for each virtual Device.

For Cluster topology, the Virtual devices must be on the same POP.

Select Internet and MPLS Bandwidth for each Virtual Device.

Select Internet and MPLS bandwidth for the Virtual Device.

Step 3 - Virtual Edge configuration

3.1 Select the Software version.

Available software versions are :

• 22.04

3.2 Select the Virtual Device flavor.

Available flavors are :

Flavors table for Zscaler App Connector

	Standard
Small	4 vCPU 8 GB Mem 64 GB Disk
Medium	8 vCPU 16 GB Mem 64 GB Disk

Notes

• For Dual topology, different flavors can be selected for each Virtual device.
• DPDK (Data Plane Development Kit) is a set of libraries and drivers designed to acceler- ate packet processing and optimize performance in network applications. It provides a high-performance framework for managing network traffic at a low level, bypassing the traditional kernel network stack to enhance throughput and reduce latency.
  Pay attention the use of an image with DPDK significantly increases energy consumption and therefore the associated carbon footprint.

3.3 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 4 - Interfaces configuration

Interfaces

Configure the numbered interfaces shown in the portal using the canonical names from the specification:

• #1 - Internet Interface — Internet-facing. A Public IP address is provided by the platform and shown as an informational output after provisioning. You do not enter this IP during creation.
• #2 - Management interface — Management path. A Management IP address is provided by the platform as an informational output after provisioning. You do not enter this IP during creation.
• #3 - MPLS-VPN interface — Used to attach VLAN sub-interfaces (for example VLAN 101, 102, …). For each VLAN sub-interface you add in the portal:
  • Provide one or more VPN entries (each needs a VPN Name and a VPN role: any-to-any, client, server).
  • Optionally enable BGP for the VLAN sub-interface and provide the AS prepend value if required.
  • Optional subnet, gateway, service address and mask fields are available if your design or IPAM requires them.

Note: Public and Management addresses are platform-generated outputs and are not customer-provided fields during the Create journey.

Virtual device configuration

The platform provides a cloud-init template managed by the Evolution Platform. Custom user data upload is not allowed for this VNF; the platform uses predefined provisioning scripts to apply the service parameters you provide.

Virtual device configuration panel.

Cloud-init is platform-managed for this VNF; custom uploads are not supported.

Step 5 - Service specific parameters

5.1 Fill in the following service parameters:

• VM AS number: AS number to assign to the virtual machine when BGP is used. The specification allows 2- or 4-byte AS numbers. min: 1, max: 4294967295.
• Software image: ubuntu-22.04.5-server-cloudimg-amd64-20251203: The specification references the App Connector image Ubuntu 22.04 cloud image name as supported. Use the exact image name provided by the specification when selecting software image..
• Flavors: std1.c4 (Small), std1.c8 (Medium): Available IaaS flavors and their vCPU/RAM/Disk sizes are provided in the specification. Use only the flavors listed in the specification..
• ZPA license (provision key): Enter the ZPA provision key (your ZPA license/provision key). This key is required by the service during provisioning to associate the deployed App Connector with your Zscaler account. No pattern provided in the specification..
• user password: Provide the initial user password used by the VNF for the specified login user. No pattern present in the specification..
• Root password: Provide the root password that will be set on the VNF during provisioning. Not specified in the blueprint..
• Login user: Provide the user account name to create on the VNF during provisioning. No pattern specified..

5.2 Click on Continue button to continue the journey or click on Save button to save the current deployment configuration.

Step 6 - Validation

After clicking the Continue button, a page summarizing the characteristics of the Virtual Edge will be displayed.

This page is divided into several sections :

• Projects
• Deployment
• Virtual edge configuration
• Interfaces configuration
• Service specific parameters

At this stage, it is still possible to modify the characteristics for these sections.

One section is dedicated to display the Carbon footprint of the Virtual Edge :

Carbon footprint for Virtual Edge.

Click on the Provision button to initiate the provisioning of the Virtual Network Edge. You can also preserve the Virtual Network Edge configuration by clicking the Save and close button and the following toast is displayed.

In this case, you will find the Virtual Network Edge in designed state on the .