Access denied to s3

Help and Support
1

What is the problem you are having with rclone?

Getting access denied when trying to list an see bucket

Run the command 'rclone version' and share the full output of the command.

d0325mgray@Sirius:~$ rclone version   rclone v1.58.0                        - os/version: ubuntu 20.04 (64 bit)   - os/kernel: 5.13.0-40-generic (x86_64)                                     - os/type: linux                      - os/arch: amd64                      - go/version: go1.17.8                - go/linking: static                  - go/tags: none

Yes

Which cloud storage system are you using? (eg Google Drive)

Amazon S3

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Paste command here

d0325mgray@Sirius:~$ rclone ls s3:d0325mgray-b1 2022/04/27 20:17:55 Failed to ls: AccessDenied: Access Denied status code: 403, request id: 3GZG9HH0Y0K2DWR5, host id: yZc5ymg51aXtaSMZrQS37YnV3IqpOLZq1vo+nEmlSEB9VZnU43M+MrjejaaUMl1JyMaW1+GcM



#### The rclone config contents with secrets removed.  
<!--  You should use 3 backticks to begin and end your paste to make it readable.   -->

[s3]
type = s3
provider = AWS
env_auth = false
region = us-west-1
location_constraint = us-west-1
acl = private




#### A log from the command with the `-vv` flag  
<!-- You should use 3 backticks to begin and end your paste to make it readable.  Or use a service such as https://pastebin.com or https://gist.github.com/   -->

d0325mgray@Sirius:~$ rclone -vv ls s3:d0325mgray-b1 2022/04/27 20:21:03 DEBUG : rclone: Version "v1.58.0" starting with parameters ["rclone" "-vv" "ls" "s3:d0325mgray-b1"] 2022/04/27 20:21:03 DEBUG : Creating backend with remote "s3:d0325mgray-b1" 2022/04/27 20:21:03 DEBUG : Using config file from "/home/d0325mgray/.config/rclone/rclone.conf" 2022/04/27 20:21:06 DEBUG : 4 go routines active 2022/04/27 20:21:06 Failed to ls: AccessDenied: Access Denied status code: 403, request id: 5EKGDEEHZ6N4658F, host id: azzUSizq33L+EOuwuKHFWIkqnKJJMD8+8Sf/vA9AcLtwtwp3aFgTQGxOOOxtlA8T33kOj4K5Blc=


I have confirmed that the credentials are correct by running

aws s3api list-buckets --profile west-1
"Buckets": [ { "Name": "d0325mgray-b1", "CreationDate": "2022-04-17T02:56:46.000Z" } ], "Owner": { "DisplayName": "d0325mgray", "ID": "f8d19d1ac4d933fc2bc3a9a1852151fb46f37402ae4851a4b6766ef64de89b14" } } d0325mgray@Sirius:~$

2

hello and welcome to the forum,

try removing location_constraint = us-west-1

might not matter, but none of my s3 remotes use acl

3

Removed it. No change

4

Can you share your config file without credentials?

5 
[remote]
type = s3
provider = AWS
access_key_id = 
secret_access_key = 
region = us-east-1
storage_class = DEEP_ARCHIVE

[remote]
type = s3
provider = Wasabi
access_key_id = 
secret_access_key = 
endpoint = s3.us-east-2.wasabisys.com
6

could be an issue with s3 IAM/bucket polices.

7

In addition, I'm getting this

d0325mgray@Sirius:~$ rclone lsd spaces: 2022/04/27 21:29:58 NOTICE: s3: s3 provider "" not known - please set correctly -1 2022-04-27 12:47:38 -1 d0325mgray-s1

The provider is correct

8

seems your text does not have line endings, just one lone line

output should be formatted like this, enclosed with three backticks and debug output

rclone lsd remote: -vv
2022/04/27 10:35:28 DEBUG : rclone: Version "v1.58.0" starting with parameters ["rclone" "lsd" "remote:" "-vv"]
2022/04/27 10:35:28 DEBUG : Creating backend with remote "remote:"
2022/04/27 10:35:28 DEBUG : Using config file from "C:\\data\\rclone\\rclone.conf"
2022/04/27 10:35:28 DEBUG : Creating backend with remote "remote"
2022/04/27 10:35:28 DEBUG : fs cache: renaming cache item "remote:" to be canonical "remote_remote:vserver03.en07.rcloner"
           0 2022-04-27 10:35:28        -1 en07.rcloner
2022/04/27 10:35:28 DEBUG : 4 go routines active
9

But why would the AWS cli s3api command work then?

10

did not see the config posted for that remote???

11 
2022/04/27 23:31:47 DEBUG : rclone: Version "v1.58.0" starting with parameters ["rclone" "lsd" "s3:" "-vv"]
2022/04/27 23:31:47 DEBUG : Creating backend with remote "s3:"
2022/04/27 23:31:47 DEBUG : Using config file from "/home/d0325mgray/.config/rclone/rclone.conf"
2022/04/27 23:32:43 ERROR : : error listing: SerializationError: failed to decode REST XML response
	status code: 200, request id: 
caused by: XML syntax error on line 102: element <link> closed by </head>
2022/04/27 23:32:43 DEBUG : 5 go routines active
2022/04/27 23:32:43 Failed to lsd with 2 errors: last error was: SerializationError: failed to decode REST XML response
	status code: 200, request id: 
caused by: XML syntax error on line 102: element <link> closed by </head>
12

It's in the original post

[s3]
type = s3
provider = AWS
env_auth = false
region = us-west-1
location-restraint = us-west-1
acl = private
aws_access_key_id = 
aws_secret_access_key =
13

ok, but did not see a remote named spaces:

14

using the same exact client_id/secret in on the cli and with rclone?

15

No problem with spaces so cut it out

[s3]
type = s3
provider = AWS
env_auth = false
region = us-west-1
location-restraint = us-west-1
acl = private
aws_access_key_id = 
aws_secret_access_key =

[spaces]
type = s3
env_auth = false
access_key_id = 
secret_access_key = 
endpoint = sfo3.digitaloceanspaces.com
acl = private
16

Please note. I am in Cambodia which is ICT time

17

about digitaloceanspaces
provider = DigitalOcean

and maybe i am getting confused, first there was one remote, now we have two, each with different issue(s).
please pick on remote, and let's focus on solving the issues.

18

Yes. The focus should be on S3

20

ok, your first post of [s3] remote config, seems to be missing some important options.
so now that you re-posted the remotes' config, in the same format i suggested, i see an issue

between the two remotes, there is a mismatch in the names of the options.
i think that is the reason remote s3: is not working.

21

I don't know what it is. What options?