Customising the host of the presigned URL

[LarsSven]

Minio provides presigned URLs through the getPresignedObjectUrl function. This generates URLs such as:

http://localhost:31000/integration-tester/BasicTestcase/add.out?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=minioaccess%2F20250605%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250605T131638Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=355e91cc4344971919f38c7cfae6e0d6e6d151259fa651cdde491a557dcda3d9

However this presigned URL enforces the host to be localhost. So if I for example want to access the minio presigned URL from a different testcontainer, I need to access it through the host.testcontainers.internal host. However if I change localhost to host.testcontainers.internal , the URL verification fails. So I would either need to not have host included in verification, or be able to change the generated hostname for the presigned URL.

I tried using the quarkus.minio.devservices.host config parameter, however this doesn't seem to be changing the host in the generated presigned URL. How can I get the generated URL to change to host.testcontainers.internal for an injected MinioClient?

[LarsSven]

I realised that quarkus.minio.devservices.host is not an actual config parameter, so it makes sense that nothing happens.

However quarkus.minio.host is also not what I'm looking for. So I'm not sure how I can configure the host in the generated presigned URLs.

[jtama]

I guess you're invoking this method on an object instance ? If yes which one ? Wan you add the smallest possible reproducer ?

[jtama]

Ok so this is a minio server endpoint. So it would need digging to check if this can be customized through env var or other external config options.

If you have time.

[LarsSven]

I guess you're invoking this method on an object instance ? If yes which one ? Wan you add the smallest possible reproducer ?

Well the thing is that so far I haven't been invoking anything, because I don't know where to begin. Basically, I have a MinIO server running on a certain host from the perspective of the presigned URL creator, and a different host from the perspective of the consumer of the presigned URL. So I want to configure the host that is used in the presigned URL such that the consumer can actually use the presigned URL.

These may be relevant?

• presign url with different hostname ? minio/minio-java#1327 (for minio-java)
• Change host during pre-signed url creation. minio/minio-go#1616 (for minio-go)

[jtama]

Ok, so the presigned url is built using the quarkus.minio.host, so If I am not wrong you don't really have a choice. If the minio hostname you provide is an internal url, you won't be able to join the server, but would have usable preseigned url, if the minio hostname is usable, your preseigned url will be erroneous.

So the comments in the issue hint you should have to client instance, one only designed for presigned URL, and one for any other operations.

Maybe you hitting the limits of devservices. Anyhow I don't really see what we can do in the integration process to mitigate the issue.