Quick start guide missing configuration

[dicarcab]

Describe the bug

Hello, I've trying to test Polaris locally using the official Docker Image and a local gradle build, but have and issue while writing data to a catalog using S3.

I followed the Quick start guide and everything works fine until I tried to insert data to the table but I kept getting this answer
Server error: S3Exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. (Service: S3, Status Code: 301,) is there any configuration that must be specified to the docker image to be able to write data to the desired location ?

I set up the aws access and secret key and my bucket is in the same region that is used in the docker compose image. Is there missing steps in the official documentation ?

To Reproduce

1. set aws AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEYas env variables, AWS_REGION is set as us-west-2 inside docker file as the S3 bucket to be used.
2. Follow the quick start guide create roles and catalog using the docker compose file inside polaris repo
3. start local spark 3.5
4. use catalog and create namespaces and table using spark sql
5. using spark sql spark.sql("INSERT INTO quickstart_table VALUES (1, 'some data')") command

Actual Behavior

error returned by the rest api Server error: S3Exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. (Service: S3, Status Code: 301,) is there any configuration that must be specified to the docker image to be able to write data to the desired location ?

Expected Behavior

Data should be written in the table

Additional context

No response

System information

WSL ubuntu, S3 as backend

[MonkeyCanCode]

@dicarcab I think you will need to set AWS region as well depends on your setup. Maybe provide a bit more info on how to reproduce this?

[dicarcab]

@MonkeyCanCode I updated the steps to reproduce the issue. The bucket is located in us-west-2 region as the default value inside the docker compose file.

[MonkeyCanCode]

@MonkeyCanCode I updated the steps to reproduce the issue. The bucket is located in us-west-2 region as the default value inside the docker compose file.

K. I will take a look later this weekend then update. I recalled this part used to work.