|
6 | 6 | validation: 2025-08-27 |
7 | 7 | posted: 2025-08-27 |
8 | 8 | --- |
| 9 | +import Requirements from '@macros/iam/requirements.mdx' |
9 | 10 |
|
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 | +It is crucial to follow the recommendations outlined in the [shared responsibility model](/object-storage/reference-content/) when hosting health data to ensure compliance with legal and regulatory requirements, such as data protection laws and industry standards. |
11 | 12 |
|
12 | 13 | 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 |
|
14 | | -Follow the procedure below to create a compliant bucket. |
| 15 | +<Requirements /> |
| 16 | + |
| 17 | +- A Scaleway account logged into the [console](https://console.scaleway.com) |
| 18 | +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization |
| 19 | + |
| 20 | +## How to create a compliant Object Storage bucket to host healthcare data |
| 21 | + |
| 22 | +Even though you can use an existing bucket to host healthcare data, we strongly recommend you create a dedicated bucket for this purpose. This is to make sure that no lifecycle rule exists, and that every object uploaded to this bucket is properly encrypted. |
| 23 | + |
| 24 | +1. Click **Object Storage** on the left side menu of the console. The Object Storage dashboard displays. |
| 25 | +2. Click **+ Create bucket**. The bucket creation page displays. |
| 26 | +3. Enter a name for your bucket. |
| 27 | +4. Select the Paris region. |
| 28 | +5. Set the bucket visibility to **Private**. |
| 29 | + <Message type="note"> |
| 30 | +6. Select a use case for your bucket. |
| 31 | +7. Enable [bucket versioning](/object-storage/how-to/use-bucket-versioning/) if you want to store multiple versions of your objects (this may lead to higher storage costs). |
| 32 | +8. Optionally, you can use the cost estimator to simulate your Object Storage costs. |
| 33 | +10. Click **Create bucket** to confirm. A list of your buckets displays, showing the newly created bucket. |
| 34 | + |
| 35 | +## How to encrypt and push objects to your Bucket |
| 36 | + |
| 37 | +Objects in a compliant bucket must be encrypted to make sure data is protected. To achieve this, several options are available: |
| 38 | + |
| 39 | +- Scaleway's SSE-C (**S**erver-**S**ide **E**ncryption with **C**ustomer-provided keys) mechanism garantees that objects uploaded to the bucket are properly encrypted. |
| 40 | + |
| 41 | +- The `put-bucket-encryption` operation |
| 42 | + |
15 | 43 |
|
16 | 44 | ## Compliant bucket creation checklist |
17 | 45 |
|
18 | 46 | Make sure that your bucket follows the requirements below: |
19 | 47 |
|
20 | 48 | - Your bucket must be created in the **France - Paris** (`fr-par`) region. |
21 | | -- Lifecycle rules must be disabled |
| 49 | +- Your bucket must not have active lifecycle rules |
22 | 50 | - Your objects within this bucket must not be stored using the **Glacier** storage class. |
23 | 51 | - You must use a valid encryption and deletion method (as explained above) |
24 | | -- You must follow the provided security best practices at all times |
| 52 | +- You must follow the provided security best practices at all times |
| 53 | + |
| 54 | +## Enforcing compliance using bucket policies |
| 55 | + |
| 56 | +To enforce compliance regarding the storage class and lifecycle rules, you can set up a bucket policy. Bucket policies deny any action that is not explicitly allowed in a statement, allowing for fine-grained permissions management. |
| 57 | + |
| 58 | +Refer to the [dedicated documentation](/object-storage/api-cli/bucket-policy/) for more information on bucket policies. |
0 commit comments