| .config | ||
| .github/workflows | ||
| .vscode | ||
| docker | ||
| .dockerignore | ||
| .drone.yml | ||
| .env.example | ||
| .gitignore | ||
| .goreleaser.yml | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| obs.go | ||
| obs_s3.go | ||
| obs_s3_test.go | ||
| obs_storj.go | ||
| obs_storj_test.go | ||
| README.md | ||
| server.go | ||
| server_s3.go | ||
| server_storj.go | ||
| util.go | ||
| util_test.go | ||
obs-access-signer
S3 Object Storage access signer.
Run obs-access-signer behind a gateway/cache proxy is preferred as the response is static (See "Why?" section).
There's an example of using it with Varnish Cache, which you can see here.
Why?
Some S3-compatible gateways might not support ACL endpoints but they support presigned access. Currently, the behavior of obs-access-signer is similar to public-read ACL where clients can access objects anonymously and redirect them (permanently) to presigned URL with Expires set to the max signed value of int64 which has roughly 250yrs lifetime since UNIX time started.
Update: starting at v0.0.3, obs-access-signer supports custom redirection status code and expiry.
Update: starting at v0.0.4, obs-access-signer supports libuplink, we can use this feature by specifying SERVER_MODE=storj on the environment variable OR -server=storj CLI flag.
License
Apache-2.0