Explore Use Cases

Prerequisites

1 - Accounts & resources

• Active accounts (AWS/GCP/Azure; optional: DePIN like StorJ/Akave).

• At least one object bucket/container per provider you want to use (can be created/linked via Flashback).

2 - Flashback setup

1. Flashback account with access to the dashboard / API.

2. Being below the limits to create Buckets in Flashback where you link each cloud bucket with least-privilege credentials, and to create a repository and attach those Buckets.

3. Pick a protocol for your app (S3, GCS, or Azure Blob). You can mix on the backend, but each client instance uses one protocol.

4. Bridge Node endpoint for your protocol/region/provider, e.g.

   • S3: https://s3-us-east-1-aws.flashback.tech

   • GCS: https://gcs-eu-central-1-gcp.flashback.tech

   • Azure Blob: https://blob-eu-central-1-azure.flashback.tech

3 - SDKs (choose one)

• S3: AWS SDK (boto3 / aws-sdk v3 / minio client).

• GCS: google-cloud-storage.

• Azure: azure-storage-blob.

4 - Networking & security

• Outbound HTTPS to *.flashback.tech.

• Store Flashback API keys and any cloud credentials used during bucket linking in your vault (e.g., AWS Secrets Manager, GCP Secret Manager, Azure Key Vault).