This message was deleted.

hmm. it should pick up the credentials in the properties. are you sure those credentials have access?

Yes the credentials have full s3 access. Looks like error says the problem is in the wrong key

InvalidAccessKeyId

, not

AccessDenied

I tried this locally and it works fine for me: • S3 deep storage configured with

druid.storage.type=s3

,

druid.storage.bucket

,

druid.storage.baseKey

,

druid.s3.accessKey

, and

druid.s3.secretKey

• S3 input source accessing a bucket in a different account using

properties

and

accessKeyId

+

secretKeyId

thank you for support yes, you are correct the problem is in an endpoint

Hey @Yurii I I just had a quick check in Druid Forum as I seemed to remember someone else having a similar issue re: Min.IO / S3 – I really thought someone found a solution (!) but I don’t think one was found… however maybe you could DM some people in the conversation on there and see if they worked anything out? https://www.druidforum.org/t/fail-to-configure-data-ingestion-from-minio-object-storage/6783

if that’s it: try using

endpointConfig

in your s3 input source too (edited)

I didn’t understand correctly this note I see, there is that parameter in the task configuration

"endpointConfig": {
             "url" : "<http://s3-store.aws.com|s3-store.aws.com>",
             "signingRegion" : "us-west-2"
         },

let me check this point

Cool thank you 🙂. In fact @Mark Herrera and @Sergio Ferragut and I were talking about this ourselves last week (!!!) as we’re building out a template POC environment with @Steve Halladay that uses Min.IO… so we will like to know, as well!

It works as expected!🎉 Thank you guys!

great to hear!