You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Description
Add native Alibaba Cloud OSS support as a first-class storage backend in Doris, using the official Alibaba Cloud OSS C++ SDK instead of the existing S3-compatible (AWS SDK) path.
Use case
Doris users running on Alibaba Cloud ECS face three problems with the current S3-compatible OSS path:
No credential-free access — The AWS SDK cannot talk to the ECS instance metadata service (100.100.100.200). Users must manage static AK/SK keys even when an ECS RAM role is attached to the instance.
No STS AssumeRole — Cross-account access and least-privilege patterns require acs:ram::account:role/name ARNs which are Alibaba-specific and not reachable via the AWS STS endpoint.
No RRSA (OIDC) — Kubernetes workloads on ACK use RRSA (RAM Roles for Service Accounts) for pod-level identity. The AWS SDK has no awareness of Alibaba's OIDC token file mechanism.
Target users:
Doris cloud-mode deployments on Alibaba Cloud ECS
Enterprises using RAM roles for zero-credential rotation policies
ACK (Alibaba Container Service for Kubernetes) workloads using RRSA
Cross-account OSS access patterns using STS AssumeRole
Concrete scenarios:
Storage vaults backed by OSS with ECS instance profile (no AK/SK in config)
Cloud recycler cleaning up OSS garbage with RAM role credentials
Catalog/external table reads from OSS with STS-assumed least-privilege role
Related issues
No existing issue. This feature was discussed informally and a draft PR (#61329) has been submitted. This issue formalizes the feature request and tracks the work across 4 incremental PRs:
Design principle: All changes are additive and gated behind enable_oss_native_sdk = false (default). Existing S3-compatible OSS path is fully preserved when the flag is off.
Search before asking
Description
Add native Alibaba Cloud OSS support as a first-class storage backend in Doris, using the official Alibaba Cloud OSS C++ SDK instead of the existing S3-compatible (AWS SDK) path.
Use case
Doris users running on Alibaba Cloud ECS face three problems with the current S3-compatible OSS path:
No credential-free access — The AWS SDK cannot talk to the ECS instance metadata service (100.100.100.200). Users must manage static AK/SK keys even when an ECS RAM role is attached to the instance.
No STS AssumeRole — Cross-account access and least-privilege patterns require
acs:ram::account:role/nameARNs which are Alibaba-specific and not reachable via the AWS STS endpoint.No RRSA (OIDC) — Kubernetes workloads on ACK use RRSA (RAM Roles for Service Accounts) for pod-level identity. The AWS SDK has no awareness of Alibaba's OIDC token file mechanism.
Target users:
Concrete scenarios:
Related issues
No existing issue. This feature was discussed informally and a draft PR (#61329) has been submitted. This issue formalizes the feature request and tracks the work across 4 incremental PRs:
PR-1: [feature] (cloud) Add Alibaba Cloud OSS C++ SDK stack - Part 1 #61329 FE
fe-filesystem-ossSPI — ECS RAM role, AssumeRole, RRSA,oss.credentials_providertype-based dispatchPR-2: [feature](cloud) Add Alibaba Cloud OSS C++ SDK stack - Part 2 #65794 Thirdparty C++ SDK stack — apr, tea-cpp, credentials-cpp, openapi-v2, sts-20150401, alibabacloud-oss-cpp-sdk
PR-3: BE native OSS filesystem —
OSSFileSystem,OSSFileReader,OSSFileWriter, credential providers,enable_oss_native_sdkconfig flagPR-4: Cloud recycler OSS accessor —
OSSAccessor,OssObjClient, reuses shareddelete_objects_recursively_()helperDesign principle: All changes are additive and gated behind
enable_oss_native_sdk = false(default). Existing S3-compatible OSS path is fully preserved when the flag is off.Are you willing to submit PR?
Code of Conduct