Skip to main content

Foxglove Cloud, bring your own storage

Set up a Foxglove Cloud Primary Site that reads data directly from your own cloud storage bucket. Foxglove manages all processing infrastructure — you provide the bucket and grant access.

note

GCP support is in development. AWS and Azure are available now.

Overview​

With Foxglove Cloud bring-your-own-storage, your recordings stay in your cloud storage while Foxglove operates the indexing, querying, and streaming services in the same cloud region. There's no Kubernetes cluster to deploy or Helm chart to manage.

The setup process:

  1. Create a storage bucket (or use an existing one)
  2. Create a site in the Foxglove app, selecting your cloud provider and region
  3. Grant the Foxglove read identity access to your bucket
  4. Configure bucket notifications so Foxglove knows when new files arrive
  5. Verify the connection

How it works​

Bring-your-own-storage sites use index-in-place storage. Once bucket notifications are configured, the flow for each recording is:

  1. You upload a file to your bucket, which triggers a notification to Foxglove.
  2. Foxglove's indexer reads metadata from the file — time ranges, topics, and channel information — and stores that index.
  3. When you visualize or query data, Foxglove's query service reads directly from the original file in your bucket.

The original recordings remain the only copy of your data. Foxglove never transcodes, duplicates, or moves your files. Recording lifecycle is entirely yours — delete a file from your bucket and Foxglove's index updates automatically.

Each site gets a Foxglove-provided read identity scoped to the cloud provider and region. Grant bucket access to the identity shown on the site details page.

Metadata sent to Foxglove​

At index time, Foxglove extracts and stores metadata such as time ranges, topic names, and channel information. At query time, Foxglove's query service reads message data directly from your bucket — message contents, sensor data, and attachments are never copied to Foxglove storage. See the Primary Sites FAQ (applicable to all deployment models) for the full list of metadata fields.

Prerequisites​

  • A cloud provider account (AWS, GCP, or Azure)
  • Organization admin access in Foxglove

Setup​

Create a storage bucket​

Create a cloud storage bucket for your recordings, or use an existing one.

tip

Foxglove reads directly from your original files, so file layout affects query performance. Before uploading:

  • Use lz4 or zstd chunk compression for MCAP files; use lz4 for ROS 1 .bag files (bz2 is not recommended)
  • Keep chunk sizes small (< 1 MiB) to minimize query latency
  • Partition high-bitrate topics (for example, images, point clouds) into separate files from low-bitrate telemetry

See storage mode for more details.

Create a site​

  1. Go to the Sites settings page
  2. Click Create site
  3. Select your cloud provider (AWS, GCP, or Azure)
  4. Enter your bucket details and region

No additional fields are required.

  1. Click Create

After creation, the site details page displays the identifiers and ready-to-run CLI commands you need for the next two steps. Enter your values below and the commands on this page will update automatically:

Bucket name:

IAM principal ARN:

SNS topic ARN:

Grant bucket access​

Grant Foxglove read access to your storage bucket.

The service account is an IAM role ARN. Add a bucket policy granting it read access:

aws s3api put-bucket-policy --bucket <your-bucket> --policy '{
"Version": "2012-10-17",
"Statement": [
  {
    "Effect": "Allow",
    "Principal": { "AWS": "<site-role-arn>" },
    "Action": ["s3:GetObject", "s3:ListBucket"],
    "Resource": ["arn:aws:s3:::<your-bucket>", "arn:aws:s3:::<your-bucket>/*"]
  }
]
}'

Or apply through the S3 Console under your bucket's Permissions > Bucket policy section.

Configure bucket notifications​

Foxglove needs to know when files in your bucket are added or removed. Some cloud providers can also notify Foxglove when files transition between storage tiers. The notification mechanism varies by cloud provider.

Configure S3 Event Notifications on your bucket for object change events, pointing to the Foxglove SNS topic ARN shown on your site's details page:

aws s3api put-bucket-notification-configuration --bucket <your-bucket> --notification-configuration '{
"TopicConfigurations": [
  {
    "TopicArn": "<foxglove-sns-topic-arn>",
    "Events": [
      "s3:ObjectCreated:*",
      "s3:ObjectRemoved:*",
      "s3:LifecycleExpiration:*",
      "s3:LifecycleTransition",
      "s3:IntelligentTiering",
      "s3:ObjectRestore:*"
    ]
  }
]
}'

Foxglove's SNS topic policy already permits your bucket to publish to it. You can also configure this through the S3 Console under Properties > Event notifications.

You can also notify Foxglove of new files directly via the /site-bucket-notifications API endpoint. This is useful if you want to trigger indexing from a custom pipeline rather than relying on cloud-native bucket events.

Verify the connection​

After completing setup, the site details page shows the connection status:

  • Bucket access — Foxglove periodically checks that the Foxglove read identity can read from your bucket. Once access is confirmed, the status updates automatically.
  • Bucket notifications — Upload or update a test file in your bucket. Once Foxglove receives the notification, the status updates.

If either check fails, review the access grants and notification configuration above.

Manage data​

Uploading recordings​

Upload recordings directly to your storage bucket using your cloud provider's tools (for example, aws s3 cp, gcloud storage cp, or az storage blob upload). Once the bucket notification fires, Foxglove indexes the file and it appears on the Recordings page.

You can associate metadata with recordings using object metadata or MCAP metadata records. See the Primary Site metadata documentation (applicable to all deployment models) for details on supported keys and formats.

Deleting recordings​

Delete recording files directly from your storage bucket. The indexer periodically scans object storage and automatically removes recordings whose underlying files no longer exist.

Site deletion​

When you delete a bring-your-own-storage site, Foxglove tears down the associated compute resources. You're responsible for:

  • Revoking the bucket access grant for the site's Foxglove read identity
  • Removing bucket notification configuration

Supported file formats​

Bring-your-own-storage sites support the same file formats as index-in-place on-premises sites:

  • MCAP files with chunk indexes
  • ROS 1 .bag files with an index section
tip

If a recording lacks an index section, rebuild it with mcap recover or rosbag reindex.

Other deployment models​

For a full comparison of all deployment models — including Foxglove Cloud and on-premises — see choosing a deployment model.

Support​

For assistance, contact support@foxglove.dev.