-
Notifications
You must be signed in to change notification settings - Fork 274
docs(blk): add hds doc #5887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
docs(blk): add hds doc #5887
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| --- | ||
| title: How to create a compliant volume to host healthcare data | ||
| description: This page details the steps to follow to create a compliant Scaleway Block Storage volume to host healthcare data | ||
| tags: | ||
| dates: | ||
| validation: 2025-11-12 | ||
| posted: 2025-11-12 | ||
| --- | ||
| import Requirements from '@macros/iam/requirements.mdx' | ||
|
|
||
| When hosting healthcare data using Scaleway Block Storage, you must follow the recommendations outlined in the [shared responsibility model](/block-storage/reference-content/storage-shared-responsibility-model/) to ensure compliance with legal and regulatory requirements, such as data protection laws, and industry standards. | ||
|
|
||
| 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. | ||
|
|
||
| <Requirements /> | ||
|
|
||
| - 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 | ||
| - Signed an HDS contract with Scaleway for the guarantees outlined in the [shared responsibility model](/block-storage/reference-content/storage-shared-responsibility-model/) to apply | ||
|
|
||
| ## How to create a compliant volume | ||
|
|
||
| To host healthcare data in compliance with HDS requirements, you must create a new Block Storage volume. | ||
|
|
||
| 1. Click **Block Storage** in the **Storage** section of the side menu. The Block Storage page displays. | ||
| 2. Click **+ Create volume**. | ||
| 3. Follow the steps in the creation wizard: | ||
| - Select an [Availability Zone](/instances/concepts/#availability-zone) within the **PARIS** region. | ||
| - Configure the volume: | ||
| - Enter a name for your volume or leave the automatically generated name. | ||
| - Select an [IOPS](/block-storage/concepts/#iops) option. You cannot edit the IOPS of a volume after its creation. | ||
|
SamyOubouaziz marked this conversation as resolved.
|
||
| - Define a volume size of at least 5 GB. | ||
| - Optionally, select an **HDS-compliant Instance** from the drop-down to attach your volume. The Instance must be within the same Availability Zone as your volume. | ||
|
SamyOubouaziz marked this conversation as resolved.
|
||
| - Verify the estimated cost. | ||
| 4. Click **Create volume**. The volumes overview page displays. | ||
|
SamyOubouaziz marked this conversation as resolved.
|
||
|
|
||
| ## How to encrypt data | ||
|
|
||
| To guarantee compliance with HDS requirements, you must proactively encrypt data stored on the Block Storage volume using a reliable mechanism, such as [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup). | ||
|
|
||
| Refer to the dedicated documentation for comprehensive information on [how to encrypt volumes using Cryptsetup with LUKS](/tutorials/encrypt-volumes/). | ||
|
|
||
| ## How to delete data | ||
|
|
||
| Data must be deleted in a compliant way to make sure data can not be retrieved by any means immediately afterward. | ||
|
SamyOubouaziz marked this conversation as resolved.
|
||
|
|
||
| To do so, delete data from your volume as you would with a standard Block Storage volume, then delete the encryption keys used to encrypt the deleted data. | ||
|
|
||
| ## Prohibited actions on a compliant volume | ||
|
|
||
| To host healthcare data, you must comply with the following requirements: | ||
|
|
||
| - You must not use an existing Block Storage volume. | ||
|
|
||
| - You must not export snapshots to an Object Storage bucket **that is not HDS-compliant**. Refer to the [dedicated documentation](/object-storage/how-to/host-healthcare-data/) to create an HDS-compliant bucket. | ||
|
|
||
| <Message type="important"> | ||
| Failure to comply with these requirements may lead to voiding compliance on the data contained in the volume. | ||
| </Message> | ||
|
|
||
| ## Compliant volume creation checklist | ||
|
|
||
| Make sure that your volume follows the requirements below: | ||
|
|
||
| 1. Make sure you are using a **new** Block Storage volume. | ||
|
|
||
| 2. Make sure you [created your volume](#how-to-create-a-compliant-volume) in an Availability Zone within the **France - Paris** region (`fr-par-1`, `fr-par-2`, `fr-par-3`). | ||
|
SamyOubouaziz marked this conversation as resolved.
|
||
|
|
||
| 3. Use a [proactive encryption method](#how-to-encrypt-data) to encrypt your data. | ||
|
|
||
| 4. Follow the provided security best practices at all times. | ||
|
|
||
| Refer to the [Storage Shared Responsibility Model](/block-storage/reference-content/storage-shared-responsibility-model/) for comprehensive information on the legal framework to host healthcare data. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.