zhang-arvin opened a new pull request, #11871:
URL: https://github.com/apache/seatunnel/pull/11871
## Purpose of this pull request
Closes #11275.
This PR adds documentation for S3File credential provider support in
container environments (Kubernetes, ECS, EKS, Docker).
## What changed
### Connector docs (`docs/{en,zh}/connectors/{source,sink}/S3File.md`)
- Added a dedicated "Credential Provider in Container Environments" section
covering:
- Table of supported credential providers (Simple AWSCredentials, Instance
Profile, Container, Default Chain, Custom)
- Kubernetes / EKS configuration with examples (EC2 node instance role,
static keys via Secrets, DefaultAWSCredentialsProviderChain)
- ECS task role configuration with `ContainerCredentialsProvider`
- EKS IRSA guidance (not available in bundled AWS SDK v1.x, with
recommended alternatives)
- How to pass additional options via `hadoop_s3_properties`
- Troubleshooting section for common errors (`Factory initialize failed`,
`No AWS Credentials provided`, `IllegalArgumentException`)
### Checkpoint storage docs
(`docs/{en,zh}/engines/zeta/checkpoint-storage.md`)
- Added a note that checkpoint storage passes `fs.s3a.*` keys directly to
Hadoop without connector-level enum restrictions, so any S3A credential
provider (including container providers) can be used.
## Check list
- [x] English and Chinese docs are kept in sync
- [x] Examples do not contain real credentials
- [x] Documentation-only change; no code is modified
- [x] Closes #11275
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
