Tag Instances hosting healthcare data (HDS)

Reviewed on October 15, 2026

When hosting healthcare data using Scaleway Instances, you are responsible for knowing which of your resources are HDS-compliant and which are not, as outlined in the Instances Shared responsibility model.

To identify these resources, you are legally obligated to add the HDS tag to every Instance within your HDS scope. This tag is metadata only: it does not change how the Instance works, but it lets you filter, audit, and report on your HDS scope.

To tag several Instances at once, or to tag Instances from your scripts and automation tools, see Tag Instances hosting healthcare data using the CLI and API.

Before you start

To complete the actions presented below, you must have:

• A Scaleway account logged in to the console (External link)
• Owner status or IAM permissions allowing you to perform actions in the intended Organization
• Signed an HDS contract with Scaleway for the guarantees outlined in the Shared responsibility model to apply

Tag naming convention

Use exactly one tag, HDS, in uppercase, on all Instances within your HDS scope. Tag filters are case-sensitive and match exact values, so hds or HDS-prod do not match a filter on HDS.

Tag a new Instance

1. In the Compute section of the side menu, click CPU & GPU Instances. The Instances page opens.
2. Click + Create Instance. The Instance creation wizard opens.
3. Select an Availability Zone within the PARIS region (fr-par-1, fr-par-2, or fr-par-3).
4. Select an HDS-eligible Instance type.
5. Complete the other steps of the wizard.
6. In the Tags field, enter HDS.
7. Click Create Instance. The Instance Overview page opens.

Tag an existing Instance

1. In the Compute section of the side menu, click CPU & GPU Instances. The Instances page opens.
2. Click the name of the Instance you want to tag. The Instance Overview page opens.
3. In the Tags field, add HDS. Keep the existing tags.
4. Save your changes.

HDS Instance checklist

To host healthcare data, ensure that your Instances meet the following requirements:

• Each Instance within your HDS scope has the HDS tag, in uppercase.
• Each tagged Instance is located in an Availability Zone within the France - Paris region (fr-par-1, fr-par-2, or fr-par-3).
• Each tagged Instance uses an HDS-eligible Instance offer.
• The volumes, snapshots, and backups of each tagged Instance are located in the France - Paris region. Check the default zone of your scripts and automation tools.
• Only HDS-compliant volumes are attached to each tagged Instance.
• Snapshots are exported only to an HDS-compliant Object Storage bucket.
• You follow the provided security best practices at all times.

See the Instances Shared responsibility model for more information on the legal framework to host healthcare data.