gaocho commented on issue #3742: URL: https://github.com/apache/polaris/issues/3742#issuecomment-3886337578
@jbonofre Thanks for the quick response! Based on my testing, this appears to be a **generic issue with S3-compatible storage that doesn't support AWS STS**, though I want to be transparent about what I've verified vs. what I'm inferring. ## What I can confirm: - Setting `stsUnavailable: true` in `storageConfigInfo` ✓ - Static credentials (my access key and secret access key) configured in catalog properties ✓ - These same credentials work successfully via AWS CLI against NetApp S3 ✓ - Spark CREATE TABLE fails with: "The AWS Access Key Id you provided does not exist" - The error shows what appears to be a randomly generated credential: `q7A5xELO357+g9nPhhIMEU52W14snVD...` (not my configured key) ## What I'm inferring: - That Polaris is attempting credential vending despite `stsUnavailable: true` - That this would affect any S3-compatible storage without STS support (MinIO, Ceph, Dell ECS, Wasabi, etc.) -- 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]
