Ceph Signature v4 Exception Error

Hello community, anyone with experience with setting up a ceph storage cluster and getting signature version errors when connecting to a bucket via S3 client. I have a cluster running Ceph Pacific(16.2.5). I have radosgw installed to expose my pool via S3. When I connect to my bucket using signature version 2 I am able to connect but when using signature version 4, which is the required standard by a lot of services now, I am unable to connect. I am not seeing any info online on how to configure my cluster to use signature version 4

Is this the correct way to use signature version 4?

rgysi@zephir:~$ s3fs rgysi: bucket.rgysi/ -o url=http://zephir:5502,sigv4,use_path_request_style
rgysi@zephir:~$ ls -l bucket.rgysi/
total 43
-rw-r–r-- 1 rgysi rgysi 43272 Okt 24 08:58 new-fio.txt
rgysi@zephir:~$

If yes then it seems to work on ceph 17.2.7 (just upgraded yesterday (still having some issues with the upgrade)). I can’t remember that I have configured anything special for signature 4, but I see that my script used before had sigv2 in the URL, so I guess it was required to use sigv2 in the past, but I can’t remember.