Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

update s3 forwarding docs

Justin D'Souza24e6bb49c36a
diff --git a/docs/guides/jamf-anthropic-openai-cursor-mdm.mdx b/docs/guides/jamf-anthropic-openai-cursor-mdm.mdx
index a781e599..34e2b1d7 100644
--- a/docs/guides/jamf-anthropic-openai-cursor-mdm.mdx
+++ b/docs/guides/jamf-anthropic-openai-cursor-mdm.mdx
@@ -440,6 +440,23 @@ sudo launchctl print system/com.beacon.endpoint.s3-forwarder
sudo tail -n 100 /tmp/com.beacon.endpoint.s3-forwarder.err
```
+If `launchctl` reports `Could not find service "com.beacon.endpoint.s3-forwarder"`,
+the S3 files may still be present but the optional LaunchDaemon is not loaded.
+When the saved S3 environment exists, rerun the packaged installer to rewrite
+the Vector config and plist and start the service:
+
+```bash
+sudo sh -c '. "/Library/Application Support/Beacon/Forwarders/s3-vector.env"; /opt/beacon/jamf/claude/s3/install-forwarder.sh'
+sudo launchctl print system/com.beacon.endpoint.s3-forwarder | egrep 'state =|pid =|last exit code'
+```
+
+Use the same command as a Jamf remediation policy for devices where this health
+check fails:
+
+```bash
+sudo launchctl print system/com.beacon.endpoint.s3-forwarder >/dev/null 2>&1
+```
+
Verify that the env file has non-secret settings without printing credentials:
```bash
diff --git a/docs/guides/jamf-s3-mdm.mdx b/docs/guides/jamf-s3-mdm.mdx
index e9ac5615..b0b893a5 100644
--- a/docs/guides/jamf-s3-mdm.mdx
+++ b/docs/guides/jamf-s3-mdm.mdx
@@ -446,13 +446,71 @@ sudo tail -n 100 /tmp/com.beacon.endpoint.s3-forwarder.err
### Forwarder Is Not Loaded
-Load it manually:
+If `launchctl` reports `Could not find service "com.beacon.endpoint.s3-forwarder"`,
+first confirm the managed files are still present:
+
+```bash
+ls -l /opt/beacon/bin/vector
+ls -l /opt/beacon/jamf/claude/s3/install-forwarder.sh
+ls -l "/Library/LaunchDaemons/com.beacon.endpoint.s3-forwarder.plist"
+ls -l "/Library/Application Support/Beacon/Forwarders/s3-vector.toml" \
+ "/Library/Application Support/Beacon/Forwarders/s3-vector.env"
+```
+
+If the plist exists, load it:
```bash
sudo launchctl bootstrap system /Library/LaunchDaemons/com.beacon.endpoint.s3-forwarder.plist
+sudo launchctl print system/com.beacon.endpoint.s3-forwarder | egrep 'state =|pid =|last exit code'
+```
+
+If the LaunchDaemon files exist but you want an idempotent repair, rerun the
+packaged S3 installer using the saved environment. This rewrites the Vector
+config, environment file, and plist, then starts the forwarder:
+
+```bash
+sudo sh -c '. "/Library/Application Support/Beacon/Forwarders/s3-vector.env"; /opt/beacon/jamf/claude/s3/install-forwarder.sh'
+```
+
+For Jamf remediation, scope a policy to devices where the S3 forwarder is not
+loaded:
+
+```bash
+sudo launchctl print system/com.beacon.endpoint.s3-forwarder >/dev/null 2>&1
+```
+
+Then run this script on those devices, or on all Beacon devices if the original
+S3 env file should already exist everywhere:
+
+```bash
+#!/bin/bash
+set -euo pipefail
+
+ENV_PATH="/Library/Application Support/Beacon/Forwarders/s3-vector.env"
+INSTALLER="/opt/beacon/jamf/claude/s3/install-forwarder.sh"
+LABEL="com.beacon.endpoint.s3-forwarder"
+
+if [ ! -x "$INSTALLER" ]; then
+ echo "Beacon S3 installer missing: $INSTALLER" >&2
+ exit 1
+fi
+
+if [ ! -f "$ENV_PATH" ]; then
+ echo "S3 env file missing: $ENV_PATH; rerun the original S3 configuration policy" >&2
+ exit 1
+fi
+
+set -a
+# shellcheck disable=SC1090
+. "$ENV_PATH"
+set +a
+
+"$INSTALLER"
+
+launchctl print "system/$LABEL" | egrep 'state =|pid =|last exit code' || true
```
-If launchd remains opaque, run Vector in the foreground:
+If launchd remains opaque after the repair, run Vector in the foreground:
```bash
sudo /opt/beacon/jamf/claude/s3/run-forwarder.sh