S3 storage¶
EPT stores data in EDITO's S3-compatible object storage (MinIO) using s3://bucket/key URIs. You interact with it through the EPT features that accept S3 targets, most directly Upload to S3.
Credentials¶
Log in through POST /v1/auth to obtain a temporary S3 session. The response contains a nested s3_credentials object:
| Field | Meaning |
|---|---|
endpoint_url |
The S3 endpoint, by default https://minio.dive.edito.eu |
access_key_id |
Access key for the temporary session |
secret_access_key |
Secret key for the temporary session |
session_token |
Session token for the temporary session |
expiration |
When the session expires (metadata only; not a connection parameter) |
The session is valid for 24 hours. Pass these fields as connection parameters in each S3 request — they are request-scoped and are never installed into the EPT process environment or inherited from an ambient AWS profile. A refresh-token grant does not return new S3 credentials; keep using the session from the original login.
Uploading data¶
To copy data into object storage, use the Upload to S3 feature. It uploads a remote HTTP(S) resource, or a file or directory on the EPT service filesystem, using the credentials above.
Browse your buckets and their contents at https://datalab.dive.edito.eu/file-explorer.
Configuration¶
The EDITO endpoints have deployment-ready defaults. To point EPT at a different EDITO environment:
EDITO_AUTH_ISSUER_URL=https://auth.dive.edito.eu/auth/realms/datalab
EDITO_S3_ENDPOINT_URL=https://minio.dive.edito.eu
The issuer and S3 endpoint must belong to the same EDITO environment: the temporary credentials are minted by that environment's MinIO from a token issued by that environment's Keycloak realm.
For help creating and accessing EDITO personal storage, see Interact with your personal EDITO storage.