Release artifacts - Hilt Documentation

Every release of the collector ships as two static Linux tarballs, one for aarch64 (ARM64 / Graviton) and one for x86_64 (Intel / AMD), plus a matching multi-arch container image. Use the tarball on VMs, and the container image on Kubernetes.

S3 layout

Artifacts live in the private Hilt release bucket, keyed by architecture then version (arm64 for ARM64 / Graviton, x86_64 for Intel / AMD):

s3://hilt-dag-agent-use1-297433793776/<arch>/v<X>/
└── dag-agent-v<X>-linux-<arch>.tar.gz     # <arch> = arm64 | x86_64

The bucket is private; the dashboard proxies downloads (Collectors → Add Collector) and, for Cloud Connect remote install, hands out short-lived presigned URLs — you never need bucket credentials.

Tarball contents

dag-agent-v<X>-linux-<arch>/
├── dag-agent              # static binary
├── dag-agent.service      # systemd unit
├── install.sh             # interactive installer
├── uninstall.sh           # stops service, removes binary
└── k8s/
    ├── Dockerfile
    ├── daemonset.yaml     # Kubernetes DaemonSet
    └── dag-agent

Airgapped / offline bundle

For fully airgapped environments, request the offline bundle. It is the same artifact set plus a docker save-ed tar of the container image, shipped as a single dag-agent-v<X>-offline.tar.gz you can copy to the target environment and docker load / tar xzf locally.