105 lines
3.3 KiB
Markdown
105 lines
3.3 KiB
Markdown
<p align="center">
|
|
<img src="./.forgejo/logo.svg" width="500px" alt="FrostFS logo">
|
|
</p>
|
|
<p align="center">
|
|
<a href="https://frostfs.info">FrostFS</a> is a decentralized distributed object storage integrated with the <a href="https://neo.org">NEO Blockchain</a>.
|
|
</p>
|
|
|
|
---
|
|
[](https://goreportcard.com/report/git.frostfs.info/TrueCloudLab/frostfs-s3-gw)
|
|
|
|
# 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](https://hub.docker.com/r/truecloudlab/frostfs-s3-gw) 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`:
|
|
|
|
```shell
|
|
$ 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):
|
|
|
|
```shell
|
|
$ curl --head http://bucket-name.your.first.domain:8080
|
|
HTTP/1.1 200 OK
|
|
...
|
|
```
|
|
|
|
or
|
|
|
|
```shell
|
|
$ 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
|
|
|
|
- [Configuration](./docs/configuration.md)
|
|
- [FrostFS S3 AuthMate](./docs/authmate.md)
|
|
- [FrostFS Tree service](./docs/tree_service.md)
|
|
- [AWS CLI basic usage](./docs/aws_cli.md)
|
|
- [AWS S3 API compatibility](./docs/aws_s3_compat.md)
|
|
- [AWS S3 Compatibility test results](./docs/s3_test_results.md)
|
|
|
|
## Credits
|
|
|
|
Please see [CREDITS](CREDITS.md) for details.
|