Splunk Cloud Data Manager Setup
Prerequisites
| Tool or access |
Purpose |
Verify |
| Bash and Python 3 |
Run bundled setup and validation helpers |
bash --version && python3 --version |
| Required product/platform access |
Inspect or configure the selected target |
Complete the documented preflight |
| Credential files for live modes |
Keep secrets out of chat |
Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Set up Splunk Cloud Data Manager, onboard cloud data sources through Data Manager, validate Data Manager
prerequisites, handle Data Manager CloudFormation or ARM or Terraform templates, diagnose Data Manager ingestion
health, migrate Azure.
- Preview and review the splunk cloud data manager setup workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Scope
Follow the documented read-only or render-first path whenever it is available.
This skill does not imply permission to mutate live systems. Require explicit
apply flags, protected credentials, and operator review for state changes.
Examples
Inspect the supported setup modes before selecting one:
bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed
without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/splunk-cloud-data-manager-setup/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the
skill supports them; help exits without mutation.
Troubleshooting
| Issue |
Cause |
Resolution |
| Preflight fails |
A required tool or access path is missing |
Resolve it before rendering or applying |
| Rendered assets are incomplete |
Required non-secret inputs are absent |
Complete intake and render again |
| Apply is blocked |
Review, credentials, or explicit acceptance is missing |
Use the documented handoff |
| Validation is incomplete |
Live evidence is unavailable |
Record the gap and keep completion open |
This skill is a render-first workflow for Splunk Cloud Platform Data Manager.
It covers AWS, Azure, GCP, and CrowdStrike onboarding guardrails, but it does
not claim private Data Manager APIs or Terraform CRUD for Data Manager inputs.
When Data Manager requires UI creation, render the exact handoff and validate
the surrounding prerequisites and generated artifacts.
Safety Rules
- Never ask for or print Splunk tokens, Azure client secrets, GCP keys,
CrowdStrike/FDR AWS secret access keys, passwords, or API keys.
- Never pass secrets as command-line arguments or environment-variable prefixes.
- Use spec file fields such as
azure.client_secret_file,
gcp.json_key_file, crowdstrike.aws_access_key_id_file, and
crowdstrike.aws_secret_access_key_file.
- Reject specs that contain raw
password, secret, token, api_key,
access_key, or private_key values unless the field name ends in _file
or _path.
- Do not invent Data Manager REST endpoints or Terraform resources. Splunk
Cloud input creation remains a UI handoff unless Splunk publishes a supported
API.
Workflow
Copy or adapt template.example with only non-secret values and secret file
paths.
Render a plan:
bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh \
--phase render \
--spec skills/splunk-cloud-data-manager-setup/template.example
Review splunk-cloud-data-manager-rendered/, especially
coverage-report.json, apply-plan.json, provider runbooks, and
doctor-report.md.
Run offline validation:
bash skills/splunk-cloud-data-manager-setup/scripts/validate.sh
Apply only supported user-supplied or Data Manager-downloaded artifacts:
bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh \
--phase apply \
--spec my-data-manager.yaml \
--accept-apply
GCP Terraform destroy additionally requires --accept-destroy; apply and
destroy cannot be enabled in the same reviewed plan.
Phases
render - default. Writes deterministic artifacts and never mutates.
doctor - render plus prioritized issue/fix report.
status - summarizes rendered status commands and health checks.
apply - requires --accept-apply, a fresh apply plan, and enabled
Data Manager-generated artifact paths.
validate - checks rendered artifacts and policy guardrails.
all - render, doctor, validate.
What It Renders
Under splunk-cloud-data-manager-rendered/:
README.md - operator summary and safe next commands.
coverage-report.json - ui_handoff, artifact_validate,
artifact_apply, splunk_validate, cloud_validate, handoff, or
not_applicable for every covered feature.
apply-plan.json - apply ordering, required accept gates, and artifact paths.
doctor-report.md - prioritized readiness and drift findings.
health-searches.spl - source-type/index searches for post-onboarding checks.
provider-runbooks/ - AWS, Azure, GCP, CrowdStrike, HEC, source catalog, and
migration runbooks.
scripts/ - validation/apply wrappers for Data Manager-generated
CloudFormation, ARM, and Terraform artifacts.
References
Read only the reference needed for the user request:
- reference.md - complete workflow, source coverage, and guardrails.
- references/aws.md - AWS CloudFormation, StackSets, S3,
custom logs, Organizations/OUs, and S3 Promote.
- references/azure.md - Azure ARM, Entra ID, Activity
Logs, Event Hubs, Monitor, and MSCS migration.
- references/gcp.md - GCP Terraform templates, Pub/Sub,
Dataflow, project/folder/org overlap checks, and edit/delete.
- references/crowdstrike.md - CrowdStrike FDR
S3/SQS onboarding, event families, and delete cleanup.
- references/source-catalog.md - official source
type and HEC ACK/token catalog.
- references/iac-and-terraform.md - what is
supported vs adjacent Terraform.
- references/research-ledger.md - source URLs
used to build this skill.
1---2name: splunk-cloud-data-manager-setup3description: "Use when the user asks to set up Splunk Cloud Data Manager, onboard cloud data sources through Data4 Manager, validate Data Manager prerequisites, handle Data Manager CloudFormation or ARM or Terraform5 templates, diagnose Data Manager ingestion health, migrate Azure Event Hubs from MSCS, promote6 historical AWS S3 data, or onboard CrowdStrike FDR data. Render, doctor, apply supported cloud-side7 artifacts for, and validate Splunk Cloud Platform Data Manager onboarding across AWS, Azure, GCP, and8 CrowdStrike with Data Manager 1.16 source coverage, HEC ACK/token guardrails, Data Manager-generated9 CloudFormation/ARM/Terraform template handling, provider prerequisite checks, health searches, migration10 warnings, and secret-file-only handoffs."11compatibility: "Splunk Cloud Platform 10.5.2605: conditional. Follow documented package, entitlement, topology, and customer-managed runtime guardrails; self-managed paths remain on the public 10.4 baseline."12metadata:13 source: https://skillmd.com/skills/chambear2809/splunk-cloud-data-manager-setup14 splunk_cloud_10_5: "conditional"15 compatibility_verified: "2026-08-20"16---1718# Splunk Cloud Data Manager Setup1920## Prerequisites2122| Tool or access | Purpose | Verify |23|---|---|---|24| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |25| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |26| Credential files for live modes | Keep secrets out of chat | Verify paths only |2728## Workflow Overview2930```text31┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐32│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │33└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘34```3536## When to Activate3738- Set up Splunk Cloud Data Manager, onboard cloud data sources through Data Manager, validate Data Manager39 prerequisites, handle Data Manager CloudFormation or ARM or Terraform templates, diagnose Data Manager ingestion40 health, migrate Azure.41- Preview and review the splunk cloud data manager setup workflow before any live apply phase.42- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4344## Scope4546Follow the documented read-only or render-first path whenever it is available.47This skill does not imply permission to mutate live systems. Require explicit48apply flags, protected credentials, and operator review for state changes.4950## Examples5152Inspect the supported setup modes before selecting one:5354```bash55bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh --help56```5758Expected output: usage, supported modes, and required arguments are displayed59without changing the target environment.6061Inspect validation modes before running completion checks:6263```bash64bash skills/splunk-cloud-data-manager-setup/scripts/validate.sh --help65```6667Expected output: offline, live, and completion options are displayed when the68skill supports them; help exits without mutation.6970## Troubleshooting7172| Issue | Cause | Resolution |73|---|---|---|74| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |75| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |76| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |77| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7879This skill is a render-first workflow for Splunk Cloud Platform Data Manager.80It covers AWS, Azure, GCP, and CrowdStrike onboarding guardrails, but it does81not claim private Data Manager APIs or Terraform CRUD for Data Manager inputs.82When Data Manager requires UI creation, render the exact handoff and validate83the surrounding prerequisites and generated artifacts.8485## Safety Rules8687- Never ask for or print Splunk tokens, Azure client secrets, GCP keys,88 CrowdStrike/FDR AWS secret access keys, passwords, or API keys.89- Never pass secrets as command-line arguments or environment-variable prefixes.90- Use spec file fields such as `azure.client_secret_file`,91 `gcp.json_key_file`, `crowdstrike.aws_access_key_id_file`, and92 `crowdstrike.aws_secret_access_key_file`.93- Reject specs that contain raw `password`, `secret`, `token`, `api_key`,94 `access_key`, or `private_key` values unless the field name ends in `_file`95 or `_path`.96- Do not invent Data Manager REST endpoints or Terraform resources. Splunk97 Cloud input creation remains a UI handoff unless Splunk publishes a supported98 API.99100## Workflow1011021. Copy or adapt `template.example` with only non-secret values and secret file103 paths.1042. Render a plan:105106 ```bash107 bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh \108 --phase render \109 --spec skills/splunk-cloud-data-manager-setup/template.example110 ```1111123. Review `splunk-cloud-data-manager-rendered/`, especially113 `coverage-report.json`, `apply-plan.json`, provider runbooks, and114 `doctor-report.md`.1154. Run offline validation:116117 ```bash118 bash skills/splunk-cloud-data-manager-setup/scripts/validate.sh119 ```1201215. Apply only supported user-supplied or Data Manager-downloaded artifacts:122123 ```bash124 bash skills/splunk-cloud-data-manager-setup/scripts/setup.sh \125 --phase apply \126 --spec my-data-manager.yaml \127 --accept-apply128 ```129130 GCP Terraform destroy additionally requires `--accept-destroy`; apply and131 destroy cannot be enabled in the same reviewed plan.132133## Phases134135- `render` - default. Writes deterministic artifacts and never mutates.136- `doctor` - render plus prioritized issue/fix report.137- `status` - summarizes rendered status commands and health checks.138- `apply` - requires `--accept-apply`, a fresh apply plan, and enabled139 Data Manager-generated artifact paths.140- `validate` - checks rendered artifacts and policy guardrails.141- `all` - render, doctor, validate.142143## What It Renders144145Under `splunk-cloud-data-manager-rendered/`:146147- `README.md` - operator summary and safe next commands.148- `coverage-report.json` - `ui_handoff`, `artifact_validate`,149 `artifact_apply`, `splunk_validate`, `cloud_validate`, `handoff`, or150 `not_applicable` for every covered feature.151- `apply-plan.json` - apply ordering, required accept gates, and artifact paths.152- `doctor-report.md` - prioritized readiness and drift findings.153- `health-searches.spl` - source-type/index searches for post-onboarding checks.154- `provider-runbooks/` - AWS, Azure, GCP, CrowdStrike, HEC, source catalog, and155 migration runbooks.156- `scripts/` - validation/apply wrappers for Data Manager-generated157 CloudFormation, ARM, and Terraform artifacts.158159## References160161Read only the reference needed for the user request:162163- [reference.md](reference.md) - complete workflow, source coverage, and guardrails.164- [references/aws.md](references/aws.md) - AWS CloudFormation, StackSets, S3,165 custom logs, Organizations/OUs, and S3 Promote.166- [references/azure.md](references/azure.md) - Azure ARM, Entra ID, Activity167 Logs, Event Hubs, Monitor, and MSCS migration.168- [references/gcp.md](references/gcp.md) - GCP Terraform templates, Pub/Sub,169 Dataflow, project/folder/org overlap checks, and edit/delete.170- [references/crowdstrike.md](references/crowdstrike.md) - CrowdStrike FDR171 S3/SQS onboarding, event families, and delete cleanup.172- [references/source-catalog.md](references/source-catalog.md) - official source173 type and HEC ACK/token catalog.174- [references/iac-and-terraform.md](references/iac-and-terraform.md) - what is175 supported vs adjacent Terraform.176- [references/research-ledger.md](references/research-ledger.md) - source URLs177 used to build this skill.