scaleway · bene2k1 · Jul 31, 2025 · Jul 31, 2025 · Jul 31, 2025
diff --git a/changelog/march2025/2025-03-25-iam-added-iam-members.mdx b/changelog/march2025/2025-03-25-iam-added-iam-members.mdx
@@ -8,7 +8,7 @@ product: iam
 
 IAM Members can now be created, managed, and deleted in Scaleway Organizations. 
 
-Members are users who only exist in one Organization and can not own their own Organization. IAM Administrators can manage Member credentials and enforce security requirements for members to ensure Organization security. [Inviting Guests](/iam/how-to/invite-user-to-orga/) remains possible but will be deprecated in the following months.
+Members are users who only exist in one Organization and can not own their own Organization. IAM Administrators can manage Member credentials and enforce security requirements for members to ensure Organization security. [Inviting Guests](/iam/how-to/manage-members/) remains possible but will be deprecated in the following months.
 
 Read our [documentation on Members](/iam/how-to/manage-members) to learn more.
 
@@ -29,7 +29,7 @@ The [scope](/iam/concepts/#scope) of these permission sets is at [Organization](
 
 You can also use Audit Trail if you are part of the IAM `Administrators` [group](/iam/concepts/#group).
 
-1. Follow the [following procedure](/iam/how-to/invite-user-to-orga/) until step 3.
+1. Follow the [following procedure](/iam/how-to/manage-members/) until step 3.
 2. Click the drop-down under **Add to an existing group** and add the users to the **Administrators** group.
 3. Click **Invite** to send the invitation. The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/account/how-to/create-an-account/) first.
 4. The user will appear in the **Users** tab** once they have accepted the invitation.
@@ -94,7 +94,7 @@ Understanding this order helps you optimize your savings and ensure that you mak
 
 Savings plans cannot be canceled or exchanged.
 
-If you need to request a change to your savings plan, [contact the sales team](http://scaleway.com/en/cancel-saving-plans/ ).
+If you need to request a change to your savings plan, [contact the sales team](https://www.scaleway.com/en/contact-sales/).
 
 We do not make refunds for savings plans that have already been invoiced.
 

@@ -79,4 +79,4 @@ Each Dedibox VPS is isolated from other virtual servers on the same host, ensuri
 
 ## Are IP addresses for Dedibox VPS assigned statically?
 IP addresses for Dedibox VPS are generally assigned statically. However, in rare cases, such as maintenance or replacement of a faulty host node, we may perform IP migrations, which can result in a change of IP address.
-You can find your updated IP address in the Dedibox console. Please note that we do not currently notify users of such changes. You can contact our [support team](https://console.online.net/en/assistance/ticket) if you experience any issues.
+You can find your updated IP address in the Dedibox console. Please note that we do not currently notify users of such changes. You can contact our [support team](https://console.online.net/en/assistance/commercial) if you experience any issues.
@@ -21,7 +21,7 @@ Rescue mode is a minimal operating system that can be booted on demand over the
 We offer three types of rescue modes:
 
 - [Ubuntu](https://www.ubuntu.com/)
-- [Windows PE](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766093(v=ws.10))
+- [Windows PE](https://learn.microsoft.com/fr-fr/windows-hardware/manufacture/desktop/winpe-intro?view=windows-11)
 - [FreeBSD](https://www.freebsd.org/)
 
 <Requirements />

@@ -44,7 +44,7 @@ We provide a number of ways to keep track of your Edge Services consumption:
 
     <Lightbox image={image} alt="In the Edge Services section of the Scaleway console, information displays about your current plan, last monthly invoice, and charges accumulated this month for Edge Services" />
 
-- Use [Scaleway Cockpit](/network/edge-services/how-to/monitor-cockpit/) to monitor the data egressing from your Edge Services caches.
+- Use [Scaleway Cockpit](/edge-services/how-to/monitor-cockpit/) to monitor the data egressing from your Edge Services caches.
 
 ## WAF add-on
 

diff --git a/pages/file-storage/how-to/attach-file-system.mdx b/pages/file-storage/how-to/attach-file-system.mdx
@@ -18,7 +18,7 @@ import Requirements from '@macros/iam/requirements.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
-- [Created a file system](/file-system/how-to/create-file-system/)
+- [Created a file system](/file-storage/how-to/create-file-system/)
 - [Created at least one POP2 Instance](/instances/how-to/create-an-instance/)
 
 ## How to attach a file system to an Instance

diff --git a/pages/file-storage/how-to/create-file-system.mdx b/pages/file-storage/how-to/create-file-system.mdx
@@ -34,5 +34,5 @@ This page explains how to create a file system using the Scaleway console.
 The **Overview** page of your newly created file system displays.
 
 <Message type="note">
-You must [attach, then mount](/file-storage/how-to/attach-mount-file-system/) your file system to an Instance before using it.
+You must [attach, then mount](/file-storage/how-to/attach-file-system/) your file system to an Instance before using it.
 </Message>
diff --git a/pages/file-storage/how-to/manage-delete-file-system.mdx b/pages/file-storage/how-to/manage-delete-file-system.mdx
@@ -18,7 +18,7 @@ This page explains how to manage and delete a file system.
 
 - 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
-- [Created a file system](/file-system/how-to/create-file-system/)
+- [Created a file system](/file-storage/how-to/create-file-system/)
 
 ## How to manage a file system
 

diff --git a/pages/file-storage/how-to/mount-file-system.mdx b/pages/file-storage/how-to/mount-file-system.mdx
@@ -18,7 +18,7 @@ This page explains how to mount a file system to one or several Scaleway Instanc
 
 - 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
-- [Created a file system](/file-system/how-to/create-file-system/)
+- [Created a file system](/file-storage/how-to/create-file-system/)
 - [Attached](/file-storage/how-to/attach-file-system/) a file system to one or several Instances
 
 1. Click **File Storage** in the **Storage** section of the side menu. A list of your file systems displays.

diff --git a/pages/file-storage/how-to/resize-file-system.mdx b/pages/file-storage/how-to/resize-file-system.mdx
@@ -18,7 +18,7 @@ import Requirements from '@macros/iam/requirements.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
-- [Created a file system](/file-system/how-to/create-file-system/)
+- [Created a file system](/file-storage/how-to/create-file-system/)
 
 1. Click **File Storage** in the **Storage** section of the side menu. A list of your file systems displays.
 

diff --git a/pages/file-storage/how-to/unmount-file-system.mdx b/pages/file-storage/how-to/unmount-file-system.mdx
@@ -18,7 +18,7 @@ This page explains how to unmount a file system from one or several Scaleway Ins
 
 - 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
-- [Created a file system](/file-system/how-to/create-file-system/)
+- [Created a file system](/file-storage/how-to/create-file-system/)
 - [Attached](/file-storage/how-to/attach-file-system/) and [mounted](/file-storage/how-to/mount-file-system/) a file system to at least one Scaleway Instance
 
 1. Click **File Storage** in the **Storage** section of the side menu. A list of your file systems displays.

diff --git a/pages/file-storage/index.mdx b/pages/file-storage/index.mdx
@@ -36,13 +36,6 @@ description: Explore Scaleway File Storage with quickstart guides, how-tos, and
         label="View How-Tos"
         url="/file-storage/how-to/"
     />
-    <SummaryCard
-        title="Additional Content"
-        icon="book-open-outline"
-        description="Go further with detailed, in-depth information on File Storage."
-        label="View Additional Content"
-        url="/file-storage/reference-content/"
-    />
 </Grid>
 
 <ClickableBanner

@@ -49,7 +49,7 @@ The table below summarizes the key account and access management features that S
 | Feature | Guests | Members |
 |:--------:|:---------:|:---------:|
 | Login | Guests logged into their own accounts and could access all Organizations they were a part of via the console. | Members are identified by email address. If you are a Member in more than one Organization with the same email address, you can switch between Organizations. You must perform a first connection as a Member to remain connected and easily switch between Organizations. A first login is required for each device you use to connect to the Scaleway console. You remain logged into each device unless you clear your cookies. |
-| Enforcement of MFA | It was not possible to enforce MFA if a Guest in your Organization had not enabled MFA in their account. Organization admins could send reminder emails, but had to wait for the Guest to enable MFA, or remove them from the Organization to complete the enforce process. | When MFA is enforced in the Organization, Members have a [grace period](iam/concepts/#grace-period) to enable MFA in their accounts. This period is set by the Organization admins and starts as soon as a new Member is added. If they fail to enable MFA within this period, their accounts are locked. |
+| Enforcement of MFA | It was not possible to enforce MFA if a Guest in your Organization had not enabled MFA in their account. Organization admins could send reminder emails, but had to wait for the Guest to enable MFA, or remove them from the Organization to complete the enforce process. | When MFA is enforced in the Organization, Members have a [grace period](/iam/concepts/#grace-period) to enable MFA in their accounts. This period is set by the Organization admins and starts as soon as a new Member is added. If they fail to enable MFA within this period, their accounts are locked. |
 | Password renewal | Guests were not required to renew their passwords to stay in an Organization. | As a security measure, Organization admins can require Members to renew their passwords within a grace period. If a password was attributed to Members upon their creation, they must renew this password after their first login. |
 | User management | Guest accounts and personal Organizations could not be managed by anyone other than them. Their permissions on Organizations they were invited to are the prerogative of Organization admins. | Member accounts are a 100% manageable resource - they can be created, updated, locked and deleted by Organization admins. |
 | Organizations | Guests were users who had their own personal Organizations and were invited into another. They had full management rights on their accounts and Organizations. If they were removed from an Organization, they would continue to have a Scaleway account. |   Members exist only within an Organization and they exist solely in that Organization. Members cannot own Organizations. They must [comply with the security requirements](/iam/how-to/comply-with-sec-requirements-member) set for the Organization to ensure their continuous access.  |

@@ -22,7 +22,7 @@ This page shows the most common Scaleway CLI commands for creating and managing
 <Message type="tip">
   This content is also available as a printable PDF file:
 
-  [Download Instances CLI Cheatsheet - Printable](Scaleway-Instances-CLI-Cheatsheet.pdf)
+  [Download Instances CLI Cheatsheet - Printable](/pdf/Scaleway-Instances-CLI-Cheatsheet.pdf)
 </Message>
 
 
@@ -40,4 +40,3 @@ To help build and manage your applications, consider complementing your Workload
 Try Scaleway Workload-Optimized Instances with the following tutorials:
 - [Setting up a MySQL database engine on Ubuntu Linux](/tutorials/setup-mysql/)
 - [Project management for technical teams with Focalboard on Ubuntu Instances](/tutorials/focalboard-project-management/)
-- [Installing a multi-node Cockroach database with HA Proxy](/tutorials/setup-cockroachdb-cluster/)
@@ -126,7 +126,7 @@ Helm does not automatically migrate releases between storage backends. Follow th
 
 ### Need further assistance?
 
-Learn more about configuring Helm with an SQL storage backend by visiting the [official Helm documentation on SQL storage](https://helm.sh/docs/topics/plugins/helm-secrets/).
+Learn more about configuring Helm with an SQL storage backend by visiting the [official Helm documentation on SQL storage](https://helm.sh/docs/topics/advanced/#sql-storage-backend).
 
 
 If you have further questions, feel free to engage with the [Scaleway Slack community](https://slack.scaleway.com) to exchange insights, share experiences, and discover practical solutions.
@@ -71,7 +71,7 @@ Instance security groups and/or Load Balancer ACLs are incorrectly configured.
 
 ### Solution
 
-Instance [security groups](instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface. This means the Instance in question must be attached to the Load Balancer via its public IP and not any private IP.
+Instance [security groups](/instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface. This means the Instance in question must be attached to the Load Balancer via its public IP and not any private IP.
 - Ensure that your Instance is attached via its public IP address. If your Instance behind a Load Balancer is attached via a private IP address, the security group rules will not be applied.
 - Double check your [security group rules](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings), to verify that they correspond to the required ports, protocols, and IP addresses configured for your Load Balancer
 - To filter incoming traffic to your backend servers **as it passes through the Load Balancer**, use [Load Balancer ACLs](/load-balancer/how-to/create-manage-acls/).
@@ -24,7 +24,7 @@ You may find that when attempting to connect to the domain linked to your Load B
 - Try accessing your application directly, and not through your Load Balancer, to eliminate the possibility that the problem does not come from the Load Balancer. Use a tool such as `cURL` or Postman to compare headers and body content to check how the Load Balancer is modifying requests.
 - Check your Load Balancer's [Grafana dashboard](/load-balancer/how-to/monitor-lb-cockpit/) for any additional information about the way the request was handled.
 - Verify your certificate and [SSL bridging/offloading/passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) settings. For example, if SSL is terminated at the Load Balancer, but the backend expects HTTPS, requests may be rejected.
-- Check if [Proxy Protocol](load-balancer/reference-content/configuring-backends/#proxy-protocol) is enabled on your Load Balancer. If your backend server is not configured to handle Proxy Protocol headers correctly, it may reject the requests. Try [disabling Proxy Protocol](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) on your Load Balancer to see if it resolves the issue. If the issue is resolved when Proxy Protocol is disabled, [ensure your backend server is correctly configured for Proxy Protocol](/tutorials/proxy-protocol-v2-load-balancer/) before re-enabling.
+- Check if [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) is enabled on your Load Balancer. If your backend server is not configured to handle Proxy Protocol headers correctly, it may reject the requests. Try [disabling Proxy Protocol](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) on your Load Balancer to see if it resolves the issue. If the issue is resolved when Proxy Protocol is disabled, [ensure your backend server is correctly configured for Proxy Protocol](/tutorials/proxy-protocol-v2-load-balancer/) before re-enabling.
 
 ## I am getting a 503 Service Unavailable error when trying to access my application through my Load Balancer 
 

@@ -18,7 +18,7 @@ If an object is public, you can retrieve the link to access it from the [Scalewa
 <Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
-- [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) and have [uploaded objects](object-storage/how-to/upload-files-into-a-bucket/) to it
+- [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) and have [uploaded objects](/object-storage/how-to/upload-files-into-a-bucket/) to it
 
 1. Click **Object Storage** on the side menu. The list of your buckets displays.
 2. Click the bucket that contains the file you want to access. A list of your objects displays.

diff --git a/pages/partner-space/how-to/grant-access-to-partner-space.mdx b/pages/partner-space/how-to/grant-access-to-partner-space.mdx
@@ -41,7 +41,7 @@ Only users to whom this policy applies will have access to the Partner Space.
 Now that you have created the Reseller policy, you can apply it to users who need access to the Partner Space.
 
 1. Click the **Users** tab.
-2. Locate the user you want to grant access to. If the user is not yet part of the Organization, you will need to [invite them](/iam/how-to/invite-user-to-orga/) first.
+2. Locate the user you want to grant access to. If the user is not yet part of the Organization, you will need to [invite them](/iam/how-to/manage-members/) first.
 3. Click <Icon name="more" /> to the right of the row. The overview of the user’s information displays.
 4. Click the **Group & Policies** tab.
 5. Click **Add to group**.

@@ -43,7 +43,7 @@ Before attaching a Private Network to a Serverless Container, you must create it
     - Tick the **Enable VPC support** box. This parameter cannot be edited once the namespace is created.
     - Click **+ Add advanced options** to define any **environment variables** you want to inject into your container. For each environment variable, click **+ Add variable** and enter the key/value pair.
     - Set optional secret environment variables. **Secrets** are environment variables which are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**.
-4. Click **Create namespace only** to finish, or click **Create namespace and add a container** if you want to [create a container](/serverless-containers/how-to/create-a-container/) next.
+4. Click **Create namespace only** to finish, or click **Create namespace and add a container** if you want to [create a container](/serverless-containers/how-to/build-push-container-image/) next.
 
 ## How to attach a Serverless Container to a Private Network
 
@@ -64,7 +64,7 @@ Before attaching a Private Network to a Serverless Container, you must create it
   3. Click **+ Create container**. The container creation wizard displays.
   4. Scroll to the **Advanced options** section.
   5. In the **VPC** tab, select a Private Network from the dropdown menu.
-  6. Configure the other parameters of your container, then click **Create container**. Refer to the [How to create a container](/serverless-containers/how-to/create-a-container/) for more information.
+  6. Configure the other parameters of your container, then click **Create container**. Refer to the [How to create a container](/serverless-containers/how-to/build-push-container-image/) for more information.
 
   Your new container is deployed, and is attached to the selected Private Network.
   </TabsTab>