<commit_before># Create Splunk Enterprise standalone or cluster on Azure

**US Government Cloud**

[![Deploy to Azure Gov](https://azuredeploy.net/AzureGov.png)](https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fazure%2Fazure-quickstart-templates%2Fmaster%2Fsplunk-on-ubuntu%2Fazuredeploy-gov.json)

**NOTE regarding deployment to US Government Cloud**

The template system that deploys to US Government Cloud is largely identical to that for the public cloud. If launched using the "Deploy to Azure Gov" button above, the **standalone** and **cluster** deployment types are available but without as many configuration options in the UI as the public cloud. To gain access to the additional configuration options, tailor the templates to your needs and use the Azure CLI to launch. Deployment to the US Government Cloud requires your Azure subscription to be whitelisted for that purpose.

**Public Cloud**

[![Deploy to Azure](https://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsplunk-on-ubuntu%2Fazuredeploy.json)

This template deploys Splunk Enterprise 6.6 on Azure as either **standalone** instance or distributed **cluster** (up to 20 indexers). Each instance has eight (8) 1-TB data drives in RAID0 configuration. The template also provisions a storage account, a virtual network with subnets, public IP address, and all network interfaces & security groups required.

Once the deployment is complete, Splunk Enterprise can be accessed using the configured DNS address. The DNS address will include the `domainNamePrefix` and `location` entered as parameters in the format `{domainNamePrefix}.{location}.cloudapp.azure.com`. If you created a deployment with `domainNamePrefix` parameter set to "splunk" in the West US region, then Splunk Enterprise can be accessed at `https://splunk.westus.cloudapp.azure.com`.

Below is the list of template parameters:

| Name   | Required | Description |
|:--- |:--- |:---|
| location | :heavy_check_mark: | Location where Azure resources will be created |<commit_msg>update uri for template testing<commit_after># Create Splunk Enterprise standalone or cluster on Azure

**US Government Cloud**

[![Deploy to Azure Gov](https://azuredeploy.net/AzureGov.png)](https://portal.azure.us/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fazure%2Fazure-quickstart-templates%2Fmaster%2Fsplunk-on-ubuntu%2Fazuredeploy-gov.json)

**NOTE regarding deployment to US Government Cloud**

The template system that deploys to US Government Cloud is largely identical to that for the public cloud. If launched using the "Deploy to Azure Gov" button above, the **standalone** and **cluster** deployment types are available but without as many configuration options in the UI as the public cloud. To gain access to the additional configuration options, tailor the templates to your needs and use the Azure CLI to launch. Deployment to the US Government Cloud requires your Azure subscription to be whitelisted for that purpose.

**Public Cloud**

[![Deploy to Azure](https://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Frockygiglio%2Fazure-quickstart-templates%2Fmaster%2Fsplunk-on-ubuntu%2Fazuredeploy.json)


This template deploys Splunk Enterprise 6.6 on Azure as either **standalone** instance or distributed **cluster** (up to 20 indexers). Each instance has eight (8) 1-TB data drives in RAID0 configuration. The template also provisions a storage account, a virtual network with subnets, public IP address, and all network interfaces & security groups required.

Once the deployment is complete, Splunk Enterprise can be accessed using the configured DNS address. The DNS address will include the `domainNamePrefix` and `location` entered as parameters in the format `{domainNamePrefix}.{location}.cloudapp.azure.com`. If you created a deployment with `domainNamePrefix` parameter set to "splunk" in the West US region, then Splunk Enterprise can be accessed at `https://splunk.westus.cloudapp.azure.com`.

Below is the list of template parameters:

| Name   | Required | Description |
|:--- |:--- |:---|
| location | :heavy_check_mark: | Location where Azure resources will be created |
{'fraction_non_alphanumeric': 0.08833522083805209, 'fraction_numerical': 0.010419026047565118, 'mean_word_length': 5.4941176470588236, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3798548', 'n_tokens_mistral': 1206, 'n_tokens_neox': 1152, 'n_words': 484}