ERROR can't connect to storage: unable to determine if bucket "test-kopia" exists: Access Denied.
We use role_arn with multiple accounts. We have one “master” account with our API key, then we use role_arn and source_profile to give access to other accounts.
Example :
I’m using kopia with non-aws S3, and in that case it is very important to add the endpoint URL, but I don’t know if kopia will auto-use AWS endpoints if it is not given. See if you can add verbosity until you see where it tries to connect?
In my case, I often use s3cmd to test that URL, accesskey and secretkey work, it allows for very short config files if all I need to do is test that a third-party program can create buckets and upload data using only those three pieces of information.
aws-cli and other official AWS kits might have builtin assumptions that kopia might not have.
One last thing, this is the only time when you can control the hash,splitter and crypto algorithms, so run “kopia benchmark ( splitter , crypto ) --print-options” and see which ones are best/fastest for your particular computer and add them to the “kopia repository create s3 command. In my case it is " --block-hash=HMAC-SHA224 --encryption=AES256-GCM-HMAC-SHA256 --object-splitter=DYNAMIC-1M-BUZHASH” but it differs from machine to machine so making your own tests is probably best.