Set up Data Manager

Data Manager ships as a built-in application in Splunk Cloud Platform and is available on Amazon Web Services (AWS) commercial stacks, for Splunk Cloud Platform customers on the Classic or Victoria Experience.

For more information on Splunk Cloud Platform experiences, see the Experience designations section of the Splunk Cloud Platform Service Description manual.

Splunk platform roles and capabilities

Role requirements

If the user of the Data Manager app has either the admin or sc_admin role, then all role and capability requirements are met by default.

If a user does not have the admin or sc_admin role, they must verify that their assigned roles collectively contain all of the capabilities listed in the Capability requirements section of this topic.

Note: The following roles do not have custom Tags. These roles are created as part of the prerequisites step in the Data Manager app:
  1. SplunkDMReadOnly
  2. AWSCloudFormationStackSetAdministrationRole
  3. AWSCloudFormationStackSetExecutionRole

Capability requirements

In order to operate Data Manager, each user must have a role that has the following capabilities on Splunk Cloud Platform:

'accelerate_search' 
'admin_all_objects'  
'dmc_deploy_apps' 
'dmc_deploy_token_http' 
'edit_httpauths' 
'edit_sourcetypes' 
'edit_token_http' 
'edit_view_html' 
'get_metadata' 
'get_typeahead' 
'indexes_edit' 
'indexes_list_all' 
'list_accelerate_search' 
'list_httpauths' 
'list_inputs' 
'list_settings' 
'list_storage_passwords' 
'list_tokens_own' 
'list_tokens_scs' 
'output_file' 
'rest_apps_management'
'rest_properties_get'
'rest_properties_set'
'run_collect'
'run_mcollect'
'schedule_rtsearch'
'schedule_search'
'search'

Splunk platform requirements

Search head requirements

Data Manager is available only on the primary search head of your Splunk Cloud deployment. Contact your Splunk Cloud administrator to find out which node or cluster has primary set to true.

Enable indexes

After creating the role with the listed capabilities, perform the following steps to enable the indexes needed for Data Manager to work.

  1. Navigate to Edit Role.
  2. Navigate to Indexes, and select the Included box for All non-internal indexes.
  3. Save your changes.

Regional availability by cloud providers

Data Manager is supported on different regions depending on your cloud provider.

Cloud providerRegions
Amazon Web Services

Data Manager is available on Splunk Cloud in the following AWS regions:

  • US East Virginia
  • US West Oregon
  • UK (London)
  • Europe (Dublin, Frankfurt, Paris)
  • Asia Pacific (Mumbai, Seoul, Singapore, Sydney, Tokyo)
  • Canada (Central)

For more information on Splunk Cloud experiences, see the Available regions and region differences section of the Splunk Cloud Platform manual.

Microsoft AzureData Manager is supported in all Azure regions, except for Azure Government regions.
Google Cloud PlatformData Manager is currently supported on all Google Cloud Platform regions.

Supported regions for data ingestion

The supported regions for data ingestion from AWS, Azure, and Google Cloud Platform.

The supported regions for data ingestion from AWS, Azure, and Google Cloud Platform.

Cloud providerRegions
Amazon Web Services
  • US East (N. Virginia) us-east-1
  • US East (Ohio) us-east-2
  • US West (N. California) us-west-1
  • US West (Oregon) us-west-2
  • Canada (Central) ca-central-1
  • South America (Sao Paulo) sa-east-1
  • EU (Frankfurt) eu-central-1
  • EU (Ireland) eu-west-1
  • EU (London) eu-west-2
  • EU (Milan) eu-south-1
  • EU (Paris) eu-west-3
  • EU (Stockholm) eu-north-1
  • Middle East (Bahrain) me-south-1
  • Africa (Cape Town) af-south-1
  • Asia Pacific (Tokyo) ap-northeast-1
  • Asia Pacific (Seoul) ap-northeast-2
  • Asia Pacific (Mumbai) ap-south-1
  • Asia Pacific (Singapore) ap-southeast-1
  • Asia Pacific (Sydney) ap-southeast-2
  • Asia Pacific (Hong Kong) ap-east-1
Microsoft Azure

You can select your Azure region from the available options in Data Manager. The list of available regions applies to a given configuration only.

  • (Africa) South Africa North southafricanorth
  • (Asia Pacific) East Asia eastasia
  • (Asia Pacific) Australia East australiaeast
  • (Asia Pacific) Australia Southeast australiasoutheast
  • (South America) Brazil South brazilsouth
  • (Canada) Canada Central canadacentral
  • (Canada) Canada East canadaeast
  • (Europe) North Europe northeurope
  • (Europe) West Europe westeurope
  • (Europe) France Central francecentral
  • (Europe) Germany West Central germanywestcentral
  • (Asia Pacific) Central India centralindia
  • (Asia Pacific) West India westindia
  • (Asia Pacific) Japan East japaneast
  • (Asia Pacific) Japan West japanwest
  • (Asia Pacific) Korea Central koreacentral
  • (Europe) Norway East norwayeast
  • (Europe) Switzerland North switzerlandnorth
  • (Middle East) UAE North uaenorth
  • (Europe) UK South uksouth
  • (US) Central US centralus
  • (US) East US eastus
  • (US) East US 2 eastus2
  • (US) North Central US northcentralus
  • (US) South Central US southcentralus
  • (US) West Central US westcentralus
  • (US) West US westus
  • (US) West US 2 westus2
Google Cloud Platform

The regions where the Google Cloud Dataflow job will be created.

To learn more about regions, search for "Regions and zones" in the Google Cloud documentation.

  • EU (Zurich) europe-west6
  • EU (Zurich) europe-west6
  • EU (Zurich) europe-west6
  • EU (Frankfurt) europe-west3
  • EU (London) europe-west2
  • EU (Belgium) europe-west1
  • EU (Madrid) europe-southwest1
  • EU (Finland) europe-north1
  • EU (Warsaw) europe-central2
  • Asia Pacific (Melbourne) australia-southeast2
  • Asia Pacific (Sydney) australia-southeast1
  • Asia Pacific (Jakarta) asia-southeast2
  • Asia Pacific (Singapore) asia-southeast1
  • Asia Pacific (Delhi) asia-south2
  • Asia Pacific (Mumbai) asia-south1
  • Asia Pacific (Seoul) asia-northeast3
  • Asia Pacific (Osaka) asia-northeast2
  • Asia Pacific (Tokyo) asia-northeast1
  • Asia Pacific (Hong Kong) asia-east2
  • Asia Pacific (Taiwan) asia-east1
  • US South (Dallas, Texas) us-south1
  • US West (Las Vegas, Nevada) us-west4
  • US West (Salt Lake City, Utah) us-west3
  • US West (Los Angeles, California) us-west2
  • US West (Oregon) us-west1
  • US East (Columbus, Ohio) us-east5
  • US East (Northern Virginia) us-east4
  • US East (SouthCarolina) us-east1
  • US Central (Iowa) us-central1
  • South America (Santiago) southamerica-west1
  • South America (São Paulo) southamerica-east1
  • North America (Toronto) northamerica-northeast2
  • North America (Montréal) northamerica-northeast1

Cost considerations

Deploying templates in the accounts of your cloud service provider will incur a cost. The total amount of this cost depends on your cloud service provider, and the amount of data that you wish to ingest.

For more information, see the pricing documentation for your cloud service provider.