Sign in
← AI PulseAug 11, 2026

Wire · news · Single-source brief

Grok Build Requires User-Supplied S3 Storage for Video Output Under Zero Data Retention

xAI's Grok Build video tools necessitate user-configured S3-compatible storage for generated videos when operating under Zero Data Retention (ZDR), ensuring videos are not stored by xAI.

By Illumora Editorial

Source · Aug 11, 2026, 5:34 PM · On Illumora · Aug 11, 2026, 5:42 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — Video Output Storage under ZDR | SpaceXAI Docs
Save

xAI has detailed a requirement for Grok Build video tools: under Zero Data Retention (ZDR), generated videos must be stored in user-supplied storage. Until this storage is configured, the video tools within Grok Build will return an error. This mechanism ensures that videos land directly in the user's bucket and are never stored by xAI.

Key Points

  • Grok Build video tools require user-supplied storage under Zero Data Retention (ZDR).
  • Without configured storage, Grok Build video tools will return an error.
  • Users must configure an S3-compatible bucket for video output.
  • The configuration involves setting parameters in ~/.grok/managed_config.toml.
  • Grok Build presigns an upload URL for each video generation.
  • The presigned URL directs the video to the user's bucket, bypassing xAI storage.
  • Credentials for S3 access are used to presign URLs but are not sent to xAI.
  • Grok Build must be restarted after configuration changes for them to take effect.

Context

According to xAI Docs, the Grok Build environment, specifically when operating with Zero Data Retention, mandates that all video output is handled by the user's own storage infrastructure. This approach is designed to maintain user data privacy by preventing xAI from retaining generated video content.

Why It Matters

This requirement impacts builders using Grok Build for video generation under ZDR, as they must integrate and manage their own S3-compatible storage. This shifts responsibility for video data retention and access directly to the user, aligning with privacy-focused operational models.

What To Do

  • Configure an S3-compatible bucket (e.g., AWS S3, Cloudflare R2, MinIO).
  • Edit ~/.grok/managed_config.toml to specify the bucket name, endpoint, and region.
  • Provide access_key_id and secret_access_key for read_write operations.
  • Consider providing read_only credentials for playback/download URLs, or manage retrieval independently.
  • Restart Grok Build after making configuration changes.

Keep Exploring

/atlas/**grok**-family