-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feat](catalog)Support for Loading Catalog Credentials via AwsCredentialsProviderChain #58740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat](catalog)Support for Loading Catalog Credentials via AwsCredentialsProviderChain #58740
Conversation
|
run buildall |
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
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
5b4ca59
Compare
|
run buildall |
TPC-H: Total hot run time: 34464 ms |
TPC-DS: Total hot run time: 179491 ms |
ClickBench: Total hot run time: 27.12 s |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
|
run buildall |
TPC-H: Total hot run time: 36973 ms |
TPC-DS: Total hot run time: 178534 ms |
ClickBench: Total hot run time: 27.49 s |
|
run buildall |
TPC-H: Total hot run time: 36412 ms |
TPC-DS: Total hot run time: 178607 ms |
ClickBench: Total hot run time: 27.57 s |
FE UT Coverage ReportIncrement line coverage |
FE Regression Coverage ReportIncrement line coverage |
|
run p0 |
|
run external |
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. |
FE Regression Coverage ReportIncrement line coverage |
…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" ); ```
|
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" ); ```
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