Skip to content

Commit 404e311

Browse files
committed
Formatting fixes
1 parent aaacc55 commit 404e311

File tree

1 file changed

+13
-17
lines changed

1 file changed

+13
-17
lines changed

docs/storage/object.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ CSCS offers a public cloud object storage service, based on the Ceph Object Gate
2222

2323
The first step is to configure the profile:
2424

25-
```bash
26-
> aws configure --profile naret-testuser
25+
```console
26+
$ aws configure --profile naret-testuser
2727
AWS Access Key ID [None]: [REDACTED]
2828
AWS Secret Access Key [None]: [REDACTED]
2929
Default region name [None]: cscs-zonegroup
@@ -42,8 +42,8 @@ s3 =
4242

4343
#### Creating a pre-signed URL
4444

45-
```bash
46-
> aws --profile=naret-testuser s3 presign s3://test-bucket/file.txt --expires-in 300
45+
```console
46+
$ aws --profile=naret-testuser s3 presign s3://test-bucket/file.txt --expires-in 300
4747
4848
https://rgw.cscs.ch/test-bucket/file.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=IA6AOCNMKPDXQ0YNA3DP%2F20241209%2Fcscs-zonegroup%2Fs3%2Faws4_request&X-Amz-Date=20241209T080748Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=f2e2adb457f6fd43401124e4ea2650fba528e614ab661f9c05e2fa2e77691b5d
4949
```
@@ -57,7 +57,7 @@ A more thorough explanation can be found in the [RGW documentation](https://docs
5757
First, a bucket policy needs to be written:
5858

5959
```json
60-
> cat test-public-bucket-anon-from-internet.json
60+
$ cat test-public-bucket-anon-from-internet.json
6161
{
6262
"Version": "2012-10-17",
6363
"Statement": [
@@ -84,8 +84,8 @@ $ aws --profile=naret-testuser s3api put-bucket-policy \
8484

8585
At this point, the objects in test-public-bucket are accessible via direct links:
8686

87-
```
88-
> s3cmd --configure
87+
```console
88+
$ s3cmd --configure
8989
9090
Enter new values or accept defaults in brackets with Enter.
9191
Refer to user manual for detailed description of all options.
@@ -133,18 +133,18 @@ And then confirm.
133133

134134
__IMPORTANT__: The configuration is not complete yet.
135135

136-
```
137-
> s3cmd ls s3://test-bucket
136+
```console
137+
$ s3cmd ls s3://test-bucket
138138
ERROR: S3 error: 403 (SignatureDoesNotMatch)
139139
```
140140

141141
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.
142142

143-
```
144-
> cat .s3cfg | grep signature_v2
143+
```console
144+
$ cat .s3cfg | grep signature_v2
145145
signature_v2 = True
146146
147-
> s3cmd ls s3://test-bucket
147+
$ s3cmd ls s3://test-bucket
148148
2024-12-09 08:05 15 s3://test-bucket/file.txt
149149
```
150150

@@ -154,11 +154,7 @@ signature_v2 = True
154154

155155
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.
156156

157-
158-
```bash
159-
> cat "S3 (Deprecated path style requests).cyberduckprofile"
160-
```
161-
```xml
157+
```xml title="S3 (Deprecated path style requests).cyberduckprofile"
162158
<?xml version="1.0" encoding="UTF-8"?>
163159
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
164160
<plist version="1.0">

0 commit comments

Comments
 (0)