beacon endpoint gcs
Usebeacon endpoint gcs to generate Google Cloud Storage forwarding content for Beacon endpoint events. The generated pack keeps Beacon as a local JSONL producer and helps your customer-managed Vector agent upload runtime.jsonl to a GCS bucket as gzip-compressed NDJSON.
Beacon does not store Google Cloud credentials, service accounts, workload identity settings, bucket IAM, lifecycle rules, retention policies, or encryption settings. Keep those values in Google Cloud, Vector, endpoint-management policy, or deployment tooling.
Commands
beacon endpoint gcs print-config
Print the Vector Google Cloud Storage forwarding template for the configured runtime log.
beacon endpoint gcs install-pack
Write Google Cloud Storage forwarding content to a directory.
beacon endpoint gcs validate
Write and describe a Beacon Google Cloud Storage validation event.
Runtime log paths
| Mode | Path |
|---|---|
| User mode | ~/.beacon/endpoint/logs/runtime.jsonl |
| System mode | /var/log/beacon-agent/runtime.jsonl |
beacon endpoint gcs print-config
beacon endpoint gcs print-config prints a Vector configuration that tails the selected Beacon runtime JSONL log and writes gzip-compressed NDJSON objects to Google Cloud Storage.
Examples
Print Vector config for the default per-user Beacon install:Flags
| Flag | Description |
|---|---|
--user | Use per-user endpoint paths. Enabled by default |
--system | Use system endpoint paths and launch daemon |
--log-path <path> | Runtime JSONL log path |
beacon endpoint gcs install-pack
beacon endpoint gcs install-pack writes Google Cloud Storage forwarding content to a directory.
gcp_cloud_storage forwarding template, and sample Beacon endpoint events.
Examples
Generate a content pack for the default per-user install:Flags
| Flag | Description |
|---|---|
--output <dir> | Output directory for the Google Cloud Storage content pack. Defaults to beacon-gcs-pack |
--user | Use per-user endpoint paths. Enabled by default |
--system | Use system endpoint paths and launch daemon |
--log-path <path> | Runtime JSONL log path |
beacon endpoint gcs validate
beacon endpoint gcs validate writes a Beacon validation event to the runtime JSONL log and prints the expected GCS validation fields and follow-up Google Cloud checks.
Examples
Write a validation event for the default per-user install:Flags
| Flag | Description |
|---|---|
--user | Use per-user endpoint paths. Enabled by default |
--system | Use system endpoint paths and launch daemon |
--log-path <path> | Runtime JSONL log path |
Related
Google Cloud Storage forwarding
Configure Vector forwarding from Beacon JSONL into Google Cloud Storage.
SIEM forwarding
Review forwarding patterns and validation steps.
Endpoint agent
Install and inspect the local endpoint agent.
Endpoint event schema
Review normalized Beacon JSONL fields and example events.

