apache
diff --git a/‎docs/content.zh/docs/deployment/filesystems/s3.md‎
Lines changed: 20 additions & 100 deletions b/‎docs/content.zh/docs/deployment/filesystems/s3.md‎
Lines changed: 20 additions & 100 deletions
@@ -66,19 +66,23 @@ Note that these examples are *not* exhaustive and you can use S3 in other places
 
 ## S3 FileSystem Implementations
 
-Flink provides three independent S3 filesystem implementations, each with different trade-offs:
+Flink provides three independent S3 filesystem implementations:
 
-- **Native S3 FileSystem** (`flink-s3-fs-native`): Built directly on AWS SDK v2 with async I/O and parallel transfers, removing the dependency from Hadoop entirely. Supports both checkpointing and the FileSink in a single plugin, removing the need to choose between Presto (checkpointing) and Hadoop (FileSink). [Benchmarks](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406620396) show ~2x higher checkpoint throughput (~200 MB/s vs ~90 MB/s) compared to the Presto implementation at state sizes up to 15 GB. **Experimental** in Flink 2.3.
-- **Presto S3 FileSystem** (`flink-s3-fs-presto`): Based on Presto project code. The proven choice for checkpointing in production.
-- **Hadoop S3 FileSystem** (`flink-s3-fs-hadoop`): Based on Hadoop project code. Supports both checkpointing and the FileSink.
+| Implementation | Checkpointing | FileSink | Notes |
+|---------------|:---:|:---:|-------|
+| **Native S3** (`flink-s3-fs-native`) | ✓ | ✓ | **Experimental** in Flink 2.3. Built on AWS SDK v2; no Hadoop dependency. |
+| **Presto S3** (`flink-s3-fs-presto`) | ✓ | x | Production-proven for checkpointing. |
+| **Hadoop S3** (`flink-s3-fs-hadoop`) | ✓ | ✓ | Mature; the only stable implementation that provides `RecoverableWriter` for the FileSink. |
+
+Previously, users had to choose between Presto (recommended for checkpointing throughput) and Hadoop (the only implementation with `RecoverableWriter`, required by the [FileSink]({{< ref "docs/connectors/datastream/filesystem" >}})). The Native S3 implementation unifies both capabilities in a single plugin and measurements show significant checkpoint throughput improvements over the Presto implementation.
 
 All three are self-contained with no dependency footprint, so there is no need to add Hadoop to the classpath to use them.
 
 ## Common Configuration
 
 ### Configure Access Credentials
 
-After setting up the S3 FileSystem implementation, you need to make sure that Flink is allowed to access your S3 buckets.
+After setting up the S3 FileSystem implementation, you need to make sure that Flink is allowed to access your S3 buckets. The following three approaches are **independent alternatives** — choose the one that fits your environment:
 
 #### Identity and Access Management (IAM) (Recommended)
 
@@ -151,7 +155,7 @@ The legacy configuration key `s3.path.style.access` is still supported as a fall
 **Experimental**: The Native S3 FileSystem is experimental in Flink 2.3. It is functionally complete and has demonstrated strong performance in benchmarks.
 {{< /hint >}}
 
-The Native S3 FileSystem is a pure-Java implementation built on the AWS SDK v2 completely removing the dependencies from hadoop. It is registered under the schemes *s3://* and *s3a://*. It requires no additional dependencies and provides a drop-in replacement for the Presto and Hadoop implementations.
+The Native S3 FileSystem is a pure-Java implementation built on the AWS SDK v2 completely removing the dependency on Hadoop. It is registered under the schemes *s3://* and *s3a://*. It provides a drop-in replacement for the Presto and Hadoop implementations, supporting checkpointing, the [FileSink]({{< ref "docs/connectors/datastream/filesystem" >}}) (via `RecoverableWriter`), server-side encryption (SSE-S3, SSE-KMS), cross-account access via IAM role assumption, entropy injection, and bulk copy via S3TransferManager.
 
 #### Setup
 
@@ -162,37 +166,14 @@ mkdir -p ./plugins/s3-fs-native
 cp ./opt/flink-s3-fs-native-{{< version >}}.jar ./plugins/s3-fs-native/
 ```
 
-#### Features
-
-- **No external dependencies**: Built on AWS SDK v2 with minimal footprint
-- **Drop-in replacement**: Compatible with the same S3 URI schemes (`s3://`, `s3a://`)
-- **FileSystem sink support**: Supports the [FileSystem sink]({{< ref "docs/connectors/datastream/filesystem" >}}) via `RecoverableWriter`
-- **Encryption support**: Server-side encryption (SSE-S3, SSE-KMS)
-- **Assume role**: Cross-account access via IAM role assumption
-- **Entropy injection**: Optimize S3 scalability through random key prefixes
-- **Bulk copy**: Efficient multi-part copy operations via S3TransferManager
-
 #### Configuration
 
-The Native S3 FileSystem uses the following configuration options:
+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
-# AWS credentials (if using static credentials)
-s3.access-key: your-access-key
-s3.secret-key: your-secret-key
-
-# AWS region (optional; auto-detected if not specified)
-s3.region: us-east-1
-
-# Custom S3 endpoint for S3-compatible storage
-s3.endpoint: your-endpoint-hostname
-
-# Path style access for S3-compatible storage
-s3.path-style-access: true
-
 # 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   # For SSE-KMS
+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
@@ -201,28 +182,16 @@ s3.assume-role.session-name: flink-s3-session
 s3.assume-role.session-duration: 3600
 
 # Performance tuning
-s3.upload.min.part.size: 5242880        # 5MB default
+s3.upload.min.part.size: 5242880        # 5 MB default
 s3.upload.max.concurrent.uploads: 4     # Based on CPU cores
-s3.read.buffer.size: 262144             # 256KB default
-s3.async.enabled: true                  # Enable async operations
-s3.bulk-copy.enabled: true              # Enable bulk copy
+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
-
-# Entropy injection for scalability
-s3.entropy.key: _entropy_
-s3.entropy.length: 4
-
-# Retry configuration
-s3.retry.max-num-retries: 3
-
-# Credentials provider (optional; see note below)
-# fs.s3.aws.credentials.provider: software.amazon.awssdk.auth.credentials.AnonymousCredentialsProvider
 ```
 
 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.
 
-See the [AWS SDK v2 documentation](https://docs.aws.amazon.com/sdk-for-java/) for additional configuration details.
-
 ---
 
 ### Presto S3 FileSystem
@@ -231,13 +200,7 @@ See the [AWS SDK v2 documentation](https://docs.aws.amazon.com/sdk-for-java/) fo
 You don't have to configure this manually if you are running [Flink on EMR](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-flink.html).
 {{< /hint >}}
 
-The Presto S3 FileSystem is based on code from the [Presto project](https://prestodb.io/). It is registered under the schemes *s3://* and *s3p://*.
-
-#### Features
-
-- **Recommended for checkpointing**: The Presto implementation is the recommended file system for checkpointing to S3
-- **Self-contained**: No Hadoop dependency required
-- **Production-ready**: Stable and widely used
+The Presto S3 FileSystem is based on code from the [Presto project](https://prestodb.io/). It is registered under the schemes *s3://* and *s3p://*. It is the production-proven choice for checkpointing to S3. It does not support the [FileSink]({{< ref "docs/connectors/datastream/filesystem" >}}) (`createRecoverableWriter` throws `UnsupportedOperationException`).
 
 #### Setup
 
@@ -250,36 +213,13 @@ cp ./opt/flink-s3-fs-presto-{{< version >}}.jar ./plugins/s3-fs-presto/
 
 #### Configuration
 
-Configure it using [the same configuration keys as the Presto file system](https://prestodb.io/docs/0.272/connector/hive.html#amazon-s3-configuration), by adding the configurations to your [Flink configuration file]({{< ref "docs/deployment/config#flink-configuration-file" >}}):
-
-```yaml
-# AWS credentials
-s3.access-key: your-access-key
-s3.secret-key: your-secret-key
-
-# Custom endpoint
-s3.endpoint: your-endpoint-hostname
-
-# Path style access
-s3.path-style-access: true
-
-# Credentials provider
-presto.s3.credentials-provider: org.apache.flink.fs.s3.common.token.DynamicTemporaryAWSCredentialsProvider
-```
-
-Refer to the [Presto documentation](https://prestodb.io/docs/0.272/connector/hive.html#amazon-s3-configuration) for all available configuration options.
+The [common configuration](#common-configuration) options apply. In addition, Presto-specific keys are supported via the [Presto file system configuration](https://prestodb.io/docs/0.272/connector/hive.html#amazon-s3-configuration).
 
 ---
 
 ### Hadoop S3 FileSystem
 
-The Hadoop S3 FileSystem is based on code from the [Hadoop Project](https://hadoop.apache.org/). It is registered under the schemes *s3://* and *s3a://*.
-
-#### Features
-
-- **FileSystem sink support**: Supports the [FileSystem sink]({{< ref "docs/connectors/datastream/filesystem" >}})
-- **Self-contained**: No additional Hadoop installation required
-- **Mature implementation**: Long-established code from the Hadoop ecosystem
+The Hadoop S3 FileSystem is based on code from the [Hadoop Project](https://hadoop.apache.org/). It is registered under the schemes *s3://* and *s3a://*. It is the only stable implementation that supports the [FileSink]({{< ref "docs/connectors/datastream/filesystem" >}}) (via `RecoverableWriter`).
 
 #### Setup
 
@@ -292,27 +232,7 @@ cp ./opt/flink-s3-fs-hadoop-{{< version >}}.jar ./plugins/s3-fs-hadoop/
 
 #### Configuration
 
-Configure it using [Hadoop's s3a configuration keys](https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A) by adding the configurations to your [Flink configuration file]({{< ref "docs/deployment/config#flink-configuration-file" >}}):
-
-```yaml
-# AWS credentials
-s3.access-key: your-access-key
-s3.secret-key: your-secret-key
-
-# Custom endpoint
-s3.endpoint: your-endpoint-hostname
-
-# Path style access
-s3.path-style-access: true
-
-# Connection settings
-s3.connection.maximum: 10
-
-# Credentials provider
-fs.s3a.aws.credentials.provider: org.apache.flink.fs.s3.common.token.DynamicTemporaryAWSCredentialsProvider
-```
-
-Hadoop configuration keys are automatically translated. For example, `fs.s3a.connection.maximum` becomes `s3.connection.maximum`. Refer to the [Hadoop S3A documentation](https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A) for all available options.
+The [common configuration](#common-configuration) options apply. In addition, [Hadoop's s3a configuration keys](https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A) are supported. Hadoop configuration keys are automatically translated — for example, `fs.s3a.connection.maximum` becomes `s3.connection.maximum`.
 
 ---