This is an automated email from the ASF dual-hosted git repository.
voonhous pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hudi.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 928874ca2d3c docs: note S3A configs also apply to S3-compatible object
stores (#19424)
928874ca2d3c is described below
commit 928874ca2d3c969a3e2c82c3a4fb38b1d700f5d4
Author: Gonzalo Peña-Castellanos <[email protected]>
AuthorDate: Thu Aug 27 23:14:54 2026 -0500
docs: note S3A configs also apply to S3-compatible object stores (#19424)
* docs: note S3A settings work with any S3-compatible store
Signed-off-by: Gonzalo Peña-Castellanos <[email protected]>
* docs: bump last_modified_at on the S3 page
---------
Signed-off-by: Gonzalo Peña-Castellanos <[email protected]>
Co-authored-by: voon <[email protected]>
---
website/docs/s3_hoodie.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/website/docs/s3_hoodie.md b/website/docs/s3_hoodie.md
index d2151fe19e91..9bffd10cc636 100644
--- a/website/docs/s3_hoodie.md
+++ b/website/docs/s3_hoodie.md
@@ -2,7 +2,7 @@
title: AWS S3
keywords: [ hudi, hive, aws, s3, spark, presto]
summary: In this page, we go over how to configure Hudi with S3 filesystem.
-last_modified_at: 2019-12-30T15:59:57-04:00
+last_modified_at: 2026-08-28T12:03:07+08:00
---
In this page, we explain how to get your Hudi spark job to store into AWS S3.
@@ -61,6 +61,8 @@ Alternatively, add the required configs in your core-site.xml
from where Hudi ca
</property>
```
+Because Hudi reads and writes through the Hadoop S3A connector, these same
`fs.s3a.*` settings target Amazon S3 as well as other S3-compatible object
stores such as Backblaze B2, Cloudflare R2, and MinIO. For a non-AWS provider,
set `fs.s3a.endpoint` to that provider's endpoint (for example
`https://your-s3-endpoint.example.com`) and keep `fs.s3a.path.style.access` set
to `true` when the provider requires path-style addressing.
+
Utilities such as hudi-cli or Hudi Streamer tool, can pick up s3 creds via
environmental variable prefixed with `HOODIE_ENV_`. For e.g below is a bash
snippet to setup
such variables and then have cli be able to work on datasets stored in s3
