Skip to main content
Version: 2.9

Installation and setup

Constellation runs entirely in your cloud environment and can be controlled via a dedicated command-line interface (CLI).

The following guides you through the steps of installing the CLI on your machine, verifying it, and connecting it to your cloud service provider (CSP).


Make sure the following requirements are met:

  • Your machine is running Linux or macOS
  • You have admin rights on your machine
  • kubectl is installed
  • Your CSP is Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP)

Install the Constellation CLI

The CLI executable is available at GitHub. Install it with the following commands:

  1. Download the CLI:
curl -LO
  1. Verify the signature (optional)

  2. Install the CLI to your PATH:

sudo install constellation-linux-amd64 /usr/local/bin/constellation

The CLI supports autocompletion for various shells. To set it up, run constellation completion and follow the given steps.

Set up cloud credentials

The CLI makes authenticated calls to the CSP API. Therefore, you need to set up Constellation with the credentials for your CSP.


If you don't have a cloud subscription, you can also set up a local Constellation cluster using virtualization for testing.

Required permissions

The following resource providers need to be registered in your subscription:

  • Microsoft.Attestation
  • Microsoft.Compute
  • Microsoft.Insights
  • Microsoft.ManagedIdentity
  • Microsoft.Network

By default, Constellation tries to register these automatically if they haven't been registered before.

To create the IAM configuration for Constellation, you need the following permissions:

  • */register/action [1]
  • Microsoft.Authorization/roleAssignments/*
  • Microsoft.Authorization/roleDefinitions/*
  • Microsoft.ManagedIdentity/userAssignedIdentities/*
  • Microsoft.Resources/subscriptions/resourcegroups/*

The built-in Owner role is a superset of these permissions.

To create a Constellation cluster, you need the following permissions:

  • Microsoft.Attestation/attestationProviders/*
  • Microsoft.Compute/virtualMachineScaleSets/*
  • Microsoft.Insights/components/*
  • Microsoft.ManagedIdentity/userAssignedIdentities/*
  • Microsoft.Network/loadBalancers/*
  • Microsoft.Network/loadBalancers/backendAddressPools/*
  • Microsoft.Network/networkSecurityGroups/*
  • Microsoft.Network/publicIPAddresses/*
  • Microsoft.Network/virtualNetworks/*
  • Microsoft.Network/virtualNetworks/subnets/*
  • Microsoft.Network/natGateways/*

The built-in Contributor role is a superset of these permissions.

Follow Microsoft's guide on understanding and assigning roles.

1: You can omit */register/Action if the resource providers mentioned above are already registered and the ARM_SKIP_PROVIDER_REGISTRATION environment variable is set to true when creating the IAM configuration.


You need to authenticate with your CSP. The following lists the required steps for testing and production environments.


The steps for a testing environment are simpler. However, they may expose secrets to the CSP. If in doubt, follow the production steps.


Simply open the Azure Cloud Shell.


Use the latest version of the Azure CLI on a trusted machine:

az login

Other options are described in Azure's authentication guide.

Next steps

You are now ready to deploy your first confidential Kubernetes cluster and application.