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
It is useful to support all the identity sources (ec2 instance metadata, EKS pod identity, temporary credentials, credentials helper, AWS IAM Roles Anywhere) and allows setting up Trino using the canonical AWS setup process.
I suggest:
adding a s3.credentials-provider parameter to the native s3 implementation (similar to what's done in legacy s3)
adding hive.metastore.glue.credentials-provider to the AWS Glue catalog configuration properties
This would add flexibility for the user to chose its preferred auth method, and write custom classes to do so.
Thanks
The text was updated successfully, but these errors were encountered:
There is no documented way to use the AWS default credentials provider for hive / native s3.
It is useful to support all the identity sources (ec2 instance metadata, EKS pod identity, temporary credentials, credentials helper, AWS IAM Roles Anywhere) and allows setting up Trino using the canonical AWS setup process.
I suggest:
This would add flexibility for the user to chose its preferred auth method, and write custom classes to do so.
Thanks
The text was updated successfully, but these errors were encountered: