s3scanner returns `not_exist` for everything on most default conditions

[fededamian]

Existing Issues

• I've searched the current issues

Command

docker run --rm ghcr.io/sa7mon/s3scanner -bucket s3scanner-bucketsize

Observed behavior (what happened?)

I am trying to run this tool, something I remember succeeded in before, but now, no matter what I do, I get the not_exist output. Either something is broken or I must be doing something very dumb but even in that case it may be helpful to have a couple command examples in the readme guaranteed to succeed to test the behavior.

I am using the docker image to make sure the infrastructure is not the culprit. See the output:

root@ip:~# docker run --rm ghcr.io/sa7mon/s3scanner -version
v3.0.4

root@ip:~# docker run --rm ghcr.io/sa7mon/s3scanner -bucket s3scanner-bucketsize
level=info msg="not_exist | s3scanner-bucketsize"

root@ip:~# docker run --rm ghcr.io/sa7mon/s3scanner -verbose -bucket s3scanner-bucketsize
level=debug msg="bucket not found" bucket_name=s3scanner-bucketsize method="aws.BucketExists()" region=
level=info msg="not_exist | s3scanner-bucketsize"

I know the testing buckets work fine because I can open and get the right response (https://s3scanner-bucketsize.s3.amazonaws.com/).

Am I doing something wrong? Or did something change that made the tool break these last days?

Thanks and apologizes for the inconvenience if this is on me.

Expected behaviour

Getting the exists output.

Debug output

docker run --rm ghcr.io/sa7mon/s3scanner -verbose -bucket s3scanner-bucketsize

level=debug msg="bucket not found" bucket_name=s3scanner-bucketsize method="aws.BucketExists()" region=
level=info msg="not_exist | s3scanner-bucketsize"

OS Info

Docker Image maintained by the project

Config file

No response

Additional info

No response