ForkDatabricks (DBRX)Databricks (DBRX)published Mar 19, 2023seen 5d

databricks/cloudflare-b2-proxy

forked from backblaze-b2-samples/cloudflare-b2-proxy

Open original ↗

Captured source

source ↗
published Mar 19, 2023seen 5dcaptured 17hhttp 200method plain

databricks/cloudflare-b2-proxy

Description: Proxy Backblaze S3 compatible API requests, optionally sending notifications to a webhook

License: Apache-2.0

Stars: 0

Forks: 0

Open issues: 0

Created: 2023-03-19T18:15:10Z

Pushed: 2023-03-22T19:56:12Z

Default branch: master

Fork: yes

Parent repository: backblaze-b2-samples/cloudflare-b2-proxy

Archived: yes

README:

Cloudflare Worker Backblaze B2 Proxy

Proxy Backblaze S3 compatible API requests, optionally sending notifications to a webhook.

  • Incoming requests must be signed with the same credentials that you configure in the worker. The worker validates the AWS V4 signature on all downstream (incoming) requests and then signs the upstream (outgoing) request.
  • Notifications are dispatched asynchronously to avoid delaying the response to the client.

You can use any S3 SDK or CLI to send requests as long as you set the endpoint URL to the worker endpoint. For example:

% export AWS_ACCESS_KEY_ID=
% export AWS_SECRET_ACCESS_KEY=
% aws s3 cp --endpoint-url https://cloudflare-b2-proxy..workers.dev hello.txt s3:///hello.txt
upload: hello.txt to s3:///hello.txt

Informal testing suggests that there is negligible performance overhead imposed by the signature verification and resigning.

Configuration

You must configure AWS_ACCESS_KEY_ID and AWS_S3_ENDPOINT in wrangler.toml. Configure WEBHOOK_URL if you wish to supply a webhook URL.

[vars]
AWS_ACCESS_KEY_ID = ""
AWS_S3_ENDPOINT = ""
WEBHOOK_URL = ""

You must also configure AWS_SECRET_ACCESS_KEY as a secret:

echo "" | wrangler secret put AWS_SECRET_ACCESS_KEY

Webhook Notification

If you set WEBHOOK_URL, the worker POSTs a JSON payload to that URL for each request that it processes. For example:

{
"contentLength": "14",
"contentType": "text/plain",
"method": "PUT",
"signatureTimestamp": "20220224T193204Z",
"status": 200,
"url": "https://s3.us-west-004.backblazeb2.com/my-private-bucket/tester.txt"
}

You can customize the handleRequest() function to add additional data as you require.

Wrangler

You can use this repository as a template for your own worker using `wrangler`:

wrangler generate projectname https://github.com/backblaze-b2-samples/cloudflare-b2-proxy

Serverless

To deploy using serverless add a `serverless.yml` file.

Acknowledgements

Based on https://github.com/obezuk/worker-signed-s3-template