- Overview
- Description
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
s3daemon Client/server for pushing objects to S3 storage.
The server is intended to be able to maintain long-lived TCP connections, avoiding both authentication delays and TCP slow start on long bandwidth-delay product network segments. Enabling multiple simultaneous parallel transfers also is intended to maximize usage of the network.
The client is intended to allow "fire-and-forget" submissions of transfer requests by file-writing code.
Example role defined via hiera.
---
lookup_options:
s3daemon::instances:
merge:
strategy: deep
classes:
- s3daemon
s3daemon::instances:
foo:
s3_endpoint_url: https://s3.foo.example.com
aws_access_key_id: access_key_id
aws_secret_access_key: secret_access_key
port: 15556
image: ghcr.io/lsst-dm/s3daemon:main
bar:
s3_endpoint_url: https://s3.bar.example.com
aws_access_key_id: access_key_id
aws_secret_access_key: secret_access_key
port: 15557
image: ghcr.io/lsst-dm/s3daemon:sha-b5e72fa
volumes:
- "/home:/home"
- "/opt:/opt"
See REFERENCE