© Copyright 2024, Intel Corporation
The module can deploy an Azure Data Explorer cluster on Intel recommended Azure instances. Instance Selection have been defaulted in the code. This module was intended to be ran with an Intel Sentinel Policy as Code module that can be found here: https://registry.terraform.io/policies/intel/intel-azure/latest
For Compute Optimized instances, we recommend: Standard_E2d_v5 (default) Standard_E4d_v5 Standard_E8d_v5 Standard_E16d_v5
For Storage Optimized instances, we recommend: Standard_L8sv3 Standard_L16sv3 Standard_L32sv3 Standard_E2sv5 Standard_E4sv5 Standard_E8sv5 Standard_E16sv5
For Isolated instances, we recommend: E80idsv4
Edv5-series virtual machines run on the 3rd Generation Intel® Xeon® Platinum 8370C (Ice Lake) processor reaching an all core turbo clock speed of up to 3.5 GHz. These virtual machines offer up to 104 vCPU and 672 GiB of RAM and fast, local SSD storage up to 3800 GiB. Edv5-series virtual machines are ideal for memory-intensive enterprise applications and applications that benefit from low latency, high-speed local storage.
Esv5-series virtual machines run on the 3rd Generation Intel® Xeon® Platinum 8370C (Ice Lake) processor reaching an all core turbo clock speed of up to 3.5 GHz. These virtual machines offer up to 104 vCPU and 672 GiB of RAM. Esv5-series virtual machines don't have temporary storage thus lowering the price of entry.
The Lsv3-series of Azure Virtual Machines (Azure VMs) features high-throughput, low latency, directly mapped local NVMe storage. These VMs run on the 3rd Generation Intel® Xeon® Platinum 8370C (Ice Lake) processor in a hyper-threaded configuration. This new processor features an all-core turbo clock speed of 3.5 GHz with Intel® Turbo Boost Technology, Intel® Advanced-Vector Extensions 512 (Intel® AVX-512) and Intel® Deep Learning Boost.
Example of main.tf (located in the examples sub-folder)
## This module deploys a Azure Data Explorer with assigned principal in a user provided resource group
## 'principal_id' should be the Azure AD Object ID of the User or Service Principal to grant access to the cluster and database. It should already exist, ex: 4631d538-f3e8-3457-b155-802b52e432525(this is a fake id)
module "azure-dataexplorer" {
source = "intel/azure-adx/intel"
resource_group_name = "DS-KUSTO-RG1"
adx_sku = "Standard_E8d_v5"
principal_id = "4631d538-f3e8-3457-b155-802b52e432525"
tags = {
Owner = "user@company.com"
Duration = "4"
}
}
* **Prerequisites:**
1. Have an existing Azure Resource Group in the region you want to deploy the Azure Data Explorer cluster
2. Have an existing User or Service Principal and their Azure AD Object ID
Run Terraform
terraform init
terraform plan
terraform apply
Note that this example may create resources. Run terraform destroy
when you don't need these resources anymore.
More information regarding deploying Azure Data Explorer can be found here:Azure Data Explorer
Name | Version |
---|---|
terraform | >=1.3.0 |
azurerm | ~>3.86 |
Name | Version |
---|---|
azurerm | ~>3.86 |
random | n/a |
No modules.
Name | Type |
---|---|
azurerm_kusto_cluster.kustocluster | resource |
azurerm_kusto_cluster_principal_assignment.kustoprincipal | resource |
azurerm_kusto_database.kustodatabase | resource |
random_id.rid | resource |
azurerm_client_config.current | data source |
azurerm_resource_group.kustorg | data source |
Name | Description | Type | Default | Required |
---|---|---|---|---|
adx_sku | Instance SKU, see comments above for guidance | string |
"Standard_E8d_v5" |
no |
enable_intel_tags | If true adds additional Intel tags to resources | bool |
true |
no |
intel_tags | Intel Tags | map(string) |
{ |
no |
maximum_instances | The User or Principal ID to grant access to the cluster and database. The prinicpal id should already exist | string |
"4" |
no |
minimum_instances | The User or Principal ID to grant access to the cluster and database. The prinicpal id should already exist | string |
"2" |
no |
principal_id | The Object ID of the User or Service Principal to grant access to the cluster and database. It should already exist | string |
n/a | yes |
resource_group_name | Existing Resource Group where databricks reosurce will be created. | string |
n/a | yes |
tags | A mapping of tags to assign to all resources. | map(string) |
{} |
no |
Name | Description |
---|---|
kusto_cluster_data_ingestion_uri | Kusto Data Ingestion URI |
kusto_cluster_name | Name of the Kusto Cluster |
kusto_cluster_principal_name | Name of the Kusto Cluster Principle |
kusto_cluster_uri | Kusto Cluster URI |
kusto_rg_name | Name of the Kusto Cluster Resource Group |
kusto_sku | Kusto Cluster SKU |
kusto_tenant_id | ID of the Kusto Cluster Principle |
kusto_tenant_name | Name of the Kusto Cluster Principle |