Skip to content

Commit 57e838e

Browse files
committed
docs(obj): add compliant bucket creation how to MTA-6389
1 parent cdc7fb1 commit 57e838e

File tree

2 files changed

+28
-0
lines changed

2 files changed

+28
-0
lines changed

menu/navigation.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5234,6 +5234,10 @@
52345234
"label": "Manage lifecycle rules",
52355235
"slug": "manage-lifecycle-rules"
52365236
},
5237+
{
5238+
"label":"Create a compliant bucket",
5239+
"slug":"create-compliant-bucket"
5240+
},
52375241
{
52385242
"label": "View and abort incomplete multipart uploads",
52395243
"slug": "abort-incomplete-mpu"
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: How to create a compliant bucket
3+
description: This page details the steps to follow to create a compliant bucket using Scaleway Object Storage
4+
tags:
5+
dates:
6+
validation: 2025-08-27
7+
posted: 2025-08-27
8+
---
9+
10+
It is crucial to follow the recommendations outlined in the shared responsibility model when hosting health data to ensure compliance with legal and regulatory requirements, such as data protection laws and industry standards.
11+
12+
Adhering to these guidelines helps safeguard sensitive information against unauthorized access, breaches, and data loss, while also clarifying the roles and responsibilities between the cloud provider and the customer.
13+
14+
Follow the procedure below to create a compliant bucket.
15+
16+
## Compliant bucket creation checklist
17+
18+
Make sure that your bucket follows the requirements below:
19+
20+
- Your bucket must be created in the **France - Paris** (`fr-par`) region.
21+
- Lifecycle rules must be disabled
22+
- Your objects within this bucket must not be stored using the **Glacier** storage class.
23+
- You must use a valid encryption and deletion method (as explained above)
24+
- You must follow the provided security best practices at all times

0 commit comments

Comments
 (0)