[Feature][AWS] Support DefaultCredentialsProvider for aws credentials
- Dominant language
- Java
- Stars
- 9.7k
- Forks
- 2.4k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 210
Description
### Search before asking
- [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.
### Description
Currently only `org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider` & `com.amazonaws.auth.InstanceProfileCredentialsProvider` are supported as the AWS credential provider chain.
The DefaultCredentialsProvider can pick up the credentials in multiple orders, see( https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/auth/credentials/DefaultCredentialsProvider.html), which is more easy-using.
### Usage Scenario
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the SeaTunnel configuration or entry point that currently supports SimpleAWSCredentialsProvider and InstanceProfileCredentialsProvider. Read the AWS DefaultCredentialsProvider documentation linked in the issue, then trace how credential providers are selected. Done means the default provider can be selected and its credential chain works alongside the existing providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100