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
Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Instance API. Note that the `volume_type` field is set to `b_ssd`, meaning the volumes were created via the Instance API.
37
+
38
+
Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Instance API.
39
+
40
+
The `volume_type` field is set to `b_ssd`, meaning the volumes were created via the Instance API.
38
41
39
42
```
40
43
{
@@ -74,24 +77,6 @@ Below is an example of the output that should display if you have created volume
Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Block Storage API. Note that the `volume_type` field is set to either `sbs_15k` or `sbs_5k`, meaning the volumes were created via the Block Storage API.
95
+
Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Block Storage API.
96
+
97
+
The `volume_type` field is set to either `sbs_15k` or `sbs_5k`, meaning the volumes were created via the Block Storage API.
111
98
112
99
```
113
100
{
@@ -135,21 +122,9 @@ Below is an example of the output that should display if you have created volume
135
122
"class": "sbs"
136
123
},
137
124
"zone": "fr-par-1"
138
-
},
139
-
{
140
-
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
141
-
"name": "volume-interesting-keller",
142
-
"type": "sbs_5k",
143
-
"size": 25000000000,
144
-
"status": "available",
145
-
"specs": {
146
-
"perf_iops": 5000,
147
-
"class": "sbs"
148
-
},
149
-
"zone": "fr-par-1"
150
125
}
151
126
],
152
-
"total_count": 3
127
+
"total_count": 2
153
128
}
154
129
```
155
130
@@ -164,7 +139,8 @@ Open a terminal and run the following command to list all snapshots created via
@@ -254,7 +211,9 @@ An output similar to the following should display:
254
211
```bash
255
212
scw instance volume list
256
213
```
257
-
An output similar to the following should display:
214
+
215
+
An output similar to the following displays:
216
+
258
217
```
259
218
ID STATE SERVER ID
260
219
b582c548-6dc0-4e77-bb93-9615b9baa380 available a4138186-f362-41b2-adc2-c46a2e1a46b7
@@ -265,12 +224,15 @@ An output similar to the following should display:
265
224
7c232b97-63da-46e3-a018-399e1690b14b available ea5b27d7-268f-40fe-aff7-6943fbcac379
266
225
1a506e55-0741-4afd-8fbc-bc086ace0265 available 8860802f-0337-4901-b58c-ba3975922349
267
226
```
268
-
2. Note the ID of the volume you want to check the type of.
269
-
3. Get more information about your volume, including its type. Make sure that you replace `<volume-id>` with the ID of the volume.
227
+
228
+
2. Copy the ID of the volume for which you want to check the type.
229
+
230
+
3. Run the command below to get information about your volume, including its type. Make sure that you replace `<volume-id>` with the ID of the volume.
231
+
270
232
```bash
271
233
scw instance volume get <volume-id>
272
234
```
273
-
An output similar to the following should display:
235
+
An output similar to the following displays:
274
236
```
275
237
Volume.ID 7c232b97-63da-46e3-a018-399e1690b14b
276
238
Volume.Name System volume
@@ -285,16 +247,20 @@ An output similar to the following should display:
285
247
Volume.State available
286
248
Volume.Zone fr-par-1
287
249
```
250
+
288
251
4. Check the `Volume.VolumeType` field to learn if your volume is managed by the Instance API or the Block Storage API. Note that in our example, the `Volume.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API.
289
252
290
253
### Using the Scaleway Block Storage CLI
291
254
292
255
Open your terminal and run the following command to list all your volumes.
256
+
293
257
```bash
294
258
scw block volume list
295
259
```
260
+
296
261
An output similar to the following should display:
@@ -338,6 +308,7 @@ An output similar to the following should display:
338
308
Snapshot.ModificationDate 10 months ago
339
309
Snapshot.Zone fr-par-1
340
310
```
311
+
341
312
4. Check the `Snapshot.VolumeType` field to see the type of the snapshot. Note that in the example above, the `Snapshot.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API.
342
313
343
314
### Using the Scaleway Block Storage CLI
@@ -347,19 +318,23 @@ An output similar to the following should display:
347
318
```bash
348
319
scw block snapshot list
349
320
```
350
-
An output similar to the following should display.
2. Note the ID of the snapshot you want to check the type of.
358
-
3. Get more information about your snapshot, including its type. Make sure that you replace `<snapshot-id>` with the ID of the snapshot.
328
+
2. Note the ID of the snapshot for which you want to check the type.
329
+
330
+
3. Run the command below to get information about your snapshot, including its type. Make sure that you replace `<snapshot-id>` with the ID of the snapshot.
331
+
359
332
```bash
360
333
scw block snapshot get <snapshot-id>
361
334
```
362
-
An output similar to the following should display:
description: Perform various operations on buckets in Scaleway Object Storage using the CLI.
4
4
tags: object storage object-storage bucket
5
5
dates:
6
-
validation: 2025-01-15
6
+
validation: 2025-07-31
7
7
posted: 2018-09-14
8
8
---
9
9
@@ -34,7 +34,9 @@ aws s3 mb s3://bucketname
34
34
This operation allows you to delete the bucket mentioned in the command.
35
35
36
36
<Messagetype="important">
37
-
Deleting a bucket will also delete all of its objects. For safety measures, the effective deletion of the bucket will start 24 hours after the deletion request. The bucket name will then be available for other customers to use.<br /><br />The billing of your resources stops as soon as you request the deletion of your resources.<br /><br />Once you do so, the bucket and its objects and versions will no longer be displayed in the console or available via the API. For this reason, we recommend you delete all objects and versions in the bucket before requesting the deletion, if you wish the bucket deletion to be effective immediately.
37
+
- Deleting a bucket will also delete all of its objects. For safety measures, the effective deletion of the bucket will start 24 hours after the deletion request. The bucket name will then be available for other customers to use.
38
+
39
+
- The billing of your resources stops as soon as you request the deletion of your resources. Once you do so, the bucket and its objects and versions will no longer be displayed in the console or available via the API. For this reason, we recommend you delete all objects and versions in the bucket before requesting the deletion, if you wish the bucket deletion to be effective immediately.
The bucket website feature allows you to host static websites using Scaleway [Object Storage](https://www.scaleway.com/en/object-storage/).
13
-
14
-
It is possible to enable and configure the bucket website feature via the [AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/).
12
+
The bucket website feature allows you to host static websites using Scaleway [Object Storage](https://www.scaleway.com/en/object-storage/) via the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/).
15
13
16
14
To enable and configure the bucket website using the Scaleway console, refer to our [dedicated documentation](/object-storage/how-to/use-bucket-website/).
17
15
@@ -26,7 +24,7 @@ To enable and configure the bucket website using the Scaleway console, refer to
26
24
27
25
To use the bucket website feature, you need to enable it on the bucket or buckets you wish to host your website on.
28
26
29
-
You can use an API call or the AWS-CLI to enable it using `put-bucket-website`.
27
+
You can use an API call or the AWSCLI to enable it using `put-bucket-website`.
Requests sent to the Object Storage API require an HTTP Authorization header. Scaleway Object Storage supports [AWS v4 signature](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) protocol to add an authentication signature to API requests.
11
12
12
-
Requests sent to the Object Storage API require an HTTP Authorization header.
13
+
When using third-party tools such as [aws-cli](https://aws.amazon.com/cli/), [s3cmd](https://s3tools.org/s3cmd), [s3fs](https://github.com/s3fs-fuse/s3fs-fuse), or [MinIO Client](https://github.com/minio/mc), signatures are automatically generated for you.
13
14
14
15
<Requirements />
15
16
16
17
-[Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
18
+
- A valid [API key](/iam/how-to/create-api-keys/)
17
19
18
-
<Messagetype="note">
19
-
Currently, the [AWS v4 signature type](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) is supported.
20
-
</Message>
21
-
22
-
When using a client library such as [aws-cli](https://aws.amazon.com/cli/), [s3cmd](https://s3tools.org/s3cmd) or [s3fs](https://github.com/s3fs-fuse/s3fs-fuse), signatures are automatically generated by the library for you.
23
-
24
-
To generate the signature, you need to have an access key and secret key generated in the [Credentials section](https://console.scaleway.com/project/credentials) of your management console.
25
-
26
-
A v4 signature consists of different parts:
20
+
An AWSv4 authentication signature consists of different parts:
27
21
28
22
AWS4-HMAC-SHA256
29
23
: Indicates AWS Signature Version 4 (AWS4) and the signing algorithm (HMAC-SHA256).
@@ -206,7 +206,7 @@ When using the `awscli` to perform a [multipart upload](/object-storage/api-cli/
206
206
207
207
You can automate the removal of incomplete multipart uploads by adding or uploading a lifecycle configuration to your bucket. The setup can be done via an API call or an [AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/) command.
208
208
209
-
Send a [putbucketlifecycleconfiguration](/object-storage/api-cli/bucket-operations/#putbucketlifecycleconfiguration) request with the following XML payload:
209
+
Send a [PutBucketLifecycleConfiguration](/object-storage/api-cli/bucket-operations/#putbucketlifecycleconfiguration) request with the following XML payload:
0 commit comments