Unable to mount S3 compatible bucket

[matthewblott]

I'm trying to mount an S3 compatible bucket hosted with IDrive. I can attach a bucket to a folder using rclone without any issues. However, I am unable to do the same with goofys. My credentials appear correct (as far as I can tell). The contents of the $HOME/.aws/credentials file are:

[default]
access_key_id = <my bucket key>
secret_access_key = <my bucket secret>

And the goofys command I'm using to mount is:

goofys --endpoint https://the-correct-prefix-idrivee2-the-correct-suffix.com bucket-name /mount/path

But I get the following error:

2023/05/22 22:52:52.494877 s3.DEBUG HEAD https://the-correct-prefix-idrivee2-the-correct-suffix.com/default = 403 []
2023/05/22 22:52:52.494935 s3.DEBUG Content-Length = [0]
2023/05/22 22:52:52.494944 s3.DEBUG Connection = [keep-alive]
2023/05/22 22:52:52.494954 s3.DEBUG Accept-Ranges = [bytes]
2023/05/22 22:52:52.494963 s3.DEBUG Content-Security-Policy = [block-all-mixed-content]
2023/05/22 22:52:52.494969 s3.DEBUG Strict-Transport-Security = [max-age=31536000; includeSubDomains]
2023/05/22 22:52:52.494978 s3.DEBUG Vary = [Origin Accept-Encoding]
2023/05/22 22:52:52.494985 s3.DEBUG Server = [nginx]
2023/05/22 22:52:52.494991 s3.DEBUG Date = [Mon, 22 May 2023 21:52:52 GMT]
2023/05/22 22:52:52.494998 s3.DEBUG X-Amz-Request-Id = [176195BC825BD071]
2023/05/22 22:52:52.495004 s3.DEBUG X-Content-Type-Options = [nosniff]
2023/05/22 22:52:52.495010 s3.DEBUG X-Xss-Protection = [1; mode=block]
2023/05/22 22:52:55.546744 s3.DEBUG DEBUG: Sign Request s3/HeadObject failed, not retrying, error NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
2023/05/22 22:52:55.546779 s3.ERROR code=NoCredentialProviders msg=no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors, err=<nil>

2023/05/22 22:52:55.546793 main.ERROR Unable to access 'default': NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
2023/05/22 22:52:55.546807 main.FATAL Mounting file system: Mount: initialization failed

One thing I noticed is I'm receiving a 403 error because it appends [default] to the mount point which isn't required for IDrive. Other than that, I'm at a loss. I've had a good look through the issues to see if I could find any pointers for other S3 compatible providers but there's not much to go on. Any help appreciated :-)

[mizzuri]

Can you try again this time with "aws_" prepended to your credentials?
e.g. aws_access_key_id

[matthewblott]

Yes @mizzuri that worked (brain fart on my part). Thanks 🙂