[I] [BUG] - AWS_REGION mandatory ? [polaris]

["lefebsy (via GitHub)" <gi...@apache.org>]

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

   ### Is this a possible security vulnerability?
   
   - [X] This is NOT a possible security vulnerability
   
   ### Describe the bug
   
   Hello,
   Maybe I am wrong and this is an expected behavior.
   
   If there is no AWS_REGION setted in the environnement where Polaris is running (inMemory), the action of creating a catalog throw an error during the initialization of the STS Client. 
   
   
   
   ### To Reproduce
   
   - Do not have AWS_REGION setted in environnement running Polaris
   - start Polaris in mode "InMemory" (metaStoreManagerFactory == InMemoryPolarisMetaStoreManagerFactory)
   - after Polaris is started with success
   - create a catalog (with curl by example)
   - STSClient fail during instantiation in polaris-service/src/main/java/org/apache/polaris/service/PolarisApplication.java line 160 (metaStoreManagerFactory)
   
   
   
   ### Actual Behavior
   
   - In polaris-service/src/main/java/org/apache/polaris/service/PolarisApplication.java
   - line 160 the PolarisStorageIntegrationProviderImpl will try to intantiate by default a AWS stsClient
   - without AWS_REGION setted, it's failing
   
   ### Expected Behavior
   
   - Maybe let the polaris Core storage implementation fully manage this STS client (why is it instantiated in the Service ?)
   - Maybe set a default Region in the STSbuilder to avoid an error ?
   
   
   ### Additional context
   
   _No response_
   
   ### System information
   
   Dev mode


-- 
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: issues-unsubscribe@polaris.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org