ByteStack can automatically write each job run’s results to your own S3-compatible bucket, giving you full control over data retention, access, and downstream processing. Once configured, results are pushed to your bucket after every run in addition to being available through ByteStack’s built-in storage API.Documentation Index
Fetch the complete documentation index at: https://docs.bytestack.com/llms.txt
Use this file to discover all available pages before exploring further.
ByteStack’s built-in storage retains result files until you explicitly delete them. Raw scrape logs are automatically purged after 90 days. If you need longer retention or want to pipe results into your own data pipeline, connect your own bucket using the steps below.
Configuring your bucket
Enter your bucket details
Provide the following details for your bucket:
| Field | Description |
|---|---|
| Endpoint | The S3-compatible endpoint URL (e.g. https://s3.us-east-1.amazonaws.com for AWS, https://<account>.r2.cloudflarestorage.com for Cloudflare R2). |
| Bucket name | The name of the bucket to write results into. |
| Access key | Your storage access key ID. |
| Secret key | Your storage secret access key. |
Supported providers
ByteStack is compatible with any S3-compatible object store. Tested providers include:AWS S3
The original S3 API. Use your region-specific endpoint, e.g.
https://s3.us-east-1.amazonaws.com.Cloudflare R2
Zero egress fees. Endpoint format:
https://<account_id>.r2.cloudflarestorage.com.MinIO
Self-hosted S3-compatible storage. Use your MinIO server’s URL as the endpoint.
Backblaze B2
Cost-effective object storage. Use the S3-compatible endpoint from your B2 bucket settings.