splunk-connect-for-syslog-setup

Automate Splunk Connect for Syslog setup by coordinating default index creation, verifying HEC token configuration, and rendering Docker or Kubernetes deployment assets for Splunk Enterprise or Cloud.

Yes, you can render Kubernetes deployment assets by generating Helm charts for SC4S, or alternatively render Docker or Podman assets using compose and systemd configurations for host-based deployments.

No, SC4S setup automates Splunk-side preparation by creating default SC4S indexes and verifying or creating the necessary HEC token, enforcing credential handling safety throughout the configuration process.

Validate SC4S startup readiness by running provided validation steps that check credential configuration and ensure syslog ingestion via HEC is fully operational before deploying the rendered assets.

Rendered SC4S deployment assets are written exclusively to a gitignored render directory to enforce credential safety, requiring Python3 and limiting direct deployment outputs to host or Kubernetes environments.

Yes, Python3 is required as a dependency to run the setup workflow that validates credentials, renders host or Kubernetes deployment assets, and validates SC4S startup readiness.