FrostFS S3 Protocol Gateway
Find a file
Denis Kirillov 93cd6afede
Some checks failed
/ DCO (pull_request) Successful in 1m17s
/ Vulncheck (pull_request) Successful in 2m37s
/ Lint (pull_request) Failing after 14s
/ Tests (1.21) (pull_request) Successful in 2m50s
/ Tests (1.22) (pull_request) Successful in 2m45s
/ Builds (1.21) (pull_request) Successful in 2m35s
/ Builds (1.22) (pull_request) Successful in 2m30s
[#430] multipart: Support removing duplicated parts
Previously after tree split we can have duplicated parts
(several objects and tree node referred to the same part number).
Some of them couldn't be deleted after abort or compete action.

Signed-off-by: Denis Kirillov <d.kirillov@yadro.com>
2024-07-18 17:00:34 +03:00
.docker [#203] Add go1.21 to CI 2023-08-31 15:26:07 +03:00
.forgejo/workflows [#430] ci: Update go version 2024-07-17 09:08:12 +03:00
.github [#2] Keep issue templates in .github 2023-06-07 15:35:57 +00:00
api [#430] multipart: Support removing duplicated parts 2024-07-18 17:00:34 +03:00
authmate [#372] authmate: Don't create creds with eacl table 2024-07-01 16:26:21 +03:00
cmd [#414] authmate: Add register-user command 2024-07-08 14:13:00 +03:00
config [#372] Drop kludge.acl_enabled flag 2024-07-01 16:26:19 +03:00
creds [#372] Drop [e]ACL related code 2024-07-01 16:58:44 +03:00
debian [#68] Fix pre-commit issues 2023-03-24 16:22:06 +03:00
docs [#414] authmate: Add register-user command 2024-07-08 14:13:00 +03:00
internal [#430] Delete all split version at once 2024-07-18 17:00:13 +03:00
metrics [#321] Use correct owner id in billing metrics 2024-02-28 14:52:44 +03:00
pkg [#430] multipart: Support removing duplicated parts 2024-07-18 17:00:34 +03:00
.dockerignore [#471] Add docker/* target in Makefile 2022-06-16 11:12:42 +03:00
.gitignore [#133] Drop sync-tree 2023-06-09 09:34:36 +03:00
.gitlint [#65] Enable pre-commit 2023-03-24 07:28:04 +00:00
.golangci.yml [#195] Add log constants linter 2023-08-28 12:58:44 +03:00
.pre-commit-config.yaml [#195] Add log constants linter 2023-08-28 12:58:44 +03:00
CHANGELOG.md [#414] authmate: Add register-user command 2024-07-08 14:13:00 +03:00
CONTRIBUTING.md [#2] Update CONTRIBUTING 2023-06-07 15:35:57 +00:00
CREDITS.md [#68] Fix pre-commit issues 2023-03-24 16:22:06 +03:00
go.mod [#430] Fix split tree 2024-07-16 17:31:29 +03:00
go.sum [#430] Fix split tree 2024-07-16 17:31:29 +03:00
help.mk [#725] Fix help 2022-10-17 19:16:05 +03:00
LICENSE [#264] Change NeoFS S3 Gateway license to AGPLv3 2021-09-20 10:38:28 +03:00
Makefile [#430] ci: Update go version 2024-07-17 09:08:12 +03:00
README.md [#2] Keep issue templates in .github 2023-06-07 15:35:57 +00:00
updateTestsResult.sh [#68] Fix pre-commit issues 2023-03-24 16:22:06 +03:00
VERSION [#395] Port changelog and prepare it for next release 2024-05-27 14:27:11 +03:00

FrostFS logo

FrostFS is a decentralized distributed object storage integrated with the NEO Blockchain.


Report Release License

FrostFS S3 Gateway

FrostFS S3 gateway provides API compatible with Amazon S3 cloud storage service.

Installation

go get -u git.frostfs.info/TrueCloudLab/frostfs-s3-gw

Or you can call make to build it from the cloned repository (the binary will end up in bin/frostfs-s3-gw with authmate helper in bin/frostfs-s3-authmate). To build binaries in clean docker environment, call make docker/all.

Other notable make targets:

dep          Check and ensure dependencies
image        Build clean docker image
dirty-image  Build dirty docker image with host-built binaries
format       Run all code formatters
lint         Run linters
version      Show current version

Or you can also use a Docker image provided for released (and occasionally unreleased) versions of gateway (:latest points to the latest stable release).

Execution

Minimalistic S3 gateway setup needs:

  • FrostFS node(s) address (S3 gateway itself is not a FrostFS node) Passed via -p parameter or via S3_GW_PEERS_<N>_ADDRESS and S3_GW_PEERS_<N>_WEIGHT environment variables (gateway supports multiple FrostFS nodes with weighted load balancing).
  • a wallet used to fetch key and communicate with FrostFS nodes Passed via --wallet parameter or S3_GW_WALLET_PATH environment variable.

These two commands are functionally equivalent, they run the gate with one backend node, some keys and otherwise default settings:

$ frostfs-s3-gw -p 192.168.130.72:8080 --wallet wallet.json

$ S3_GW_PEERS_0_ADDRESS=192.168.130.72:8080 \
  S3_GW_WALLET=wallet.json \
  frostfs-s3-gw

It's also possible to specify uri scheme (grpc or grpcs) when using -p or environment variables:

$ frostfs-s3-gw -p grpc://192.168.130.72:8080 --wallet wallet.json

$ S3_GW_PEERS_0_ADDRESS=grpcs://192.168.130.72:8080 \
  S3_GW_WALLET=wallet.json \
  frostfs-s3-gw

Domains

By default, s3-gw enable only path-style access. To be able to use both: virtual-hosted-style and path-style access you must configure listen_domains:

$ frostfs-s3-gw -p 192.168.130.72:8080 --wallet wallet.json --listen_domains your.first.domain --listen_domains your.second.domain

So now you can use (e.g. HeadBucket. Make sure DNS is properly configured):

$ curl --head http://bucket-name.your.first.domain:8080
HTTP/1.1 200 OK
...

or

$ curl --head http://your.second.domain:8080/bucket-name
HTTP/1.1 200 OK
...

Also, you can configure domains using .env variables or yaml file.

Documentation

Credits

Please see CREDITS for details.