Edit

Test a Public Bridge Node

Note: All code examples in this guide use Bash shell commands for AWS CLI, gsutil, and Azure CLI. Flashback is also expected to support all existing client SDKs of providers available for all languages and major API operations.

The guide is experimental and may contain errors as our technology continues to evolve. If you encounter any problems, please do not hesitate to contact us in Discord and give us your feedback.

Instructions

This guide walks you through connecting your preferred S3‑, GCS‑, or Azure‑compatible client to a Flashback Bridge Node for programmatic access to your Repositories.

1

Prerequisites

  • Repository & API Key: You’ve already created a Repository in Flashback and generated a READ or WRITE API key (see Create a Repository).

  • Client Tools Installed: One of the following installed on your machine:

    • AWS CLI or any S3‑compatible SDK (e.g., awscli, boto3)

    • gsutil or GCS‑compatible SDK (e.g., google-cloud-storage)

    • Azure CLI or Azure Blob SDK

2

Define Your Bridge Endpoint

  1. In the Flashback UI, go to Storage > Repositories.

  2. Click your target Repository to open its overview.

  3. In the Overview tab, copy the Bridge URL for your desired protocol and region:

    • S3 endpoint: https://s3-<region>-<provider>.flashback.tech

    • GCS endpoint: https://gcs-<region>.flashback.tech

    • Azure Blob endpoint: https://blob-<region>.flashback.tech

Note: Replace <region> and <provider> with the values shown in your UI.

3

Configure Your Client

S3‑Compatible Clients (AWS CLI / SDKs)

# Configure AWS CLI profile for Flashback
aws configure set profile.flashback.s3.endpoint_url https://s3-us-east-1-aws.flashback.tech
aws configure set profile.flashback.s3.region us-east-1
aws configure set profile.flashback.aws_access_key_id YOUR_API_KEY_ID
aws configure set profile.flashback.aws_secret_access_key YOUR_API_SECRET

To test listing your repository buckets:

aws --profile flashback s3 ls

GCS‑Compatible Clients (gsutil / SDKs)

Edit (or create) ~/.boto and add:

[Credentials]
gs_access_key_id = YOUR_API_KEY_ID
gs_secret_access_key = YOUR_API_SECRET

[Boto]
storage_host = gcs-us-east-1.flashback.tech

Test listing buckets:

gsutil ls

Azure Blob Clients (Azure CLI / SDKs)

# Log in using SAS token or account key
export AZURE_STORAGE_ACCOUNT=<account-name>
export AZURE_STORAGE_KEY=YOUR_API_SECRET

# Override endpoint
az storage blob list --account-name $AZURE_STORAGE_ACCOUNT \
  --endpoint https://blob-us-east-1.flashback.tech
4

Verify Access

  • List Buckets/Containers: run the list commands shown above.

  • Upload/Download: use aws s3 cp, gsutil cp, or az storage blob upload/download to transfer test files.

Example S3 upload:

aws --profile flashback s3 cp hello.txt s3://<your-bucket>/hello.txt

Troubleshooting

  • Authentication Errors: Double‑check your API key ID and secret.

  • Endpoint Not Found: Confirm you’re using the exact URL from the UI.

  • Permission Denied: Ensure your API key has the correct READ/WRITE scope for the repository.

Last updated: 07/06/2025

PreviousCreate a RepositoryNextUpload/Download a File

Last updated

Was this helpful?