📃
Confidential Computing 101
HomeTechnologyTry CC!
  • Welcome
  • Confidential Computing
    • What is Confidential Computing
    • What problems Confidential Computing solves
      • Bare Metal
      • Docker
      • Kubernetes
      • Knative
    • Why Confidential Computing
    • How Confidential Computing works
      • Memory Encryption
      • Workload Attestation
      • Confidential Boot
      • Sealing / Binding
      • Secret Provisioning
    • Technology Overview
    • Cloud Service Providers
  • Technology in depth
    • Intel SGX
      • Getting Started
        • Bare Metal Server Installation
        • Enclave Development Environment
        • Intel SGX SDK Setup
      • Technology
        • 🎭Features
        • 💂Threat Model
        • 🆚Versions
        • 🟦Concepts
          • 🏦Memory Encryption
          • 👮Local and Remote Attestation
          • 🖼️DCAP-Attestation Framework
          • 🔑Secret Key Provisioning
      • enclaive Development Kit
        • 🏢Architecture
        • 🌪️Workflow
        • 🌍Tutorials
          • Azure DCdsv3, DCsv2, or DCsv3 Setup
          • Redis in cK8s
          • MongoDB in cK8s
          • K8s + HashiCorp Vault on Azure DCsv3
      • Vault Remote Attestation Plug-In
        • 🏃‍♂️Initialization
        • 👮Attestation
        • ⚙️Configuration
    • Intel TDX
      • Getting Started
        • Azure
        • AWS
        • GCP
      • Technology
        • History
          • VT
          • TME/MKTME
          • SGX
        • Features
        • Threat Model
        • Concepts
          • Architecture
            • TDX Module
          • Memory Encryption
            • Confidentiality and Integrity
            • Keys and Key Management
          • TD Partitioning
          • DCAP-Attestation
            • Overview
            • Platform Registration
            • Attestation Report
    • AMD SEV
      • Getting Started
        • Azure
        • AWS
        • GCP
      • Technology
        • History
        • Threat Model
        • SME Concepts
          • Use Models
        • SEV-SNP Concepts
          • Features
            • Integrity Threats
            • Reverse Map Table
            • Page Validation
            • Page States
            • Virtual Machine Privilege Levels
            • Interrupt/Exception Protection
            • Trusted Platform Information
            • TCB Versioning
            • VM Launch & Attestation
            • VM Migration
            • Side Channels
          • Use Cases
          • Architecture
            • Encrypted Memory
            • Key Management
          • Software Implications
    • ARM CC
      • Technology
        • Introduction
        • Threat Model
        • Design
        • Comparison
    • Attestation Methods
      • Raw Attestation
      • Raw Attestation with Secure-Boot
      • Raw Attestation with a vTPM
        • AMD Secure VM Service Module and vTPMs
      • Raw Attestation with paravirtualized TPM
  • Resources
    • Youtube
    • Github
    • Products
Powered by GitBook
On this page

Was this helpful?

  1. Technology in depth
  2. Intel SGX
  3. enclaive Development Kit
  4. Tutorials

Azure DCdsv3, DCsv2, or DCsv3 Setup

Last updated 11 months ago

Was this helpful?

: When deploying a confidential computing VM instance, exploring options such as pay-as-you-go subscriptions or alternative purchase methods is advisable. It is important to note that Azure free or student subscriptions do not offer an adequate quota of Azure compute cores required for the deployment.

To proceed with creating an Azure Confidential Computing virtual machine, follow these steps:

  1. Navigate to the page.

  2. Choose a region that offers the availability of DCdsv3, DCsv2, or DCsv3 series instances. You can check the availability of Azure products by region . We generally recommend selecting the nearest region to your location for better performance.

  3. Under the security type, select trusted launch virtual machines.

  4. We recommend opting for a Linux distribution with a Kernel version of 5.11 or higher for the image selection. Ensure that you choose the images that include the confidential VM option. Ubuntu Server 22.04 LTS (Confidential VM) is the minimum recommended image fitting all requirements.

  5. Regarding the size of the virtual machine, it is necessary to have a minimum of 2 CPU cores for smooth Kubernetes operation. It is highly recommended to allocate a host machine with a memory size of 16 GB or more to ensure sufficient memory availability. Therefore, we suggest utilizing at least DCdsv3, DC2s_v3 or DC4s_v2 instances as they meet these minimum requirements.

An example of the configuration can be seen in the accompanying image below.

Complete the setup by either configuring the settings according to your requirements or leaving them as the default values.

Once the setup is finished, refer to the to establish a connection to your virtual machine from your local machine.

🌍
instructions provided here
Note
Create a virtual machine
on this page
Example: Azure Confidential VM Configuration