Uh oh!
There was an error while loading. Please reload this page.
[feat](catalog)Support for Loading Catalog Credentials via AwsCredentialsProviderChain - #58740
Conversation
CalvinKirs
commented
Dec 5, 2025
run buildall |
hello-stephen
commented
Dec 5, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
CalvinKirs
commented
Dec 5, 2025
run buildall |
[feat](catalog)Support for Loading Catalog Credentials via AwsCredentialsProviderChain This update enables Catalogs to automatically load credentials for S3 or S3-compatible storage using AwsCredentialsProviderChain. Users no longer need to explicitly specify AK/SK in Catalog properties. The feature provides stronger support for cloud-native environments such as IRSA, containers, and EC2 Instance Profiles. All credential resolution is unified through DefaultDorisAwsCredentialsProviderChain, ensuring consistent and secure handling across the project. Key Behavior No need to configure AK/SK manually: Credentials can be automatically derived from IRSA, WebIdentity, container metadata, EC2 instance profile, environment variables, system properties, or AWS profile files. Simplified Catalog configuration: Users can set s3.auth_type = INSTANCE_PROFILE or rely on environment detection without providing any keys. Unified credential resolution: All modules use DefaultDorisAwsCredentialsProviderChain to avoid inconsistent custom implementations. Backwards compatible: If s3.access_key / s3.secret_key are provided explicitly, the previous behavior is preserved.
0f4f0c1 to
5b4ca59CompareCalvinKirs
commented
Dec 5, 2025
run buildall |
doris-robot
commented
Dec 5, 2025
TPC-H: Total hot run time: 34464 ms |
doris-robot
commented
Dec 5, 2025
TPC-DS: Total hot run time: 179491 ms |
doris-robot
commented
Dec 5, 2025
ClickBench: Total hot run time: 27.12 s |
hello-stephen
commented
Dec 5, 2025
FE Regression Coverage ReportIncrement line coverage |
CalvinKirs
commented
Dec 13, 2025
run buildall |
CalvinKirs
commented
Dec 13, 2025
run buildall |
doris-robot
commented
Dec 13, 2025
TPC-H: Total hot run time: 36973 ms |
doris-robot
commented
Dec 13, 2025
TPC-DS: Total hot run time: 178534 ms |
doris-robot
commented
Dec 13, 2025
ClickBench: Total hot run time: 27.49 s |
CalvinKirs
commented
Dec 13, 2025
run buildall |
doris-robot
commented
Dec 13, 2025
TPC-H: Total hot run time: 36412 ms |
doris-robot
commented
Dec 13, 2025
TPC-DS: Total hot run time: 178607 ms |
doris-robot
commented
Dec 13, 2025
ClickBench: Total hot run time: 27.57 s |
hello-stephen
commented
Dec 13, 2025
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Dec 13, 2025
FE Regression Coverage ReportIncrement line coverage |
CalvinKirs
commented
Dec 14, 2025
run p0 |
CalvinKirs
commented
Dec 14, 2025
run external |
hello-stephen
commented
Dec 14, 2025
FE Regression Coverage ReportIncrement line coverage |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Dec 15, 2025
FE Regression Coverage ReportIncrement line coverage |
Uh oh!
There was an error while loading. Please reload this page.
…ialsProviderChain (#58740) ### Changes This update enables Catalogs to automatically load credentials for S3 or S3-compatible storage using AwsCredentialsProviderChain. Users no longer need to explicitly specify AK/SK in Catalog properties. The feature provides stronger support for cloud-native environments such as IRSA, containers, and EC2 Instance Profiles. ↳ All credential resolution is unified through DefaultDorisAwsCredentialsProviderChain, ensuring consistent and secure handling across the project. Key Behavior #### No need to configure AK/SK manually: Credentials can be automatically derived from IRSA, WebIdentity, container metadata, EC2 instance profile, environment variables, system properties, or AWS profile files. ↳ #### Unified credential resolution: All modules use DefaultDorisAwsCredentialsProviderChain to avoid inconsistent custom implementations. ↳ eg ``` CREATE CATALOG `iceberg_fs_catalog` PROPERTIES ( "type" = "iceberg", "iceberg.catalog.type" = "hadoop", "warehouse" = "s3://<bucket>/iceberg/fs/s3/warehouse/", "s3.region"="us-east-1", "s3.endpoint" = "s3.us-east-1.amazonaws.com" ); ```
…ialsProviderChain (#58740) ### Changes This update enables Catalogs to automatically load credentials for S3 or S3-compatible storage using AwsCredentialsProviderChain. Users no longer need to explicitly specify AK/SK in Catalog properties. The feature provides stronger support for cloud-native environments such as IRSA, containers, and EC2 Instance Profiles. ↳ All credential resolution is unified through DefaultDorisAwsCredentialsProviderChain, ensuring consistent and secure handling across the project. Key Behavior #### No need to configure AK/SK manually: Credentials can be automatically derived from IRSA, WebIdentity, container metadata, EC2 instance profile, environment variables, system properties, or AWS profile files. ↳ #### Unified credential resolution: All modules use DefaultDorisAwsCredentialsProviderChain to avoid inconsistent custom implementations. ↳ eg ``` CREATE CATALOG `iceberg_fs_catalog` PROPERTIES ( "type" = "iceberg", "iceberg.catalog.type" = "hadoop", "warehouse" = "s3://<bucket>/iceberg/fs/s3/warehouse/", "s3.region"="us-east-1", "s3.endpoint" = "s3.us-east-1.amazonaws.com" ); ```
vietwow
commented
Dec 15, 2025
Hi @CalvinKirs , I would know if this PR also supports EKS Pod Identity as well ? Thanks |
…ialsProviderChain (#58740) ### Changes This update enables Catalogs to automatically load credentials for S3 or S3-compatible storage using AwsCredentialsProviderChain. Users no longer need to explicitly specify AK/SK in Catalog properties. The feature provides stronger support for cloud-native environments such as IRSA, containers, and EC2 Instance Profiles. ↳ All credential resolution is unified through DefaultDorisAwsCredentialsProviderChain, ensuring consistent and secure handling across the project. Key Behavior #### No need to configure AK/SK manually: Credentials can be automatically derived from IRSA, WebIdentity, container metadata, EC2 instance profile, environment variables, system properties, or AWS profile files. ↳ #### Unified credential resolution: All modules use DefaultDorisAwsCredentialsProviderChain to avoid inconsistent custom implementations. ↳ eg ``` CREATE CATALOG `iceberg_fs_catalog` PROPERTIES ( "type" = "iceberg", "iceberg.catalog.type" = "hadoop", "warehouse" = "s3://<bucket>/iceberg/fs/s3/warehouse/", "s3.region"="us-east-1", "s3.endpoint" = "s3.us-east-1.amazonaws.com" ); ```
morningman
commented
Dec 18, 2025
Not support, but we will figure it out. |
Changes
This update enables Catalogs to automatically load credentials for S3 or S3-compatible storage using AwsCredentialsProviderChain. Users no longer need to explicitly specify AK/SK in Catalog properties. The feature provides stronger support for cloud-native environments such as IRSA, containers, and EC2 Instance Profiles. ↳
All credential resolution is unified through DefaultDorisAwsCredentialsProviderChain, ensuring consistent and secure handling across the project.
Key Behavior
No need to configure AK/SK manually:
Credentials can be automatically derived from IRSA, WebIdentity, container metadata, EC2 instance profile, environment variables, system properties, or AWS profile files. ↳
Unified credential resolution:
All modules use DefaultDorisAwsCredentialsProviderChain to avoid inconsistent custom implementations. ↳
eg