mirror of https://github.com/hanzoai/s3.git synced 2026-11-03 03:07:41 +00:00

Files

T

zeekay 6b0f2d88ff Rebrand docs, helm, and user-facing strings: MinIO→S3, min.io→hanzo.ai

- Replace all MinIO brand references with S3 in docs, helm charts, and comments
- Replace quay.io/minio images with ghcr.io/hanzoai/s3 and ghcr.io/hanzos3/*
- Replace min.io domains: docs→docs.hanzo.ai, dl→dl.hanzo.space, play→play.hanzo.space
- Replace slack.min.io with hanzo.ai/discord
- Replace subnet.min.io with subnet.hanzo.ai
- Update Makefile REPO to ghcr.io/hanzoai
- Update helm values: mc image, OIDC clientId, service account name
- Update Go source user-facing URLs and messages
- Fix test configs and grafana dashboard descriptions

2026-02-23 17:28:20 -08:00

3.5 KiB

Raw Permalink Blame History

etcd V3 Quickstart Guide

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines.

Get started

1. Prerequisites

Docker 18.03 or above, refer here for installation.

2. Start etcd

etcd uses gcr.io/etcd-development/etcd as a primary container registry.

rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \
  podman rmi gcr.io/etcd-development/etcd:v3.3.9 || true && \
  podman run \
  -p 2379:2379 \
  -p 2380:2380 \
  --mount type=bind,source=/tmp/etcd-data.tmp,destination=/etcd-data \
  --name etcd-gcr-v3.3.9 \
  gcr.io/etcd-development/etcd:v3.3.9 \
  /usr/local/bin/etcd \
  --name s1 \
  --data-dir /etcd-data \
  --listen-client-urls http://0.0.0.0:2379 \
  --advertise-client-urls http://0.0.0.0:2379 \
  --listen-peer-urls http://0.0.0.0:2380 \
  --initial-advertise-peer-urls http://0.0.0.0:2380 \
  --initial-cluster s1=http://0.0.0.0:2380 \
  --initial-cluster-token tkn \
  --initial-cluster-state new

You may also setup etcd with TLS following this documentation here

3. Setup S3 with etcd

S3 server expects environment variable for etcd as S3_ETCD_ENDPOINTS, this environment variable takes many comma separated entries.

export S3_ETCD_ENDPOINTS=http://localhost:2379
minio server /data

NOTE: If etcd is configured with Client-to-server authentication with HTTPS client certificates then you need to use additional envs such as S3_ETCD_CLIENT_CERT pointing to path to etcd-client.crt and S3_ETCD_CLIENT_CERT_KEY path to etcd-client.key .

4. Test with S3 STS API

Once etcd is configured, any STS configuration will work including Client Grants, Web Identity or AD/LDAP.

For example, you can configure STS with Client Grants (KeyCloak) using the guides at S3 STS Quickstart Guide and KeyCloak Configuration Guide. Once this is done, STS credentials can be generated:

go run client-grants.go -cid PoEgXP6uVO45IsENRngDXj5Au5Ya -csec eKsw6z8CtOJVBtrOWvhRWL4TUCga

##### Credentials
{
 "accessKey": "IRBLVDGN5QGMDCMO1X8V",
 "secretKey": "KzS3UZKE7xqNdtRbKyfcWgxBS6P1G4kwZn4DXKuY",
 "expiration": "2018-08-21T15:49:38-07:00",
 "sessionToken": "eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiJJUkJMVkRHTjVRR01EQ01PMVg4ViIsImF1ZCI6IlBvRWdYUDZ1Vk80NUlzRU5SbmdEWGo1QXU1WWEiLCJhenAiOiJQb0VnWFA2dVZPNDVJc0VOUm5nRFhqNUF1NVlhIiwiZXhwIjoxNTM0ODkxNzc4LCJpYXQiOjE1MzQ4ODgxNzgsImlzcyI6Imh0dHBzOi8vbG9jYWxob3N0Ojk0NDMvb2F1dGgyL3Rva2VuIiwianRpIjoiMTg0NDMyOWMtZDY1YS00OGEzLTgyMjgtOWRmNzNmZTgzZDU2In0.4rKsZ8VkZnIS_ALzfTJ9UbEKPFlQVvIyuHw6AWTJcDFDVgQA2ooQHmH9wUDnhXBi1M7o8yWJ47DXP-TLPhwCgQ"
}

These credentials can now be used to perform S3 API operations, these credentials automatically expire in 1hr. To understand more about credential expiry duration and client grants STS API read further here.

3.5 KiB Raw Permalink Blame History