ndrluis commented on issue #495:
URL: https://github.com/apache/iceberg-rust/issues/495#issuecomment-2256052967

   @Xuanwo
   
   > Hi, does remote signing means presign in s3?
   
   Yes and no. I'm not sure if this is the flow, because I haven't found any 
documentation; this is based on my understanding from reading the Python 
implementation.
   
   It's a presign process, but it's not the client's responsibility to presign. 
The get config will return the s3.signer.uri, and the load table will return 
s3.remote-signing-enabled as true along with some other S3 configurations. With 
that, we need to "presign" using the token returned in the load table.
   
   This is the specification for the server responsible for the signing: 
[s3-signer-open-api.yaml](https://github.com/apache/iceberg/blob/main/aws/src/main/resources/s3-signer-open-api.yaml)
   
   > I'm guessing https://github.com/apache/iceberg-rust/pull/498 should close 
this issue. Would you like to verify it?
   
   I'm not comfortable closing this issue without a regression test that 
guarantees the expected behavior.
   


-- 
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-unsubscr...@iceberg.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to