Skip to content
This repository has been archived by the owner on Aug 2, 2024. It is now read-only.

Latest commit

 

History

History
36 lines (22 loc) · 1.91 KB

File metadata and controls

36 lines (22 loc) · 1.91 KB

Create a confidential compute jumpbox VM inside a vnet

This tutorial will let you create a jumpbox VM inside a vnet, optionally by using Azure Bastion to connect via HTTPS.

⚠️ This should be used for development purpose only.

Prerequisites

To enjoy these quickstart, you will need to:

  • have an active Azure subscription that you can use for development purposes,
  • have permissions to create resources, set permissions, and create identities in this subscription (or at least in one resource group),
    • Note that to set permissions, you typically need Owner role in the subscription or resource group - Contributor role is not enough. This is key for being able to secure the setup.
  • install the Azure CLI.

Deploy a confidential compute VM inside a vNet

Check availability of confidential compute VMS in your region..

Option 1 : one click deployment

  1. Click on Deploy to Azure

  2. Adjust parameters, in particular:

    • vnetName: name of the vNet to join.
    • subnetName: name of the subnet inside the vNet.
    • nsgName: name of the existing security group applying to the VM.

Option 2 : deployment using az cli

In the resource group of your AzureML workspace, use the following command with parameters corresponding to your setup:

az deployment group create --template-file ./mlops/bicep/modules/resources/jumpbox_cc.bicep --resource-group <resource group name> --parameters vnetName="..." subnetName="..." nsgName="..." jumpboxOs="linux"