You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, the objects in test-public-bucket are accessible via direct links:
86
86
87
-
```
88
-
> s3cmd --configure
87
+
```console
88
+
$s3cmd --configure
89
89
90
90
Enter new values or accept defaults in brackets with Enter.
91
91
Refer to user manual for detailed description of all options.
@@ -133,18 +133,18 @@ And then confirm.
133
133
134
134
__IMPORTANT__: The configuration is not complete yet.
135
135
136
-
```
137
-
> s3cmd ls s3://test-bucket
136
+
```console
137
+
$s3cmd ls s3://test-bucket
138
138
ERROR: S3 error: 403 (SignatureDoesNotMatch)
139
139
```
140
140
141
141
To fix this, it is necessary to edit the `.s3cfg` file, normally located in the user's home directory, and change the `signature_v2` setting to true.
142
142
143
-
```
144
-
> cat .s3cfg | grep signature_v2
143
+
```console
144
+
$cat .s3cfg | grep signature_v2
145
145
signature_v2 = True
146
146
147
-
> s3cmd ls s3://test-bucket
147
+
$s3cmd ls s3://test-bucket
148
148
2024-12-09 08:05 15 s3://test-bucket/file.txt
149
149
```
150
150
@@ -154,11 +154,7 @@ signature_v2 = True
154
154
155
155
In order to be able to connect to the S3 endpoint using Cyberduck, a profile supporting path-style requests must be downloaded from [here](https://profiles.cyberduck.io/S3%20(Deprecated%20path%20style%20requests).cyberduckprofile) or copied from below.
0 commit comments