Splunk® Cloud Gateway

Install and Administer Splunk Cloud Gateway

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

Install Splunk Cloud Gateway

Admins can install Splunk Cloud Gateway to manage mobile devices and configure the Connected Experiences mobile apps. If you run into issues with installation or connection, see Troubleshoot Splunk Cloud Gateway and Troubleshoot Splunk Cloud Gateway Connection Issues for more information.

To learn more about Splunk Cloud Gateway, see About Splunk Cloud Gateway.

Splunk Cloud Gateway is not SOC2 compliant.

Prerequisites and Requirements

  • Have admin or sc_admin role access.
  • Make sure that KV store is running. See KV store troubleshooting tools and Back up and restore KV store to learn how to check the status of KV store and for KV store best practices.
  • If you're using a proxy, open port 443 outbound to prod.spacebridge.spl.mobi to enable Splunk Cloud Gateway.
  • Use a compatible proxy server, operating system, and Splunk Enterprise or Splunk Cloud version. See the following table for compatible proxies, operating systems, Splunk Enterprise versions, and directory services:
Component Requirements
Proxy server

Set up a proxy in server.conf

If you're using a proxy server, it must be a forward HTTPS proxy and support HTTP CONNECT. Squid Forward Proxy, Apache Forward Proxy, and Nginx Forward Proxy have been tested and verified as compatible. If you're using another forward proxy and running into issues, there might be a configuration issue. See Troubleshoot Splunk Cloud Gateway Connection Issues for more information about troubleshooting proxy issues.

Because Splunk Gateway doesn't trust third party certificates, man-in-the-middle proxy servers are not supported.

To configure your proxy server, see Configure splunkd to use your HTTP Proxy Server in the Splunk Enterprise Admin Manual.

Here's how to edit server.conf to configure splunkd to work with your server proxy:

[proxyConfig] 
https_proxy = <string that identifies the server proxy. When set, splunkd sends all HTTPS requests through the proxy server defined here. If not set, splunkd uses the proxy defined in http_proxy. The default value is unset.>  
no_proxy = <string that identifies the no proxy rules. When set, splunkd uses the [no_proxy] rules to decide whether the proxy server needs to be bypassed for matching hosts and IP Addresses. Requests going to localhost/loopback address are not proxied. Default is "localhost, 127.0.0.1, ::1">

If using a proxy that requires authentication, do not use # or @ in your password. Splunk Cloud Gateway misinterprets # and @ in passwords.

Set up a Splunk Cloud Gateway specific proxy in cloudgateway.conf

Configuring [proxyConfig] in cloudgateway.conf allows all outgoing Splunk Cloud Gateway calls to pass through the defined proxy. To set up a Splunk Cloud Gateway specific proxy in cloudgateway.conf, see the [proxyConfig] stanza in Configure cloudgateway.conf.

The [proxyConfig] stanza in cloudgateway.conf does not affect any other traffic in the splunkd process. For example, if you set [proxyConfig] in cloudgateway.conf and in server.conf, splunkd will stlll respect the [proxyConfig] stanza in server.conf for all other traffic.

Operating System Splunk Cloud Gateway is compatible with Mac, Windows, and Linux operating systems.

If you're using Splunk Cloud Gateway version 1.13.0 with Windows, Create inputs.conf in the /local directory and add the following lines:

[subscription_modular_input://default]
subscription_processor_parallelism = 1
Hardware Splunk Cloud Gateway requires a minimum processor size of 4 cores and 16GB of ram. The minimum AWS instance size is m5.xlarge.
Splunk Platform Version

Splunk Cloud Gateway requires Splunk Enterprise or Splunk Cloud version 7.1.0 or later. Splunk Cloud Gateway is not compatible with Python 3 yet. If you're using Splunk 8.0, set python.version = 2 in server.conf. See Python 3 migration with the Splunk platform for information about the Splunk Platform versions that support Python 3.

Splunk Cloud Gateway does not work with free trial instances.

Splunk Enterprise Role Admin, power, and normal users can use Splunk Cloud Gateway if they have the cloudgateway role.
Directory Service Splunk Cloud Gateway supports LDAP authentication, SAML authentication, and local Splunk accounts. See Set up SAML authentication for Splunk Cloud Gateway for more information about SAML authentication.

Install Splunk Cloud Gateway from Splunkbase

Install Splunk Cloud Gateway on the search head cluster.

  1. Launch Splunk Enterprise.
  2. Log in.
  3. Download Splunk Cloud Gateway from Splunkbase.
  4. Click the Apps gear icon in Splunk Enterprise.
  5. Click Install app from file.
  6. Click Choose File and select the downloaded Splunk Cloud Gateway file.
  7. Click Upload.
  8. Restart your Splunk Platform.

Install Splunk Cloud Gateway on Splunk Cloud

Installing Splunk Cloud Gateway on Splunk Cloud through SSAI requires Splunk Cloud version 7.1.x or later.

Download Splunk Cloud Gateway in your Splunk Cloud Deployment from Splunkbase. See Install apps in your Splunk Cloud deployment in the Splunk Cloud User Manual for further instructions.

To install Splunk Cloud Gateway on Splunk Cloud version 7.0.x or earlier, submit a case to Splunk Support. See Contact Splunk Support for contact information and how to submit a case.

Upgrade Splunk Cloud Gateway

Upgrade Splunk Cloud Gateway by downloading the latest version from Splunkbase and installing it on your Splunk Enterprise or Splunk Cloud instance.

Upgrade Splunk Cloud Gateway on Mac or Linux

To upgrade Splunk Cloud Gateway on Mac or Linux, follow these steps:

  1. Download the app from Splunkbase.
  2. Check Upgrade app to overwrite the older version of Splunk Cloud Gateway.
  3. Click Upload.

Upgrade Splunk Cloud Gateway on Windows

To upgrade Splunk Cloud Gateway, first stop Splunk and remove the existing Splunk Cloud Gateway App. To stop Splunk, see Stop Splunk Enterprise in the Splunk Enterprise Admin Manual. To uninstall the existing Splunk Cloud Gateway app, see Uninstall an app or add-on in the Splunk Admin Manual.

  1. Stop Splunk.
  2. Uninstall the existing Splunk Cloud Gateway app.
  3. Install the app from Splunk Cloud Gateway.
  4. Check Upgrade app to overwrite the older version of Splunk Cloud Gateway.
  5. Click Upload.

Deploy Splunk Cloud Gateway in a distributed environment

If you're installing Splunk Cloud Gateway in a distributed environment, install it on all members of the search head cluster. See Deploy apps to clusters in the Splunk Enterprise Admin Manual to deploy Splunk Cloud Gateway to search head clusters.

Splunk Cloud Gateway operations occur on all search heads.

Last modified on 28 October, 2020
PREVIOUS
About Splunk Cloud Gateway
  NEXT
About the Splunk Cloud Gateway security process

This documentation applies to the following versions of Splunk® Cloud Gateway: 1.9.0, 1.9.1, 1.11.0, 1.12.0, 1.12.1, 1.12.2, 1.12.4, 1.13.0


Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters