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
In the docs, it is mentioned that we can create an S3 catalog to enhance security by avoiding hardcoded credentials, and use system credentials.
However, it seems like I cannot create a catalog with type="S3" (ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown catalog type: s3).
It is also not possible to create a resource without omitting the access key and the secret key:
ERROR 1105 (HY000): Unexpected exception: Access key ID cannot be blank.
Solution
IMHO, no need for an S3 catalog here, contrary to what the docs suggest.
The simplest solution would be to allow to create a resource without access key and secret key. The logic to automatically search for the credential chain is already handled it the java AWS SDK, and also seem to be handled on Doris side:
The text was updated successfully, but these errors were encountered:
tgho-brrrr
changed the title
[Missing feature] S3 catalog type not found for system credentials instead of hardcoded ones
[Missing feature] S3 Credentials: catalog type s3 not found when trying to use system IAM credentials instead of hardcoded ones
Jun 6, 2024
tgho-brrrr
changed the title
[Missing feature] S3 Credentials: catalog type s3 not found when trying to use system IAM credentials instead of hardcoded ones
[Missing feature] S3 Credentials: Cannot use system IAM credentials instead of hardcoded ones
Jun 6, 2024
Search before asking
Description
In the docs, it is mentioned that we can create an S3 catalog to enhance security by avoiding hardcoded credentials, and use system credentials.
However, it seems like I cannot create a catalog with type="S3" (ERROR 1105 (HY000): errCode = 2, detailMessage = Unknown catalog type: s3).
It is also not possible to create a resource without omitting the access key and the secret key:
ERROR 1105 (HY000): Unexpected exception: Access key ID cannot be blank.
Solution
IMHO, no need for an S3 catalog here, contrary to what the docs suggest.
The simplest solution would be to allow to create a resource without access key and secret key. The logic to automatically search for the credential chain is already handled it the java AWS SDK, and also seem to be handled on Doris side:
In this file: S3Util.java
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: