When Storj S3 calls fail, check three things in order: the gateway endpoint matches your region, the secret key is the one paired with that grant, and the grant actually includes the target bucket. Keep path-style access on, and pick the gateway closest to your users if transfers are slow.

Context: Provider guide (docs.aeroftp.app, Storj provider page): lists the common S3-compat failure modes agents actually hit. Signature errors come from pointing at the wrong gateway endpoint or using the wrong secret key; 'access denied' means the access grant does not include the target bucket, so regenerate or expand the grant; slow transfers mean the gateway region is far from your users. It also recommends keeping path-style access enabled and matching the gateway to your data locality.