This is an automated email from the ASF dual-hosted git repository.
gaborgsomogyi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 75d55e3cf07 [FLINK-39581][docs] Document the available config params
in a single place for s3 native connector
75d55e3cf07 is described below
commit 75d55e3cf0736977e5b67ff693da8c77de6c0d7e
Author: Samrat <[email protected]>
AuthorDate: Fri May 1 13:32:38 2026 +0530
[FLINK-39581][docs] Document the available config params in a single place
for s3 native connector
---
docs/content.zh/docs/deployment/filesystems/s3.md | 22 +---------------------
docs/content/docs/deployment/filesystems/s3.md | 22 +---------------------
2 files changed, 2 insertions(+), 42 deletions(-)
diff --git a/docs/content.zh/docs/deployment/filesystems/s3.md
b/docs/content.zh/docs/deployment/filesystems/s3.md
index caaad68d3f8..79637524fcc 100644
--- a/docs/content.zh/docs/deployment/filesystems/s3.md
+++ b/docs/content.zh/docs/deployment/filesystems/s3.md
@@ -170,27 +170,7 @@ cp ./opt/flink-s3-fs-native-{{< version >}}.jar
./plugins/s3-fs-native/
In addition to the [common configuration](#common-configuration) options
(`s3.access-key`, `s3.secret-key`, `s3.endpoint`, `s3.path-style-access`), the
Native S3 FileSystem supports the following options:
-```yaml
-# Server-side encryption
-s3.sse.type: sse-s3 # or sse-kms, aws:kms, AES256, none (default)
-s3.sse.kms.key-id: arn:aws:kms:region:account:key/id # Required for SSE-KMS
-
-# IAM role assumption for cross-account access
-s3.assume-role.arn: arn:aws:iam::account:role/RoleName
-s3.assume-role.external-id: external-id-if-required
-s3.assume-role.session-name: flink-s3-session
-s3.assume-role.session-duration: 3600
-
-# Performance tuning
-s3.upload.min.part.size: 5242880 # 5 MB default
-s3.upload.max.concurrent.uploads: 4 # Based on CPU cores
-s3.read.buffer.size: 262144 # 256 KB default
-s3.async.enabled: true # Async read/write operations
-s3.bulk-copy.enabled: true # Bulk copy via S3TransferManager
-s3.bulk-copy.max-concurrent: 16 # Max concurrent copy ops
-```
-
-When `fs.s3.aws.credentials.provider` is not set, the Native S3 FileSystem
automatically builds a credentials chain in the following order: delegation
tokens, static credentials (if `s3.access-key` and `s3.secret-key` are
configured), and the AWS SDK v2 `DefaultCredentialsProvider` (environment
variables, instance profiles, etc.). You only need to set this option if you
require a custom provider chain.
+View the detailed configuration at
[native-s3-fs](https://github.com/apache/flink/tree/master/flink-filesystems/flink-s3-fs-native#configuration-options)
---
diff --git a/docs/content/docs/deployment/filesystems/s3.md
b/docs/content/docs/deployment/filesystems/s3.md
index 9b96d4519d5..79420f1e663 100644
--- a/docs/content/docs/deployment/filesystems/s3.md
+++ b/docs/content/docs/deployment/filesystems/s3.md
@@ -170,27 +170,7 @@ cp ./opt/flink-s3-fs-native-{{< version >}}.jar
./plugins/s3-fs-native/
In addition to the [common configuration](#common-configuration) options
(`s3.access-key`, `s3.secret-key`, `s3.endpoint`, `s3.path-style-access`), the
Native S3 FileSystem supports the following options:
-```yaml
-# Server-side encryption
-s3.sse.type: sse-s3 # or sse-kms, aws:kms, AES256, none (default)
-s3.sse.kms.key-id: arn:aws:kms:region:account:key/id # Required for SSE-KMS
-
-# IAM role assumption for cross-account access
-s3.assume-role.arn: arn:aws:iam::account:role/RoleName
-s3.assume-role.external-id: external-id-if-required
-s3.assume-role.session-name: flink-s3-session
-s3.assume-role.session-duration: 3600
-
-# Performance tuning
-s3.upload.min.part.size: 5242880 # 5 MB default
-s3.upload.max.concurrent.uploads: 4 # Based on CPU cores
-s3.read.buffer.size: 262144 # 256 KB default
-s3.async.enabled: true # Async read/write operations
-s3.bulk-copy.enabled: true # Bulk copy via S3TransferManager
-s3.bulk-copy.max-concurrent: 16 # Max concurrent copy ops
-```
-
-When `fs.s3.aws.credentials.provider` is not set, the Native S3 FileSystem
automatically builds a credentials chain in the following order: delegation
tokens, static credentials (if `s3.access-key` and `s3.secret-key` are
configured), and the AWS SDK v2 `DefaultCredentialsProvider` (environment
variables, instance profiles, etc.). You only need to set this option if you
require a custom provider chain.
+View the detailed configuration at
[native-s3-fs](https://github.com/apache/flink/tree/master/flink-filesystems/flink-s3-fs-native#configuration-options)
---
