mthirani2021 opened a new issue, #1146:
URL: https://github.com/apache/polaris/issues/1146

   ### Describe the bug
   
   Trying to use/ configure MinIO server for storing all my tables/ metadata 
file for Polaris Catalogs.
   I spinned up Polaris at my local setting my default base location to MinIO 
bucket and used a dummy ARN (not sure if it has to be dummy btw). Any 
transaction related API like creating tables throws the below error:
   
   `Unable to process: Failed to get subscoped credentials: User: 
arn:aws:iam::<aws_account>:user/mayank.thirani is not authorized to perform: 
sts:AssumeRole on resource: arn:aws:iam::<aws_account>:role/dummy_arn (Service: 
Sts, Status Code: 403, Request ID: 6c3d0a67-3d94-4c55-b4ae-9372b7046669)`
   
   NOTE: aws_account is the real AWS account but dummy_arn doesn't exists. 
Trying to by pass it for MinIO like storage providers.
   
   ### To Reproduce
   
   1. All my access keys at local env are set to MinIO based access/ secret 
keys. This is how I spinned up Polaris:
   `./polaris --client-id ${CLIENT_ID} --client-secret ${CLIENT_SECRET} 
catalogs create --storage-type s3 --role-arn 
arn:aws:iam::<aws_account>:role/dummy_arn --default-base-location 
s3://minio-bucket default`
   2. Creating a table using the API mentioned per 
https://polaris.io/#tag/Catalog-API/operation/createTable, which throws the 
error mentioned in description
   
   
   ### Actual Behavior
   
   System throws the error as mentioned in description
   
   ### Expected Behavior
   
   System should allow to create tables in MinIO (S3 compatible like) storage 
providers.
   
   ### Additional context
   
   _No response_
   
   ### System information
   
   OS: MacOS
   Latest OSS Polaris pulled from repo
   Stortage: MinIO
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to