Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
You are connecting to a Kubernetes cluster running in the private subnet of Azure Virtual Network (VNET) from your DevBox.
Here, you will connect to a Kubernetes cluster running in a private subnet from your DevBox. This would be done by setting up a bastion host that advertises the VNET CIDR to your DevZero network so that you can access the private service through the network tunneling.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
To connect to AKS running in the private subnet, ensure it is within the same Resource Group and VNET containing the Bastion Host.
If the above criteria are followed, then log into your DevBox and follow these steps:
Go to your DevBox and install Azure CLI:
After the installation is successful, you need to authenticate your Microsoft Azure account with Azure CLI using the following command:
Following your setup with Azure CLI, you also need to download the kubectl binaries:
Install kubectl:
After your initial setup is done, your DevBox should be ready for accessing the cluster:
You need to select your Subscription ID in Azure Cli with the following command:
Use the following command to connect to your cluster:
Check if the cluster is accessible:
If you need to make a new AKS Cluster running in a private subnet and access it through DevZero's network, then follow the below steps:
Go to Home > Kubernetes Services or you can search for Azure Kuberntes Service in the search bar and click on Create Kubernetes Cluster.
In the Basics section, select the resource group you previously selected for your VNET.
Enter your Cluster name and region and choose your desired node image.
Select your desired Node Pool machine configuration in the Node Pools section.
Go to the Networking section and check the Enable private cluster
and Bring your own Azure virtual network
options, respectively.
After checking these two options, you will be asked to choose your VNET. Then, create a new subnet dedicated to Kubernetes and choose that subnet.
Enter a Kubernetes service address range that doesn't overlap with your VNET CIDR. For Example, if your VNET CIDR Range is 10.0.0.0/16, then it is recommended that you make your Kubernetes service address range 192.168.0.0/16.
Provide a Kubernetes DNS service IP Address and enter your DNS name prefix.
Click on Review + Create and click on Create to create Kubernetes Cluster.
Now that you have created the cluster, you need to authenticate your DevBox with the az
cli tool:
Go to your DevBox and install Azure CLI:
After the installation is successful, you need to authenticate your Microsoft Azure account with Azure CLI using the following command:
Following your setup with Azure CLI, you also need to download the kubectl binaries:
Install kubectl:
After your initial setup is done, your DevBox should be ready for accessing the cluster:
You need to select your Subscription ID in Azure CLI with the following command:
Use the following command to connect to your cluster:
Check if the cluster is accessible:
You are connecting to a Azure database instance running in the private subnet of Azure Virtual Network (VNET) from your DevBox.
Here, you will connect to a private Azure database instance from your DevBox. This would be done by setting up a bastion host that advertises the private routes to your DevZero network so that you can access the private service through network tunneling.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
To connect to a database running in the private subnet, ensure it is within the same Resource Group and VNET containing the Bastion Host.
Now follow the below steps to access the Database instance on your DevBox:
Go to DevBox.
To Setup Database client and connect to the instance, follow these steps:
If you need to make a new database running in a private subnet and access it through DevZero's network, then follow the below steps:
Now you just need to follow the below steps to install the database clients and connect to DevBox:
Go to DevBox.
To Setup Database client and connect to the instance, follow the steps:
Connecting to an Azure Table Storage from your DevBox.
Here, you will connect to a Table Storage from your DevBox. This would be done by setting up a bastion host that advertises the private routes to your DevZero network so that you can access the private service through network tunneling. You must also set up a DNS Private Resolver to access the Table Storage's Private Endpoint from your DevBox.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
To connect to a Storage Account, ensure it is within the same Resource Group containing the Bastion Host.
Now follow the below steps to access the Table Storage on your DevBox:
Go to DevBox and install the Azure CLI tool using the following command:
Login into your Azure account using the login
command:
After you have completed your authentication, go to Home > Storage Accounts and select your storage account.
Then go to the Security + Networking > Access Keys section and note down either of the two access keys presented to you.
After you have acquired the access key, you may use the following command to Check existence and List the available tables:
If you need to make a new Table Storage and access it through DevBox, then follow the below steps:
After the above mentioned steps are completed, you may go ahead and create a container for Blob Storage by following these steps:
Go to Home > Storage Accounts and click on your storage account.
Go to the Data Storage tab and click on Tables.
Create a new Table by entering the table name and clicking on Create.
After creating the table, go to the Security + Networking > Access Keys section and note down either access key.
After creating the table, you must install and authenticate your Azure CLI to easily access Blob Storage. To do so, you may follow the below steps:
Go to DevBox and install the Azure CLI tool using the following command:
Login into your Azure account using the login
command:
You may use the following command to Check existence and List the available tables:
Configuring the Azure Storage Account to access its endpoint from DevBox.
Here, you will configure a Storage Account to access it from your DevBox. This would be done by setting up a bastion host that advertises the private routes to your DevZero network so that you can access the private service through network tunneling. You would also need to set up a DNS Private Resolver to access the Storage Account's Private Endpoint from your DevBox.
To configure a Storage Account, ensure it is within the same Resource Group containing the Bastion Host.
Now follow the below steps to configure the Storage Account:
Go to Home > Storage Accounts and click on the Storage Account you want to access through the private endpoint.
Go to Networking > Firewalls and virtual networks tab in the Security + Networking section and under Public network access
choose the Disabled
option. Click on Save. This will make your storage account completely private.
After that, go to Networking > Private endpoint connections and click on Private endpoint.
Choose your Resource group and enter the instance name.
Click Resource and select your desired Target sub-resource
for your private endpoint. Remember that if you have more than one sub-resource type, you need to create a separate endpoint for each one.
Click on Virtual Network and select your Virtual Network (VNET), which houses the bastion host and DNS Private Resolver.
Select a compatible subnet, then click on Next, and leave the rest of the settings as default.
Click on Create, and your Private Endpoint will be created.
To verify if you can access the storage account endpoint from your DevBox, just use the following command in your DevBox:
If you need to make a new Storage Account and access it through DevBox, then follow the below steps:
Go to Home > Storage Accounts and click on Create.
In the Basics section, select the resource group you previously selected for your VNET.
Then, input your account name, region, and desired performance type.
Go to the Networking section and choose Disable public access and use private access
option in Network access.
Click on Add private endpoint and enter the Name, **Storage sub-resource type.
In the Networking section, select the VNET which houses the bastion host.
Select a compatible subnet and then choose your private DNS zone.
Click on OK and then click on Review + Create. Finally, click on Create.
To verify if you can access the Storage Account, follow the below steps:
Go to the DevBox.
Use the following command to see if the private endpoint is accessible to you:
Setting up a DNS Private Resolver so that you can access the Azure Private DNS zones connected to your Azure Virtual Network (VNET).
Here, you will setup DNS Private Resolver through which you would resolve DNS queries from the DNS Private zones and direct them to the Bastion Host. The Bastion Host will then forward those queries to the DevZero Network through advertised routes.
To create a DNS Private Resolver, you need to ensure that you have no other DNS Private Resolver instances in your Resource Group.
If the above criteria are followed, then follow these steps:
Go to Home > DNS Private Resolvers and click on Create.
Enter Subscription and Resource Group name in the Project Details section.
Then enter the instance name and region. Remember to choose the region which houses your VNET.
Then select your Virtual Network (VNET).
In the Inbound Endpoint page, click on Add an endpoint and then enter the endpoint name.
While selecting the subnet for Inbound Endpoint, create a new subnet and then click on Save.
Click on Review + Create and click on Create to create the DNS Private Resolver.
After you are done with creating the DNS Private Resolver, you need to add the DNS IP address to the DevZero Network so that you can use the Azure DNS Private Zones.
Go to Home > DNS Private Resolver and click on the new DNS Private Resolver you just created.
Then navigate to Settings > Inbound Endpoints and note down the IP Address of the inbound endpoint which you created.
Go to DevBox and enter the following command:
we need to add the IP address to this configuration file so that the DevZero Network can use the Conditional Forwarder.
Enter the following line to the resolv.conf
file:
save the file and you will now be able to access the domains within the Azure DNS Private Zones.
For Example, we have a DNS Private Zone named privatelink.postgres.database.azure.com
and it houses a private domain endpoint named test-db-devzero.postgres.database.azure.com
. You can verify the setup by using nslookup
:
If everything goes well then you should see a output similar to this.
You are connecting to a Virtual Machine running in the private subnet of Azure Virtual Network (VNET) from your DevBox.
Here, you will connect to a virtual machine running in a private subnet from your DevBox. This would be done by setting up a bastion host that advertises the VNET CIDR to your DevZero network so that you can access the private service through the network tunneling.
To connect to a Virtual Machine running in the private subnet, ensure it is within the same Resource Group and VNET containing the Bastion Host.
If the above criteria are followed, then log into your DevBox and SSH into the private VM by following these steps:
Go to DevBox.
Copy the private SSH key within the .ssh
directory.
Connect to the virtual machine:
If you need to make a new virtual machine running in a private subnet and access it through DevZero's network, then follow the below steps:
Go to Home > Virtual Machines > Create a virtual machine.
In the Basics section, select the resource group you previously selected for your VNET.
Enter your desired username and select the allow selected ports for the Public inbound ports option.
Go to the Networking section and enter your Virtual Network (VNET). Please remember to choose None in the public IP option because we must make the instance private.
Select the Basic option for the NIC network security group. It will create a security group for you that allows port access for SSH.
Click on Review + Create and click on Create to create virtual machine.
Download the SSH private key when prompted. This will help you SSH into the Bastion Host later.
Go to DevBox and make a copy of the key pair.
Connect to the Virtual Machine using ssh and the new key pair:
Connecting to an Azure Blob Storage from your DevBox.
Here, you will connect to a Blob Storage from your DevBox. This would be done by setting up a bastion host that advertises the private routes to your DevZero network so that you can access the private service through network tunneling. You must also set up a DNS Private Resolver to access the Blob Storage's Private Endpoint from your DevBox.
To connect to a Storage Account, ensure it is within the same Resource Group containing the Bastion Host.
Now follow the below steps to access the Blob Storage on your DevBox:
Go to DevBox and install the Azure CLI tool using the following command:
Login into your Azure account using the login
command:
After you have completed your authentication, go to Home > Storage Accounts and select your storage account.
Then go to the Security + Networking > Access Keys section and note down either of the two access keys presented to you.
After you have acquired the access key, you may use the following command to Upload, Download, or list the blob in the container:
If you need to make a new Blob Storage and access it through DevBox, then follow the below steps:
After the above mentioned steps are completed, you may go ahead and create a container for Blob Storage by following these steps:
Go to Home > Storage Accounts and click on your storage account.
Go to the Data Storage tab and click on Containers.
Create a new container by entering the container name and clicking on Create.
After creating the container, go to the Security + Networking > Access Keys section and note down either access key.
After creating the container, you must install and authenticate your Azure CLI to easily access Blob Storage. To do so, you may follow the below steps:
Go to DevBox and install the Azure CLI tool using the following command:
Login into your Azure account using the login
command:
You may use the following command to Upload, Download, or list the Blob in the container:
You are connecting to an Azure Key Vault from your DevBox.
Here, you will connect to a Key Vault from your DevBox. This would be done by setting up a bastion host that advertises the private routes to your DevZero network so that you can access the private service through network tunneling.
To connect to an existing Key Vault, ensure it is within the same Resource Group that houses the Bastion Host.
To make the connection, you need to set up the IAM role and install dependencies in your DevBox.
Go to Home > Key Vaults and click on the key vault you want to access.
Then go to Access Control (IAM) and click on Add role assignment.
Click on the Key Vault Reader role and click on next.
Click on Select Members and select the users you want to give access to the Key Vault. Click on Select.
Then click on Next and then click on Review + Assign to assign the role.
Now, you can read the Secrets in the key vault without error.
We are assuming the Key Vault is private, and in this case, you will not be able to see the value of the secret. For some reason, if you want to see the value of the secrets, then turn the access to Public in the Settings > Networking section. After viewing the value of the secret, Disable the Public Access again.
Now, to retrieve the value from the secrets using the API, you need to set Service Principals on the Azure Portal using the below steps:
Go to Microsoft Entra ID and click on App registrations.
Click on New registration, enter the app name as you like, and click on Register.
Go to All applications and click on the app you just created.
Copy the Client ID and Tenant ID and add it to the DevBox environmental variables.
Click on Client credentials and click on New client secret.
Enter the description if you want to, and click on Add.
Copy the Value of the client secret you just created and add it to the environmental variables of your DevBox by using the following command.
Now, go to Home > Key Vaults and click on the key vault you want to access.
Then go to Access Control (IAM) and click on Add role assignment.
Click on the Key Vault Reader role and click on next.
Click on Select Members and select the App Name you just registered in Microsoft Entra ID. Click on Select.
Then click on Next and then click on Review + Assign to assign the role.
Here we are using Python to show the key vault usage, you can choose other programming stack as well. Now, you need to install the necessary packages in Python to write the script by following the below steps:
Install the required packages using the following command:
Write the following Python script to retrieve the secret:
If you need to make a new Key Vault and access it through DevBox, then follow the below steps:
Go to Home > Key vaults and click on Create.
In the Basics section, select the Resource group which houses your Bastion Host.
Then input your Key Vault name, Region and the desired Pricing Tier.
You can set the Days to retain deleted vaults duration as you like.
Go to the Networking page and disable the Enable public access and enable the Private Endpoint section.
Click on Create a private endpoint and enter the Resource group, Location, Name, and Target sub-resource type of the endpoint.
In the Networking section, select the virtual network (VNET) you used to set up the DNS resolver and Bastion Host.
Choose a compatible subnet or create a new one, and a new private DNS zone will be created for you.
Click on Ok, then click on Review + Create.
Click on Create to initialize the deployment for the key vault.
To make the connection, you need to set up the IAM Role and install dependencies in your DevBox.
Go to Home > Key Vaults and click on the key vault you just created.
Then go to Access Control (IAM) and click on Add role assignment.
Click on the Key Vault Reader role and click on next.
Click on Select Members and select the users you want to give access to the Key Vault. Click on Select.
Then click on Next and then click on Review + Assign to assign the role.
Now go to Obejcts > Secrets and click on Generate/Import.
Enter the Name and Secret Value and click on Create.
In this case, the Key Vault is private, and you will not be able to see the value of the secret. For some reason, if you want to see the value of the secrets, then turn the access to Public in the Settings > Networking section. After viewing the value of the secret, Disable the Public Access again.
Now, to retrieve the value from the secrets using the API, you need to set Service Principals on the Azure Portal using the below steps:
Go to Microsoft Entra ID and click on App registrations.
Click on New registration, enter the app name as you like, and click on Register.
Go to All applications and click on the app you just created.
Copy the Client ID and Tenant ID and add it to the DevBox environmental variables.
Click on Client credentials and click on New client secret.
Enter the description if you want to, and click on Add.
Copy the Value of the client secret you just created and add it to the environmental variables of your DevBox by using the following command.
Now, go to Home > Key Vaults and click on the key vault you want to access.
Then go to Access Control (IAM) and click on Add role assignment.
Click on the Key Vault Reader role and click on next.
Click on Select Members and select the App Name you just registered in Microsoft Entra ID. Click on Select.
Then click on Next and then click on Review + Assign to assign the role.
Here we are using Python to show the key vault usage, you can choose other programming stack as well. Now, you need to install the necessary packages in Python to write the script by following the below steps:
Install the required packages using the following command:
Write the following Python script to retrieve the secret:
Before you begin, follow the guide to set up the Bastion Host to access your private Azure services.
Following the above criteria, follow the guide to access the DNS Private Zones.
If the above steps are completed, you must follow the guide to access the DNS Private Zones.
Before you begin, follow the guide to set up the Bastion Host to access your private Azure services.
Before you begin, follow the guide to set up the Bastion Host to access your private Azure services.
Then input your VM name and region and choose your desired image. You can view the available images .
Before you begin, follow the guide to set up the Bastion Host to access your private Azure services.
Following the above criteria, follow the guide to access the DNS Private Zones.
After successfully setting up the DNS Private Resolver, follow the guide to access the storage account endpoint.
Firstly, you must follow the guide to create and configure a new storage account. After the setup, you must also set up the DNS Private Resolver by following the guide.
Before you begin, follow the guide to set up the Bastion Host to access your private Azure services.
Following the above criteria, follow the guide to access the DNS Private Zones.
You are connecting to a Container Instance running in the private subnet of Azure Virtual Network (VNET) from your DevBox.
Azure Container Instances (ACI) is a serverless container service that allows you to run isolated containers in Azure without managing underlying infrastructure or orchestrating container deployments. This would occur by setting up a bastion host that advertises the VNET CIDR to your DevZero network so you can access the private service through the network tunneling.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
Please make sure your container has a Private IP Address and check if the container is housed in the same Virtual Network as the Bastion Host.
First of all, we need to create a workspace:
Go to DevZero Dashboard.
Navigate to the Workspaces tab and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Click on New Recipe and enter the recipe name and click on Create a recipe.
Select a workspace region and click on Launch.
Follow the Below steps to access your container application from your DevBox :
Connect to the workspace using the following command:
You can access the application running in the container using the curl
command:
If you need to make a new container running in a private subnet and access it through DevZero's network, then follow the below steps:
Go to Home > Container Instances and click on Create.
In the Basics section, select the Resource group you previously selected for your VNET.
Then input your Container name and Region and choose your desired SKU.
Choose your desired Image source between Quickstart images
, Azure Container Registry
, and Other registry
.
We will work with Quickstart images
for this guide.
Select or input the Image and choose the desired size configuration for your container.
On the networking page, choose the Private option and select your VNET and desired subnet.
Click on Review + Create and click on Create to create container.
Follow the steps to create a workspace:
To to DevZero Dashboard.
Navigate to the Workspaces tab and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Click on New Recipe and enter the recipe name and click on Create a recipe.
Select a workspace region and click on Launch.
Follow the Below steps to access your container application from your DevBox :
Connect to the workspace using the following command:
You can access the application running in the container using the curl
command:
Connecting to an Azure File Storage from your DevBox.
Azure File Storage is a fully managed file share in the cloud that is accessible via the industry-standard Server Message Block (SMB) protocol, Network File System (NFS) protocol, and Azure Files REST API. Azure file shares can be mounted concurrently by cloud or on-premises deployments. SMB Azure file shares are accessible from Windows, Linux, and macOS clients.
This connection between the Azure File Share and your DevBox would occur by setting up a bastion host that advertises the private routes to your DevZero network so you can access the private service through network tunneling. You must also set up a DNS Private Resolver to access the File Storage's Private Endpoint from your DevBox.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
To connect to a Storage Account, ensure it is within the same Resource Group containing the Bastion Host.
First, we need to create a recipe for the workspace:
Go to the DevZero Dashboard > Recipes and click on New recipe.
Enter the recipe name and click on Create a recipe.
Now use the below-provided snippet to create a recipe for your workspace:
Click on Save and Build and when the build is successful, click on Publish.
Go to the Devzero Dashboard > Workspaces and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Select the recipe you just created and click on Select.
Click on Launch, and your workspace will be ready shortly.
Now follow the below steps to access the File Storage on your DevBox:
Connect to DevBox and login into your Azure account using the login
command:
After you have completed your authentication, go to Home > Storage Accounts and select your storage account.
Then go to the Security + Networking > Access Keys section and note down either of the two access keys presented to you.
After you have acquired the access key, you may use the following command to Upload, Download, or list the files in the file share:
If you need to make a new File Storage and access it through DevBox, then follow the below steps:
After the steps mentioned earlier are completed, you may go ahead and create a file share for File Storage by following these steps:
Go to Home > Storage Accounts and click on your storage account.
Go to the Data Storage tab and click on File Shares.
Create a new File Share by entering the file share name and clicking on Create.
After creating the file share, go to the Security + Networking > Access Keys section and note down either access key.
First, we need to create a recipe for the workspace:
Go to the DevZero Dashboard > Recipes and click on New recipe.
Enter the recipe name and click on Create a recipe.
Now use the below-provided snippet to create a recipe for your workspace:
Click on Save and Build and when the build is successful, click on Publish.
Go to the Devzero Dashboard > Workspaces and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Select the recipe you just created and click on Select.
Click on Launch, and your workspace will be ready shortly.
After creating the File Share, you must install and authenticate your Azure CLI to easily access File Storage. To do so, you may follow the below steps:
Connect to your DevBox and login into your Azure account using the login
command:
Use the following command to create a directory in the File Share:
You may use the following command to Upload, Download, or list the File in the File Share:
You are connecting to an App Service running on your Azure infrastructure from your DevBox.
Azure App Service enables you to build and host web apps, mobile backends, and RESTful APIs in the programming language of your choice without managing infrastructure. This connection between the app service and workspace would occur by setting up a bastion host that advertises the private routes to your DevZero network so you can access the private service through network tunneling. You must also set up a DNS Private Resolver to access the App Service's Private Endpoint from your DevBox.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
To connect to an App Service running in the private subnet, please ensure it is within the same Resource Group and VNET containing the Bastion Host.
It would be best if you created a workspace so you can access the app service:
Go to DevZero Dashboard.
Navigate to the Workspaces tab and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Click on New Recipe and enter the recipe name and click on Create a recipe.
Select a workspace region and click on Launch.
Navigate to Networking and open Private Endpoints page.
Click on Add > Express and then enter the name of your private endpoint.
Then select the VNET and a compatible subnet. Turn on the Integrate with private DNS zone option.
Click on Ok, and your private connection to your web app will be successfully deployed.
Follow the Below steps to access your Web App from your DevBox :
Connect to the workspace using the following command:
Copy the Default domain of the App Service you want to access.
Connect to the App Service:
It would be best if you created a workspace so you can access the app service:
Go to DevZero Dashboard.
Navigate to the Workspaces tab and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Click on New Recipe and enter the recipe name and click on Create a recipe.
Select a workspace region and click on Launch.
Follow the Below steps to access your Web App from your DevBox :
Connect to the workspace using the following command:
Copy the Default domain of the App Service you want to access.
Connect to the App Service:
You connect to an Azure Elastic SAN Service running on Azure infrastructure from your DevBox.
Azure Elastic SAN is a fully integrated solution that simplifies deploying, scaling, managing, and configuring a SAN while also offering built-in cloud capabilities like high availability. This connection will occur by setting up a bastion host that advertises the private routes to your DevZero network so you can access the private service through network tunneling. You must also set up a DNS Private Resolver to access the Elastic SAN's Private Endpoint from your DevBox.
Before you begin, follow the Connecting to Azure guide to set up the Bastion Host to access your private Azure services.
Ensure the existing SAN is in the same resource group that houses the Bastion Host.
First, we need to create a recipe for the workspace:
Go to the DevZero Dashboard > Recipes and click on New recipe.
Enter the recipe name and click on Create a recipe.
Now use the below-provided snippet to create a recipe for your workspace:
Click on Save and Build and when the build is successful, click on Publish.
Go to the Devzero Dashboard > Workspaces by clicking New workspace.
Enter the workspace name and click on Select from recipe library.
Select the recipe you just created above and click on Select.
Click on Launch, and your workspace will be ready shortly.
To connect to the Elastic SAN volumes, we first need to create a Volume Group and give it private endpoint access:
Go to Home > Azure Elastic SAN and click on the SAN you want to access.
Go to Volume groups and click on Create.
Enter the Volume group name and click on Next.
Click on Create a private endpoint and enter the Resource group, Location, Name and select the Volume group you just created.
Select the Virtual network and choose an available subnet.
Select Yes for Integrate with private DNS zone option, and click on Ok.
After creating the endpoint, click on Create.
You can also add your VNET by clicking on Create under the Virtual Networks section and entering the details of the VNET, which exists in the same region as the Elastic SAN instance.
Now, with everything set, we need to create a volume and generate the connection script:
Go to Home > Azure Elastic SAN and click on the SAN you want to access.
Go to Volumes and click on Create volume.
Choose the Volume group and enter the Volume name, Source type and Size of the volume.
Click on Create and wait for it to initialize.
After creating the volume, select the volume and click on Connect.
Note down the script code for Linux as we will use it to connect Azure infrastructure and the DevBox.
Now you need to follow the below steps to connect to DevBox:
Connect to the workspace from your terminal.
Create a Python script by using the following command:
Paste in the connection script we got from the volume.
Run the Python file with elevated access to make the connection:
If you need to make a new Elastic SAN instance and access it through DevZero's network, then follow the below steps:
Go to Home > Azure Elastic SAN and click on Create.
In the Basics section, select the Resource group you previously selected for your VNET.
Then input your SAN Name, Region, and Redundancy type.
You can allocate the desired SAN size in the Resource provisioning on Elastic SAN section.
Remember that the size of your SAN is directly proportional to the IOPS (Input/Output operations per second) and bandwidth allocated to the instance.
In the Networking section, choose the Disabled option for Public network access.
You can also choose the Enabled option and connect to a VNET if you have a VNET in the same Region as the Elastic SAN instance.
Click on Review + Create and click on Create.
Go to the DevZero Dashboard > Recipes and click on New recipe.
Enter the recipe name and click on Create a recipe.
Now use the below-provided snippet to create a recipe for your workspace:
Click on Save and Build and when the build is successful, click on Publish.
Go to the Devzero Dashboard > Workspaces and click on New workspace.
Enter the workspace name and click on Select from recipe library.
Select the recipe you just created and click on Select.
Click on Launch, and your workspace will be ready shortly.
To connect to the Elastic SAN volumes, we first need to create a Volume Group and give it private endpoint access:
Go to Home > Azure Elastic SAN and click on the SAN you want to access.
Go to Volume groups and click on Create.
Enter the Volume group name and click on Next.
Click on Create a private endpoint and enter the Resource group, Location, Name and select the Volume group you just created.
Select the Virtual network and choose an available subnet.
Select Yes for Integrate with private DNS zone option, and click on Ok.
After creating the endpoint, click on Create.
You can also add your VNET by clicking on Create under the Virtual Networks section and entering the details of the VNET, which exists in the same region as the Elastic SAN instance.
Now, with everything set, we need to create a volume and generate the connection script:
Go to Home > Azure Elastic SAN and click on the SAN you want to access.
Go to Volumes and click on Create volume.
Choose the Volume group and enter the Volume name, Source type and Size of the volume.
Click on Create and wait for it to initialize.
After creating the volume, select the volume and click on Connect.
Note down the script code for Linux as we will use it to connect Azure infrastructure and the DevBox.
Now, you need to follow the below steps to connect to DevBox:
Connect to the workspace from your terminal.
Create a Python script by using the following command:
paste in the connection script we got from the volume.
Run the Python file with elevated access to make the connection: