Migrate to the enhanced Edge Processor solution
Welcome! We are migrating the Edge Processor product with an enhanced control plane that will allow us to offer more advanced features in the future releases. We are scheduled to automatically migrate all your existing Edge Processors starting from 09/15/2025. This migration will cause your Edge Processors to restart. Here is your chance to proactively migrate existing Edge Processors at your convenience prior to the scheduled forced migration.
This guide will walk you through the simple process of migrating your existing Edge Processor (EP) to our new Enhanced version. The entire process typically takes about 5-10 minutes. You will need to migrate each EP instance separately.
For more information contact the Splunk support team for assistance by joining #dm-pipeline-builders on the Splunk Community Slack (request access: http://splk.it/slack).
Prerequisites
You will need SSH access to the instance where your Edge Processor is installed.
Steps
Upgrade your Edge Processor to the enhanced version by performing the following steps:
- Download the migration script:
- Navigate to your Edge Processor instance, and log in using SSH.
- Navigate to the directory where the initial Edge Processor installation occurred. The directory should contain the splunk-edge folder.
- In your deployment's Command Line Interface (CLI), download the migration script onto your instance:
curl -O https://beam.scs.splunk.com/edge-processor/migration/enhance-ep.sh
- Execute the migration script:
- Modify the script to be executable by running the following command in your terminal:
chmod +x enhance-ep.sh
- Create the migration command:
- Review the following CLI command:
./enhance-ep.sh "<AUTH_TOKEN>"
- Perform the following steps to replace the placeholder "<AUTH_TOKEN>" parameter in the command.
- Navigate into the Edge Processor that you want to migrate.
- Navigate to the Instances tab, click on the Install/uninstall button, and navigate to the Enhanced install script tab.
- In the Enhanced install script tab, copy the token (the long string in quotation marks) from the command that looks similar to the following command:
# Create an authentication token file used to connect the Edge Processor instance to your Splunk platform deployment echo "eyJhb..." > splunk-edge/var/token
- Verify that you have copied only the token.
- Replace "<AUTH_TOKEN>" in the command line with your copied token, wrapped in quotation marks. Note: Your token can be reused to migrate all instances in the same Edge Processor.
- Execute the migration command. It should look similar to the following CLI command:
./enhance-ep.sh "eyJhbGci...."
- Review the following CLI command:
- Modify the script to be executable by running the following command in your terminal:
- Verify the migration script:
- Wait for the EP instance to initialize:
- The new Edge Processor will now start and connect to the Data Management UI. This process usually takes a few minutes:
- Review the Data Management UI, and wait for the new Edge Processor instance to appear with a healthy status.
- Final verification (optional):
- Once the Edge Processor instance is displayed as healthy in the Data Management UI, run the following command in your terminal to confirm all processes are running correctly
ps -ef | grep edge | grep -v grep | awk '{print $8}'
- Expected Result: You should see three lines of output like below, which represent the core processes of the new Enhanced EP instance.
Your migration to the enhanced Edge Processor is complete.$ ps -ef | grep edge | grep -v grep | awk '{print $8}' ./splunk-edge/bin/splunk-edge /home/splunker/splunk-edge/var/sup-run/pkg-splunksup1333137856/splunksup /home/splunker/splunk-edge/var/run/pkg-edge2881476095/edge_linux_amd64
- Once the Edge Processor instance is displayed as healthy in the Data Management UI, run the following command in your terminal to confirm all processes are running correctly
- Wait for the EP instance to initialize: