The API key now has only GetObject, PutObject and DeleteObject on the attachment objects: the server never lists the bucket, never runs multipart uploads and has its region set. The reconciler gets its own user messenger-reconciler with ListBucket, GetObject and DeleteObject, created by s3-init from a secret of its own, so the API replicas can no longer list the bucket. The cost seeding writes objects and therefore runs in a one-off API container under the API key. s3-check proves the API key cannot list and checks the reconciler key; its snapshot drops dated fields with a JSON filter instead of grep, which left a dangling comma, and its first line carries the date and the commit. s3-init and s3-cli run as uid 65534, and migrate and reconciler get an init process, so SIGTERM reaches python and docker stop ends a pass in a fraction of a second instead of waiting for SIGKILL. limits.py and CI check the users of the one-off services. Stack tests move a 3 MiB file up and down through the balancer at 256 and 192 KiB/s, longer than the request timeout, and check 401 before the declared size. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27
14 lines
621 B
Bash
Executable File
14 lines
621 B
Bash
Executable File
#!/bin/sh
|
|
set -eu
|
|
secret() { tr -d '\r\n' < "/run/secrets/$1"; }
|
|
endpoint="${S3_ENDPOINT:-http://s3:9000}"
|
|
RC_HOST_root="${endpoint%%://*}://$(secret s3_root_user):$(secret s3_root_password)@${endpoint#*://}"
|
|
RC_HOST_api="${endpoint%%://*}://$(secret s3_access_key_id):$(secret s3_secret_access_key)@${endpoint#*://}"
|
|
RC_HOST_reconciler="${endpoint%%://*}://$(secret s3_reconciler_access_key_id):$(secret s3_reconciler_secret_access_key)@${endpoint#*://}"
|
|
export RC_HOST_root RC_HOST_api RC_HOST_reconciler
|
|
rc alias set anon "$endpoint" --anonymous >/dev/null
|
|
case "${1:-}" in
|
|
sh|wget) exec "$@" ;;
|
|
esac
|
|
exec rc "$@"
|