From 8762fe4c499ab89df443cc1e65f27c281a09c03f Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Tue, 3 Feb 2026 18:03:20 +0100 Subject: [PATCH 01/11] feat(obj): sse MTA-6858 --- pages/object-storage/api-cli/enable-sse-c.mdx | 4 +- .../object-storage/api-cli/enable-sse-one.mdx | 72 +++++++++++++++++++ pages/object-storage/menu.ts | 4 ++ 3 files changed, 78 insertions(+), 2 deletions(-) create mode 100644 pages/object-storage/api-cli/enable-sse-one.mdx diff --git a/pages/object-storage/api-cli/enable-sse-c.mdx b/pages/object-storage/api-cli/enable-sse-c.mdx index 633235bf4c..9a617ca3e8 100644 --- a/pages/object-storage/api-cli/enable-sse-c.mdx +++ b/pages/object-storage/api-cli/enable-sse-c.mdx @@ -1,5 +1,5 @@ --- -title: Enabling server-side encryption (SSE-C) +title: Enabling server-side encryption with customer-provided keys (SSE-C) description: Enable server-side encryption with customer-provided keys (SSE-C) in Scaleway. tags: object storage server side encryption sse sse-c cli s3 dates: @@ -12,7 +12,7 @@ import Requirements from '@macros/iam/requirements.mdx' **S**erver-**S**ide **E**ncryption with **C**ustomer-provided keys (SSE-C) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to supply your own encryption keys to encrypt data when it is uploaded, and to decrypt data when accessed. -Currently, Scaleway does not support other types of server-side encryption methods, such as SSE-KMS, or SSE-S3. +Scaleway also supports SSE-SCW. Refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-scw/) for more information. ## SSE-C overview diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx new file mode 100644 index 0000000000..024d179149 --- /dev/null +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -0,0 +1,72 @@ +--- +title: Enabling server-side encryption with object native encryption (SSE-ONE) +description: Enable server-side encryption with object native encryption (SSE-ONE) for Scaleway Object Storage. +tags: object storage server side encryption sse one cli scaleway managed keys +dates: + validation: 2026-02-03 + posted: 2026-02-03 +--- +import Requirements from '@macros/iam/requirements.mdx' + +**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-S3) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). + +By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. + +Scaleway SSE-ONE behaves similarly to Server Side Encryption with Amazon S3 managed keys (SSE-S3). + + +Scaleway also supports SSE-C. Refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-c/) for more information. + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- Installed and initialized the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) + +## Enabling SSE-ONE on an existing bucket + +You can enable SSE-ONE on existing buckets. Objects uploaded **after** enabling SSE-ONE are automatically encrypted. However, objects existing in the bucket before enabling SSE-ONE will not be encrypted, as encryption occurs during object upload. + +1. In a terminal, run the command below to enable SSE-ONE on the target bucket. Make sure to replace `` with the correct value. + + ```bash + aws s3api put-bucket-encryption \ + --bucket \ + --server-side-encryption-configuration '{ + "Rules": [ + { + "ApplyServerSideEncryptionByDefault": { + "SSEAlgorithm": "AES256" + } + } + ] + }' + ``` + +2. run the command below to make sure the encryption was properly applied. Make sure to replace `` with the correct value. + + ```bash + aws s3api get-bucket-encryption --bucket + ``` + + An output similar to the following displays: + + ```json + { + "ServerSideEncryptionConfiguration": { + "Rules": [ + { + "ApplyServerSideEncryptionByDefault": { + "SSEAlgorithm": "AES256" + }, + "BucketKeyEnabled": false + } + ] + } + } + ``` + +SSE-ONE is enabled on your bucket. Each object uploaded from now on will be automatically encrypted using AES-256 keys managed by Scaleway. + diff --git a/pages/object-storage/menu.ts b/pages/object-storage/menu.ts index 6a5c9d2302..9f00540433 100644 --- a/pages/object-storage/menu.ts +++ b/pages/object-storage/menu.ts @@ -141,6 +141,10 @@ export const objectStorageMenu = { label: 'Enabling SSE-C', slug: 'enable-sse-c', }, + { + label: 'Enabling SSE-SCW', + slug: 'enable-sse-scw', + }, { label: 'Setting CORS rules', slug: 'setting-cors-rules', From 868ac40491add45ab9041f2f426d6142725518d0 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Mon, 16 Feb 2026 15:16:23 +0100 Subject: [PATCH 02/11] feat(obj): fixes --- pages/object-storage/api-cli/enable-sse-one.mdx | 2 +- pages/object-storage/menu.ts | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx index 024d179149..6d971defe2 100644 --- a/pages/object-storage/api-cli/enable-sse-one.mdx +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -8,7 +8,7 @@ dates: --- import Requirements from '@macros/iam/requirements.mdx' -**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-S3) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). +**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. diff --git a/pages/object-storage/menu.ts b/pages/object-storage/menu.ts index 9f00540433..302f586fbc 100644 --- a/pages/object-storage/menu.ts +++ b/pages/object-storage/menu.ts @@ -142,8 +142,8 @@ export const objectStorageMenu = { slug: 'enable-sse-c', }, { - label: 'Enabling SSE-SCW', - slug: 'enable-sse-scw', + label: 'Enabling SSE-ONE', + slug: 'enable-sse-one', }, { label: 'Setting CORS rules', From df163a8d951e5f39863561a05e9ca349e25f9d60 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Tue, 24 Feb 2026 11:58:47 +0100 Subject: [PATCH 03/11] doc(obj): update --- .../object-storage/sse-one-introduction.mdx | 13 +++++++++++++ .../object-storage/api-cli/enable-sse-one.mdx | 11 ++--------- .../object-storage/how-to/enable-sse-one.mdx | 19 +++++++++++++++++++ 3 files changed, 34 insertions(+), 9 deletions(-) create mode 100644 macros/object-storage/sse-one-introduction.mdx create mode 100644 pages/object-storage/how-to/enable-sse-one.mdx diff --git a/macros/object-storage/sse-one-introduction.mdx b/macros/object-storage/sse-one-introduction.mdx new file mode 100644 index 0000000000..bbef146166 --- /dev/null +++ b/macros/object-storage/sse-one-introduction.mdx @@ -0,0 +1,13 @@ +--- +title: sse-one-introduction +--- + +**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). + +By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. + +Scaleway SSE-ONE behaves similarly to Server Side Encryption with Amazon S3 managed keys (SSE-S3). + + +Scaleway also supports SSE-C. Refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-c/) for more information. + \ No newline at end of file diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx index 6d971defe2..e54511ac7b 100644 --- a/pages/object-storage/api-cli/enable-sse-one.mdx +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -7,16 +7,9 @@ dates: posted: 2026-02-03 --- import Requirements from '@macros/iam/requirements.mdx' +import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' -**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). - -By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. - -Scaleway SSE-ONE behaves similarly to Server Side Encryption with Amazon S3 managed keys (SSE-S3). - - -Scaleway also supports SSE-C. Refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-c/) for more information. - + diff --git a/pages/object-storage/how-to/enable-sse-one.mdx b/pages/object-storage/how-to/enable-sse-one.mdx new file mode 100644 index 0000000000..01cb614a2f --- /dev/null +++ b/pages/object-storage/how-to/enable-sse-one.mdx @@ -0,0 +1,19 @@ +--- +title: Enabling server-side encryption with object native encryption (SSE-ONE) +description: Enable server-side encryption with object native encryption (SSE-ONE) for Object Storage using the Scaleway console. +tags: object storage server side encryption sse one cli scaleway managed keys +dates: + validation: 2026-02-24 + posted: 2026-02-24 +--- +import Requirements from '@macros/iam/requirements.mdx' +import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' + + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) (optional) + From 2caa3f9a3a77c83e10ab767ed1499e7916bd38b4 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Tue, 24 Feb 2026 11:59:42 +0100 Subject: [PATCH 04/11] doc(obj): update --- pages/object-storage/menu.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/object-storage/menu.ts b/pages/object-storage/menu.ts index 302f586fbc..79d1ecf30b 100644 --- a/pages/object-storage/menu.ts +++ b/pages/object-storage/menu.ts @@ -58,6 +58,10 @@ export const objectStorageMenu = { label: 'Manage lifecycle rules', slug: 'manage-lifecycle-rules', }, + { + label: 'Enable SSE-ONE', + slug: 'enable-sse-one', + }, { label: 'Host healthcare data (HDS)', slug: 'host-healthcare-data', From 96953a36aa6944806154f76387edebc8e9917abb Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Fri, 27 Feb 2026 12:23:42 +0100 Subject: [PATCH 05/11] feat(obj): update --- .../object-storage/api-cli/enable-sse-one.mdx | 31 +++++++++++++++++-- 1 file changed, 28 insertions(+), 3 deletions(-) diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx index e54511ac7b..d6ec0ed90a 100644 --- a/pages/object-storage/api-cli/enable-sse-one.mdx +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -18,9 +18,9 @@ import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' - An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) - Installed and initialized the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) -## Enabling SSE-ONE on an existing bucket +## Enabling SSE-ONE on a bucket -You can enable SSE-ONE on existing buckets. Objects uploaded **after** enabling SSE-ONE are automatically encrypted. However, objects existing in the bucket before enabling SSE-ONE will not be encrypted, as encryption occurs during object upload. +Objects uploaded **after** enabling SSE-ONE are automatically encrypted. However, objects existing in the bucket before enabling SSE-ONE will not be encrypted, as encryption occurs during object upload. 1. In a terminal, run the command below to enable SSE-ONE on the target bucket. Make sure to replace `` with the correct value. @@ -38,7 +38,7 @@ You can enable SSE-ONE on existing buckets. Objects uploaded **after** enabling }' ``` -2. run the command below to make sure the encryption was properly applied. Make sure to replace `` with the correct value. +2. run the command below to make sure the encryption was properly applied. Do not forget to replace `` with the correct value. ```bash aws s3api get-bucket-encryption --bucket @@ -63,3 +63,28 @@ You can enable SSE-ONE on existing buckets. Objects uploaded **after** enabling SSE-ONE is enabled on your bucket. Each object uploaded from now on will be automatically encrypted using AES-256 keys managed by Scaleway. +## Disabling SSE-ONE on a bucket + +Objects uploaded **after** disabling SSE-ONE will not be automatically encrypted. However, objects existing in the bucket before disabling SSE-ONE will remain encrypted, as encryption occurs during object upload. + +1. In a terminal, run the command below to disable SSE-ONE on the target bucket. Make sure to replace `` with the correct value. + + ```bash + aws s3api delete-bucket-encryption --bucket + ``` + +2. run the command below to make sure the encryption was properly disabled. Do not forget to replace `` with the correct value. + + ```bash + aws s3api get-bucket-encryption --bucket + ``` + + An output similar to the following displays: + + ```json + { + "ServerSideEncryptionConfiguration": {} + } + ``` + +SSE-ONE is now disabled, and can be [enabled again](#enabling-sse-one-on-a-bucket) at any time. \ No newline at end of file From 37e87e33c2f4b6d12956b7999bf98128457beec3 Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Mon, 2 Mar 2026 16:34:46 +0100 Subject: [PATCH 06/11] feat(obj): update --- .../object-storage/api-cli/enable-sse-one.mdx | 2 + .../object-storage/how-to/enable-sse-one.mdx | 39 +++++++++++++++++++ 2 files changed, 41 insertions(+) diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx index d6ec0ed90a..88ac351f18 100644 --- a/pages/object-storage/api-cli/enable-sse-one.mdx +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -9,6 +9,8 @@ dates: import Requirements from '@macros/iam/requirements.mdx' import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' +This page explains how to use SSE-ONE with the AWS CLI. To use it with the Scaleway console, refer to the [dedicated documentation](/object-storage/how-to/enable-sse-one/). + diff --git a/pages/object-storage/how-to/enable-sse-one.mdx b/pages/object-storage/how-to/enable-sse-one.mdx index 01cb614a2f..e6110b09d4 100644 --- a/pages/object-storage/how-to/enable-sse-one.mdx +++ b/pages/object-storage/how-to/enable-sse-one.mdx @@ -9,6 +9,8 @@ dates: import Requirements from '@macros/iam/requirements.mdx' import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' +This page explains how to use SSE-ONE with the Scaleway Console. To use it with the AWS CLI, refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-one/) + @@ -17,3 +19,40 @@ import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) (optional) +## How to enable SSE-ONE during bucket creation + +When you [create a new Object Storage bucket](/object-storage/how-to/create-a-bucket/), you can enable SSE-ONE using the toggle under **Bucket encryption**. + +Objects pushed to this bucket will be automatically encrypted at rest with keys managed by Scaleway. + +## How to enable SSE-ONE on an existing bucket + +1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. + +2. Click the name of the desired bucket. The **Overview** tab displays. + +3. Select the **Settings** tab. + +4. Under **Bucket encryption**, click **Edit encryption mode**. A pop-up displays. + +5. Click the toggle to enable SSE-ONE, then click **Edit** to confirm. + +New objects uploaded to this bucket will be automatically encrypted at rest with keys managed by Scaleway. + + +Objects uploaded to this bucket before enabling SSE-ONE will not be encrypted. + + +## How to disable SSE-ONE on an existing bucket + +1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. + +2. Click the name of the desired bucket. The **Overview** tab displays. + +3. Select the **Settings** tab. + +4. Under **Bucket encryption**, click **Edit encryption mode**. A pop-up displays. + +5. Click the toggle to disable SSE-ONE, then click **Edit** to confirm. + +New objects uploaded to this bucket will not be encrypted. However, objects uploaded while SSE-ONE was enabled will remain encrypted. \ No newline at end of file From 814af84b1b9539719dcebc01d565447069fb0989 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 3 Mar 2026 12:03:24 +0100 Subject: [PATCH 07/11] Apply suggestion from @jcirinosclwy Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- macros/object-storage/sse-one-introduction.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/macros/object-storage/sse-one-introduction.mdx b/macros/object-storage/sse-one-introduction.mdx index bbef146166..e3b386046f 100644 --- a/macros/object-storage/sse-one-introduction.mdx +++ b/macros/object-storage/sse-one-introduction.mdx @@ -2,7 +2,7 @@ title: sse-one-introduction --- -**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and to decrypt data when accessed, with Scaleway managing encryption keys (AES-256). +**S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and decrypt it when accessed, with Scaleway managing encryption keys (AES-256). By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. From 09c8f8b7da4c274f0d2ac774859e0221260b2258 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 3 Mar 2026 12:03:30 +0100 Subject: [PATCH 08/11] Apply suggestion from @bene2k1 Co-authored-by: Benedikt Rollik --- macros/object-storage/sse-one-introduction.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/macros/object-storage/sse-one-introduction.mdx b/macros/object-storage/sse-one-introduction.mdx index e3b386046f..83c88036d0 100644 --- a/macros/object-storage/sse-one-introduction.mdx +++ b/macros/object-storage/sse-one-introduction.mdx @@ -4,7 +4,7 @@ title: sse-one-introduction **S**erver-**S**ide **E**ncryption with **O**bject **N**ative **E**ncryption (SSE-ONE) is an encryption method provided by Scaleway Object Storage to protect your data at rest. It allows you to encrypt data when it is uploaded, and decrypt it when accessed, with Scaleway managing encryption keys (AES-256). -By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each PutObject operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. +By default, SSE-ONE is applied per-upload, meaning that you must specify the encryption parameter for each `PutObject` operation. However, you can enable SSE-ONE on a bucket, so that each object uploaded is automatically encrypted at rest with an individual encryption key. Scaleway manages the creation, lifecycle, and deletion of encryption keys. Scaleway SSE-ONE behaves similarly to Server Side Encryption with Amazon S3 managed keys (SSE-S3). From 5896579300d40a658247b228e2e2131dc23f0367 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 3 Mar 2026 12:03:43 +0100 Subject: [PATCH 09/11] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- pages/object-storage/api-cli/enable-sse-one.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/object-storage/api-cli/enable-sse-one.mdx b/pages/object-storage/api-cli/enable-sse-one.mdx index 88ac351f18..12542f9e7b 100644 --- a/pages/object-storage/api-cli/enable-sse-one.mdx +++ b/pages/object-storage/api-cli/enable-sse-one.mdx @@ -40,7 +40,7 @@ Objects uploaded **after** enabling SSE-ONE are automatically encrypted. However }' ``` -2. run the command below to make sure the encryption was properly applied. Do not forget to replace `` with the correct value. +2. Run the command below to ensure the encryption was properly applied. Do not forget to replace `` with the correct value. ```bash aws s3api get-bucket-encryption --bucket @@ -69,13 +69,13 @@ SSE-ONE is enabled on your bucket. Each object uploaded from now on will be auto Objects uploaded **after** disabling SSE-ONE will not be automatically encrypted. However, objects existing in the bucket before disabling SSE-ONE will remain encrypted, as encryption occurs during object upload. -1. In a terminal, run the command below to disable SSE-ONE on the target bucket. Make sure to replace `` with the correct value. +1. Run the command below in a terminal to disable SSE-ONE on the target bucket. Make sure to replace `` with the correct value. ```bash aws s3api delete-bucket-encryption --bucket ``` -2. run the command below to make sure the encryption was properly disabled. Do not forget to replace `` with the correct value. +2. Run the following command to ensure the encryption was properly disabled. Do not forget to replace `` with the correct value. ```bash aws s3api get-bucket-encryption --bucket From 7f2ad5aa7def5c77449611afcfed3c9d71094d7f Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 3 Mar 2026 12:03:56 +0100 Subject: [PATCH 10/11] Apply suggestions from code review Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- pages/object-storage/how-to/enable-sse-one.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/object-storage/how-to/enable-sse-one.mdx b/pages/object-storage/how-to/enable-sse-one.mdx index e6110b09d4..67ff578128 100644 --- a/pages/object-storage/how-to/enable-sse-one.mdx +++ b/pages/object-storage/how-to/enable-sse-one.mdx @@ -33,7 +33,7 @@ Objects pushed to this bucket will be automatically encrypted at rest with keys 3. Select the **Settings** tab. -4. Under **Bucket encryption**, click **Edit encryption mode**. A pop-up displays. +4. Click **Edit encryption mode**, under **Bucket encryption**. A pop-up displays. 5. Click the toggle to enable SSE-ONE, then click **Edit** to confirm. @@ -51,7 +51,7 @@ Objects uploaded to this bucket before enabling SSE-ONE will not be encrypted. 3. Select the **Settings** tab. -4. Under **Bucket encryption**, click **Edit encryption mode**. A pop-up displays. +4. Click **Edit encryption mode**, under **Bucket encryption**. A pop-up displays. 5. Click the toggle to disable SSE-ONE, then click **Edit** to confirm. From f14ffd53b7c77c4df422ed8839b4faba218c741d Mon Sep 17 00:00:00 2001 From: Samy OUBOUAZIZ Date: Tue, 3 Mar 2026 13:45:04 +0100 Subject: [PATCH 11/11] feat(obj): update --- pages/object-storage/how-to/enable-sse-one.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/object-storage/how-to/enable-sse-one.mdx b/pages/object-storage/how-to/enable-sse-one.mdx index 67ff578128..e591afd003 100644 --- a/pages/object-storage/how-to/enable-sse-one.mdx +++ b/pages/object-storage/how-to/enable-sse-one.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' import SseOneIntroduction from '@macros/object-storage/sse-one-introduction.mdx' -This page explains how to use SSE-ONE with the Scaleway Console. To use it with the AWS CLI, refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-one/) +This page explains how to use SSE-ONE with the Scaleway Console. To use it with the AWS CLI, refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-one/).