Was this page helpful?
Caution
You're viewing documentation for a previous version of ScyllaDB Open Source. Switch to the latest stable version.
This article will guide you through self-managed ScyllaDB deployment on Azure. For a fully-managed deployment of ScyllaDB as-a-service, see ScyllaDB Cloud documentation.
Note
The article covers launching a ScyllaDB image from CLI. As an alternative, you can launch a ScyllaDB instance from the Azure VM portal - search for ScyllaDB Image in Community Images.
Active Azure account
ScyllaDB Image requires at least 2 vCPU servers.
Choose an instance type. See Cloud Instance Recommendations for Azure for the list of recommended instances.
Other instance types will work, but with lesser performance. If you choose an instance type other than the recommended ones, make sure to run the scylla_setup script.
Log in to your account with az login.
If you have more than one subscription, choose one with az account set (see Change the active subscription for details).
If you do not have a resource group, create one with az group create (see az group create for details).
az group create --name <name of the group> --location <region name>
For example:
az group create --name my-group --location eastus
See the following table to obtain image information for the latest patch release. For earlier releases, see Azure Images
Gallery Image Definition |
Gallery Image Version |
Public Gallery Name |
|---|---|---|
scylla-6.1 |
6.1.3 |
scylladb-7e8d8a04-23db-487d-87ec-0e175c0615bb |
Get the ScyllaDB image ID using the information from the previous step:
scyllaImageID=$(az sig image-version show-community --location <your region name> --gallery-image-definition <ScyllaDB gallery-image-definition> --gallery-image-version <ScyllaDB gallery-image-version> --public-gallery-name <ScyllDB public-gallery-name> --query ['uniqueId'] --output tsv)
For example:
scyllaImageID=$(az sig image-version show-community --location eastus --gallery-image-definition scylla-5.2 --gallery-image-version 5.2.1 --public-gallery-name 6c268694-47ab-43ab-b306-3c5514bc4112 --query ['uniqueId'] --output tsv)
Create VM using az vm create, providing the ScyllaDB image ID from the previous step:
az vm create --resource-group <name of your resource group> --name scylladb-vm --image $scyllaImageID --admin-username <username for the VM> --ssh-key-name <existing SSH key resource in Azure> --size <VM size to be created> --location <region name> --accept-term --public-ip-sku Standard
For example:
az vm create --resource-group my-group --name scylladb-vm --image $scyllaImageID --admin-username scyllaadm --ssh-key-name ssh-key --size Standard_L8s_v3 --location eastus --accept-term --public-ip-sku Standard
Connect to the servers using the SSH key and admin-username used when creating the VM. For example:
ssh -i ~/.ssh/ssh-key.pem scyllaadm@public-ip
To check that the ScyllaDB server and the JMX component are running, run:
nodetool status
Manage your clusters with ScyllaDB Manager
Monitor your cluster and data with ScyllaDB Monitoring
Get familiar with ScyllaDB’s command line reference guide.
Learn about ScyllaDB at ScyllaDB University
Was this page helpful?