diff --git a/pages/account/assets/closed-account.webp b/pages/account/assets/closed-account.webp
new file mode 100644
index 0000000000..673fe150c8
Binary files /dev/null and b/pages/account/assets/closed-account.webp differ
diff --git a/pages/account/assets/scaleway-account-levels.webp b/pages/account/assets/scaleway-account-levels.webp
new file mode 100644
index 0000000000..692bc017a0
Binary files /dev/null and b/pages/account/assets/scaleway-account-levels.webp differ
diff --git a/pages/account/concepts.mdx b/pages/account/concepts.mdx
new file mode 100644
index 0000000000..2fad1c9675
--- /dev/null
+++ b/pages/account/concepts.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: Account - Concepts
+ description: Understand key concepts related to Scaleway accounts.
+content:
+ h1: Account - Concepts
+ paragraph: Understand key concepts related to Scaleway accounts.
+tags: active-session abuse api-key billing-alert kyc 2fa ssh-key mac-address
+dates:
+ validation: 2024-08-13
+categories:
+ - console
+---
+
+## Abuse
+
+[Abuse](https://www.scaleway.com/en/abuse-notice/) of Scaleway services includes cyber-crime, copyright violation, illegal or offensive content, spamming and malware distribution. Abuse should be [reported in the console](https://console.scaleway.com/support/abuses/create).
+
+Multiple instances of abuse from the same offending resource for the same reason within a given timeframe are grouped by case. An abuse report either creates a case if no case is currently open or joins an existing case. Scaleway clients are responsible for taking the appropriate security measures to solve the case and related abuse reports.
+
+## Active session
+
+An active session begins when a computer or device signs into your account. To connect you to your account, Scaleway uses JSON Web Tokens (JWT). JWT allows secure transmission of information between parties through tokens. These parties can be users, servers, or any other combination of services. In the case of Scaleway, when a user connects to their account (e.g. via an email address and password), we generate a token, associate it with the session and send it to the user. The token is composed of a header, a payload, and a signature. You can see the list of your active sessions in the [Scaleway console](https://console.scaleway.com/account/user/profile), to get an overview of all devices that are signed in and recently active on your account.
+
+## Console
+
+The Scaleway console allows you to view and manage your Scaleway products, billing information, support tickets and more. [Access the Scaleway console](https://console.scaleway.com/organization).
+
+## KYC
+
+**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/account/how-to/verify-identity/).
+
+## Login information
+
+Consists of the **e-mail address** your account is registered to and its corresponding [**password**](#password). With your login information, you can connect to your Scaleway Organization via the Scaleway console. As an alternative to using a password, you can use login using a [magic link](#magic-link).
+
+## MAC Address
+
+A **M**edia **A**ccess **C**ontrol Address is a unique ID assigned to network interface cards (NICs), used to ensure the physical address of a computer. It identifies the hardware manufacturer and is used for network communication between devices in a network segment.
+
+## Magic Link
+
+A magic link provides quick and secure access to your account without the hassle of remembering your [password](#login-information). When you choose to sign in with a magic link, you receive a unique link sent directly to your email inbox which you can use one time only to authenticate your login. Afterward, it automatically becomes invalid.
+
+## Multifactor Authentication (MFA)
+
+Multifactor authentication (MFA) is any form of verification that requires two factors to authenticate to a device you wish to connect to. Scaleway supports MFA for Cloud accounts in the form of a security code that you use in addition to your [password](#password) when you log in. You can receive the code via SMS or an authenticator app on your smartphone. Enabling MFA adds an additional layer of security against unauthorized access to your account.
+
+## Organization Quotas
+
+Every [Organization](/organizations-and-projects/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Quotas are per product (e.g. Instances) and product type (e.g. GP1-L Instance). Quotas are designed to prevent abuse, and can be viewed on the [Organization dashboard](https://console.scaleway.com/organization/settings) of the console.
+
+## Password
+
+A password is a string of characters associated to your account's email address that allows you to access the [Scaleway console](https://console.scaleway.com/). It is personal and must not be shared with anyone. Alternatively, you can use a [magic link](#magic-link) to authenticate yourself.
+
+## Support plan
+
+Scaleway provides four different types of [support plans](https://console.scaleway.com/support/plans): Basic, Silver, Gold and Platinum. Your support plan determines the level of service and dedicated assistance you have access to, and the guaranteed response time of your support requests. You can [configure your support plan in the console](/account/how-to/configure-support-plans/).
+
+## UUID
+
+A Universally Unique Identifier (UUID) is a 128-bit label attributed by Scaleway to each resource, used to identify them in CLI and API operations. UUIDs can also identify users and Organizations, as well as cloud resources.
\ No newline at end of file
diff --git a/pages/account/how-to/assets/scaleway-2FA-disable.webp b/pages/account/how-to/assets/scaleway-2FA-disable.webp
new file mode 100644
index 0000000000..36dcc90b40
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-2FA-disable.webp differ
diff --git a/pages/account/how-to/assets/scaleway-2FA-login.webp b/pages/account/how-to/assets/scaleway-2FA-login.webp
new file mode 100644
index 0000000000..25f2d24956
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-2FA-login.webp differ
diff --git a/pages/account/how-to/assets/scaleway-2FA-popup-1.webp b/pages/account/how-to/assets/scaleway-2FA-popup-1.webp
new file mode 100644
index 0000000000..39c224dc0b
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-2FA-popup-1.webp differ
diff --git a/pages/account/how-to/assets/scaleway-2FA-popup-2.webp b/pages/account/how-to/assets/scaleway-2FA-popup-2.webp
new file mode 100644
index 0000000000..0e942bdb43
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-2FA-popup-2.webp differ
diff --git a/pages/account/how-to/assets/scaleway-access-personal-data.webp b/pages/account/how-to/assets/scaleway-access-personal-data.webp
new file mode 100644
index 0000000000..1f9d98ec5f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-access-personal-data.webp differ
diff --git a/pages/account/how-to/assets/scaleway-account-levels.webp b/pages/account/how-to/assets/scaleway-account-levels.webp
new file mode 100644
index 0000000000..692bc017a0
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-account-levels.webp differ
diff --git a/pages/account/how-to/assets/scaleway-add-billing-information-button.webp b/pages/account/how-to/assets/scaleway-add-billing-information-button.webp
new file mode 100644
index 0000000000..abaa2b5855
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-add-billing-information-button.webp differ
diff --git a/pages/account/how-to/assets/scaleway-add-billing-information-page.webp b/pages/account/how-to/assets/scaleway-add-billing-information-page.webp
new file mode 100644
index 0000000000..03f478bca5
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-add-billing-information-page.webp differ
diff --git a/pages/account/how-to/assets/scaleway-add-id-document.webp b/pages/account/how-to/assets/scaleway-add-id-document.webp
new file mode 100644
index 0000000000..0cf30bd68f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-add-id-document.webp differ
diff --git a/pages/account/how-to/assets/scaleway-add-sepa-mandate.webp b/pages/account/how-to/assets/scaleway-add-sepa-mandate.webp
new file mode 100644
index 0000000000..7d027fb9d8
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-add-sepa-mandate.webp differ
diff --git a/pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-api-keys.webp b/pages/account/how-to/assets/scaleway-api-keys.webp
similarity index 100%
rename from pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-api-keys.webp
rename to pages/account/how-to/assets/scaleway-api-keys.webp
diff --git a/pages/account/how-to/assets/scaleway-bank-statement.webp b/pages/account/how-to/assets/scaleway-bank-statement.webp
new file mode 100644
index 0000000000..fe61850fcc
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-bank-statement.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-alerts-warning.webp b/pages/account/how-to/assets/scaleway-billing-alerts-warning.webp
new file mode 100644
index 0000000000..c09d32cda9
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-alerts-warning.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-corporate-info.webp b/pages/account/how-to/assets/scaleway-billing-corporate-info.webp
new file mode 100644
index 0000000000..881b8b6710
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-corporate-info.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-dropdown.webp b/pages/account/how-to/assets/scaleway-billing-dropdown.webp
new file mode 100644
index 0000000000..6f11df6035
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-dropdown.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-info.webp b/pages/account/how-to/assets/scaleway-billing-info.webp
new file mode 100644
index 0000000000..311e4bb1c8
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-info.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-personal-info.webp b/pages/account/how-to/assets/scaleway-billing-personal-info.webp
new file mode 100644
index 0000000000..491ff533aa
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-personal-info.webp differ
diff --git a/pages/account/how-to/assets/scaleway-billing-tab.webp b/pages/account/how-to/assets/scaleway-billing-tab.webp
new file mode 100644
index 0000000000..cf8d93de5b
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-billing-tab.webp differ
diff --git a/pages/account/how-to/assets/scaleway-choose-country-of-issue.webp b/pages/account/how-to/assets/scaleway-choose-country-of-issue.webp
new file mode 100644
index 0000000000..b13844680a
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-choose-country-of-issue.webp differ
diff --git a/pages/account/how-to/assets/scaleway-configuring-billing-alerts.webp b/pages/account/how-to/assets/scaleway-configuring-billing-alerts.webp
new file mode 100644
index 0000000000..2602a04a6b
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-configuring-billing-alerts.webp differ
diff --git a/pages/account/how-to/assets/scaleway-console-appearance.webp b/pages/account/how-to/assets/scaleway-console-appearance.webp
new file mode 100644
index 0000000000..fe65f7d875
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-console-appearance.webp differ
diff --git a/pages/account/how-to/assets/scaleway-console-menu.webp b/pages/account/how-to/assets/scaleway-console-menu.webp
new file mode 100644
index 0000000000..fa1f09d8e7
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-console-menu.webp differ
diff --git a/pages/account/how-to/assets/scaleway-console-my-profile.webp b/pages/account/how-to/assets/scaleway-console-my-profile.webp
new file mode 100644
index 0000000000..06eef5a0c8
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-console-my-profile.webp differ
diff --git a/pages/account/how-to/assets/scaleway-deactivate-organization.webp b/pages/account/how-to/assets/scaleway-deactivate-organization.webp
new file mode 100644
index 0000000000..6e75b4049d
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-deactivate-organization.webp differ
diff --git a/pages/account/how-to/assets/scaleway-default-payment-method.webp b/pages/account/how-to/assets/scaleway-default-payment-method.webp
new file mode 100644
index 0000000000..0d08ab4914
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-default-payment-method.webp differ
diff --git a/pages/account/how-to/assets/scaleway-edit-pen.webp b/pages/account/how-to/assets/scaleway-edit-pen.webp
new file mode 100644
index 0000000000..f9fa46e309
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-edit-pen.webp differ
diff --git a/pages/account/how-to/assets/scaleway-edit-profile.webp b/pages/account/how-to/assets/scaleway-edit-profile.webp
new file mode 100644
index 0000000000..e452fa4a05
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-edit-profile.webp differ
diff --git a/pages/account/how-to/assets/scaleway-enable-billing-alerts-slider.webp b/pages/account/how-to/assets/scaleway-enable-billing-alerts-slider.webp
new file mode 100644
index 0000000000..4030ecfdc3
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-enable-billing-alerts-slider.webp differ
diff --git a/pages/account/how-to/assets/scaleway-erase-account.webp b/pages/account/how-to/assets/scaleway-erase-account.webp
new file mode 100644
index 0000000000..46bd049e53
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-erase-account.webp differ
diff --git a/pages/account/how-to/assets/scaleway-exercise-right-portability.webp b/pages/account/how-to/assets/scaleway-exercise-right-portability.webp
new file mode 100644
index 0000000000..d65f765c00
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-exercise-right-portability.webp differ
diff --git a/pages/account/how-to/assets/scaleway-forgotten-password-screen.webp b/pages/account/how-to/assets/scaleway-forgotten-password-screen.webp
new file mode 100644
index 0000000000..ec80687ae4
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-forgotten-password-screen.webp differ
diff --git a/pages/account/how-to/assets/scaleway-get-started-page.webp b/pages/account/how-to/assets/scaleway-get-started-page.webp
new file mode 100644
index 0000000000..ce2ac3e759
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-get-started-page.webp differ
diff --git a/pages/account/how-to/assets/scaleway-joined-organizations-list.webp b/pages/account/how-to/assets/scaleway-joined-organizations-list.webp
new file mode 100644
index 0000000000..49757d51d7
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-joined-organizations-list.webp differ
diff --git a/pages/account/how-to/assets/scaleway-leave-organization.webp b/pages/account/how-to/assets/scaleway-leave-organization.webp
new file mode 100644
index 0000000000..7f8ee90e47
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-leave-organization.webp differ
diff --git a/pages/account/how-to/assets/scaleway-login-page-magic-link.webp b/pages/account/how-to/assets/scaleway-login-page-magic-link.webp
new file mode 100644
index 0000000000..b903ce10b0
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-login-page-magic-link.webp differ
diff --git a/pages/account/how-to/assets/scaleway-magic-link-email.webp b/pages/account/how-to/assets/scaleway-magic-link-email.webp
new file mode 100644
index 0000000000..842f07e28f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-magic-link-email.webp differ
diff --git a/pages/account/how-to/assets/scaleway-manage-data.webp b/pages/account/how-to/assets/scaleway-manage-data.webp
new file mode 100644
index 0000000000..93b118afb1
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-manage-data.webp differ
diff --git a/pages/account/how-to/assets/scaleway-my-privacy.webp b/pages/account/how-to/assets/scaleway-my-privacy.webp
new file mode 100644
index 0000000000..e4aa16f85f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-my-privacy.webp differ
diff --git a/pages/account/how-to/assets/scaleway-my-profile.webp b/pages/account/how-to/assets/scaleway-my-profile.webp
new file mode 100644
index 0000000000..307e1392e3
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-my-profile.webp differ
diff --git a/pages/account/how-to/assets/scaleway-one-last-thing-page.webp b/pages/account/how-to/assets/scaleway-one-last-thing-page.webp
new file mode 100644
index 0000000000..7a3ed51f6e
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-one-last-thing-page.webp differ
diff --git a/pages/account/how-to/assets/scaleway-org-dropdown-myprofile.webp b/pages/account/how-to/assets/scaleway-org-dropdown-myprofile.webp
new file mode 100644
index 0000000000..c542b70bad
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-org-dropdown-myprofile.webp differ
diff --git a/pages/account/how-to/assets/scaleway-orga-dashboard.webp b/pages/account/how-to/assets/scaleway-orga-dashboard.webp
new file mode 100644
index 0000000000..bbc0a6f311
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-orga-dashboard.webp differ
diff --git a/pages/account/how-to/assets/scaleway-organization-dashboard.webp b/pages/account/how-to/assets/scaleway-organization-dashboard.webp
new file mode 100644
index 0000000000..0644df66fb
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-organization-dashboard.webp differ
diff --git a/pages/account/how-to/assets/scaleway-password-reset.webp b/pages/account/how-to/assets/scaleway-password-reset.webp
new file mode 100644
index 0000000000..ef6fda703f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-password-reset.webp differ
diff --git a/pages/account/how-to/assets/scaleway-payment-methods.webp b/pages/account/how-to/assets/scaleway-payment-methods.webp
new file mode 100644
index 0000000000..4d517fae7f
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-payment-methods.webp differ
diff --git a/pages/account/how-to/assets/scaleway-rectify-personal-data.webp b/pages/account/how-to/assets/scaleway-rectify-personal-data.webp
new file mode 100644
index 0000000000..2432a6cae8
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-rectify-personal-data.webp differ
diff --git a/pages/account/how-to/assets/scaleway-redeem-coupon.webp b/pages/account/how-to/assets/scaleway-redeem-coupon.webp
new file mode 100644
index 0000000000..0734d2d7b3
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-redeem-coupon.webp differ
diff --git a/pages/account/how-to/assets/scaleway-send-a-magic-link.webp b/pages/account/how-to/assets/scaleway-send-a-magic-link.webp
new file mode 100644
index 0000000000..7283e5c524
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-send-a-magic-link.webp differ
diff --git a/pages/account/how-to/assets/scaleway-support-center.webp b/pages/account/how-to/assets/scaleway-support-center.webp
new file mode 100644
index 0000000000..0977d6be5e
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-support-center.webp differ
diff --git a/pages/account/how-to/assets/scaleway-support-history.webp b/pages/account/how-to/assets/scaleway-support-history.webp
new file mode 100644
index 0000000000..17abfd3f09
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-support-history.webp differ
diff --git a/pages/account/how-to/assets/scaleway-support-in-the-menu.webp b/pages/account/how-to/assets/scaleway-support-in-the-menu.webp
new file mode 100644
index 0000000000..810b5a04bc
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-support-in-the-menu.webp differ
diff --git a/pages/account/how-to/assets/scaleway-support-plan-confirmation.webp b/pages/account/how-to/assets/scaleway-support-plan-confirmation.webp
new file mode 100644
index 0000000000..505ffc48c6
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-support-plan-confirmation.webp differ
diff --git a/pages/account/how-to/assets/scaleway-support-plans-overview.webp b/pages/account/how-to/assets/scaleway-support-plans-overview.webp
new file mode 100644
index 0000000000..3b346070d1
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-support-plans-overview.webp differ
diff --git a/pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-terminal-icon.webp b/pages/account/how-to/assets/scaleway-terminal-icon.webp
similarity index 100%
rename from pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-terminal-icon.webp
rename to pages/account/how-to/assets/scaleway-terminal-icon.webp
diff --git a/pages/account/how-to/assets/scaleway-upper-right-menu.webp b/pages/account/how-to/assets/scaleway-upper-right-menu.webp
new file mode 100644
index 0000000000..4cce3056b8
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-upper-right-menu.webp differ
diff --git a/pages/account/how-to/assets/scaleway-website.webp b/pages/account/how-to/assets/scaleway-website.webp
new file mode 100644
index 0000000000..2f72c4fe83
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-website.webp differ
diff --git a/pages/account/how-to/assets/scaleway-welcome-aboard-modal.webp b/pages/account/how-to/assets/scaleway-welcome-aboard-modal.webp
new file mode 100644
index 0000000000..2e04c93683
Binary files /dev/null and b/pages/account/how-to/assets/scaleway-welcome-aboard-modal.webp differ
diff --git a/pages/account/how-to/change-console-appearance.mdx b/pages/account/how-to/change-console-appearance.mdx
new file mode 100644
index 0000000000..75f1d5822e
--- /dev/null
+++ b/pages/account/how-to/change-console-appearance.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to switch the color scheme of the console
+ description: Customize the appearance of the Scaleway console.
+content:
+ h1: How to switch the color scheme of the console
+ paragraph: Customize the appearance of the Scaleway console.
+tags: color-scheme change color theme dark-mode change-color
+dates:
+ validation: 2024-11-04
+ posted: 2022-10-12
+categories:
+ - console
+---
+
+You can choose the color scheme of the [Scaleway console](/account/concepts/#console) according to your preferences. We offer a light, dark, darker, or system-based color scheme.
+
+
+
+- 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
+
+1. Click on your name in the top right corner of the Scaleway console. A pop-up menu opens.
+
+2. Click **Profile** to view your Scaleway user profile.
+
+3. Scroll to the **Appearance** section and select the color scheme for your Scaleway console. You can choose from four options:
+ * A light color scheme
+ * A dark color scheme
+ * A darker color scheme
+ * A color scheme based on your system preferences
+
+
+
+ Your selection is saved automatically once you have chosen a color scheme.
+
+
diff --git a/pages/account/how-to/change-language.mdx b/pages/account/how-to/change-language.mdx
new file mode 100644
index 0000000000..3bb22bbf40
--- /dev/null
+++ b/pages/account/how-to/change-language.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: How to change the account language
+ description: Switch languages in the Scaleway account interface.
+content:
+ h1: How to change the account language
+ paragraph: Switch languages in the Scaleway account interface.
+tags: account language change
+dates:
+ validation: 2024-07-29
+ posted: 2021-06-22
+categories:
+ - console
+---
+
+You can choose which language you would like to view the [Scaleway console](/account/concepts/#console) in. This language will also be used for any marketing and product communications Scaleway sends you.
+
+
+
+- A [Scaleway account](https://console.scaleway.com)
+
+1. Log into the [Scaleway console](https://console.scaleway.com).
+2. Click your Organization name in the top right corner of the console to open the Organization drop-down menu (A), then click the **Profile** button (B). The **User Account** screen displays:
+
+3. In the User information section, click the **Edit profile** button. The **Edit your account profile** screen displays:
+
+4. Choose your preferred language from the drop-down list, then click **Confirm changes**.
+
+Your console will now be displayed in your preferred language, which will also be used for all marketing and product communications you receive. You can change your preferred language at any time by repeating this procedure.
diff --git a/pages/account/how-to/close-account.mdx b/pages/account/how-to/close-account.mdx
new file mode 100644
index 0000000000..0d81e2492b
--- /dev/null
+++ b/pages/account/how-to/close-account.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to close an account
+ description: Close your Scaleway account securely.
+content:
+ h1: How to close an account
+ paragraph: Close your Scaleway account securely.
+tags: account close cancel delete deactivate close-account
+dates:
+ validation: 2024-09-02
+ posted: 2021-06-22
+categories:
+ - console
+---
+
+If you do not want to use Scaleway services anymore, you can close your account and/or [erase your personal data](/account/how-to/manage-my-personal-data-gdpr/#how-to-erase-your-account-and-personal-data).
+
+## Closing your account or erasing your personal data: what’s the difference
+
+
+
+## How to close your account
+
+Closing your account will permanently delete your Organization’s servers, resources, services, and backups. However, you keep access to the Scaleway console.
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Ownership](/iam/concepts/#owner) of the Organization you intend to delete
+
+
+ We recommend that you delete all resources before closing your account. Otherwise, the remaining resources will be billed for usage before their manual deletion, which can take up to 10 days.
+
+
+
+
+1. Access the [Settings](https://console.scaleway.com/organization/settings) tab of your Organization dashboard (alternatively, you can go to the [User account](https://console.scaleway.com/account/profile) page).
+2. Scroll down to the **Close** account section.
+3. Click the **Close account** button once you have read and agreed with the warning message.
+4. Type **CLOSE**, then click **Continue closing** to confirm your decision.
+5. Select the reasons why you are closing your account.
+6. Click **Close account**. A message appears to confirm that closing has been scheduled.
+
+## How to reopen your account
+
+When your account is closed, you can still access the Scaleway console. A red banner in the top navigation bar will display to inform you that your account has been closed. If you want to reopen it, you can create a support ticket by clicking the link in the banner.
+
+
diff --git a/pages/account/how-to/configure-support-plans.mdx b/pages/account/how-to/configure-support-plans.mdx
new file mode 100644
index 0000000000..2ca43582e1
--- /dev/null
+++ b/pages/account/how-to/configure-support-plans.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to configure support plans
+ description: Set up and configure support plans in Scaleway.
+content:
+ h1: How to configure Support Plans
+ paragraph: Set up and configure support plans in Scaleway.
+tags: support-plans support-plan configure
+dates:
+ validation: 2024-07-29
+ posted: 2021-06-22
+categories:
+ - console
+---
+
+
+
+- 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
+
+The default support plan for an Organization is the **Basic** plan, but it can be upgraded on the **Support Plan** tab of the Organization page:
+
+
+
+- Select a plan and click **Select Plan** to proceed. A pop-up displays a disclaimer message informing you that your payment will be made automatically on the current month's invoice. Make sure you have carefully read the message.
+- Click **I understand** to confirm the change.
+
+
+
+An overview of your previous and current plans is available under **Support Plans History**.
+
+
diff --git a/pages/account/how-to/create-an-account.mdx b/pages/account/how-to/create-an-account.mdx
new file mode 100644
index 0000000000..a18952bb0b
--- /dev/null
+++ b/pages/account/how-to/create-an-account.mdx
@@ -0,0 +1,18 @@
+---
+meta:
+ title: How to create an account
+ description: Create a new Scaleway account quickly and securely.
+content:
+ h1: How to create an account
+ paragraph: Create a new Scaleway account quickly and securely.
+tags: create account console create-account
+dates:
+ validation: 2024-07-29
+ posted: 2021-06-22
+categories:
+ - console
+---
+
+Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Create your Scaleway account to gain access to the [Scaleway console](/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and deploy our products and services with ease.
+
+
diff --git a/pages/account/how-to/download-scaleway-contracts.mdx b/pages/account/how-to/download-scaleway-contracts.mdx
new file mode 100644
index 0000000000..0e47195c05
--- /dev/null
+++ b/pages/account/how-to/download-scaleway-contracts.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to download Scaleway contracts
+ description: Download General Terms of Services, Data Processing Agreement, and more.
+content:
+ h1: How to download Scaleway contracts
+ paragraph: Download General Terms of Services, Data Processing Agreement, and more.
+tags: account contracts gdpr
+dates:
+ validation: 2024-12-12
+ posted: 2024-12-12
+categories:
+ - console
+---
+
+Scaleway contracts define the terms, conditions, and commitments that govern the use of our services. They ensure transparency and compliance with legal and regulatory requirements while outlining the rights and responsibilities of both Scaleway and its customers.
+
+## Contracts available for download
+
+You can access and download the following types of contracts:
+
+| **Contract type** | **Description** |
+|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| General Terms of Services | Defines the respective rights and obligations of Scaleway and the client in connection with the client's use of the services provided by Scaleway. |
+| Data Processing Agreement | Defines the conditions under which Scaleway undertakes to carry out, on behalf of the client and for the sole purpose of the strict execution of the contract, personal data processing operations. |
+| Specific Conditions | The contractual document issued by Scaleway, specific to a service, that defines the conditions of provision and use applicable to said service. |
+| Technical and Organizational Measures | Describes the measures taken by Scaleway to ensure the security of client's data. |
+| Intrusion Testing Agreement | Defines the conditions applicable in the context of carrying out intrusion tests by the client or any third party acting on its behalf. |
+
+## How to download Scaleway contracts
+
+You can download Scaleway contracts either via the [console](https://console.scaleway.com/organization) or Scaleway's website:
+
+### From the Scaleway console
+You can access and download the contracts applicable to your Organization:
+1. Click the [Contracts](https://console.scaleway.com/organization/contracts) tab in your [Organization dashboard](https://console.scaleway.com/organization).
+2. Click the download icon next to the contract you want to download.
+
+### From Scaleway's website
+All available contracts can be viewed and downloaded directly from the [Contracts page](https://www.scaleway.com/en/contracts/).
\ No newline at end of file
diff --git a/pages/account/how-to/enforce-mfa.mdx b/pages/account/how-to/enforce-mfa.mdx
new file mode 100644
index 0000000000..0bc3b7e3b1
--- /dev/null
+++ b/pages/account/how-to/enforce-mfa.mdx
@@ -0,0 +1,65 @@
+---
+meta:
+ title: How to enforce Multifactor Authentication for an Organization
+ description: Enable and enforce Multi-Factor Authentication (MFA).
+content:
+ h1: How to enforce Multifactor Authentication for an Organization
+ paragraph: Enable and enforce Multi-Factor Authentication (MFA).
+tags: authentication 2FA two-factor two multi factor security google authenticator authenticator mfa
+dates:
+ validation: 2025-01-15
+ posted: 2023-06-12
+categories:
+ - console
+---
+
+[Multifactor Authentication (MFA)](/account/concepts/#multifactor-authentication-mfa) adds an extra layer of security to your Organization. Enforcing MFA will make it mandatory for all users in the Organization.
+
+
+
+- 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
+
+## How to enforce MFA
+
+1. Click the name of your Organization in the top right drop-down menu. The Organization dashboard displays.
+2. Go to the **Settings** tab.
+3. Scroll to the **Organization Multifactor Authentication (MFA)** section.
+4. Click **Enforce MFA**.
+5. Type **ENFORCE** in the box.
+
+ MFA will become mandatory for all users in the Organization. When you invite users to your Organization in the future, they must have set up MFA to be able to join.
+ You can only enforce MFA if all users in your Organization have already set up MFA on their accounts.
+
+6. Click **Enforce MFA**.
+ - If all users in your Organization already have MFA enabled, a confirmation message appears on the top right corner of the screen.
+
+ - If at least one of the users does not have MFA enabled, you must send them an [MFA reminder](#how-to-send-an-mfa-reminder).
+
+
+ If you invite users who are not yet a part of your Organization, they must enable MFA before joining.
+
+
+## How to send an MFA reminder
+
+1. Click **IAM** in the top right drop-down menu. The IAM dashboard displays.
+2. Go to the **Users** tab.
+3. Click > **Send MFA reminder** next to the name of a user that has MFA disabled.
+ The user will receive an email requesting that they enable MFA.
+
+## How to stop enforcing MFA
+
+
+ [MFA is enforced](#how-to-enforce-mfa) in your Scaleway Organization.
+
+
+1. Click the name of your Organization in the top right drop-down menu. The Organization dashboard displays.
+2. Go to the **Settings** tab.
+3. Scroll to the **Organization Multifactor Authentication (MFA)** section.
+4. Click **Stop enforcing MFA**.
+
+ Disabling this feature means that users in this Organization will no longer be required to have MFA set up on their accounts.
+
+5. Type **STOP**.
+6. Click **Stop enforcing MFA** to confirm.
+ The Owner of your Organization will receive an informative email saying MFA is no longer enforced.
diff --git a/pages/account/how-to/index.mdx b/pages/account/how-to/index.mdx
new file mode 100644
index 0000000000..7a0a6ef593
--- /dev/null
+++ b/pages/account/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Account - How Tos
+ description: Find step-by-step instructions for managing Scaleway accounts.
+content:
+ h1: Account - How Tos
+ paragraph: Find step-by-step instructions for managing Scaleway accounts.
+---
diff --git a/pages/account/how-to/log-in-to-the-console.mdx b/pages/account/how-to/log-in-to-the-console.mdx
new file mode 100644
index 0000000000..9c1b15e373
--- /dev/null
+++ b/pages/account/how-to/log-in-to-the-console.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: How to log in to the console
+ description: Steps to log in to the Scaleway console.
+content:
+ h1: How to log in to the console
+ paragraph: Steps to log in to the Scaleway console.
+tags: account login password access magic-link magic link SSO
+dates:
+ validation: 2024-12-05
+ posted: 2024-06-11
+categories:
+ - console
+---
+
+
+
+- A [Scaleway](https://www.scaleway.com/en/) account
+
+## Log in to the console with a Magic Link
+
+Instead of using your password, you can use a **Magic Link** to authenticate yourself when you log into the Scaleway console. This provides quick and secure access to your account without the hassle of remembering your password. When you choose to sign in with Magic Link, you receive a unique link sent directly to your email inbox which you can use one time only to authenticate your login. Afterward, it automatically becomes invalid.
+
+1. Open your web browser and go to the [Scaleway console](https://console.scaleway.com).
+2. Enter your email address in the form and click **Send a Magic Link**.
+ A magic link will be sent to your email inbox.
+3. Check your email inbox for an email with the subject **Scaleway - Passwordless Authentication** and open it.
+4. Click **Authenticate Myself** to connect to the Scaleway console.
+
+
+You will be redirected to and logged into your management console.
+
+A confirmation email is sent to your inbox, confirming that you have authenticated using the Magic Link.
+
+
+ The Magic Link becomes invalid as soon as you have used it. If you log out from the console and want to log in again without your password, you will need to request a new magic link by repeating the steps above.
+
+
+## Log in to the console with SSO
+
+Scaleway provides Single Sign-On (SSO) options for a seamless login experience. You can use your Google or Microsoft account to log in to the console. To do so, make sure the email address associated with your Scaleway account matches the email address of your Google or Microsoft account.
+
+1. Open your web browser and go to the [Scaleway console](https://console.scaleway.com).
+2. Click the **Log in with Google** , **Log in with Microsoft**, or **Log in with GitHub** button, depending on the account you want to use.
+3. You will be redirected to the respective login page of Google, Microsoft or GitHub.
+4. If multifactor authentication (MFA) is activated, enter the authentication code.
diff --git a/pages/account/how-to/manage-my-personal-data-gdpr.mdx b/pages/account/how-to/manage-my-personal-data-gdpr.mdx
new file mode 100644
index 0000000000..eab476e9c6
--- /dev/null
+++ b/pages/account/how-to/manage-my-personal-data-gdpr.mdx
@@ -0,0 +1,90 @@
+---
+meta:
+ title: How to manage your personal data
+ description: Manage personal data under GDPR regulations in Scaleway.
+content:
+ h1: How to manage your personal data
+ paragraph: Manage personal data under GDPR regulations in Scaleway.
+tags: personal-data manage privacy portability
+dates:
+ validation: 2024-07-29
+ posted: 2021-05-28
+categories:
+ - console
+---
+
+Scaleway makes it easy for you to manage your personal data and privacy via the console.
+
+
+
+- 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
+
+To access the privacy page, open the Organization drop-down menu in the top-right corner of the Scaleway console, and click **Privacy**.
+
+The **My Privacy** tab of your User Account dashboard displays.
+
+This page offers you a number of possibilities to manage your personal data and privacy.
+
+## How to access your personal data
+
+1. Scroll to the **Access your personal data** panel.
+2. Either:
+ - Check the first box to obtain information about your personal data processed by Scaleway, or
+ - Check the second box to obtain a copy of your personal data processed by Scaleway
+3. Check the box marked **I certify that I have the necessary rights to make this request**.
+4. Click **Send request**.
+
+## How to rectify your personal data
+
+1. Scroll to the **Rectify your personal data** panel.
+2. Click the **User Profile** link.
+3. In the **User Information** panel, click **Edit Profile**.
+4. Edit your first name, last name, email address, and preferred language as required.
+5. Click **Confirm changes**.
+
+## How to exercise your right to data portability
+
+In exercising your right to data portability, you have the right to have your personal data transmitted directly elsewhere, where technically feasible.
+
+1. Scroll to the **Exercise your right to data portability** panel.
+2. Check the box marked **I certify that I have the necessary rights to make this request**.
+3. Click **Send your request**.
+
+## How to request to limit the processing of your personal data
+
+1. Scroll to the **Manage the use of your personal data** panel.
+2. Under **Limit the processing of my personal data**, check the box that best describes the nature of your request.
+3. Use the text box to provide any further relevant information.
+4. Check the box marked **I certify that I have the necessary rights to make this request**.
+5. Click **Send request**.
+
+## How to erase your account and personal data
+
+If you do not want to use Scaleway services anymore, you can [close your account](/account/how-to/close-account/) and/or delete your personal data.
+
+### Closing your account or erasing your personal data: what’s the difference?
+
+
+
+### How to erase your personal data
+
+Erasing your account and personal data will permanently delete your Organization’s servers, resources, services, backups, and all data related to your account.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Ownership](/iam/concepts/#owner) of the Organization you intend to delete
+
+
+ Before requesting your personal data be deleted, ensure all your invoices are paid, and no resources are running. **Your request to erase your account will fail if you have unpaid consumption.**
+
+
+1. Click your Organization’s name at the top-right corner of the Scaleway console.
+2. Click **Profile** to access your User Account space.
+3. Click the **My privacy** tab.
+4. Scroll down to the **Erase my personal data** panel.
+5. Click the **Send request** button once you have read and agreed with the warning message.
+6. Type **Erase**, then click **Send request** to confirm your decision.
+
+A message appears to confirm that your account and personal data will be erased soon. The process can take up to 72 hours.
diff --git a/pages/account/how-to/open-a-support-ticket.mdx b/pages/account/how-to/open-a-support-ticket.mdx
new file mode 100644
index 0000000000..7ced6dd8a1
--- /dev/null
+++ b/pages/account/how-to/open-a-support-ticket.mdx
@@ -0,0 +1,77 @@
+---
+meta:
+ title: How to open and write a support ticket
+ description: Learn how to open and write an effective support ticket
+content:
+ h1: How to open and write a support ticket
+ paragraph: Learn how to open and write an effective support ticket
+tags: support help ticket support-ticket assistance
+dates:
+ validation: 2025-01-15
+ posted: 2021-06-22
+categories:
+ - console
+---
+
+Scaleway provides 24/7 basic technical support by ticket for free. You can contact our support team directly from the console. You can also [upgrade your support level](/account/how-to/configure-support-plans/) to benefit from phone support and a dedicated account manager.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+## Opening a support ticket
+
+1. Click **Help** at the right of the top menu. The [Help center](https://console.scaleway.com/support/tickets) displays.
+2. Click **Open a support ticket** under **Contact us**.
+3. Fill in the required information:
+
+- **Selected product**: choose the product related to your issue from the available options, such as Instances, GPU, or Elastic Metal.
+
+- **Related resource**: specify the exact resource affected by the issue, such as a specific Instance or volume.
+
+- **Severity**: select the severity level based on the impact of the issue (see table below).
+
+
+| **Severity** | **Description** | **Examples** |
+|--------------|---------------------------------------------------------------------------|--------------------------------------------------------|
+| **Low** | Non-urgent issues with minimal impact on your operations. | General questions about product configuration. |
+| **Medium** | Issues that affect your operations but have workarounds available. | Instance is slower than expected but still accessible. |
+| **High** | Critical issues that block your operations, with no available workaround. | API calls consistently fail with errors. |
+
+
+## Writing an effective subject and description
+
+Providing a clear subject and description will help us resolve your issue faster.
+
+- **Subject**: write a short and clear title that summarizes the issue (e.g., "Instance not starting after configuration update", "API call returns 500 error for all requests").
+
+- **Description**: write a detailed description to help us resolve the issue faster. Here are a few tips on how to write a ticket description:
+
+### Clearly describe the issue
+- **Context:** explain when and where the problem occurs.
+Example: “The issue occurs when attempting to start an Instance after applying a configuration update in the Scaleway console.”
+
+- **Expected behavior:** explain what you expected to happen.
+Example: “The instance should start within 2 minutes without errors.”
+
+- **Actual behavior:** describe what is happening instead.
+Example: “The Instance remains in "Starting" status for over 10 minutes and then switches to "Error".
+
+### Include relevant technical details
+
+- **Environment details:** mention your operating system, tools, or SDKs (e.g., “Ubuntu 20.04, Scaleway API v2, Python SDK.”)
+
+- **Logs or error messages:** include any logs, request/response payloads, or error codes (e.g., “API call GET /instances returns 500 Internal Server Error.”)
+
+### Add supporting files
+
+Attach screenshots (png, jpg), or files (pdf).
+Examples:
+- Screenshot of the Scaleway console
+- Screenshot of the network tab of your browser’s Developer Tools (right-click anywhere on the page and select **Inspect**. Go to the **Network tab** in the Developer Tools panel.)
+- Logs
+
+
+
+ If you have lost access to the Scaleway console and want to create a ticket, you must first [follow this procedure](/account/how-to/use-2fa/#how-to-regain-access-to-your-account) to regain access to your account.
+
diff --git a/pages/account/how-to/recover-a-lost-password.mdx b/pages/account/how-to/recover-a-lost-password.mdx
new file mode 100644
index 0000000000..3f116bade8
--- /dev/null
+++ b/pages/account/how-to/recover-a-lost-password.mdx
@@ -0,0 +1,70 @@
+---
+meta:
+ title: How to recover a lost password
+ description: Recover a lost password for your Scaleway account.
+content:
+ h1: How to recover a lost password
+ paragraph: Recover a lost password for your Scaleway account.
+tags: account password recovery login
+dates:
+ validation: 2024-10-01
+ posted: 2021-06-11
+categories:
+ - console
+---
+
+If you forget or lose the password to your [Scaleway account](https://console.scaleway.com), there are several methods you can use to regain access.
+
+
+
+- A [Scaleway](https://www.scaleway.com/en/) account
+
+## Log in without a password using a magic link
+
+The [magic link](/account/how-to/log-in-to-the-console/) allows you to access your account without a password, using multifactor authentication.
+
+Click **Send magic link** on the Login page of the Scaleway console.
+
+A secret link is sent to your email. You can access your account by clicking on the link.
+
+## Reset your password using email validation
+
+If you forget or lose your password, you can request to reset it.
+
+1. From the [Scaleway console login page](https://account.scaleway.com/), Click **Log in with password**.
+1. Click **Forgot your password?**, or access the [lost password](https://console.scaleway.com/forgot-password/) page.
+2. Enter your email address and click **Reset password**. A password reset link is sent to your email address.
+3. Click the link in the email address to reset your password.
+4. Enter your new password and click **Reset password** to set the new password for your account. You are redirected to the Login page.
+5. Log in to the console with your email address and your new password.
+
+## Recover your password if you lost access to your email account
+
+If you lose access to your email account, you will not be able to reset the password directly from the Scaleway console.
+
+If you cannot access your email account, you must send us a request to update your contact information with the following pieces of identification:
+
+* Email address
+* Postal address
+* If your account is:
+ - an individual account, a document proving your identity (passport or local ID card)
+ - a corporate account, a copy of a business registration certificate,
+ and a certified translation in either English or French if the document was issued in another language
+* A phone number to contact you
+* Copy of your last Scaleway invoice or the amount charged if you do not have a copy
+* A card or bank statement showing your Scaleway invoice debit
+
+Once you have gathered all the required documents, send the request by email to: [document@scaleway.com](mailto:document@scaleway.com).
+
+We will update the email address on receipt of the application, subject to validation.
+
+Once your email address has been updated, you can use the [lost password form](https://console.scaleway.com/forgot-password) to receive the recovery codes for your account.
+
+## Password security guidelines
+
+Besides the usual guidelines you should follow to create a complex password (must contain UPPERCASE and lowercase letters, symbols (`@`, `$`, `&`, …) and numbers), some basic rules exist to keep your password and your account safe:
+
+ - Never give your password to anyone. Especially not via email, IRC, Slack, WhatsApp, or any messaging system. Scaleway employees will never ask you for your password.
+ - Use [multifactor authentication](https://console.scaleway.com/account/profile) to add an extra layer of security.
+ - Do not write down your password.
+ - Always log out of your account at the end of each session, or if you are away from your computer.
diff --git a/pages/account/how-to/report-abuse.mdx b/pages/account/how-to/report-abuse.mdx
new file mode 100644
index 0000000000..c6bc4587e2
--- /dev/null
+++ b/pages/account/how-to/report-abuse.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to report abuse
+ description: Report abuse incidents related to Scaleway accounts.
+content:
+ h1: How to report abuse
+ paragraph: Report abuse incidents related to Scaleway accounts.
+tags: report incident abuse
+dates:
+ validation: 2025-01-07
+ posted: 2024-02-19
+categories:
+ - account
+---
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+## How to report an abuse
+
+1. Go to the [Report Abuse](https://console.scaleway.com/support/abuses/create/) page. A form displays.
+2. Enter the IP address, domain name, or URL of the source you want to report.
+3. Enter the date of publication of the illegal content or the start date of the illegal behavior.
+4. Enter the time of the publication of the illegal content or the time the illegal behavior started.
+5. Select the type of abuse you wish to report in the drop-down box
+
+ The different types of content or illegal behavior that can be reported are described in Scaleway’s [Abuse notice](https://www.scaleway.com/en/abuse-notice/).
+
+
+ Falsely reporting content or activity as illegal only to obtain its removal or to stop its distribution, is punishable by one year imprisonment and a €15,000 fine.
+
+6. Enter your email address and name if required.
+7. Describe what you have observed in as much detail as possible. Provide information such as logs, time zones, headers, the precise location and, if applicable, the email addresses to which the content is made accessible.
+
+ This description will be directly forwarded to our customer. Therefore, refrain from including any confidential or personal information which you do not want them to have access to.
+ Scaleway denies all responsibility for the use that could be made by third parties of any information that you provide in this field.
+
+8. Check the box confirming that you are submitting this report in good faith.
+9. Once you have entered the information mentioned above, check the CAPTCHA form and click **Submit abuse report**.
+
+ If you encounter difficulties submitting an abuse report, contact [Scaleway’s abuse team](https://www.scaleway.com/fr/contact-trust-et-safety/).
+
+
+## How is my report processed?
+
+Once you have submitted the [report abuse form](https://abuse.scaleway.com/), you will receive an email confirming its reception from Scaleway’s abuse team.
+
+Scaleway’s abuse team will verify the exactness of the report, and that all the necessary information has been provided for the report to be processed. They will also verify whether the report indeed relates to explicitly illegal behavior or content about French regulations and the evidence and information you have provided. If your report meets the above criteria, it will be validated by the abuse team and sent to Scaleway’s customer so that the necessary corrective measures can be taken.
+
+1. You will receive updates regarding the resolution of the abuse via the email address provided in the form if you provided one.
+
+ Should Scaleway’s customer not respond, or should the transferred report not be processed correctly, appropriate measures will be taken by Scaleway. These measures may vary from a simple warning to termination of all services of said customer.
+
+2. If your report is rejected, you will be informed of the reasons why by email.
+
+ * Do not repeatedly report the same practices or content, as it forces the abuse team to carry out unnecessary actions and negatively impacts their work.
+ * Remain courteous when communicating with the abuse team. Abuse reports shall not contain any offensive, vulgar, or threatening language.
+ * If you consider that your report has been unduly rejected, you can contact Scaleway’s abuse team.
+
diff --git a/pages/account/how-to/resolve-abuse.mdx b/pages/account/how-to/resolve-abuse.mdx
new file mode 100644
index 0000000000..a7da0aeb50
--- /dev/null
+++ b/pages/account/how-to/resolve-abuse.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: How to resolve Scaleway abuse tickets and cases
+ description: Take actions to resolve abuse issues in Scaleway.
+content:
+ h1: How to resolve Scaleway abuse tickets and cases
+ paragraph: Take actions to resolve abuse issues in Scaleway.
+tags: resolve abuse complaint ticket scaleway
+dates:
+ validation: 2024-08-28
+ posted: 2024-02-19
+categories:
+ - account
+---
+
+Abuses are complaints regarding the use of Scaleway services for illegal behavior or hosting of illegal content. Abuse reports for the same issue on the same resource within a given time frame are grouped by case.
+
+If you have been the subject of an abuse report, you are responsible for taking the appropriate security measures to solve the case. You must also prevent any further abuse of your resources to avoid your services being locked by Scaleway.
+
+However, Scaleway reserves the right to immediately suspend the infringing services if it is deemed necessary, and proportionate to keep Scaleway’s network safe or to abide by legal requirements.
+
+If you encounter any issue with the resolution of an abuse, ensure that you contact the abuse team by opening a [support ticket](https://console.scaleway.com/support/tickets/create) directly from your console.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+1. Click **Abuse** in the bottom left corner of the Scaleway console. A list of your open cases displays. You can also view the closed cases by clicking on **Closed cases**.
+2. Click the **case ID** to view the specifics of the complaint.
+3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue.
+
+ If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/).
+
+ If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly.
+ * For other types of abuse, here are some suggestions to help you to correct them:
+ * Backup all your server data
+ * Check for recent file changes
+ * Check log files on your server
+ * Check your PHP and CGI files for any backdoors
+ * Check if any software you use is vulnerable, and update them
+ * Reinstall your server after backup
+ * Change passwords of your server
+ * Backup your website and your email data
+ * Check for recent file changes, and security holes in common CMS you may use (Joomla, SPIP, WordPress…)
+ * Check the version in some software you may use on your computer (email client, FTP client)
+ * Change your FTP and email passwords
+ If you do not know how to solve the problem, you can contact our [outsourcing partners](https://www.scaleway.com/en/dedibox/outsourcing/) or reach out to Scaleway’s abuse team by opening a ticket directly from your Scaleway console account.
+
+4. The case will be closed at the end of its lifetime by Scaleway’s abuse team, and so will the abuse tickets forming the case.
+ If you receive more abuse reports on the same resource within the case lifetime, it means that you did not take the appropriate measures to prevent further abuse from happening.
+ Therefore, we recommend you take additional actions and contact our support team if you need assistance. Failure to take appropriate measures to solve the case may result in the locking of your service as per our [Terms of Services](https://www.scaleway.com/en/contracts/) and the legal framework in force.
+
+In specific instances, the case will be closed automatically:
+* abuse reports submitted by Scaleway’s abuse partners may be closed automatically after the automated locking of your services, if several complaints were received within the same case, or if Scaleway considers that the type of abuse reported requires immediate locking of your services.
+* cases regarding security holes will be closed automatically. Refer to the description of the abuse to find more details on patches and updates available.
+
+
+Refer to our [abuse notice](https://www.scaleway.com/en/abuse-notice/) for further information about Scaleway’s abuse policy.
+
\ No newline at end of file
diff --git a/pages/account/how-to/switch-account-to-corporate.mdx b/pages/account/how-to/switch-account-to-corporate.mdx
new file mode 100644
index 0000000000..d59882c37b
--- /dev/null
+++ b/pages/account/how-to/switch-account-to-corporate.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to switch from a personal to a corporate account
+ description: Convert your Scaleway account to a corporate account.
+content:
+ h1: How to switch from a personal to a corporate account
+ paragraph: Convert your Scaleway account to a corporate account.
+tags: account personal corporate business
+dates:
+ validation: 2024-09-23
+ posted: 2023-09-03
+categories:
+ - console
+---
+
+The [Scaleway console](https://console.scaleway.com) allows you to choose between two types of accounts, Personal and Corporate. All users are given the possibility to select one or the other option when first signing up for a Scaleway account. If you signed up for a personal account and need to convert to a corporate one, follow these instructions.
+
+
+ Switching to a corporate account is permanent. You will not be able to switch back to a personal account once the conversion to corporate is completed.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+1. From your [Organization dashboard](https://console.scaleway.com/organization), click Billing in the top right drop-down menu. The **Billing** dashboard displays.
+2. Click the **Payment and billing tab**.
+3. Scroll down to billing information, then click **Edit**. A pop-up with your billing information displays.
+
+4. Check the box at the top to confirm you wish to have a corporate account. A new form displays.
+
+5. Enter your company's information, including name, address, and valid VAT number.
+
+ European B2B customers are exempted from VAT, as long as they provide a registered VAT number. Learn more about our [tax policy](/faq/billing/#do-the-prices-shown-on-the-website-include-eu-vat).
+
+6. Click **Confirm changes** to permanently convert your account from personal to corporate.
\ No newline at end of file
diff --git a/pages/account/how-to/use-2fa.mdx b/pages/account/how-to/use-2fa.mdx
new file mode 100644
index 0000000000..85696dddf4
--- /dev/null
+++ b/pages/account/how-to/use-2fa.mdx
@@ -0,0 +1,103 @@
+---
+meta:
+ title: How to use Multifactor Authentication (MFA)
+ description: Enable and use Two-Factor Authentication (2FA) in Scaleway.
+content:
+ h1: How to use Multifactor Authentication (MFA)
+ paragraph: Enable and use Two-Factor Authentication (2FA) in Scaleway.
+tags: authentication 2FA two-factor two multi factor security google authenticator authenticator
+dates:
+ validation: 2025-01-15
+ posted: 2022-01-14
+categories:
+ - console
+---
+
+You can enable multifactor authentication on your Scaleway account for heightened security. Once enabled, an additional security code generated by your phone is required to access your account.
+
+Multifactor authentication provides extra layers of security. In addition to your password (the first factor), other factors (such as an MFA app) are required to gain access to your account. Even in the event of a leaked password, your account is protected.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+## How to download an MFA app
+
+To use [multifactor authentication](/account/concepts/#multifactor-authentication-mfa) on your account, you first need to download an MFA app onto your smartphone. Once configured, MFA apps display a constantly rotating set of codes to use with your different accounts when you are prompted for one during login. Popular MFA apps include:
+- [Authy](https://authy.com/download/)
+- [FreeOTP](https://freeotp.github.io/)
+- [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en&gl=US)
+
+Download the app of your choice and install it onto your smartphone.
+
+## How to enable MFA
+
+1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**.
+
+2. Scroll to the bottom of your profile page, and click **Enable MFA**. A pop-up displays.
+
+3. Enter the code shown on the pop-up into your MFA app, or scan the QR code into your app.
+ Your app sets up MFA for your Scaleway account and displays a 6-digit code.
+4. Enter the 6-digit code given by your app into the pop-up box, and click **Submit**. A pop-up displays:
+
+5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way you can regain access to your account without your MFA app.
+
+MFA is now enabled. Next time you log in to your Scaleway account, you will be prompted for an MFA code. Use your MFA app to get the code and enter it in the Scaleway console.
+
+## How to update MFA
+
+If you no longer have access to the device in which you set up your MFA, you can update your MFA information and set it up via the Scaleway console.
+
+
+
+- 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
+- [Enabled MFA](#how-to-enable-mfa) on your account
+
+
+ If you have lost access to your account and are not able to log in, follow the [Cannot log into my account](/account/troubleshooting/cannot-log-into-my-account/) troubleshooting procedure.
+
+
+1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**.
+2. Scroll to the bottom of your profile page, and click **Update MFA**. A pop-up displays.
+3. Enter the code shown on the pop-up into your MFA app, or scan the QR code into your app.
+ Your app sets up MFA for your Scaleway account and displays a 6-digit code.
+4. Enter the 6-digit code given by your app into the pop-up box, and click **Submit**. A pop-up displays.
+5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way you can regain access to your account without your MFA app.
+
+## How to disable MFA
+
+
+ You cannot disable MFA if you are a member of one or more Organizations where MFA is enforced. If you wish to disable MFA, you must first leave these Organizations. If you do not know which of your Organizations enforce MFA, follow the procedure below until step 2. The Organizations will be listed in the **Disable MFA** pop-up.
+
+
+1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**.
+2. Scroll to the bottom of the page, and click **Disable MFA**. A pop-up displays.
+
+3. Type **DISABLE** in the box to confirm, and click **Disable**.
+
+## How to regain access to your account
+
+### If you lose your MFA device
+
+If you lose your MFA device, you can use the backup codes that were generated when you activated MFA to regain access.
+
+When you log into your account, you are prompted for an MFA code:
+
+
+
+Enter one of your backup codes (instead of a code generated by your MFA device in real-time) and click **Send token**. You are logged into your account, and can disable MFA if you wish by [following the instructions above](#how-to-disable-mfa).
+
+### If you lose your MFA device and backup codes
+
+If you lose both your MFA device and backup codes, it is more difficult to regain access to your account. You will need to go through a manual identity verification process.
+
+The only way to regain access to your account is to contact our support team with the following information:
+ * Email address
+ * Postal address
+ * Two different documents proving your identity (passport or local ID card for individual accounts + certificate of incorporation for companies)
+ * A contact phone number
+ * A copy of your last Scaleway invoice, or details about the amount charged if you do not have a copy
+ * A card or bank statement showing your Scaleway invoice debit
+
+Once you have collected all this information, send it to [document@scaleway.com](mailto:document@scaleway.com).
\ No newline at end of file
diff --git a/pages/account/how-to/use-the-search-bar.mdx b/pages/account/how-to/use-the-search-bar.mdx
new file mode 100644
index 0000000000..0b88ab6bdd
--- /dev/null
+++ b/pages/account/how-to/use-the-search-bar.mdx
@@ -0,0 +1,61 @@
+---
+meta:
+ title: How to use the search bar
+ description: Efficiently search for features and settings in the Scaleway console.
+content:
+ h1: How to use the search bar
+ paragraph: Efficiently search for features and settings in the Scaleway console.
+tags: account search-bar resource
+dates:
+ validation: 2025-01-03
+ posted: 2024-03-14
+categories:
+ - account
+---
+
+The **search bar** functionality of the Scaleway console allows you to quickly find Scaleway resources and products.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+1. Log into the [Scaleway console](https://console.scaleway.com).
+
+2. Navigate to the search bar located next to the Organization dashboard menu.
+
+
+ You can also access the search bar by typing `Cmd + K` on macOS and `Ctrl + K` on Linux or Windows.
+
+
+3. Click in the search bar and enter the keyword you are looking for. The keyword can be the name or the ID of a resource, or the name of a Scaleway product.
+
+
+ As this is an early version (v2) of the search bar, results are limited. This version of the search bar may not yet include all resources and a "no result" message may appear despite the existence of the resource.
+
+
+#### Resources available
+
+In addition to the products present in the Scaleway catalog, you can look for the following resources using the search bar:
+
+- Instances
+- Instance volumes
+- Instance images
+- Elastic Metal servers
+- Apple Silicon servers
+- Kubernetes clusters
+- Kubernetes nodes
+- Kubernetes pools
+- Serverless Functions
+- Serverless Containers
+- Block Storage volumes
+- Block Storage snapshots
+- PostgreSQL snapshots
+- PostgreSQL backups
+- Redis™ Database Instances
+- Redis™ clusters
+- VPC
+- VPC Private Networks
+- Public Gateways
+- Load Balancers
+- Web Hosting
+- Secrets (Secret Manager)
diff --git a/pages/account/how-to/verify-identity.mdx b/pages/account/how-to/verify-identity.mdx
new file mode 100644
index 0000000000..680755d552
--- /dev/null
+++ b/pages/account/how-to/verify-identity.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: How to verify your identity
+ description: Verify your identity for secure Scaleway account access.
+content:
+ h1: How to verify your identity
+ paragraph: Verify your identity for secure Scaleway account access.
+tags: verification identify account id id-verification
+dates:
+ validation: 2024-07-29
+ posted: 2021-06-11
+categories:
+ - console
+---
+
+Verifying your identity allows you to [unlock resource quotas](/organizations-and-projects/additional-content/organization-quotas/) and fully benefit from the console's features and products.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- A valid payment method linked to your account
+
+1. Click **Add ID document** under **(Optional) Verify my ID document** on the [Organization dashboard](https://console.scaleway.com/organization/). You can also verify your identity from the [Settings tab](https://console.scaleway.com/organization/settings) of your Organization dashboard.
+
+2. Click **Start** to proceed.
+
+
+ Use a valid government-issued photo ID. A residence permit is also considered a valid identity card.
+ These are some examples of documents **not accepted** by the ID verification tool:
+ - Birth certificate
+ - Company ID
+ - Credit card
+ - International driving license
+ - Student ID (except for Poland)
+ - Visa (except for student/work visa issued by the U.S. and China).
+
+4. Select between taking a photo of your ID with your PC or mobile, and follow the next three steps to submit proof of your identity.
+
+5. Click **Start** to center your ID and take a photo.
+
+ The **console.scaleway.com** website will request access to your camera. If you wish to proceed, allow your browser to use the camera.
+
+6. Check the photo, as instructed, and click **Confirm** if you can:
+ - Read the details
+ - See the whole ID
+ The facial verification steps begin.
+7. Click **Start** to proceed.
+8. Frame your face in the designated areas as requested by the validation process.
+
+ Once the verification is complete, a confirmation message appears in the Organization dashboard.
diff --git a/pages/account/index.mdx b/pages/account/index.mdx
new file mode 100644
index 0000000000..4701ee132d
--- /dev/null
+++ b/pages/account/index.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: Account Documentation
+ description: Navigate Scaleway account management features.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/account/quickstart.mdx b/pages/account/quickstart.mdx
new file mode 100644
index 0000000000..4fe47a73f1
--- /dev/null
+++ b/pages/account/quickstart.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: Account - Quickstart
+ description: Quickly get started with managing Scaleway accounts.
+content:
+ h1: Account - Quickstart
+ paragraph: Quickly get started with managing Scaleway accounts.
+tags: create-account delete-account create-resources create corporate
+dates:
+ validation: 2024-07-29
+ posted: 2021-05-26
+categories:
+ - console
+---
+
+Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Creating your Scaleway account gives you access to the [Scaleway console](/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and you can deploy our products and services with ease.
+
+## Console overview
+Follow this guided tour to discover how to navigate the console.
+
+
+## How to create an account
+
+
+
+## How to create resources
+
+Once you have validated your payment method, you can start ordering resources like Instances, Kubernetes Kapsule, Object Storage and more. Find out more about [how to add resources to your Projects](/organizations-and-projects/how-to/add-resources-project/).
+
+## How to close an account
+
+Every account has an associated Organization, which in turn has an Owner. When you create your account, you are designated as the Owner of the Organization associated with your account.
+
+When you [close your account](/account/how-to/close-account/), you delete all its resources and backups. Any guests who have joined your Organization will lose access because your Organization will no longer exist.
+
+
+ There is a delay of up to 10 days between the time your account is closed and the time the system deletes your resources. It is recommended to manually delete all your Organization's resources before closing your account. To reopen your account, [contact support](https://console.scaleway.com/support).
+
+
+
diff --git a/pages/account/reference-content/index.mdx b/pages/account/reference-content/index.mdx
new file mode 100644
index 0000000000..ae23906549
--- /dev/null
+++ b/pages/account/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Account - Additional content
+ description: Browse through Scaleway account reference content.
+content:
+ h1: Account - Additional content
+ paragraph: Browse through Scaleway account reference content.
+---
diff --git a/pages/account/reference-content/products-availability.mdx b/pages/account/reference-content/products-availability.mdx
new file mode 100644
index 0000000000..ac419551db
--- /dev/null
+++ b/pages/account/reference-content/products-availability.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: Scaleway account - Product availability guide
+ description: Check availability details of Scaleway products.
+content:
+ h1: Product availability guide
+ paragraph: Check availability details of Scaleway products.
+tags: availability region zone availability-zone
+dates:
+ validation: 2024-11-25
+ posted: 2023-01-05
+categories:
+ - console
+---
+
+Scaleway products are available in multiple regions and locations worldwide. This page provides an overview of the availability of all Scaleway products in our regions and Availability Zones.
+
+* A **region** is a separate geographical area (Paris, Amsterdam, Warsaw). Each region contains one or multiple Availability Zones.
+* **Availability Zones** are isolated locations in a specific region. Each Availability Zone provides its own services and infrastructure. Our current Availability Zones are:
+ * Paris: PAR1, PAR2, PAR3
+ * Amsterdam: AMS1, AMS2, AMS3
+ * Warsaw: WAW1, WAW2, WAW3
+
+| Product Category | Product | Paris region | Amsterdam region | Warsaw region |
+|---------------------------|---------------------------------------|------------------------|-------------------------|------------------------|
+| **Compute** | Instances | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 |
+| | GPU H100-X-80G | PAR2 | Not available yet | WAW2 |
+| | GPU L40S-X-48G | PAR2 | Not available yet | Not available yet |
+| | GPU L4-X-24G | PAR2 | Not available yet | WAW2 |
+| | GPU RENDER-S | PAR1 | Not available yet | Not available yet |
+| | GPU 3070-S | PAR2 | Not available yet | Not available yet |
+| **Bare Metal** | Elastic Metal | PAR1, PAR2 | AMS1, AMS2 | WAW2, WAW3 |
+| | Apple Silicon | PAR1, PAR3 | Not available yet | Not available yet |
+| | Dedibox | DC2, DC3, DC5 | AMS1 | Not available yet |
+| **Containers** | Kubernetes | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 |
+| | Container Registry | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| **Storage** | Object Storage Multi-AZ + One Zone IA | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Object Storage Glacier | Paris* | Not available yet | Not available yet |
+| | Block Storage | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 |
+| **Managed Databases** | PostgreSQL - MySQL | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Redis™ | PAR1, PAR2 | AMS1, AMS2 | WAW1 |
+| **Network** | Private Networks | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Public Gateway | PAR1, PAR2 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 |
+| | Load Balancer | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 |
+| | Edge Services | Global | Global | Global |
+| | Domains and DNS | Automatically assigned | Automatically assigned | Automatically assigned |
+| **Serverless** | Containers | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Functions | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Jobs | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | SQL Databases | Across Paris region | Not available yet | Not available yet |
+| | NATS | Across Paris region | Across Amsterdam region | Not available yet |
+| | Queues | Across Paris region | Across Amsterdam region | Not available yet |
+| | Topics and Events | Across Paris region | Across Amsterdam region | Not available yet |
+| **Managed Services** | Web Hosting | Across Paris region | Not available yet | Not available yet |
+| | IoT Hub | Across Paris region | Not available yet | Not available yet |
+| | Transactional Email | Automatically assigned | Automatically assigned | Automatically assigned |
+| **Observability** | Cockpit | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| **Security and Identity** | Secret Manager | Across Paris region | Across Amsterdam region | Across Warsaw region |
+| | Audit Trail | Across Paris region | Across Amsterdam region | Not available yet |
+
+
+* \* All Glacier data is stored in [Paris DC4](/faq/objectstorage/#why-are-glacier-objects-stored-in-paris-dc4-is-it-accessible-from-buckets-in-all-locations).
diff --git a/pages/account/reference-content/scaleway-network-information.mdx b/pages/account/reference-content/scaleway-network-information.mdx
new file mode 100644
index 0000000000..3c79ca6647
--- /dev/null
+++ b/pages/account/reference-content/scaleway-network-information.mdx
@@ -0,0 +1,111 @@
+---
+meta:
+ title: Scaleway network information
+ description: Access detailed network information for Scaleway services.
+content:
+ h1: Scaleway network information
+ paragraph: Access detailed network information for Scaleway services.
+tags: scaleway ip-range ntp rpn vpn dns
+dates:
+ validation: 2024-10-22
+ posted: 2021-08-20
+categories:
+ - console
+---
+
+This page serves as a resourceful hub for information related to the Scaleway network infrastructure.
+It provides a detailed overview of the IP ranges used by Scaleway, details about the DNS resolver IPs in each data center, and further information regarding various other network-associated services.
+
+## IP ranges used by Scaleway
+
+Currently, we use the following IP ranges:
+
+### IPv4
+* `62.210.0.0/16`
+* `195.154.0.0/16`
+* `212.129.0.0/18`
+* `62.4.0.0/19`
+* `212.83.128.0/19`
+* `212.83.160.0/19`
+* `212.47.224.0/19`
+* `163.172.0.0/16`
+* `51.15.0.0/16`
+* `151.115.0.0/16`
+* `51.158.0.0/15`
+
+### IPv6
+* `2001:bc8::/32`
+
+## DNS cache servers
+
+DNS cache servers are available in every data center. The IPs for each DC are:
+
+### AMS1
+IPv4:
+* `51.158.139.28`
+* `51.158.139.25`
+
+IPv6:
+* `2001:bc8:1408:1::f`
+* `2001:bc8:1408:1::c`
+
+### DC2
+IPv4:
+* `51.159.69.156`
+* `51.159.69.162`
+
+IPv6:
+* `2001:bc8:408:1::c`
+* `2001:bc8:408:1::12`
+
+### DC3
+IPv4:
+* `51.159.69.156`
+* `51.159.69.162`
+
+IPv6:
+* `2001:bc8:408:1::c`
+* `2001:bc8:408:1::12`
+
+### DC5
+IPv4:
+* `51.159.47.28`
+* `51.159.47.26`
+
+IPv6:
+* `2001:bc8:1008:1::16`
+* `2001:bc8:1008:1::14`
+
+
+ The previously used DNS caches below are deprecated and should no longer be used:
+ * IPv4: `62.210.16.6`
+ * IPv6: `2001:bc8:401::3`
+ * IPv4: `62.210.16.7`
+ * IPv6: `2001:bc8:1::16`
+
+
+## Additional services
+
+### NTP server
+
+Generic: `ntp.online.net`
+
+- Primary NTP server: `51.159.47.151` (`ntp1.online.net`)
+- Seconday NTP server: `51.158.192.3` (`ntp2.online.net`)
+
+### Rdate server
+
+Generic: `rdate.dedibox.com`
+
+- Primary rdate server: `51.159.47.151` (`ntp1.online.net`)
+- Seconday rdate server: `51.158.192.3` (`ntp2.online.net`)
+
+Backup server: `dedibackup.dedibox.fr`
+
+### RPN VPN access server
+
+IP: `62.210.16.24` (`vpn-rpn-dc3.online.net`)
+
+### Monitoring of Dedibox servers
+
+Our monitoring servers are located in the IP subnet `62.210.16.0/24`.
\ No newline at end of file
diff --git a/pages/account/troubleshooting/assets/scaleway-forgotten-password-screen.webp b/pages/account/troubleshooting/assets/scaleway-forgotten-password-screen.webp
new file mode 100644
index 0000000000..b7426194d7
Binary files /dev/null and b/pages/account/troubleshooting/assets/scaleway-forgotten-password-screen.webp differ
diff --git a/pages/account/troubleshooting/assets/scaleway-password-reset.webp b/pages/account/troubleshooting/assets/scaleway-password-reset.webp
new file mode 100644
index 0000000000..a715c76c9a
Binary files /dev/null and b/pages/account/troubleshooting/assets/scaleway-password-reset.webp differ
diff --git a/pages/account/troubleshooting/assets/scaleway-unrecognized-ip.webp b/pages/account/troubleshooting/assets/scaleway-unrecognized-ip.webp
new file mode 100644
index 0000000000..b0f7b61abb
Binary files /dev/null and b/pages/account/troubleshooting/assets/scaleway-unrecognized-ip.webp differ
diff --git a/pages/account/troubleshooting/cannot-erase-account.mdx b/pages/account/troubleshooting/cannot-erase-account.mdx
new file mode 100644
index 0000000000..4a8e93162f
--- /dev/null
+++ b/pages/account/troubleshooting/cannot-erase-account.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: I cannot close my account and erase personal data
+ description: Resolve issues encountered when deleting Scaleway accounts.
+content:
+ h1: I cannot erase my account and personal data
+ paragraph: Resolve issues encountered when deleting Scaleway accounts.
+tags: account close delete deactivate close-account
+dates:
+ validation: 2024-27-11
+ posted: 2024-03-28
+categories:
+ - console
+---
+
+## My request to close my account and erase personal data has failed
+
+### Problem
+When you click the **Send request** button, an error message appears. This message says that you still have active resources.
+
+### Cause
+You have active resources, preventing us from proceeding with your request.
+
+### Solution
+You can check all your active resources from your [Organization dashboard](https://console.scaleway.com/organization). If one or more resources are listed, they are active. You need to delete all of them manually. In this situation, you must wait for the current month's invoice to be paid before sending another request to erase your account.
+
+
+### Problem
+I received an email explaining that my request to erase my account and personal data had failed.
+
+### Cause
+You may have unpaid consumption, preventing us from proceeding with your request.
+
+### Solution
+You can check your consumption from your [Billing space](https://console.scaleway.com/billing). All invoices must be marked as paid, and your current consumption must be zero. Once these criteria are met, you can send another request to delete your account and erase personal data.
diff --git a/pages/account/troubleshooting/cannot-log-into-my-account.mdx b/pages/account/troubleshooting/cannot-log-into-my-account.mdx
new file mode 100644
index 0000000000..1cd24ae670
--- /dev/null
+++ b/pages/account/troubleshooting/cannot-log-into-my-account.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: I cannot log into my account
+ description: Fix issues preventing login to Scaleway accounts.
+content:
+ h1: I cannot log into my account
+ paragraph: Fix issues preventing login to Scaleway accounts.
+tags: login unrecognized-ip password 2fa
+dates:
+ validation: 2024-11-27
+ posted: 2022-10-19
+categories:
+ - console
+---
+
+If you encounter issues when connecting to your Scaleway account, there are several procedures you can follow to make sure you can log in securely.
+
+## Unrecognized IP address error
+When logging into your Scaleway account, you may encounter the following message:
+
+
+
+This means you tried to log into your account from an unknown [IP address](/public-gateways/concepts/#ip-address). You may be logging in from a new device or location. As a security measure, we require you to use a [magic link](/account/concepts/#magic-link) to complete authentication.
+
+1. Check your inbox for the latest email sent by the Scaleway team.
+2. Click the **Authenticate myself** button in the email.
+
+You are redirected to the Scaleway console and safely logged into your Scaleway account.
+
+
+If [MFA](/account/concepts/#multifactor-authentication-mfa) is enforced for your account, you must also enter the security code received by SMS or provided by an authenticator smartphone app.
+
+
+
+## I have forgotten my password
+
+If you forgot or lost your password, you need to reset it. There are several methods to recover it:
+ - [Passwordless authentication using a Magic Link](/account/how-to/recover-a-lost-password/#log-in-without-a-password-using-a-magic-link)
+ - [Password reset using email validation](/account/how-to/recover-a-lost-password/#reset-your-password-using-email-validation)
+ - [Password recovery in case of lost email account](/account/how-to/recover-a-lost-password/#recover-your-password-if-you-lost-access-to-your-email-account)
+
+## I have lost my 2FA device
+
+Refer to the [How to use two-factor authentication (MFA)](/account/how-to/use-2fa/) page to find the instructions to recover access to your MFA device.
+
+Remember that if you lose both your MFA device and backup codes, you will need to gather all the following information:
+
+* Email address
+* Postal address
+* If your account is:
+ - an individual account, a document proving your identity (passport or local ID card)
+ - a corporate account, a copy of a business registration certificate,
+ and a certified translation in either English or French if the document was issued in another language
+* A phone number to contact you
+* Copy of your last Scaleway invoice or the amount charged if you do not have a copy
+* A card or bank statement showing your Scaleway invoice debit
+
+Once you have gathered all the required documents, the request has to be sent by email to: [document@scaleway.com](mailto:document@scaleway.com).
+
+## SSO authentication is not working
+
+If the email address of your Google, Microsoft, or GitHub account does not match the email address associated with your Scaleway account, you will not be able to log in using SSO. Make sure both email addresses are the same.
\ No newline at end of file
diff --git a/pages/account/troubleshooting/index.mdx b/pages/account/troubleshooting/index.mdx
new file mode 100644
index 0000000000..fc93af869c
--- /dev/null
+++ b/pages/account/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Account Troubleshooting
+ description: Troubleshoot common issues with Scaleway accounts.
+content:
+ h1: Account Troubleshooting
+ paragraph: Troubleshoot common issues with Scaleway accounts.
+---
diff --git a/pages/account/troubleshooting/protecting-yourself-fraud-phishing.mdx b/pages/account/troubleshooting/protecting-yourself-fraud-phishing.mdx
new file mode 100644
index 0000000000..a051786819
--- /dev/null
+++ b/pages/account/troubleshooting/protecting-yourself-fraud-phishing.mdx
@@ -0,0 +1,70 @@
+---
+meta:
+ title: Protecting yourself against phishing and fraud
+ description: Protect yourself from fraud and phishing in Scaleway.
+content:
+ h1: Protecting yourself against phishing and fraud
+ paragraph: Protect yourself from fraud and phishing in Scaleway.
+tags: login unrecognized-ip phising fraud
+dates:
+ validation: 2024-12-05
+ posted: 2024-05-22
+categories:
+ - console
+---
+
+Phishing and fraud attempts are a significant threat to online security. This guide provides essential steps to safeguard your Scaleway account from such attacks.
+
+## Recognizing phishing attempts
+
+Phishing is a method where attackers trick you into providing personal information by pretending to be a trusted entity. These attempts can come via email, phone calls, or fake websites.
+
+### Signs of phishing
+
+- **Urgency or threats:** Messages that create a sense of urgency, warning of account closure or legal action.
+- **Suspicious links:** Emails containing links that do not match the legitimate Scaleway URL (e.g., slight misspellings).
+- **Attachments:** Unexpected attachments that may contain malware.
+- **Unusual sender:** Emails from unrecognized or suspicious email addresses.
+
+### Actions to take
+
+- **Verify the sender:** Always check the email address of the sender to ensure it is from an official Scaleway domain.
+- **Hover over links:** Hover your mouse over links to see the actual URL before clicking.
+- **Do not share sensitive information:** Never provide your passwords or personal information via email.
+- **Use official channels:** Access your account by navigating directly to the [Scaleway website](https://www.scaleway.com/) rather than clicking on email links.
+
+## Securing your account
+
+### Multi-factor authentication (MFA)
+
+Enable [Multi-factor authentication (MFA) on your Scaleway account](/account/how-to/use-2fa/#how-to-update-mfa) to add an extra layer of security. MFA requires a second form of verification beyond just a password.
+
+### Strong password practices
+
+- **Create a strong password:** Use a combination of letters, numbers, and special characters. Avoid easily guessable information like birthdays.
+- **Unique passwords:** Use different passwords for different accounts.
+- **Password managers:** Use a password manager to store and generate strong passwords.
+
+### Regular account monitoring
+
+- **Review login activity:** Regularly check your account [login activity and active sessions](https://console.scaleway.com/account/profile) for any unauthorized access.
+- **Update information:** Ensure your contact information is up-to-date to receive security alerts.
+
+## Reporting suspicious activity
+
+If you suspect a phishing attempt or any suspicious activity on your account, [report it](#steps-to-report) immediately.
+
+### Steps to report
+
+1. **Do not engage:** Do not reply to the suspicious email or message.
+2. **Report to Scaleway:** Forward the email or provide details of the suspicious activity to Scaleway’s security team [by ticket](https://console.scaleway.com/support/tickets/create) from your Scaleway console.
+3. **Change passwords:** Immediately change your account password and any other accounts that might be affected.
+
+## Educating yourself and your team
+
+- **Security Awareness Training:** Regularly participate in security training to stay informed about the latest threats and how to avoid them.
+- **Stay Updated:** Follow Scaleway’s security blog and announcements for updates on potential threats and security best practices.
+
+By following these guidelines, you can significantly reduce the risk of falling victim to phishing and fraud attempts. Scaleway is committed to ensuring the security of your account and providing resources to help you stay protected.
+
+For more information, visit [Scaleway Security](https://security.scaleway.com/).
\ No newline at end of file
diff --git a/pages/apple-silicon/assets/scaleway-apple-silicon-ssh.webp b/pages/apple-silicon/assets/scaleway-apple-silicon-ssh.webp
new file mode 100644
index 0000000000..af14262f6b
Binary files /dev/null and b/pages/apple-silicon/assets/scaleway-apple-silicon-ssh.webp differ
diff --git a/pages/apple-silicon/assets/scaleway-m1-remote-desktop.webp b/pages/apple-silicon/assets/scaleway-m1-remote-desktop.webp
new file mode 100644
index 0000000000..b97974cf13
Binary files /dev/null and b/pages/apple-silicon/assets/scaleway-m1-remote-desktop.webp differ
diff --git a/pages/apple-silicon/assets/scaleway-m1-ssh.webp b/pages/apple-silicon/assets/scaleway-m1-ssh.webp
new file mode 100644
index 0000000000..bc4306e45a
Binary files /dev/null and b/pages/apple-silicon/assets/scaleway-m1-ssh.webp differ
diff --git a/pages/apple-silicon/concepts.mdx b/pages/apple-silicon/concepts.mdx
new file mode 100644
index 0000000000..ac8d0d9883
--- /dev/null
+++ b/pages/apple-silicon/concepts.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: Apple silicon - Concepts
+ description: This page explains all the concepts related to Apple silicon
+content:
+ h1: Apple silicon - Concepts
+ paragraph: This page explains all the concepts related to Apple silicon
+tags: apple-silicon apple-m1 m1 availability-zone mac-mini-m1 mac-mini vnc
+categories:
+ - bare-metal
+---
+
+## Apple silicon
+
+Apple silicon is Apple's own design of processor. It is the basis of Mac computers, as well as many other Apple products.
+
+## Apple silicon as-a-service
+
+Scaleway Apple silicon as-a-Service uses [Apple Mac mini](#mac-mini) hardware. These devices rely on the power of Apple's [silicon](#apple-silicon) technology, ensuring exceptional performance and energy efficiency.
+
+Apple silicon as-a-Service is tailored for developing, building, testing, and signing applications for Apple devices such as iPhones, iPads, Mac computers, and more. The Mac mini boasts a sophisticated neural engine that significantly enhances machine learning capabilities.
+
+## Mac mini
+
+The Mac mini is a physical hardware designed by Apple, powered by the [Apple silicon](#apple-silicon) chip. It is the basis for Scaleway's [Apple silicon as-a-service](#apple-silicon-as-a-service) offer.
+
+## Region and Availability Zone
+
+
+
+## VNC
+
+Virtual Network Computing (VNC) is a remote desktop-sharing protocol. It allows you to visualize the graphical screen output of a remote computer and transfer local keyboard and mouse events to the remote computer using a network connection. The protocol is platform-independent, which means that various clients exist for Linux, Windows, and macOS-based computers. The VNC server used on the Mac mini is directly integrated with the macOS system without any restrictions from our side. Check out our documentation on [how to connect to your Mac mini via VNC](/apple-silicon/how-to/access-remote-desktop-mac-mini/#accessing-the-remote-desktop).
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx b/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx
new file mode 100644
index 0000000000..759b6fed2f
--- /dev/null
+++ b/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx
@@ -0,0 +1,153 @@
+---
+meta:
+ title: How to access to the remote desktop of a Mac mini
+ description: Learn how to access a Mac mini using remote desktop clients on macOS, Windows, and Linux.
+content:
+ h1: How to access to the remote desktop of a Mac mini
+ paragraph: Learn how to access a Mac mini using remote desktop clients on macOS, Windows, and Linux.
+tags: apple-silicon, connection, mac-mini, mac-mini
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This guide provides detailed instructions on how to access your [Mac mini](/apple-silicon/concepts/#mac-mini) using remote desktop clients.
+
+The macOS on your Mac mini uses the VNC protocol with additional Apple-specific enhancements to provide a remote desktop access.
+Remote desktop allows you to visualize the graphical screen output of a remote computer and interact with it using your local keyboard and mouse.
+The VNC protocol is platform-independent, supporting Linux, Windows, and macOS, ensuring a seamless connection experience regardless of your operating system.
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing actions in the intended Organization
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+## Accessing the remote desktop
+
+
+ The VNC port on Mac mini systems is **randomly assigned** during system installation and may therefore be different from the default VNC port 5900. To connect successfully via VNC, use the specific port shown in the **Overview** section of your Mac mini’s configuration.
+ For manual connections, ensure that the port from the **Overview** section is correctly entered in your VNC client settings, as this is necessary for a successful connection.
+
+
+
+
+ ## Accessing the remote desktop from a macOS client
+
+ If your local machine runs macOS, you can use the Scaleway console to connect to your Mac mini using the built-in Apple ARD client.
+
+ 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+ 2. Click the Mac mini you want to connect to. The **Overview** page of your Mac mini displays.
+ 3. Click **Open remote desktop** in the **Access remote desktop from macOS ①** section to launch Apple's built-in screen sharing client for a seamless remote desktop experience.
+
+
+ Once your screen displays in your remote desktop client, log in to the graphical environment of macOS using the remote user and your password (available on the **Overview** page of your Mac mini).
+
+
+ macOS may ask for your password once logged into the remote desktop session. Change the keyboard layout of macOS to your computer's local keyboard layout before entering the password. Click "U.S. keyboard" in the top right corner to display a list of all available keyboard layouts.
+
+
+ You are now logged in and can use your Mac mini as if you were physically present.
+
+
+
+
+
+
+ ## Accessing the remote desktop from a Windows client
+
+ If your local machine runs Windows, you will need to install a remote desktop client to access the remote desktop of the Mac mini.
+
+ 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+ 2. Click the Mac mini you want to connect to. The **Overview** page of your Mac mini displays.
+ 3. Configure your remote desktop client for Windows for the connection. We suggest using one of these two remote desktop clients:
+
+ These clients are free versions of commercially supported solutions and may have usage restrictions.
+
+
+ - **RealVNC:**
+ - Download [RealVNC Viewer](https://www.realvnc.com/en/connect/download/viewer/)
+ - Open RealVNC Viewer (no sign-in required)
+ - Click **File** and **New Connection**
+ - In the **VNC Server** field, enter the Mac mini's IP address followed by the port (e.g., `192.168.1.100:5901`), then create the connection.
+ - Go back to the dashboard and find the Mac mini remote desktop in the Address book
+ - Open the remote desktop with the username and password (found in the console)
+
+ - **Devolutions Remote Desktop Manager:**
+ - Download [Devolutions Remote Desktop Manager](https://devolutions.net/remote-desktop-manager/)
+ - Download .NET Desktop Runtime if needed
+ - Open Remote Desktop Manager
+ - Click **+** and **New Entry**
+ - Choose **ARD**
+ - Enter the Mac mini's IP address in the **Host** field. Then, specify the port in the **Port** field, along with your username and password (located in the console).
+ - Open the session
+
+
+
+
+
+ ## Accessing the remote desktop from a Linux client
+
+ If your local machine runs Linux, you will need to install a remote desktop client to access the remote desktop of the Mac mini.
+
+ 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+ 2. Click the Mac mini you want to connect to. The **Overview** page of your Mac mini displays.
+ 3. Configure your remote desktop client for the connection. We suggest using one of these two remote desktop clients:
+ - **Remmina:**
+ - [Download and install Remmina](https://remmina.org/), if necessary.
+
+ Remmina is included in most Linux distributions by default.
+
+ - Open Remmina and click the **+** icon in the top left to create a new quick connection.
+ - Enter the following parameters:
+ - **Protocol**: Remmina VNC Plugin
+ - **Server**: Your Mac mini's public IP address (found on its **Overview** page in the Scaleway console), followed by the port number, separated by a colon (e.g., `192.168.1.100:5901`).
+ - **Username**: The remote desktop password of your Mac mini, available on its **Overview** page in the Scaleway console.
+ - **Password**: The remote desktop password of your Mac mini, displayed on its **Overview** page in the Scaleway console.
+ - **Color depth**: High color (16 bpp) or better, otherwise the connection will fail.
+ - Click **Save and connect** to save these settings for future use and launch a connection to your Mac mini.
+ - You can now log in to the graphical environment of macOS using the user and the remote desktop password displayed in your Scaleway console.
+
+ Once Remmina is installed and set up, you can connect to the remote desktop directly by clicking the **remote desktop** button in the console.
+
+
+ - **Devolutions Remote Desktop Manager:**
+ - Download [Devolutions Remote Desktop Manager](https://devolutions.net/remote-desktop-manager/)
+ - Download .NET Desktop Runtime if needed
+ - Open Remote Desktop Manager
+ - Click **+** and **New Entry**
+ - Choose **ARD**
+ - Enter the Mac mini's IP address in the **Host** field. Then, specify the port in the **Port** field, along with your username and password (located in the console).
+ - Open the session
+
+
+
+
+
+ ## Comparison matrix of remote desktop clients
+
+ Below is a matrix to compare the different features of the free versions of these remote desktop clients:
+
+ | Client | Compatible OS | Copy & Paste | Streaming Audio* | Security/Tunneling Mode | High Quality Compatibility | Display Responsiveness |
+ |---------------------------------|---------------|--------------------------------------------|--------------------------|--------------------------------------------------|----------------------------|------------------------|
+ | ARD (integrated) | macOS | ✅ (except for password) | ❌ | ✅ auto | ⭐⭐⭐ | ⭐⭐⭐ |
+ | RealVNC | Windows, Linux, macOS | 〰️ (some issues) | ❌ (not with free version) | ❌ (manual tunnel) | ❌ | ⭐ (not recommended) |
+ | Remmina | Linux | ✅ (manual, only from local to server) | ❌ | ❌ (manual tunnel) | ❌ | ⭐ |
+ | Devolutions Remote Desktop Manager | Windows, Linux, macOS | ✅ | ❌ | ✅ (requires additional setup - SSH tunnel) | ❌ | ⭐⭐ |
+
+ * These remote desktop clients don't allow audio streaming. If you need audio streaming, we recommend using [Reemo](/tutorials/access-mac-mini-with-reemo/). You need to configure the connection with Reemo using a VNC connection. We recommend setting up another VNC connection and using this remote desktop client before configuring Reemo.
+
+
+
+
+ If you encounter issues connecting to the remote desktop of your Mac mini, refer to our documentation on [Troubleshooting remote desktop connections to Mac mini servers](/apple-silicon/troubleshooting/cant-connect-using-vnc/).
+
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-dashboard.webp b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-dashboard.webp
new file mode 100644
index 0000000000..a040f7dd63
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-dashboard.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-remote-desktop.webp b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-remote-desktop.webp
new file mode 100644
index 0000000000..7b4afbe8e4
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-remote-desktop.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-ssh.webp b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-ssh.webp
new file mode 100644
index 0000000000..af14262f6b
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-ssh.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-vnc.webp b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-vnc.webp
new file mode 100644
index 0000000000..b7d531944a
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-apple-silicon-vnc.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-creation-wizard.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-creation-wizard.webp
new file mode 100644
index 0000000000..54875a53bb
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-creation-wizard.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-list.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-list.webp
new file mode 100644
index 0000000000..7b5258e8c0
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-list.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-reboot-modal.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-reboot-modal.webp
new file mode 100644
index 0000000000..efe5d1d542
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-reboot-modal.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-reboot.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-reboot.webp
new file mode 100644
index 0000000000..2723a4fc01
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-reboot.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-reinstall.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-reinstall.webp
new file mode 100644
index 0000000000..beb0b13302
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-reinstall.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-remote-desktop.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-remote-desktop.webp
new file mode 100644
index 0000000000..b97974cf13
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-remote-desktop.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-splash.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-splash.webp
new file mode 100644
index 0000000000..14f48b36ec
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-splash.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-ssh.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-ssh.webp
new file mode 100644
index 0000000000..bc4306e45a
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-ssh.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-m1-vnc.webp b/pages/apple-silicon/how-to/assets/scaleway-m1-vnc.webp
new file mode 100644
index 0000000000..474b229c72
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-m1-vnc.webp differ
diff --git a/pages/apple-silicon/how-to/assets/scaleway-vnc-lang.webp b/pages/apple-silicon/how-to/assets/scaleway-vnc-lang.webp
new file mode 100644
index 0000000000..9b2b3b2094
Binary files /dev/null and b/pages/apple-silicon/how-to/assets/scaleway-vnc-lang.webp differ
diff --git a/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx b/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx
new file mode 100644
index 0000000000..5373ea25f2
--- /dev/null
+++ b/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: How to connect to a Mac mini Using SSH
+ description: This page explains how to connect to a Scaleway Mac mini using SSH.
+content:
+ h1: How to connect to a Mac mini Using SSH
+ paragraph: This page explains how to connect to a Scaleway Mac mini using SSH, providing step-by-step instructions and necessary requirements.
+tags: apple-silicon, connection, mac-mini, mac-mini-m1
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+You can connect directly to the terminal of your Mac mini using the SSH protocol and your [SSH key](/organizations-and-projects/concepts/#ssh-key).
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+## Connecting to a Mac mini using SSH
+
+1. Navigate to the [Scaleway console](https://console.scaleway.com) and log in with your credentials.
+
+2. Click **Apple silicon** under the **Bare Metal** section in the side-menu. This displays a list of your Mac minis.
+
+
+3. Click the name of the Mac mini you want to connect to. The **Overview** page for your selected Mac mini displays.
+
+ You can find your SSH connection information under **SSH command**.
+
+
+
+4. Open your terminal application and use the SSH command provided on the **Overview** page to connect.
+ - The SSH command will be in the format:
+ ```sh
+ ssh your_mac_mini_username@
+ ```
+ - Replace `` with your Mac mini username.
+ - Replace `` with the actual IP address of your Mac mini.
+
+
+ * You can find the default username and IP address of your Mac mini on it's overview page in the Scaleway console.
+ * For more detailed guidance on connecting via SSH, refer to our documentation on [how to connect to an Instance](/instances/how-to/connect-to-instance/).
+
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/create-mac-mini.mdx b/pages/apple-silicon/how-to/create-mac-mini.mdx
new file mode 100644
index 0000000000..afd5416717
--- /dev/null
+++ b/pages/apple-silicon/how-to/create-mac-mini.mdx
@@ -0,0 +1,44 @@
+---
+meta:
+ title: How to create a Mac mini
+ description: This page explains how to create a Mac mini
+content:
+ h1: How to create a Mac mini
+ paragraph: This page explains how to create a Mac mini
+tags: mac-mini mac-mini apple-silicon
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This page shows how to create your first [Mac mini](/apple-silicon/concepts/#mac-mini) with the Scaleway console.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+
+
+ Due to license constraints, the minimum lease for Apple silicon is 24 hours. As a result, the earliest you can delete a Mac mini is 24 hours after the start of its lease.
+
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. The Apple silicon splash page displays.
+
+ Should your account already contain Mac minis, a list of these will be displayed rather than the Apple silicon splash page.
+ Alongside, you will see a (+ Create Mac mini) button, which you can click to create a new Mac mini.
+
+2. Click **Create Mac mini**. The Mac mini creation wizard displays.
+3. Complete the following steps in the wizard:
+ - Choose an **Availability Zone**, which is the geographical region where your Mac mini will be deployed. The available Mac mini configurations depend on the Availability Zone:
+ - Mac mini M2 pro and M2 are available in PARIS 1
+ - Mac mini M1 are available in PARIS 3
+ - Choose a macOS version. Note that if you choose a macOS other than the one installed by default, there will be a delay of about 1 hour before the Mac mini is made available.
+ - Enter a **Name** for your Mac mini, or leave the randomly-generated name in place.
+ - Verify the **Estimated cost** for your Mac mini based on your chosen specifications.
+4. Click **Create Mac mini** to finish. The installation of your Apple silicon is launched, and you are informed when it is ready.
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/delete-mac-mini.mdx b/pages/apple-silicon/how-to/delete-mac-mini.mdx
new file mode 100644
index 0000000000..d45ab31adf
--- /dev/null
+++ b/pages/apple-silicon/how-to/delete-mac-mini.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to delete a Mac mini
+ description: This page explains how to delete a Mac mini
+content:
+ h1: How to delete a Mac mini
+ paragraph: This page explains how to delete a Mac mini
+tags: mac-mini mac-mini-m1 m1 apple-silicon
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This page shows how to delete your [Mac mini](/apple-silicon/concepts/#mac-mini).
+
+
+
+- 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
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+
+ Deleting your Mac mini is an irreversible action. Any data stored on it will be lost.
+
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+2. Click next to the Mac mini you want to delete and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action.
+3. Type **DELETE** and then click **Delete Mac mini** to confirm the deletion of your Mac mini.
+
+You are returned to the list of your Mac minis, where the machine you deleted no longer appears.
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/index.mdx b/pages/apple-silicon/how-to/index.mdx
new file mode 100644
index 0000000000..afc7583934
--- /dev/null
+++ b/pages/apple-silicon/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Apple silicon - How Tos
+ description: Apple silicon How Tos
+content:
+ h1: How Tos
+ paragraph: Apple silicon How Tos
+---
diff --git a/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx b/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx
new file mode 100644
index 0000000000..4723c79021
--- /dev/null
+++ b/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx
@@ -0,0 +1,48 @@
+---
+meta:
+ title: How to install a package manager to a Mac mini
+ description: This page explains how to install the Homebrew package manager to a Scaleway Mac mini.
+content:
+ h1: How to install a package manager to a Mac mini
+ paragraph: This page explains how to install the Homebrew package manager to a Scaleway Mac mini.
+tags: apple-silicon, connection, mac-mini, mac-mini-m1
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+[Homebrew](https://brew.sh/) is a package manager for macOS. It allows you to manage the packages installed on your Mac mini and provides a way to install additional software on your machine.
+
+1. Install Homebrew by running the following command:
+ ```bash
+ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+ ```
+2. Update Homebrew by running the following command:
+ ```bash
+ brew update
+ ```
+3. Retrieve the list of all the outdated packages on your system:
+ ```bash
+ brew outdated
+ ```
+4. Upgrade these packages to the latest version available in Homebrew's repositories:
+ ```bash
+ brew upgrade
+ ```
+
+
+ If you want to upgrade selected packages only, run the following command: `brew upgrade package-name`.
+
+
+
+ Mac Mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
diff --git a/pages/apple-silicon/how-to/reboot-mac-mini.mdx b/pages/apple-silicon/how-to/reboot-mac-mini.mdx
new file mode 100644
index 0000000000..903f2e403e
--- /dev/null
+++ b/pages/apple-silicon/how-to/reboot-mac-mini.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to reboot a Mac mini
+ description: This page explains how to reboot a Mac mini
+content:
+ h1: How to reboot a Mac mini
+ paragraph: This page explains how to reboot a Mac mini
+tags: mac-mini mac-mini m1 apple-silicon reboot
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This page shows how to reboot your [Mac mini](/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is unreachable, or you want to reboot it remotely.
+
+
+
+- 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
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+2. Click the Mac mini you want to reboot. Your Mac mini information page displays.
+3. Scroll down to the **Reboot Mac mini** section, and click **Reboot**.
+4. Click **Reboot Mac mini** to confirm.
+
+ Rebooting a Mac mini is similar to pulling the electrical plug on a running computer, which can cause data corruption. To avoid data loss, save your documents before rebooting the machine.
+
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/reinstall-mac-mini.mdx b/pages/apple-silicon/how-to/reinstall-mac-mini.mdx
new file mode 100644
index 0000000000..18c165e166
--- /dev/null
+++ b/pages/apple-silicon/how-to/reinstall-mac-mini.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to reinstall a Mac mini
+ description: This page explains how to reinstall a Mac mini
+content:
+ h1: How to reinstall a Mac mini
+ paragraph: This page explains how to reinstall a Mac mini
+tags: reinstall mac-mini mac-mini apple-silicon
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This page shows how to reinstall your [Mac mini](/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is not reachable, or you want to start from scratch on the machine.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+2. Click the Mac mini you want to reinstall. Your Mac mini **Overview** displays.
+3. Scroll down to the **Reinstall Mac mini** section, and click **Reinstall**.
+4. Type **REINSTALL** to confirm the installation of your Mac mini and click **Reinstall Mac mini** to validate.
+
+ When reinstalling your Mac mini, all the data on the disk is deleted, and all configurations are reset to the default values.
+
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/how-to/shutdown-mac-mini.mdx b/pages/apple-silicon/how-to/shutdown-mac-mini.mdx
new file mode 100644
index 0000000000..887dde4045
--- /dev/null
+++ b/pages/apple-silicon/how-to/shutdown-mac-mini.mdx
@@ -0,0 +1,48 @@
+---
+
+meta:
+ title: How to shutdown a Scaleway Mac mini
+ description: Detailed guide on how to properly shutdown a Scaleway Mac mini.
+content:
+ h1: How to shutdown a Scaleway Mac mini
+ paragraph: This guide provides instructions on how to properly shutdown a Scaleway Mac mini.
+tags: mac-mini, mac-mini-m1, apple-silicon, shutdown
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Due to operational constraints, a Scaleway Mac mini should not be fully shut down using conventional methods. Below are guidelines for managing your Mac mini's usage and shutdown procedures.
+
+
+ If you force the shutdown of your Mac mini using the command line or any other method, it will not be possible to manually turn it back on via SSH or the Scaleway Console. To ensure service continuity, we have implemented safeguards that will automatically restart the Mac mini within 24 hours.
+
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+
+## Temporarily stopping usage
+
+To temporarily stop using your Mac mini:
+1. **Close the Remote Desktop Window:** If you are using a graphical interface, simply close the remote desktop window to stop your session.
+2. **End Your SSH Session:** If you are connected via terminal, terminate your SSH session to stop accessing the Mac mini.
+
+
+ You will continue to be billed for your Mac mini as long as it remains assigned to your account. Billing will only cease once the deletion process is fully completed and the Mac mini has been removed from your account.
+
+
+## Permanently stopping usage
+
+To permanently stop using your Mac mini and cease billing, you need to delete your Mac mini from your account. For detailed instructions, refer to [How to Delete a Mac mini](/apple-silicon/how-to/delete-mac-mini/).
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
diff --git a/pages/apple-silicon/how-to/update-os-mac-mini.mdx b/pages/apple-silicon/how-to/update-os-mac-mini.mdx
new file mode 100644
index 0000000000..6f39bd78ea
--- /dev/null
+++ b/pages/apple-silicon/how-to/update-os-mac-mini.mdx
@@ -0,0 +1,78 @@
+---
+meta:
+ title: How to update the OS to a Mac mini
+ description: This page explains how to update the operating system of a Scaleway Mac mini.
+content:
+ h1: How to update the OS of a Mac mini
+ paragraph: This page explains how to update the operating system of a Scaleway Mac mini.
+tags: apple-silicon, connection, mac-mini, mac-mini-m1
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This guide provides instructions on updating the operating system of a Scaleway Mac mini.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+## Recommended method: macOS provided by Scaleway
+
+The recommended method to update the macOS is to reinstall your Mac mini with an OS image provided by Scaleway:
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+
+2. Click the Mac mini you want to reinstall. Your Mac mini **Overview** displays.
+3. Scroll down to the **Reinstall Mac mini** section, and click **Reinstall**.
+4. Type **REINSTALL** to confirm the installation of your Mac mini and click **Reinstall Mac mini** to validate.
+
+ - When reinstalling your Mac mini, all the data on the disk is deleted, and all configurations are reset to the default values.
+ - **Do not forget to backup your data before reinstalling the operating system to avoid any data loss.**
+
+
+## Manually upgrading macOS
+
+
+ Manually modifying your Mac mini's OS may create incompatibilities with the preconfigured settings. Proceed only if you are capable of resolving potential configuration issues.
+
+
+### Upgrading the OS via remote desktop
+
+1. Log into your Mac mini using a [remote desktop client](/apple-silicon/how-to/access-remote-desktop-mac-mini/)
+2. Go to **System settings > General > Software update**
+3. Launch the installation of the update.
+
+ If you want to install a beta version:
+
+ 1. Sign up to the [Apple Beta Software Program](https://beta.apple.com/) with your Apple ID.
+ 2. Read through Apple's instructions carefully, and then using the link in the **Get Started** section, select enroll your Mac.
+ 3. Go back to **System settings > General > Software** update and click the Info button next to **Beta updates** to enable beta versions updates.
+
+
+### Upgrading the OS using SSH
+
+To manually update the operating system using the `softwareupdate` tool, follow these steps:
+
+1. List all available updates:
+ ```sh
+ softwareupdate --list
+ ```
+2. Install all available updates:
+ ```sh
+ sudo softwareupdate --install
+ ```
+
+ If you want to upgrade selected packages only, use the following command:
+ ```sh
+ softwareupdate --install package-name
+ ```
+
+
+
+ Mac Mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
diff --git a/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx b/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx
new file mode 100644
index 0000000000..3f87c2cc48
--- /dev/null
+++ b/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx
@@ -0,0 +1,49 @@
+---
+meta:
+ title: How to upgrade to a beta version of macOS on a Mac mini
+ description: This page explains how to upgrade the macOS of a Scaleway Mac mini to a beta version.
+content:
+ h1: How to upgrate to a beta version of macOS on a Mac mini
+ paragraph: This page explains how to upgrade the macOS of a Scaleway Mac mini to a beta version.
+tags: apple-silicon mac-mini beta macos
+dates:
+ validation: 2024-07-30
+ posted: 2024-07-30
+categories:
+ - bare-metal
+---
+
+This guide explains the steps to upgrade the macOS of a Scaleway Mac mini to a beta version.
+
+
+
+- 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
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+
+1. Access your Mac mini via a [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/).
+
+2. Back up your Mac mini.
+
+ Ensure you [back up your data and files](/faq/apple-silicon/#how-can-i-back-up-my-mac-mini) before installing beta versions of macOS.
+
+
+3. Sign up for Apple's **Beta Software Program**:
+ - Visit [beta.apple.com](https://beta.apple.com), click **Sign Up** and log in with your Apple ID.
+
+ An Apple ID is required to join the beta software program. Create an ID if you do not have one yet.
+
+
+4. Click **Enroll your Mac** in the **Get Started** section of Apple's website to register your Mac for the Beta Software Program.
+
+5. Turn on beta updates:
+ - On your Mac, go to **System Settings** > **General** > **Software Update**.
+ - Click the **Info** (ⓘ) button next to **Beta updates**.
+ - Select the **macOS Public Beta** option.
+
+6. Click the **Upgrade Now** button to start downloading and installing the beta version on your Mac.
+
+ Reverting from a macOS beta version to a previous stable version without reinstalling the operating system entirely is not officially supported by Apple. The only way to revert is to perform a full [reinstallation](/apple-silicon/how-to/reinstall-mac-mini/) of the previous macOS version.
+
+
diff --git a/pages/apple-silicon/index.mdx b/pages/apple-silicon/index.mdx
new file mode 100644
index 0000000000..7e81602482
--- /dev/null
+++ b/pages/apple-silicon/index.mdx
@@ -0,0 +1,86 @@
+---
+meta:
+ title: Apple silicon Documentation
+ description: Dive into Scaleway Apple silicon with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/apple-silicon/quickstart.mdx b/pages/apple-silicon/quickstart.mdx
new file mode 100644
index 0000000000..5b11bfd215
--- /dev/null
+++ b/pages/apple-silicon/quickstart.mdx
@@ -0,0 +1,83 @@
+---
+meta:
+ title: Apple silicon - Quickstart
+ description: This page shows you how to get started with Scaleway's Apple silicon.
+content:
+ h1: Apple silicon - Quickstart
+ paragraph: This page shows you how to get started with Scaleway's Apple silicon.
+tags: apple-silicon mac-mini- mac mini mac-mini ios
+dates:
+ validation: 2024-07-25
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Scaleway Apple silicon as-a-Service uses Apple Mac mini hardware. These devices rely on the power of Apple's silicon technology, ensuring exceptional performance and groundbreaking energy efficiency.
+
+Apple silicon as-a-Service is tailored for developing, building, testing, and signing applications for Apple devices such as iPhones, iPads, Mac computers, and more. The Mac mini boasts a sophisticated neural engine that significantly enhances machine learning capabilities.
+
+## Requirements
+
+- Be the [Owner](/iam/concepts/#owner) of the Organization in which the actions will be performed, or an IAM user with the [necessary permissions](/iam/concepts/#permission)
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+
+## How to create a Mac mini
+
+
+ - Due to license constraints, the minimum lease for Apple silicon is 24 hours. As a result, the earliest you can delete a Mac mini is 24 hours after the start of its lease.
+
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. The Apple silicon creation page displays.
+2. Click **Create Mac mini**. The Mac mini creation wizard displays.
+3. Complete the following steps in the wizard:
+ - Choose an **Availability Zone**, which is the geographical region where your Mac mini will be deployed. The available Mac mini configurations depend on the Availability Zone:
+ - Mac mini M2 pro and M2 are available in PARIS 1
+ - Mac mini M1 are available in PARIS 3
+ - Choose a macOS version.
+
+ If you choose a macOS other than the one installed by default, there will be a delay of about 1 hour before the Mac mini is made available.
+
+ - Enter a **Name** for your Mac mini, or leave the randomly-generated name in place.
+ - Verify the **Estimated cost** for your Mac mini based on your chosen specifications.
+4. Click **Create Mac mini** to finish. The installation of your Apple silicon is launched, and you are informed when it is ready.
+
+## How to connect to your Mac mini
+
+### How to connect via remote desktop
+
+You can access your Mac mini using VNC, a remote desktop-sharing protocol. It allows you to visualize the graphical screen output of a remote computer and transfer local keyboard and mouse events to the remote computer using a network connection.
+
+Refer to our detailed documentation for Windows, Linux, and macOS for OS specific information: [How to access the remote desktop of a Mac mini](/apple-silicon/how-to/access-remote-desktop-mac-mini/).
+
+
+ The VNC port on Mac mini systems is **randomly assigned** during system installation and may therefore be different from the default VNC port 5900. To connect successfully via VNC, use the specific port shown in the **Overview** section of your Mac mini’s configuration.
+ For manual connections, ensure that the port from the **Overview** section is correctly entered in your VNC client settings, as this is necessary for a successful connection.
+
+
+## How to connect using SSH
+
+1. Navigate to the [Scaleway console](https://console.scaleway.com) and log in with your credentials.
+2. Click **Apple silicon** under the **Bare Metal** section in the side-menu. This displays a list of your Mac minis.
+3. Click the name of the Mac mini you want to connect to. The **Overview** page for your selected Mac mini displays.
+4. Open your terminal application and use the SSH command provided on the **Overview** page to connect.
+ - The SSH command will be in the format:
+ ```sh
+ ssh your_mac_mini_username@
+ ```
+ - Replace `` with your Mac mini username.
+ - Replace `` with the actual IP address of your Mac mini.
+
+
+## How to delete a Mac mini
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+2. Click next to the Mac mini you want to delete and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action.
+3. Type **DELETE** and then click **Delete Mac mini**.
+
+You are returned to the list of your Mac minis, where the machine you deleted no longer appears.
+
+
+ Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/reference-content/index.mdx b/pages/apple-silicon/reference-content/index.mdx
new file mode 100644
index 0000000000..7661d3a637
--- /dev/null
+++ b/pages/apple-silicon/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Apple silicon - Additional Content
+ description: Apple silicon Additional Content
+content:
+ h1: Additional Content
+ paragraph: Apple silicon Additional Content
+---
diff --git a/pages/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx b/pages/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx
new file mode 100644
index 0000000000..7cf62097a8
--- /dev/null
+++ b/pages/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: Resolving SSH connection issues to Scaleway Mac mini
+ description: Learn how to fix SSH connection problems with Scaleway Apple silicon Mac mini by uploading your SSH key and rebooting the device.
+content:
+ h1: Resolving SSH connection issues to Scaleway Mac mini
+ paragraph: Learn how to fix SSH connection problems with Scaleway Apple silicon Mac mini by uploading your SSH key and rebooting the device.
+tags: ssh ssh-key connection
+dates:
+ validation: 2024-12-19
+ posted: 2024-06-12
+categories:
+ - bare-metal
+---
+
+This documentation addresses an issue faced by users who are unable to connect to their Mac Mini via SSH.
+This problem typically arises because the user's SSH key has not been uploaded to the Mac Mini.
+It can also happen after multiple authentication failures while trying to access the VNC server because of default fail2ban security policies.
+This guide provides the necessary steps to resolve this issue by connecting to the Scaleway console and rebooting the Mac Mini from the Apple silicon section.
+
+
+The reboot **must** be carried out via the console, and not via any other method, in order to resolve the problem.
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays.
+2. Click the Mac mini you want to configure. Your Mac mini information page displays.
+3. Scroll down to the **Reboot Mac mini** section. Click **Reboot** to reboot the Mac mini.
+
+ Ensure you have [generated and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/) before rebooting your Mac mini.
+
+4. Click **Reboot Mac mini** to confirm. The Mac mini reboots and your SSH key will be uploaded during the boot process. Banned host lists are reset as well.
\ No newline at end of file
diff --git a/pages/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx b/pages/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx
new file mode 100644
index 0000000000..a49cb469db
--- /dev/null
+++ b/pages/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx
@@ -0,0 +1,158 @@
+---
+meta:
+ title: Troubleshooting remote desktop connections to Mac mini servers
+ description: This page suggests solutions for when you cannot establish a remote desktop connection to your Mac mini
+content:
+ h1: Troubleshooting remote desktop connections to Mac mini servers
+ paragraph: This page suggests solutions for when you cannot establish a remote desktop connection to your Mac mini
+tags: remote vnc connection apple-silicon error
+dates:
+ validation: 2024-12-19
+ posted: 2023-04-07
+categories:
+ - bare-metal
+---
+
+This documentation provides a structured approach to diagnose and resolve issues when you cannot establish a remote desktop connection to your Mac mini.
+
+
+
+- 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
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+## 1. Verify the server status
+
+Execute the following `ping` command in a terminal on your local machine:
+```sh
+ping -c 5
+```
+Expected output:
+```
+PING X.X.X.X (X.X.X.X): 56 data bytes
+64 bytes from X.X.X.X: icmp_seq=0 ttl=64 time=0.182 ms
+64 bytes from X.X.X.X: icmp_seq=1 ttl=64 time=0.261 ms
+64 bytes from X.X.X.X: icmp_seq=2 ttl=64 time=0.191 ms
+64 bytes from X.X.X.X: icmp_seq=3 ttl=64 time=0.200 ms
+64 bytes from X.X.X.X: icmp_seq=4 ttl=64 time=0.201 ms
+
+--- X.X.X.X ping statistics ---
+5 packets transmitted, 5 packets received, 0.0% packet loss
+round-trip min/avg/max/stddev = 0.182/0.207/0.261/0.028 ms
+```
+- If `ping` fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/).
+- If rebooting fails or if the server was forced to shut down, wait 24 hours for automatic restart. See [How to shutdown a Mac mini](/apple-silicon/how-to/shutdown-mac-mini/) for more information.
+
+## 2. Verify the VNC connection
+
+
+ The VNC port on Mac mini systems is **randomly assigned** during system installation and may therefore be different from the default VNC port 5900. To connect successfully via VNC, use the specific port shown in the **Overview** section of your Mac mini’s configuration.
+ For manual connections, ensure that the port from the **Overview** section is correctly entered in your VNC client settings, as this is necessary for a successful connection.
+
+
+Execute the following command in a terminal on your local machine:
+```sh
+nc -zv
+```
+Expected output:
+```
+Connection to port [tcp/rfb] succeeded!
+```
+- If the connection fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/).
+- If necessary, restart screen sharing via SSH. See [Restarting screen sharing via SSH](#restarting-screen-sharing-via-ssh).
+
+## 3. Verify the SSH server response
+Execute the following command:
+```sh
+nc -zv 22
+```
+Expected output:
+```
+Connection to port 22 [tcp/ssh] succeeded!
+```
+- If the connection fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/).
+
+## 4. Check for connection blacklisting
+If VNC connection attempts repeatedly fail, the connection might be blacklisted, or the Apple screen sharing service might be unresponsive.
+
+- [Reboot the server](/apple-silicon/how-to/reboot-mac-mini/) to clear the `fail2ban` table.
+
+## 5. Verify your connection credentials
+
+### Remote desktop (VNC) credentials
+- Ensure the correct username and password are used. These can be verified in the console.
+- For errors like "Authentication failed," verify credentials and retry.
+
+### SSH keys
+- Ensure the SSH key is correctly formatted and configured before installing the Mac.
+- SSH keys provided post-installation are not considered.
+
+## 6. Verify remote connection client compatibility
+Ensure your remote connection client is compatible with macOS. Incompatible remote desktop (VNC) clients can cause failed connection attempts. For recommended VNC clients, see [How to access to the remote desktop of a Mac mini](/apple-silicon/how-to/access-remote-desktop-mac-mini/#comparison-matrix-of-remote-desktop-clients).
+
+## 7. Reinstall the Mac mini
+
+If the previous attempts to resolve connection issues to your Mac mini have been unsuccessful, you may need to reinstall your server from the Scaleway console.
+
+Follow these steps to reinstall macOS on your Mac mini:
+
+1. Log in to your Scaleway console.
+2. Navigate to your Mac mini server.
+3. Select the option to reinstall a version of macOS.
+
+For detailed instructions, refer to [How to reinstall a Mac mini](/apple-silicon/how-to/reinstall-mac-mini/).
+
+
+ Reinstalling your Mac mini will erase all data on the disk and reset all configurations to default settings. Ensure you have a backup of your data before proceeding.
+
+
+## Security and configuration
+
+### Enable and configure pf (Packet Filter)
+To restrict macOS Screen Sharing to specific IPs:
+1. Connect to your Mac mini via SSH:
+ ```sh
+ ssh@
+ ```
+2. Backup the `pf.conf` file:
+ ```sh
+ sudo cp /etc/pf.conf /etc/pf.conf.backup
+ ```
+3. Edit the `pf.conf` file:
+ ```sh
+ sudo nano /etc/pf.conf
+ ```
+4. Add rules to restrict access:
+ ```sh
+ ## Add these lines to block connections to port 5900 except from your static IP
+ block in on en0 proto tcp from any to any port 5900
+ pass in on en0 proto tcp from to any port 5900
+ ```
+ Replace `en0` with your network interface and `` with the allowed IP address.
+5. Save and close the file.
+6. Apply the new configuration:
+ ```sh
+ sudo pfctl -f /etc/pf.conf
+ ```
+7. Test the screen sharing connection from the allowed IP and verify it is blocked from other IPs.
+
+
+ For advanced configuration and further information consult our [fail2ban tutorial](/tutorials/protect-server-fail2ban/).
+
+
+### Restarting screen sharing via SSH
+If screen sharing is unresponsive, restart it via SSH:
+1. Connect to your Mac mini via SSH:
+ ```sh
+ ssh your_mac_mini_username@
+ ```
+ - Replace `` with your Mac mini username.
+ - Replace `` with the actual IP address of your Mac mini.
+2. Restart the screen sharing daemon:
+ ```sh
+ sudo killall screensharingd
+ ```
+ The service will restart automatically upon the next connection attempt.
+
+## Troubleshooting and support
+For further assistance, visit our #apple-silicon channel in the [Slack Community](https://slack.scaleway.com/).
diff --git a/pages/apple-silicon/troubleshooting/cant-create-apple-account.mdx b/pages/apple-silicon/troubleshooting/cant-create-apple-account.mdx
new file mode 100644
index 0000000000..a303f3369d
--- /dev/null
+++ b/pages/apple-silicon/troubleshooting/cant-create-apple-account.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: Troubleshooting account creation for hosted Mac minis
+ description: This page suggests solutions for when you cannot create an Apple Account directly from your hosted Mac mini
+content:
+ h1: Troubleshooting account creation for hosted Mac minis
+ paragraph: This page suggests solutions for when you cannot create an Apple Account directly from your hosted Mac mini
+tags: apple-id apple account creation issues
+dates:
+ validation: 2024-10-24
+ posted: 2024-10-24
+categories:
+ - bare-metal
+---
+
+An Apple Account is required for accessing Apple services such as the App Store, iCloud, iMessage, FaceTime, and more.
+It serves as a unique account used to authenticate your identity and connect you to the Apple ecosystem.
+
+However, you might encounter issues creating an Apple Account directly from your hosted Mac mini, especially if too many Apple Accounts have already been created on it.
+
+Apple has implemented [a limit on the number of Apple Accounts](https://support.apple.com/en-us/101661) that can be created from a single device. If you are unable to create an Apple Account on your Mac mini due to this restriction, you can still create one through the Apple website and then sign in on your machine.
+
+### Creating an Apple Account via the Apple website
+
+If you are unable to create an Apple Account on your hosted Mac mini, follow these steps to create one through the Apple website:
+
+1. Open your web browser and navigate to the Apple Account creation page: [https://account.apple.com/account](https://account.apple.com/account).
+2. Click **Create Your Apple Account**. You will be redirected to a page where you can start the registration process.
+3. Fill in your personal information:
+ - First and Last Name: Enter your full name.
+ - Country/Region: Select your country or region from the dropdown menu.
+ - Birthdate: Enter your date of birth.
+ - Email Address: Enter your existing email address. This will be your new Apple Account.
+ - Password: Create a strong and secure password for your account.
+ - Phone number: Enter your phone number. It will be used for two factor authentication and account recovery.
+ Verify your information and click **Continue** to proceed.
+ Apple will send a verification email to the address you provided.
+ 4. Open the email and follow the instructions to verify your account.
+5. After verification, agree to Apple's terms and conditions to complete the process. Tick the checkbox and click on the corresponding button to agree.
+6. Return to your hosted Mac mini and sign in using your new credentials, having successfully created your Apple Account.
+
+
+ The information provided above is for reference only. For detailed instructions or if you encounter any issues while creating your Apple Account, refer to [Apple's official documentation](https://support.apple.com/en-us/108647) on how to create a new Apple Account.
+
+
+### Further troubleshooting
+
+- If you encounter errors while creating an Apple Account on your hosted Mac mini (e.g., "Too many Apple Accounts created on this device"), use the method described above to create your Apple Account through the website.
+- If the problem persists after creating your Apple Account on the website, try signing in from a different device or contact [Apple Support](https://support.apple.com/) for further assistance.
+- For more details, you can visit [Apple's Support Page](https://support.apple.com/en-us/108647) on Apple Accounts.
diff --git a/pages/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx b/pages/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx
new file mode 100644
index 0000000000..3d555d0638
--- /dev/null
+++ b/pages/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx
@@ -0,0 +1,28 @@
+---
+meta:
+ title: I need to prevent FileVault from stopping my system from booting
+ description: This page explains how to prevent FileVault from stopping your system from booting
+content:
+ h1: I need to prevent FileVault from stopping my system from booting
+ paragraph: This page explains how to prevent FileVault from stopping your system from booting
+tags: filevault boot booting
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+
+
+- 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
+- A [Mac mini](/apple-silicon/how-to/create-mac-mini/)
+
+Apple FileVault is a disk encryption feature. Ensure that FileVault is **not enabled** on your Mac mini. If enabled, it will prevent your system from booting.
+
+To turn off FileVault, go to **System Preferences**, click on **Security**, followed by **FileVault**, then click the button that says **turn off FileVault**.
+
+
+ If FileVault is enabled and your Mac mini reboots for whatever reason, it will ask for the FileVault password during the boot process, before you can access the machine using VNC or SSH. You will **not be able** to restart it or recover your data if FileVault is enabled.
+
\ No newline at end of file
diff --git a/pages/apple-silicon/troubleshooting/index.mdx b/pages/apple-silicon/troubleshooting/index.mdx
new file mode 100644
index 0000000000..5698c14351
--- /dev/null
+++ b/pages/apple-silicon/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Apple silicon - Troubleshooting
+ description: Apple silicon Troubleshooting
+content:
+ h1: Troubleshooting
+ paragraph: Apple silicon Troubleshooting
+---
diff --git a/pages/identity-and-access-management/audit-trail/concepts.mdx b/pages/audit-trail/concepts.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/concepts.mdx
rename to pages/audit-trail/concepts.mdx
diff --git a/pages/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx b/pages/audit-trail/how-to/configure-audit-trail-permissions.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx
rename to pages/audit-trail/how-to/configure-audit-trail-permissions.mdx
diff --git a/pages/identity-and-access-management/audit-trail/how-to/index.mdx b/pages/audit-trail/how-to/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/how-to/index.mdx
rename to pages/audit-trail/how-to/index.mdx
diff --git a/pages/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx b/pages/audit-trail/how-to/use-audit-trail.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx
rename to pages/audit-trail/how-to/use-audit-trail.mdx
diff --git a/pages/identity-and-access-management/audit-trail/index.mdx b/pages/audit-trail/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/index.mdx
rename to pages/audit-trail/index.mdx
diff --git a/pages/identity-and-access-management/audit-trail/quickstart.mdx b/pages/audit-trail/quickstart.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/quickstart.mdx
rename to pages/audit-trail/quickstart.mdx
diff --git a/pages/identity-and-access-management/audit-trail/reference-content/index.mdx b/pages/audit-trail/reference-content/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/reference-content/index.mdx
rename to pages/audit-trail/reference-content/index.mdx
diff --git a/pages/identity-and-access-management/audit-trail/reference-content/resource-integration-with-adt.mdx b/pages/audit-trail/reference-content/resource-integration-with-adt.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/reference-content/resource-integration-with-adt.mdx
rename to pages/audit-trail/reference-content/resource-integration-with-adt.mdx
diff --git a/pages/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx b/pages/audit-trail/troubleshooting/cannot-see-events.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx
rename to pages/audit-trail/troubleshooting/cannot-see-events.mdx
diff --git a/pages/identity-and-access-management/audit-trail/troubleshooting/index.mdx b/pages/audit-trail/troubleshooting/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/audit-trail/troubleshooting/index.mdx
rename to pages/audit-trail/troubleshooting/index.mdx
diff --git a/pages/billing/additional-content/assets/scaleway-invoice-1.webp b/pages/billing/additional-content/assets/scaleway-invoice-1.webp
new file mode 100644
index 0000000000..dabfb9be16
Binary files /dev/null and b/pages/billing/additional-content/assets/scaleway-invoice-1.webp differ
diff --git a/pages/billing/additional-content/assets/scaleway-invoice-2.webp b/pages/billing/additional-content/assets/scaleway-invoice-2.webp
new file mode 100644
index 0000000000..7962f1ccb5
Binary files /dev/null and b/pages/billing/additional-content/assets/scaleway-invoice-2.webp differ
diff --git a/pages/billing/additional-content/assets/scaleway-savings-plan.webp b/pages/billing/additional-content/assets/scaleway-savings-plan.webp
new file mode 100644
index 0000000000..841d9a4bf4
Binary files /dev/null and b/pages/billing/additional-content/assets/scaleway-savings-plan.webp differ
diff --git a/pages/billing/additional-content/index.mdx b/pages/billing/additional-content/index.mdx
new file mode 100644
index 0000000000..c7e5120467
--- /dev/null
+++ b/pages/billing/additional-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Billing - Additional content
+ description: Billing Additional content
+content:
+ h1: Billing - Additional content
+ paragraph: Billing Additional content
+---
diff --git a/pages/billing/additional-content/reading-an-invoice.mdx b/pages/billing/additional-content/reading-an-invoice.mdx
new file mode 100644
index 0000000000..fbf7f6b39d
--- /dev/null
+++ b/pages/billing/additional-content/reading-an-invoice.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+ title: Reading an invoice
+ description: This page explains how to read an invoice
+content:
+ h1: Reading an invoice
+ paragraph: This page explains how to read an invoice
+tags: billing invoice payment
+dates:
+ validation: 2024-11-04
+ posted: 2024-02-23
+categories:
+ - billing
+---
+
+
+
+Your Scaleway invoice contains the following sections:
+
+- **Invoice number (1):** A unique reference number for your invoice.
+- **Invoice status (2):** Displays the billing period, issuing and due dates of the invoice.
+- **Seller information (3):** Contact details of Scaleway SAS along with their VAT number.
+- **Customer details (4):** Includes postal address, email address, Organization ID, and for business accounts, the EU VAT number.
+- **Project table (5):** Provides information on invoiced Projects, including Project names, consumed resources, and total Project amounts based on consumption during the accounting period.
+ Located below the Project table you find the **Consumption table**. This section details resource consumption, including Project names, services/operations consumed (e.g., Instances, Object Storage, Elastic Metal servers), consumption periods, total usage, and calculated prices based on consumption.
+- **Total invoice amount (6):** Calculated from the untaxed total of the invoice. For EU customers, the local VAT rate is applied to the untaxed total to determine the total due amount.
\ No newline at end of file
diff --git a/pages/billing/additional-content/understanding-savings-plans.mdx b/pages/billing/additional-content/understanding-savings-plans.mdx
new file mode 100644
index 0000000000..102dfd2bbd
--- /dev/null
+++ b/pages/billing/additional-content/understanding-savings-plans.mdx
@@ -0,0 +1,107 @@
+---
+meta:
+ title: Understanding Scaleway Savings Plans
+ description: This page explains how Scaleway Savings Plans work.
+content:
+ h1: Understanding Scaleway Savings Plans
+ paragraph: This page explains how Scaleway Savings Plans work.
+tags: billing invoice payment savings plans
+dates:
+ validation: 2024-12-19
+ posted: 2024-06-10
+categories:
+ - billing
+---
+
+Scaleway's Savings Plan is a commitment-based discount program that provides more cost-effective billing compared to the pay-as-you-go model. This plan merges the benefits of discounted rates with the adaptability of pay-as-you-go billing.
+
+## How do Scaleway Savings Plans work?
+
+When you purchase a Savings Plan, you:
+
+- Commit to a specific amount of resource usage each month, calculated before taxes and discounts. This is the usage amount you will be billed for at the Savings Plan rate.
+- Will be charged at the Savings Plan's discounted rate for any usage within your committed amount.
+
+ This means that:
+ - If you use less than what you committed to, you will still be billed for the committed amount with the Savings Plan discount applied.
+ - If you use more than the committed amount, the extra usage will be charged at the regular on-demand rate.
+
+- The Savings Plan discount will apply to the committed amount.
+
+ Commitment rates are calculated based on the public prices of resources before taxes and do not include any discounts.
+
+
+
+
+
+### Eligibility and quotas
+
+Your Organization is eligible to purchase a Savings Plan if:
+ - It does not have any ongoing contracts with Scaleway
+ - You have verified your identity via the Scaleway console
+ - Does not have any outstanding invoices
+
+### Scope
+
+Currently, Scaleway only offers Savings Plans for compute resources.
+
+### Commitment amount
+
+The monthly commitment amount for a Savings Plan must be at least €50 and at most €9,999. The amount you specify will determine in which discount bracket your plan falls.
+
+### Duration
+
+The commitment period can last 12 or 36 months. The longer the commitment, the higher the discount offered.
+
+### Payment options
+
+Payments are made on a monthly basis as part of your regular billing cycle.
+
+### Discounts
+
+Savings Plan discounts are applied automatically to the eligible services.
+
+At Scaleway, the discounts are applied in the following order:
+ - Free tiers or free trials - Savings Plan discounts will apply after any eligible free tier or trials have been used. This ensures that you maximize your free usage before the Savings Plan discount is applied.
+ - Savings plans, and
+ - Discounts (vouchers or credits) - Any applicable vouchers or credits are used and applied after the Savings Plan discount.
+
+Understanding this order helps you optimize your savings and ensure that you make the most of the available discounts.
+
+### Cancellations and exchanges
+
+Savings plans cannot be canceled or exchanged.
+
+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.
+
+### Taxes and currency
+
+The total cost displayed for the Savings Plan does not include applicable taxes. Taxes are displayed on a dedicated section of the invoice.
+
+Currently, we invoice all customers in euros (EUR). If your primary currency is different, our Payment Service Providers (PSPs) apply the prevailing exchange rate.
+
+## How to purchase a Savings Plan
+
+Follow the instructions on the [How to purchase a Savings Plan](/billing/how-to/purchase-savings-plan/) documentation plan to do so.
+
+## Compute Savings Plan
+
+There is currently one available Savings Plan type: the Compute Savings Plan.
+
+The **Compute Savings Plan** can be used with the following resources, simultaneously and across all regions:
+
+ - Instances
+ - Cost-optimized (DEV1, GP1, PLAY2, PRO2)
+ - Production optimized (ENT1, POP2)
+ - Workload optmized (POP2 HC)
+
+The following resources are **not** covered by the Savings Plan discount:
+
+ - Instances H100, RENDER, L40S, L4, COPARM1, START1, X64, POP-WIN
+
+
+
+ The list of products included in the Compute Savings plan is subject to periodic changes.
+
\ No newline at end of file
diff --git a/pages/billing/api-cli/index.mdx b/pages/billing/api-cli/index.mdx
new file mode 100644
index 0000000000..176be958c1
--- /dev/null
+++ b/pages/billing/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Billing - API/CLI
+ description: Billing API/CLI Documentation
+content:
+ h1: Billing - API/CLI
+ paragraph: Billing API/CLI Documentation
+---
diff --git a/pages/billing/api-cli/retrieve-monthly-consumption.mdx b/pages/billing/api-cli/retrieve-monthly-consumption.mdx
new file mode 100644
index 0000000000..1e24232ac8
--- /dev/null
+++ b/pages/billing/api-cli/retrieve-monthly-consumption.mdx
@@ -0,0 +1,106 @@
+---
+meta:
+ title: Retrieving your monthly consumption via the Scaleway API
+ description: This page explains how to retrieve your monthly consumption via the Scaleway API
+content:
+ h1: Retrieving your monthly consumption via the Scaleway API
+ paragraph: This page explains how to retrieve your monthly consumption via the Scaleway API
+tags: billing consumption report api export
+dates:
+ validation: 2024-10-01
+ posted: 2024-03-26
+categories:
+ - billing
+---
+
+Follow the procedure below to download your monthly consumption using the Scaleway [Billing API](https://www.scaleway.com/en/developers/api/billing/#path-consumption-get-monthly-consumption) and `curl`.
+
+
+
+- A Scaleway account and logged into the [console](https://console.scaleway.com/organization)
+- Created an [API key](/iam/how-to/create-api-keys/) with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page
+- [Installed `curl`](https://curl.se/download.html)
+- Configured your environment variables.
+
+## Exporting your environment variables
+
+
+ This is an optional step that aims at simplifying your usage of the API.
+
+
+Open a terminal and run the following command to export your API secret key and Organization ID.
+
+ ```bash
+ export SCW_SECRET_KEY=""
+ export SCW_ORGANIZATION_ID=""
+ ```
+
+## Consumption of the current month
+
+Run the following command to obtain your consumption over the current month.
+
+ ```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/billing/v2beta1/consumptions?organization_id=$SCW_ORGANIZATION_ID"
+ ```
+
+## Consumption of a product category
+
+Run the following command to obtain your consumption over the current month for just one category of products.
+
+ Specify the target `category_name` as one of:
+
+ - `BareMetal`
+ - `Compute`
+ - `Containers`
+ - `Labs`
+ - `Managed Databases`
+ - `Managed Services`
+ - `Network`
+ - `Object Storage`
+ - `Observability`
+ - `Security and Identity`
+ - `Serverless`
+ - `Storage`
+ - `Subscription`
+
+ ```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/billing/v2beta1/consumptions?organization_id=$SCW_ORGANIZATION_ID&category_name=Compute"
+ ```
+
+## Consumption of a specific month
+
+Run the following command to obtain your consumption for a specific month.
+
+ Specify the target billing period as `YYYY-MM`, e.g. `2023-11`.
+
+ ```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/billing/v2beta1/consumptions?organization_id=$SCW_ORGANIZATION_ID&billing_period=2023-11"
+ ```
+
+## Consumption of a specific Project
+
+Run the following command to obtain your consumption for a specific Project only.
+
+ First, choose your target `project_id`:
+
+ ```bash
+ export SCW_PROJECT_ID=""
+ ```
+
+ Then inject it in your API request:
+
+ ```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/billing/v2beta1/consumptions?project_id=SCW_PROJECT_ID"
+ ```
\ No newline at end of file
diff --git a/pages/billing/assets/scaleway-bank-statement.webp b/pages/billing/assets/scaleway-bank-statement.webp
new file mode 100644
index 0000000000..fe61850fcc
Binary files /dev/null and b/pages/billing/assets/scaleway-bank-statement.webp differ
diff --git a/pages/billing/concepts.mdx b/pages/billing/concepts.mdx
new file mode 100644
index 0000000000..531be45f11
--- /dev/null
+++ b/pages/billing/concepts.mdx
@@ -0,0 +1,90 @@
+---
+meta:
+ title: Billing - Concepts
+ description: Understand the key billing concepts in the Scaleway console.
+content:
+ h1: Billing - Concepts
+ paragraph: Understand the key billing concepts in the Scaleway console.
+tags: billing account pricing payment
+dates:
+ validation: 2024-08-13
+categories:
+ - billing
+---
+
+## Billing alerts
+
+The Billing Alerts functionality within the [Scaleway console](https://console.scaleway.com) allows users to oversee and control their expenses efficiently. This feature allows you to create alerts that notify [users](/iam/concepts/#user) when predefined budget thresholds are met. Your alerts can be seamlessly delivered through SMS, email, or API webhook channels.
+
+## Billing API
+
+Scaleway's [Billing API](https://www.scaleway.com/en/developers/api/billing/) allows you to obtain a detailed overview of your cloud consumption and to monitor your expenses programmatically.
+
+## Billing contact
+
+The billing contact is an additional contact who will receive the invoice or payment alerts by email. This allows you to add a person who may not have access to the Scaleway console, but who should be aware of billing, payment documents and notifications. You can add a billing contact directly from the user account section of your [Scaleway console](https://console.scaleway.com).
+
+## Billing cycle
+
+Scaleway issues monthly invoices for most products based on the resource consumption from the preceding month. For certain products, invoices are issued after upfront payment. Once the invoice is issued, the automatic payment occurs within the initial days of each month and will be processed using the preferred [payment method](#payment-methods) of your account.
+
+## Billing information
+
+Consists of information about the Organization that will be billed. They will appear on the invoice and can be modified on the Scaleway console. Find out more about [how to read an invoice](/faq/billing/#how-to-read-my-invoice).
+
+## Consumption pie chart
+
+The consumption pie chart reflects the amount of money spent on the products you've used for the current month, excluding taxes and organized by product category. This chart also includes any applicable discounts. Its monetary value is calculated in real-time, providing an instant overview of your consumption.
+
+## Cost manager
+
+Cost manager is a comprehensive and user-friendly tool to monitor and analyze cloud resource consumption, and costs. It offers a clear and detailed view of consumption data, enabling you to accurately reconcile costs for re-invoicing purposes.
+
+## Free tier
+
+Scaleway offers free tiers for certain products. This means these products can be used at no cost, up to the specified usage limit of the free tier. These limits do not have an expiration date but may be subject to change. Eligible customers can enjoy these select services free of charge when creating an account, with a usage limit in place.
+
+## Free trial
+
+A free trial provides users access to specific products at no cost. However, it is available only for a limited duration and usage quantity.
+
+## IAM billing permission
+
+IAM billing permissions can be given to users to allow them to read and/or manage the Organization's billing. There are two permission sets linked to billing:
+
+ - **Billing read only:** List and read access to billing information. This allows the user to view consumption, invoices, discounts, budget alerts and payment methods.
+ - **Billing Manager:** Full access to billing management. This allows the user to list, read and edit billing contact information, payment information, billing alerts and invoices.
+
+
+ You can give users permissions via [policies](/iam/concepts/#policy), or by adding them to a [group](/iam/concepts/#group) already attached to a relevant policy.
+
+
+## KYC
+
+**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/account/how-to/verify-identity/).
+
+## Pay-as-you-go
+
+Pay-as-you-go is a billing system in which you only pay for what you consume instead of having a pre-defined fixed amount. Scaleway offers a comprehensive suite of public cloud services that operate this way so you can benefit from cost-efficient usage. Our **on-demand** services operate on a pay-as-you-go basis, granting you immediate access to resources at a fixed hourly rate.
+
+## Payment methods
+
+The payment methods registered on your account are used to pay your invoice. You can set one of your payment methods as the default and manage your different payment methods from the console.
+
+## Project
+
+A Project is a grouping of Scaleway [resources](/iam/concepts/#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-regional, meaning resources located in different [regions](/instances/concepts/#region) can be grouped into one single Project. When grouping resources into different Projects, you can use [IAM](/iam/concepts/#iam) to define custom access rights for each Project.
+
+## Pro-rata billing
+
+You are billed pro-rata on certain products for the initial month of a subscription. This means the charge is adjusted to reflect the portion of the first month you used the product. Starting from the second month and onward, you are billed in full at the beginning of each month, covering the entire upcoming billing period in advance. This billing model ensures that you pay for the service based on your actual usage for the first month and then in advance for subsequent months.
+
+## Validation code
+
+Also known as "magic code", "4-digit code" or "verification code". When you [add a payment method](/billing/how-to/add-payment-method/) to your account, Scaleway carries out a dummy transaction with a €1 authorization charge, to check the card's validity. This transaction appears on your bank account statement, where a 4-digit validation code shows in the description of the transaction. You are prompted to enter this code in the console to validate the new payment method.
+
+
+
+## Voucher
+
+A Scaleway voucher provides you with a discount or credits to use on our services. You may receive one as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/account/how-to/create-an-account/) and have a valid payment method. Voucher codes are unique and valid only for a defined period.
diff --git a/pages/billing/how-to/add-billing-contact.mdx b/pages/billing/how-to/add-billing-contact.mdx
new file mode 100644
index 0000000000..02c90649ab
--- /dev/null
+++ b/pages/billing/how-to/add-billing-contact.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to add a billing contact
+ description: Learn how to add a billing contact in the Scaleway console.
+content:
+ h1: How to add a billing contact
+ paragraph: Learn how to add a billing contact in the Scaleway console.
+tags: billing payment contact
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-16
+categories:
+ - billing
+---
+
+**Billing contact** is an additional contact linked to your account who will receive your monthly invoices. This can be useful if invoices in your Organization are handled by another department.
+
+
+
+- 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
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click **Payment and billing** and scroll down to find **Billing contacts**.
+3. Click in the **Billing contacts** area. A pop-up displays.
+4. Enter the new billing contact email address and click **Save** to validate.
+
+
+ The billing contact is only an administrative contact and cannot connect to the Scaleway console.
+
\ No newline at end of file
diff --git a/pages/billing/how-to/add-payment-method.mdx b/pages/billing/how-to/add-payment-method.mdx
new file mode 100644
index 0000000000..ccee5a42bd
--- /dev/null
+++ b/pages/billing/how-to/add-payment-method.mdx
@@ -0,0 +1,70 @@
+---
+meta:
+ title: How to add a payment method
+ description: Step-by-step guide to adding a payment method to your Scaleway account.
+content:
+ h1: How to add a payment method
+ paragraph: Step-by-step guide to adding a payment method to your Scaleway account.
+tags: billing payment sepa credit-card
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-16
+categories:
+ - billing
+---
+
+Before you can order Scaleway resources, you must add a payment method to your account. You can choose between two payment methods: **credit card** or **SEPA mandate**.
+
+
+
+- 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
+
+## How to add a credit card
+
+
+ 1. Access the [Scaleway console](https://console.scaleway.com/organization).
+ 2. On the **Billing** page, click the [Payment and billing](https://console.scaleway.com/billing/payment) tab.
+ 3. Scroll down to **Payment methods** and open the **Credit card** tab.
+ 4. Click the **Add a credit card** button. A pop-up appears.
+ 5. Enter the details of your credit or debit card.
+ 6. Click **Add credit card** to confirm. A [3D Secure](https://en.wikipedia.org/wiki/3-D_Secure) validation is initiated. Depending on your bank, you may be asked to enter a code received by SMS or via an application on your smartphone.
+ 7. Enter the code and validate the form.
+
+ When you register a new credit card, an authorization charge of **€1** is debited from your account. This **Authorization Charge** is a dummy transaction made to check the validity of the card and will carry a 4-digit validation code, displayed on your bank account statement. The authorization charge will be reimbursed within 48 to 72 hours.
+
+ 8. Click **Verify**. A pop-up appears.
+ 9. Enter the 4-digit validation code displayed on your bank account statement.
+
+ * It may take up to 24 hours for the transaction to appear on your bank statement.
+ * Bank account statements have different displays depending on the bank, but the validation code can always be found in the description of your transactions. The image below provides an example of how the validation code might appear in your bank statement:
+
+
+
+
+ You have up to 10 days to enter your validation code in the console.
+
+
+
+
+
+
+
+
+ You can follow the procedure below to add a **debit** card as well.
+
+
+
+## How to add a SEPA mandate
+
+
+ * This method requires a successful [KYC verification](/account/how-to/verify-identity/).
+ * To add a SEPA mandate, both your postal and bank addresses must be part of the [SEPA zone](https://www.ecb.europa.eu/paym/integration/retail/sepa/html/index.en.html).
+
+
+1. Access the [Scaleway console](https://console.scaleway.com/organization).
+2. On the **Billing** page, click the [Payment and billing](https://console.scaleway.com/billing/payment) tab.
+3. Scroll down to **Payment methods** and open the **SEPA Direct Debit** tab.
+4. Click **+Add SEPA mandate**. A pop-up appears.
+5. Enter the required information.
+6. Click **Add SEPA mandate** to confirm.
\ No newline at end of file
diff --git a/pages/billing/how-to/assets/scaleway-bank-statement.webp b/pages/billing/how-to/assets/scaleway-bank-statement.webp
new file mode 100644
index 0000000000..fe61850fcc
Binary files /dev/null and b/pages/billing/how-to/assets/scaleway-bank-statement.webp differ
diff --git a/pages/billing/how-to/assets/scaleway-billing-alerts-warning.webp b/pages/billing/how-to/assets/scaleway-billing-alerts-warning.webp
new file mode 100644
index 0000000000..c09d32cda9
Binary files /dev/null and b/pages/billing/how-to/assets/scaleway-billing-alerts-warning.webp differ
diff --git a/pages/billing/how-to/assets/scaleway-billing-consumption-chart.webp b/pages/billing/how-to/assets/scaleway-billing-consumption-chart.webp
new file mode 100644
index 0000000000..331f5a178e
Binary files /dev/null and b/pages/billing/how-to/assets/scaleway-billing-consumption-chart.webp differ
diff --git a/pages/billing/how-to/assets/scaleway-billing-consumption-list.webp b/pages/billing/how-to/assets/scaleway-billing-consumption-list.webp
new file mode 100644
index 0000000000..00f7bd232a
Binary files /dev/null and b/pages/billing/how-to/assets/scaleway-billing-consumption-list.webp differ
diff --git a/pages/billing/how-to/change-billing-information.mdx b/pages/billing/how-to/change-billing-information.mdx
new file mode 100644
index 0000000000..dee9d98013
--- /dev/null
+++ b/pages/billing/how-to/change-billing-information.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to change your billing information
+ description: Instructions for changing your billing information in the Scaleway console.
+content:
+ h1: How to change your billing information
+ paragraph: Instructions for changing your billing information in the Scaleway console.
+tags: billing payment change address
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-15
+categories:
+ - billing
+---
+
+
+
+- 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
+
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click **Payment and billing** and scroll down to **Billing information**.
+3. Click in the **Billing information** area. A pop-up displays.
+4. Enter your new postal address and click **Confirm changes** to validate.
+
+ Your new billing address is now used for your invoices.
+
+
+ It is not possible to edit your country and region information directly from this form. Contact the [support team](https://console.scaleway.com/support/tickets/) if you need to modify this information.
+
\ No newline at end of file
diff --git a/pages/billing/how-to/change-payment-method.mdx b/pages/billing/how-to/change-payment-method.mdx
new file mode 100644
index 0000000000..42fbe2748a
--- /dev/null
+++ b/pages/billing/how-to/change-payment-method.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: How to change your default payment method
+ description: Learn how to update and manage your payment method in the Scaleway console.
+content:
+ h1: How to change your payment method
+ paragraph: Learn how to update and manage your payment method in the Scaleway console.
+tags: billing change default payment
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-15
+categories:
+ - billing
+---
+
+If you have registered both a **credit card** and a **SEPA mandate**, you can choose the default payment method you wish to use for your Scaleway account.
+
+
+
+- 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
+- A valid credit card added to your account, even if you have set up SEPA as the default payment method.
+
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click **Payment and billing**.
+3. Scroll down to **Payment Methods**.
+4. Select the payment method you wish to use as default.
\ No newline at end of file
diff --git a/pages/billing/how-to/download-an-invoice.mdx b/pages/billing/how-to/download-an-invoice.mdx
new file mode 100644
index 0000000000..f7cf2bd7d3
--- /dev/null
+++ b/pages/billing/how-to/download-an-invoice.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to download an invoice
+ description: Guide to downloading invoices from the Scaleway console.
+content:
+ h1: How to download an invoice
+ paragraph: Guide to downloading invoices from the Scaleway console.
+tags: billing payment invoice download
+dates:
+ validation: 2024-08-27
+ posted: 2024-02-23
+categories:
+ - billing
+---
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) that allow you to perform actions in the intended Organization
+
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ You can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Scroll down to **Recent invoices**.
+
+ You can download all your invoices from the [Payment and billing](https://console.scaleway.com/billing/payment) section of the [billing page](https://console.scaleway.com/billing) by clicking **View all invoices** above the **Recent invoices** area.
+
+3. Click to download a copy of the invoice. The file is saved in **PDF format** in the **Downloads** folder on your system.
\ No newline at end of file
diff --git a/pages/billing/how-to/index.mdx b/pages/billing/how-to/index.mdx
new file mode 100644
index 0000000000..5d2deb7d9c
--- /dev/null
+++ b/pages/billing/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Billing - How Tos
+ description: Billing How Tos
+content:
+ h1: Billing - How Tos
+ paragraph: Billing How Tos
+---
diff --git a/pages/billing/how-to/purchase-savings-plan.mdx b/pages/billing/how-to/purchase-savings-plan.mdx
new file mode 100644
index 0000000000..35b871d7bf
--- /dev/null
+++ b/pages/billing/how-to/purchase-savings-plan.mdx
@@ -0,0 +1,49 @@
+---
+meta:
+ title: How to purchase a Savings Plan
+ description: Learn how to purchase a savings plan to reduce costs on Scaleway services.
+content:
+ h1: How to purchase a Savings Plan
+ paragraph: Learn how to purchase a savings plan to reduce costs on Scaleway services.
+tags: billing payment invoice savings plans
+dates:
+ validation: 2024-12-19
+ posted: 2024-06-10
+categories:
+ - billing
+---
+
+Savings Plans provide a flexible pricing structure designed to optimize costs. By committing to consistent usage, you unlock substantial discounts compared to pay-as-you-go models, resulting in significant long-term savings. Savings plans are available for Compute resources.
+
+For more details about how Savings Plans work, how they are billed and which resources are covered, refer to the [Understanding Savings Plans](/billing/additional-content/understanding-savings-plans/) documentation page.
+
+
+
+- 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
+- A [valid payment method](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) added to your account.
+- A [validated identity](/account/how-to/verify-identity/)
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click the **Cost optimization** tab.
+
+3. Click **Purchase Savings plan**. You are redirected to the purchase wizard.
+
+4. Select a savings plan.
+
+ Currently, Scaleway only offers Savings Plans for compute resources.
+
+5. Select the duration of the plan. You can choose between 12 and 36 months.
+
+ Keep in mind that once purchased, Savings Plans cannot be canceled or exchanged.
+
+6. Enter the monthly commitment amount. The amount must be at least €50.
+7. Review the details of your Savings Plan. The applicable Savings Plan discount is detailed on this section.
+8. Click **Continue**.
+ A pop up appears asking you to confirm the start and end date of the Savings Plan, and that you understand that you will be charged the discounted price for your usage up to your commitment.
+9. Check the boxes and type **PURCHASE** to confirm.
+
+You can check the details of your Savings Plan in the **Cost optimization** section of your Billing space of the Scaleway console anytime.
diff --git a/pages/billing/how-to/redeem-voucher-code.mdx b/pages/billing/how-to/redeem-voucher-code.mdx
new file mode 100644
index 0000000000..178fa7af93
--- /dev/null
+++ b/pages/billing/how-to/redeem-voucher-code.mdx
@@ -0,0 +1,57 @@
+---
+meta:
+ title: How to redeem a Scaleway voucher
+ description: Instructions for redeeming a voucher code in the Scaleway console.
+content:
+ h1: How to redeem a Scaleway voucher
+ paragraph: Instructions for redeeming a voucher code in the Scaleway console.
+tags: discount voucher billing redeem
+dates:
+ validation: 2024-11-26
+ posted: 2024-02-15
+categories:
+ - billing
+---
+
+A Scaleway voucher provides you with a discount or credit to use on our services. You can receive it as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/account/how-to/create-an-account/).
+
+Voucher codes are unique and valid only for a defined period.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) that allow you to perform actions in the intended Organization
+- A valid payment method added to your account.
+
+
+## How to apply a voucher
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click the **Cost optimization** tab.
+
+3. Click **Add voucher**. A pop-up displays.
+
+4. Enter your voucher code, then click **Add voucher**.
+
+
+ The discount applied can either be a percentage of your monthly invoice or a fixed sum.
+
+
+ Once the voucher is redeemed, it will appear in the list of your vouchers.
+
+## Understanding voucher scope
+Vouchers provide discounts or credits to use on our services. However, certain conditions and exclusions apply to their usage.
+
+### Inclusive and Exclusive vouchers
+- **Incl. (Inclusive)**: The voucher applies only to the products or services listed after "Incl." (e.g., "Incl. PRO2," means that the voucher only applies to PRO2 Instances).
+
+- **Excl. (Exclusive)**: The voucher cannot be applied to the products or services listed after "Excl." (e.g., "Excl. Apple Silicon" means that the voucher does not apply to Apple Silicon machines).
+
+### Fees excluded from vouchers
+Some fees are always excluded from voucher applicability:
+
+- **Elastic Metal commitment fees**: These are fixed costs for reserving Elastic Metal servers and cannot be covered by vouchers.
+
+- **Domain names**: Fees for registering, renewing, or managing domain names are not eligible for voucher use.
\ No newline at end of file
diff --git a/pages/billing/how-to/use-billing-alerts.mdx b/pages/billing/how-to/use-billing-alerts.mdx
new file mode 100644
index 0000000000..d00d91d6b5
--- /dev/null
+++ b/pages/billing/how-to/use-billing-alerts.mdx
@@ -0,0 +1,84 @@
+---
+meta:
+ title: How to use billing alerts
+ description: Set up billing alerts to monitor your Scaleway spending.
+content:
+ h1: How to use billing alerts
+ paragraph: Set up billing alerts to monitor your Scaleway spending.
+tags: billing-alert alerts billing budget
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-14
+categories:
+ - billing
+---
+
+Billing alerts allow you to oversee your expenses efficiently. This feature allows you to create alerts that notify you when predefined budget thresholds are met. Your alerts can be seamlessly delivered through SMS, email, or API webhooks.
+
+Your budget, denominated in euros, represents the limit for your expenses. Simultaneously, the threshold corresponds to a predetermined percentage of this budget. You have the autonomy to define both the budget and the threshold within the Scaleway console.
+
+**For example:**
+
+ - If you have defined a budget of €1,000, you may configure an email notification to be sent once you have consumed 50% of this limit. In this case, once your consumption reaches €500, you will receive an email informing you that the limit threshold has been reached.
+
+
+
+- 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
+
+## How to create a billing alert
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click the **Consumption** tab.
+3. Scroll down to **Billing alerts**.
+4. Click **+ Create a billing alert** to configure your first alert. If you already have an alert, click **+ Add alert** A pop-up displays.
+5. Enter your monthly budget.
+
+ If your budget was already set previously, the first budget is the one that applies to all active alerts. You can click next to your budget to change it anytime. This automatically changes the budget for all recurring alerts.
+
+6. Enter the threshold that triggers the alert in percentage.
+7. Select how you want to receive your alerts. You can choose one or more of the following:
+ - SMS notifications - indicate the phone number
+ - E-mail notifications - indicate the email address
+ - Webhook triggers - indicate the webhook URL
+6. Click **Create billing alert** to enable the alert.
+
+ You may configure up to 10 billing alerts based on your monthly budget. To create a new billing alert, click **+ Add alert**, and repeat the steps above.
+
+
+ Billing alerts only provide a rough estimate of what may be charged to your monthly invoice. Additional costs related to your usage before the alert is triggered may still appear on your invoice after the alert is generated. Only your monthly invoice is considered legally valid.
+
+
+### Webhook API Call
+
+When you configure a Webhook, an `HTTP` request is made to the configured URL. It transmits the following information as an `HTTP POST` request to the specified URL:
+
+```
+Header: "Content-Type": "application/json"
+POST /my/configured/webhook
+{
+ "invoice_start_date": ,
+ "threshold":
+}
+```
+## How to delete a billing alert
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+2. Click the **Consumption** tab.
+3. Scroll down to **Billing alerts**.
+4. Click > **Delete alert** next to the alert. A pop-up appears.
+5. Click **Delete alert** to confirm.
+
+## How to delete the alert budget
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+2. Click the **Consumption** tab.
+3. Scroll down to **Billing alerts**.
+4. Click next to the alert budget. A pop-up appears.
+5. Type **DELETE**, then click **Confirm**.
+
+ When you delete a budget, all your alerts are deleted as well.
+
\ No newline at end of file
diff --git a/pages/billing/how-to/use-the-cost-manager.mdx b/pages/billing/how-to/use-the-cost-manager.mdx
new file mode 100644
index 0000000000..eb92d2c1c5
--- /dev/null
+++ b/pages/billing/how-to/use-the-cost-manager.mdx
@@ -0,0 +1,67 @@
+---
+meta:
+ title: How to use the billing cost manager
+ description: Manage and track your costs with the Scaleway Cost Manager.
+content:
+ h1: How to use the billing cost manager
+ paragraph: Manage and track your costs with the Scaleway Cost Manager.
+tags: billing budget cost-manager
+dates:
+ validation: 2024-10-01
+ posted: 2024-03-26
+categories:
+ - billing
+---
+
+The Scaleway cost manager is a comprehensive tool to monitor and analyze cloud resource consumption and costs. It offers a clear and detailed view of consumption data, enabling you to accurately consolidate consumption for re-invoicing purposes.
+
+
+
+- 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
+
+
+1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page.
+
+ Alternatively, you can reach the [billing page](https://console.scaleway.com/billing/overview) from your [Organization Dashboard](https://console.scaleway.com/organization) by clicking **Go to Billing** above the **Current consumption** area.
+
+2. Click the **Consumption** tab.
+3. Scroll to **Cost Manager**.
+
+ An overview of your Organization's consumption is displayed.
+
+4. Filter the data by selecting the different categories in the drop-down, then click **Filter**.
+
+ You can filter by:
+ - **Period** - Currently you can filter by year.
+ - **Category** - The product category (e.g. Compute, Storage, Containers). Each category corresponds to a different color in the consumption chart and in the detailed list.
+
+ If you are filtering by Product, you must first select the Product Category.
+
+ - **Product** - The product itself. The consumption shown is the sum of all your products of the same type. For example, if you select **Instances**, the consumption chart will display the value referring to all Instances in your selected Project.
+ - **Project** - One or all Projects in your Organization. Leave empty to select all at once.
+
+
+ The amount displayed in the chart is the total amount consumed over the period excluding tax, and **excluding** any discounts related to vouchers.
+
+
+
+
+5. Scroll the page to see a detailed list of your resource consumption based on your filter selection.
+
+ The amount displayed is the total amount consumed over the period excluding tax, and **including** any discounts related to vouchers.
+
+
+
+
+ In the list you can see the product categories on the left. They follow the same order as the left menu of the Scaleway console.
+
+ By default, values will be displayed from highest to lowest. You can click the **Cost** column header to change the order.
+
+ If a Project was deleted, its name will appear as **Deleted** in the list.
+
+ You can click **Reset** to clear all filters and start over.
+
+
+ You can retrieve your monthly consumption via the [Billing API](https://www.scaleway.com/en/developers/api/billing/#path-consumption-get-monthly-consumption). Refer to the [Retrieving your monthly consumption](/billing/api-cli/retrieve-monthly-consumption/) documentation page for more information.
+
\ No newline at end of file
diff --git a/pages/billing/index.mdx b/pages/billing/index.mdx
new file mode 100644
index 0000000000..7815846b6a
--- /dev/null
+++ b/pages/billing/index.mdx
@@ -0,0 +1,80 @@
+---
+meta:
+ title: Billing Documentation
+ description: Dive into Scaleway billing with our quickstart guides, how-tos and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## FAQ
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/billing/quickstart.mdx b/pages/billing/quickstart.mdx
new file mode 100644
index 0000000000..afda701bd6
--- /dev/null
+++ b/pages/billing/quickstart.mdx
@@ -0,0 +1,78 @@
+---
+meta:
+ title: Billing - Quickstart
+ description: Quickstart guide to setting up and managing billing in Scaleway.
+content:
+ h1: Billing - Quickstart
+ paragraph: Quickstart guide to setting up and managing billing in Scaleway.
+tags: billing payment
+dates:
+ validation: 2024-08-27
+ posted: 2024-02-20
+categories:
+ - billing
+---
+
+## Console overview
+
+Follow this guided tour to discover how to use the Billing Space.
+
+
+
+Before you can order Scaleway resources, you must add your payment method to your account.
+
+
+- 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
+
+## How to add a payment method
+
+1. Click **Billing** in the Organization drop-down menu to go to the [Billing page](https://console.scaleway.com/billing/overview).
+2. Click **Payment and billing**.
+3. Scroll down to **Payment Methods**.
+
+You can choose between two payment methods: **credit card** or **SEPA mandate**.
+
+### How to add a credit card
+
+1. Enter the details of your credit or debit card.
+2. Click **Add credit card** to confirm. A [3D Secure](https://en.wikipedia.org/wiki/3-D_Secure) validation is initiated. Depending on your bank, you may be asked to enter a code received by SMS or via an application on your smartphone.
+3. Enter the code and validate the form.
+
+ When you register a new credit card, an authorization charge of **€1** is debited from your account. This authorization charge is a **dummy transaction made to check the validity of the card, and will carry a 4-digit validation code**, displayed on **your bank account statement**. The authorization charge will be reimbursed within 48 to 72 hours.
+
+4. Click **Verify**. A pop-up appears.
+5. Enter the 4-digit validation code displayed on your bank account statement.
+
+ Bank account statements have different displays depending on the bank, but the validation code can always be found in the description of your transactions. The image below provides an example of how the validation code might appear in your bank statement:
+
+
+
+
+
+
+ You have up to 10 days to enter your validation code in the console. This helps us secure your account.
+
+
+### How to add a SEPA mandate
+
+
+ This method requires a successful [KYC verification](/account/how-to/verify-identity/).
+
+
+1. Click **SEPA Direct Debit** under **Payment Methods**.
+2. Click **+Add a SEPA mandate**. A pop-up appears.
+3. Enter the required information.
+4. Click **Add a SEPA mandate** to confirm.
+
+### How to change your billing information
+
+1. Click **Billing** in the Organization drop-down menu to go to the [Billing page](https://console.scaleway.com/billing/payment).
+2. Click in the **Billing information** area. A pop-up displays.
+3. Enter your new postal address and click **Confirm changes** to validate.
+
+ Your new billing address is now used for your invoices.
+
+
+ It is not possible to edit your country and region information directly from this form. Contact the [support team](https://console.scaleway.com/support/tickets/) if you need to modify this information.
+
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx b/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx
new file mode 100644
index 0000000000..99e31d24bc
--- /dev/null
+++ b/pages/block-storage/api-cli/identifying-volume-snapshot-api.mdx
@@ -0,0 +1,381 @@
+---
+meta:
+ title: Identifying the API managing Block Storage volumes and snapshots
+ description: Learn how to determine which API (Instance or Block Storage) manages your volumes and snapshots on Scaleway using CLI and API commands.
+content:
+ h1: Identifying the API managing Block Storage volumes and snapshots
+ paragraph: Determine whether your Block Storage volumes and snapshots are managed by the Instance API or Block Storage API.
+dates:
+ validation: 2025-01-13
+ posted: 2025-01-13
+categories:
+ - storage
+---
+
+This page shows you how to identify the API managing your Block Storage volumes and snapshots, using the Scaleway API and CLI.
+
+
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- Created [Block Storage volumes](/block-storage/how-to/create-a-volume/)
+- [Created an API key](/iam/how-to/create-api-keys/) and set [your secret key as an environment variable](/scaleway-sdk/reference-content/environment-variables/#reserved-environment-variables)
+- [Installed curl](https://curl.se/download.html)
+- Installed the [Scaleway CLI](https://cli.scaleway.com/)
+
+## Listing all volumes and snapshots created in a specific Availability Zone
+
+The Scaleway Instance and Block Storage APIs identify their volumes differently. Volumes created with the Instance API are identified as `b_ssd` volumes, whereas volumes created with the Block Storage API are identified as `sbs_5k` or `sbs_15k` volumes.
+
+### Listing volumes created with the Instance API
+
+Open a terminal and run the following command to list your volumes managed by the Instance API. Make sure that you replace `{zone}` with the desired Availability Zone.
+
+ ```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/instance/v1/zones/{zone}/volumes"
+ ```
+Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Instance API. Note that the `volume_type` field is set to `b_ssd`, meaning the volumes were created via the Instance API.
+
+```
+{
+ "volumes": [
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "System volume",
+ "volume_type": "b_ssd",
+ "export_uri": null,
+ "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "server": {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "scw-brave-elion"
+ },
+ "size": 25000000000,
+ "state": "available",
+ "creation_date": "2024-01-30T13:11:15.554809+00:00",
+ "modification_date": "2024-01-30T13:11:17.078820+00:00",
+ "tags": [],
+ "zone": "fr-par-1"
+ },
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "Volume-data",
+ "volume_type": "b_ssd",
+ "export_uri": null,
+ "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "server": {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "scw-brave-elion"
+ },
+ "size": 20000000000,
+ "state": "available",
+ "creation_date": "2024-01-30T13:11:15.554809+00:00",
+ "modification_date": "2024-01-30T13:11:15.554809+00:00",
+ "tags": [],
+ "zone": "fr-par-1"
+ },
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "System volume",
+ "volume_type": "b_ssd",
+ "export_uri": null,
+ "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "server": {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "scw-optimistic-wilbur"
+ },
+ "size": 10000000000,
+ "state": "available",
+ "creation_date": "2023-11-14T12:59:42.932912+00:00",
+ "modification_date": "2023-11-14T12:59:42.932912+00:00",
+ "tags": [],
+ "zone": "fr-par-1"
+ }
+ ]
+}
+```
+
+### Listing volumes created with the Block Storage API
+
+Open a terminal and run the following command to list your volumes managed by the Block Storage API. Make sure that you replace `{zone}` with the desired Availability Zone.
+
+```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/block/v1alpha1/zones/{zone}/volumes"
+```
+
+Below is an example of the output that should display if you have created volumes in the `fr-par-1` Availability Zone using the Block Storage API. Note that the `volume_type` field is set to either `sbs_15k` or `sbs_5k`, meaning the volumes were created via the Block Storage API.
+
+```
+{
+ "volumes": [
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "volume-nifty-allen",
+ "type": "sbs_15k",
+ "size": 25000000000,
+ "status": "in_use",
+ "specs": {
+ "perf_iops": 15000,
+ "class": "sbs"
+ },
+ "zone": "fr-par-1"
+ },
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "volume-xenodochial-mccarthy",
+ "type": "sbs_15k",
+ "size": 30000000000,
+ "status": "in_use",
+ "specs": {
+ "perf_iops": 15000,
+ "class": "sbs"
+ },
+ "zone": "fr-par-1"
+ },
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "volume-interesting-keller",
+ "type": "sbs_5k",
+ "size": 25000000000,
+ "status": "available",
+ "specs": {
+ "perf_iops": 5000,
+ "class": "sbs"
+ },
+ "zone": "fr-par-1"
+ }
+ ],
+ "total_count": 3
+}
+```
+
+## Identifying the API managing snapshots
+
+### Using the Instance API
+
+Open a terminal and run the following command to list all snapshots created via the Instance API. Make sure that you replace `{zone}` with the desired Availability Zone.
+
+```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/instance/v1/zones/{zone}/snapshots"
+```
+An output similar to the following should display:
+
+```
+{
+ "snapshots": [
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "snap-magical-driscoll",
+ "volume_type": "b_ssd",
+ "creation_date": "2024-01-29T15:19:12.357297+00:00",
+ "modification_date": "2024-01-29T15:22:13.885529+00:00",
+ "organization": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "project": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "size": 25000000000,
+ "state": "available",
+ "base_volume": null,
+ "tags": [],
+ "zone": "fr-par-1",
+ "error_details": null
+ }
+ ]
+}
+```
+
+### Using the Block Storage API
+
+Open a terminal and run the following command to list all snapshots created via the Block Storage API. Make sure that you replace `{zone}` with the desired Availability Zone.
+
+```bash
+ curl -X GET \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/block/v1alpha1/zones/{zone}/snapshots"
+```
+
+An output similar to the following should display:
+
+```
+{
+ "snapshots": [
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "snap-elated-thompson",
+ "parent_volume": {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "volume-xenodochial-mccarthy",
+ "type": "sbs_15k",
+ "status": "in_use"
+ },
+ "size": 30000000000,
+ "project_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "created_at": "2024-07-25T14:18:43.929942Z",
+ "updated_at": "2024-07-25T14:18:43.929942Z",
+ "references": [],
+ "status": "available",
+ "tags": [],
+ "class": "sbs",
+ "zone": "fr-par-1"
+ },
+ {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "snap-busy-albattani",
+ "parent_volume": {
+ "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "name": "volume-eloquent-grothendieck",
+ "type": "sbs_5k",
+ "status": "available"
+ },
+ "size": 25000000000,
+ "project_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
+ "created_at": "2024-12-06T10:16:18.565939Z",
+ "updated_at": "2024-12-06T10:16:18.565939Z",
+ "references": [],
+ "status": "available",
+ "tags": [],
+ "class": "sbs",
+ "zone": "fr-par-1"
+ }
+ ]
+}
+```
+
+## Identifying the API managing volumes with the CLI
+
+### Using the Scaleway Instance CLI
+
+1. Open your terminal and run the following command to list all your volumes.
+
+ ```bash
+ scw instance volume list
+ ```
+ An output similar to the following should display:
+ ```
+ ID STATE SERVER ID
+ b582c548-6dc0-4e77-bb93-9615b9baa380 available a4138186-f362-41b2-adc2-c46a2e1a46b7
+ 59d48a65-3501-49eb-9a93-be9a6b262e1e available bc1b3dde-b175-42f1-b322-f6d441fc49ca
+ 49985053-0141-4180-acfa-7f1a51526dac available 4780cdd0-1303-4dfe-9d72-92207eb195b1
+ 7e1a9b98-b7ee-4bbc-8f8f-a7abbfffc937 available 67003b8c-2fe2-4346-a381-405896aa87b4
+ 86bef16c-78db-4125-aa91-1ed9de9a50eb available 67003b8c-2fe2-4346-a381-405896aa87b4
+ 7c232b97-63da-46e3-a018-399e1690b14b available ea5b27d7-268f-40fe-aff7-6943fbcac379
+ 1a506e55-0741-4afd-8fbc-bc086ace0265 available 8860802f-0337-4901-b58c-ba3975922349
+ ```
+2. Note the ID of the volume you want to check the type of.
+3. Get more information about your volume, including its type. Make sure that you replace `` with the ID of the volume.
+ ```bash
+ scw instance volume get
+ ```
+ An output similar to the following should display:
+ ```
+ Volume.ID 7c232b97-63da-46e3-a018-399e1690b14b
+ Volume.Name System volume
+ Volume.Size 10 GB
+ Volume.VolumeType b_ssd
+ Volume.CreationDate 1 year ago
+ Volume.ModificationDate 1 year ago
+ Volume.Organization 0c514155-9e5e-41a2-a900-9fdf0195b563
+ Volume.Project 0c514155-9e5e-41a2-a900-9fdf0195b563
+ Volume.Server.ID ea5b27d7-268f-40fe-aff7-6943fbcac379
+ Volume.Server.Name scw-optimistic-wilbur
+ Volume.State available
+ Volume.Zone fr-par-1
+ ```
+4. Check the `Volume.VolumeType` field to learn if your volume is managed by the Instance API or the Block Storage API. Note that in our example, the `Volume.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API.
+
+### Using the Scaleway Block Storage CLI
+
+Open your terminal and run the following command to list all your volumes.
+ ```bash
+ scw block volume list
+ ```
+An output similar to the following should display:
+ ```
+ ID NAME TYPE SIZE
+ 7a9f3816-7bb7-44ea-a103-832b9685cdc6 volume-nifty-allen sbs_15k 25 GB
+ cdab395b-c1b9-4a3b-a759-2add13eb2bcb volume-xenodochial-mccarthy sbs_15k 30 GB
+ 6708229e-bd8c-46f6-bcec-cd3ab93198b7 volume-interesting-keller sbs_5k 25 GB
+ 672d6c01-465f-43bd-a315-0ac48d49fec5 volume-amazing-lamarr sbs_5k 25 GB
+ 965b5361-01c5-4ca5-81dd-fa0307e36d20 volume-eloquent-grothendieck sbs_5k 25 GB
+ 13307e4a-c075-4421-b9b5-436732a1c739 vol-admiring-noether sbs_5k 25 GB
+ ```
+
+ Note that the `TYPE` field displays `sbs_15k` or `sbs_5k`, meaning our volumes are managed by the Block Storage API.
+
+## Identifying the API managing snapshots with the CLI
+
+### Using the Scaleway Instance CLI
+
+1. Open a terminal and run the following command to list your snapshots:
+
+ ```bash
+ scw instance snapshot list
+ ```
+ An output similar to the following should display:
+ ```
+ ID NAME ORGANIZATION
+ d4b45594-7398-481d-8299-46292e07e404 snap-magical-driscoll 0c514155-9e5e-41a2-a900-9fdf0195b563
+ ```
+2. Note the ID of the snapshot you want to check the type of.
+3. Get more information about your snapshot, including its type. Make sure that you replace `` with the ID of the snapshot.
+ ```bash
+ scw instance snapshot get
+ ```
+ An output similar to the following displays:
+ ```
+ Snapshot.ID d4b45594-7398-481d-8299-46292e07e404
+ Snapshot.Name snap-magical-driscoll
+ Snapshot.Organization 0c514155-9e5e-41a2-a900-9fdf0195b563
+ Snapshot.Project 0c514155-9e5e-41a2-a900-9fdf0195b563
+ Snapshot.VolumeType b_ssd
+ Snapshot.Size 25 GB
+ Snapshot.State available
+ Snapshot.CreationDate 10 months ago
+ Snapshot.ModificationDate 10 months ago
+ Snapshot.Zone fr-par-1
+ ```
+4. Check the `Snapshot.VolumeType` field to see the type of the snapshot. Note that in the example above, the `Snapshot.VolumeType` field displays `b_ssd`, meaning our volume is managed by the Instance API.
+
+### Using the Scaleway Block Storage CLI
+
+1. Open a terminal and run the following command to list your snapshots:
+
+ ```bash
+ scw block snapshot list
+ ```
+ An output similar to the following should display.
+
+ ```
+ ID NAME SIZE PROJECT ID
+ 7f6ab0bd-cd0d-466b-b1e3-bd309dddfcf8 snap-elated-thompson 30 GB 0c514155-9e5e-41a2-a900-9fdf0195b563
+ 92fa0096-30cf-4e7e-a1fe-2fbe73f524b9 snap-busy-albattani 25 GB e53c4255-f982-4d9d-a003-5ea43cb33707
+ ```
+2. Note the ID of the snapshot you want to check the type of.
+3. Get more information about your snapshot, including its type. Make sure that you replace `` with the ID of the snapshot.
+ ```bash
+ scw block snapshot get
+ ```
+ An output similar to the following should display:
+ ```
+ ID 92fa0096-30cf-4e7e-a1fe-2fbe73f524b9
+ Name snap-busy-albattani
+ ParentVolume.ID 965b5361-01c5-4ca5-81dd-fa0307e36d20
+ ParentVolume.Name volume-eloquent-grothendieck
+ ParentVolume.Type sbs_5k
+ ParentVolume.Status available
+ Size 25 GB
+ ProjectID e53c4255-f982-4d9d-a003-5ea43cb33707
+ CreatedAt 1 week ago
+ UpdatedAt 1 week ago
+ Status available
+ Zone fr-par-1
+ Class sbs
+ ```
+4. Check the `ParentVolume.Type` field to see the type of the snapshot. Note that in the example above, the `ParentVolume.Type` field displays `sbs_5k`, meaning our volume is managed by the Block Storage API.
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/index.mdx b/pages/block-storage/api-cli/index.mdx
new file mode 100644
index 0000000000..b35f31ccd3
--- /dev/null
+++ b/pages/block-storage/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Block Storage - API/CLI Documentation
+ description: Block Storage API/CLI Documentation
+content:
+ h1: Block Storage - API/CLI Documentation
+ paragraph: Block Storage API/CLI Documentation
+---
diff --git a/pages/block-storage/api-cli/managing-a-volume.mdx b/pages/block-storage/api-cli/managing-a-volume.mdx
new file mode 100644
index 0000000000..12c0263998
--- /dev/null
+++ b/pages/block-storage/api-cli/managing-a-volume.mdx
@@ -0,0 +1,241 @@
+---
+meta:
+ title: Managing a Block Storage volume
+ description: Master Block Storage with our comprehensive guide. Learn to format, mount, transfer data, and expand partitions efficiently. Perfect for all skill levels.
+content:
+ h1: Managing a Block Storage volume
+ paragraph: Master Block Storage with our comprehensive guide. Learn to format, mount, transfer data, and expand partitions efficiently. Perfect for all skill levels.
+tags: volume block-storage block mount format use
+dates:
+ validation: 2024-12-06
+ posted: 2019-11-29
+categories:
+ - block-storage
+ - storage
+---
+
+This documentation only explains how to mount **additional block volumes to your Instance**, as the root volume of your Instance is already mounted at creation. The volume where your OS is running cannot be mounted.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/concepts/#instance)
+- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance
+
+## Mounting and using a Block Storage volume
+
+In order to mount and use your Block Storage volume, you need to connect to the Instance it is attached to, via SSH.
+Then, check that the volume is available, format it, and mount it following the instructions below.
+
+
+### Verifying device availability
+
+1. Connect to your Instance with `ssh`.
+ ```
+ ssh root@
+ ```
+2. Use the `lsblk` command to confirm that your block volume is available:
+ ```
+ lsblk
+ ```
+
+
+ You should see an output similar to the following. The root Block volume `sda`, runs your OS. The Block volume named `sdb` is the one we will be mounting to the Instance.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk
+ ```
+
+
+ The Scaleway ecosystem uses [GB](https://en.wikipedia.org/wiki/Gigabyte) to define storage sizes and not [GiB](https://en.wikipedia.org/wiki/Gibibyte) as the default on linux.
+
+
+---
+
+### Formatting the Block volume
+
+Formatting your volume prepares it for storing files.
+
+
+ The procedure below describes how to format your volume using the `mkfs` command, which will **erase all data on the volume**.
+
+
+1. Create a file system with the following command. This command uses the `ext4` file system, though you can choose another if you prefer.
+ ```
+ # Make sure that you replace `/dev/sdX` with the name of your volume
+ mkfs.ext4 /dev/sdX
+ ```
+2. Run the following command to check if your file system was correctly created.
+ ```
+ lsblk -f
+ ```
+
+ You should see an output like the following. Check that the `FSTYPE` field matches `ext4` for your Block volume. In this example, we have formatted the `sdb` volume.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk -f
+ NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
+ sda
+ ├─sda1
+ │ ext4 1.0 cloudimg-rootfs
+ │ cf5b092b-9a8b-49e9-980c-b44b5e3ed197 14.5G 18% /
+ ├─sda14
+ │
+ └─sda15
+ vfat FAT32 UEFI D590-3FD4 98.3M 6% /boot/efi
+ sdb ext4 1.0 d36bdf8b-b2ff-4e2b-9736-cc05940aea35
+ ```
+
+---
+
+### Creating the mount point and mounting the Block volume
+
+Once you have created your file system, you need to define where you want to mount your volume, and create a mount point (directory) for it.
+
+1. Create the mount point. Feel free to replace `block-volume` with another name for your mount point.
+ ```
+ mkdir /mnt/block-volume
+ ```
+2. Mount the volume. We recommend that you use the `defaults` option, as in the command below.
+ ```
+ # Make sure that you replace sdX with the name of your volume
+ mount -o defaults /dev/sdX /mnt/block-volume
+ ```
+
+ If you want to see all available options, you can run `man mount` on your Instance.
+
+3. Run the following command to check if your file system was properly mounted:
+ ```
+ lsblk
+ ```
+
+ You should see an output like the following. Check the `MOUNTPOINT` field.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk /mnt/block-volume
+ ```
+
+The `sdb` volume is mounted at `/mnt/block-volume`.
+
+---
+
+### Using fstab for Persistent Mounting
+
+With the current configuration, your volume will not be mounted automatically upon reboot. Use the `/etc/fstab` file to ensure the reboot does not impact your file system.
+
+Run the following command to make sure your volume is automatically mounted to your Instance upon reboot. You must replace `sdX` with your volume.
+
+```
+echo "UUID=$(blkid --output value /dev/sdX | head -n1) /mnt/block-volume ext4 defaults 0 0" >> /etc/fstab
+```
+
+---
+
+### Transferring data from your local machine to the remote Block volume
+
+You may wish to transfer files from your local machine to your Instance's remote Block volume. This can be achieved with [rsync](https://en.wikipedia.org/wiki/Rsync), a tool for efficiently transferring and copying files. The rsync utility is pre-installed on most Linux distributions and macOS.
+
+1. Check that rsync is installed on your local machine with the following command:
+ ```
+ rsync --version
+ ```
+
+ You should see an output similar to the following:
+
+ ```sh no-copy
+ rsync version 3.1.3 protocol version 31
+ Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others.
+ Web site: http://rsync.samba.org/
+ Capabilities:
+ 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
+ socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
+ append, ACLs, xattrs, iconv, symtimes, prealloc
+
+ rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you
+ are welcome to redistribute it under certain conditions. See the GNU
+ General Public Licence for details.
+ ```
+
+
+ If you get a `command not found` output (or similar), you need to install `rsync`:
+ - On Linux Ubuntu and Debian systems, you can do this with the APT package tool using the `sudo apt install rsync` command.
+ - For Linux CentOS/ Fedora, you can use the YUM package manager: `sudo yum install rsync`.
+ - On Mac OSX with the Homebrew package manager, you can use `brew install rsync`.
+
+2. On your local machine, open a new terminal and use the following command to create a file called `hello-world.txt`:
+ ```
+ nano hello-world.txt
+ ```
+
+3. Enter the text `Hello World!`.
+4. Press `Ctrl O`, `Enter`, and `Ctrl X` to save and exit the file.
+5. Enter the following command to transfer the file to your Instance's mounted block volume. Ensure that you use your own Instance's IP address:
+ ```
+ rsync -a hello-world.txt root@:/mnt/block-volume
+ ```
+
+The file is now transferred. You can connect to your Instance again, and use the command `cd /mnt/block-volume ; ls` to check that the file appears in the directory.
+
+---
+
+## Increasing the partition size of the volume with growpart
+
+
+ - We recommend that you make a backup of your data using the [snapshot](/block-storage/how-to/create-a-snapshot/) feature, before increasing the partition size of your volume. This helps you avoid any potential data loss.
+ - You need to have partitioned your volume to follow the procedure below
+ - If the partition you want to resize is mounted, you need to [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand
+
+
+`growpart` allows you to resize partitions. If you have increased the size of the partition's underlying volume, for example, you might want to increase the size of the partition to make use of the additional space.
+
+1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/).
+2. Use the `lsblk` command to identify your volume partition. Ensure that the partition is **not mounted before you resize it**. In the following example, we are resizing `sdb1`:
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 23.3G 0 disk
+ ├─sda1 8:1 0 23.2G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 38.6G 0 disk
+ └─sdb1 8:17 0 18.6G 0 part
+ ```
+
+3. Use `growpart` to increase the partition size of your Block Storage volume (here `sdb1`):
+ ```
+ # Replace /dev/sdX 1 with the name of your partition
+ growpart /dev/sdX 1
+ ```
+
+
+ Make sure that you add a space between the device identifier (`/dev/sdX`) and the partition number (`1`).
+
+
+ You should see an output similar to the following:
+ ```
+ CHANGED: partition=1 start=0 old: size=39061504 end=39061504 new: size=58490880 end=58490880
+ ```
+4. Use `lsblk` to check that the partition was correctly resized. In the following output, you can see in the `SIZE` field that our partition `sbd1` went from `18.6G` (step 2) to `27.9G`.
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk
+ └─sdb1 8:17 0 27.9G 0 part
\ No newline at end of file
diff --git a/pages/block-storage/api-cli/unmounting-a-volume.mdx b/pages/block-storage/api-cli/unmounting-a-volume.mdx
new file mode 100644
index 0000000000..939d2c5479
--- /dev/null
+++ b/pages/block-storage/api-cli/unmounting-a-volume.mdx
@@ -0,0 +1,56 @@
+---
+meta:
+ title: Unmounting a Block Storage volume
+ description: Learn how to safely unmount a Block Storage volume from your Instance, and ensure data integrity.
+content:
+ h1: Unmounting a Block Storage volume
+ paragraph: Learn how to safely unmount a Block Storage volume from your Instance, and ensure data integrity.
+tags: volume block-storage block unmount
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+## Unmounting a Block Storage volume
+
+
+Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command.
+
+
+- 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 an [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume
+
+
+1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console.
+ ```
+ ssh root@
+ ```
+2. Use `lsblk` to check where your volume is mounted. You should see an output similar to the following:
+
+ ```
+ root@scw-heuristic-shtern:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sdb 8:0 0 18.6G 0 disk /mnt/block-volume
+ ```
+3. Unmount the volume to remove it from your current setup. Replace `/mnt/block-volume` with your mount point.
+ ```
+ umount /mnt/block-volume
+ ```
+4. Check that the volume is no longer mounted in the system with `lsblk`. We can see in the example below that `sdb` is no longer mounted at `/mnt/block-volume`.
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sdb 8:0 0 18.6G 0 disk
+ ```
+
+ Remember to edit the `/etc/fstab` file and delete the line corresponding to your block volume if you have used [Persistent Mounting](/block-storage/api-cli/managing-a-volume/#using-fstab-for-persistent-mounting).
+
+
+Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes.
+
diff --git a/pages/block-storage/concepts.mdx b/pages/block-storage/concepts.mdx
new file mode 100644
index 0000000000..3f4ee08eb9
--- /dev/null
+++ b/pages/block-storage/concepts.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Block Storage - Concepts
+ description: Explore essential concepts of Block Storage, including block devices, IOPS, SANs, local volumes, and their roles in enhancing storage performance and reliability.
+content:
+ h1: Block Storage - Concepts
+ paragraph: Explore essential concepts of Block Storage, including block devices, IOPS, SANs, local volumes, and their roles in enhancing storage performance and reliability.
+tags: block storage volumes concept
+dates:
+ validation: 2024-11-13
+categories:
+ - block-storage
+ - storage
+---
+
+## Block device
+
+A block device is a storage volume on a network-connected storage system that is exposed to the guest operating system as if it were a physical disk.
+
+## IOPS
+
+IOPS or Input/Ouptut Operations Per Second, is a unit of measurement that indicates how many input or output operations a storage device is performing per second.
+
+Scaleway Block Storage Low Latency offers two IOPS limits:
+
+- 5000 IOPS (5K IOPS)
+- 15 000 IOPS (15K IOPS)
+
+## Local volume
+
+The local volume of an Instance is an all SSD-based storage solution, using a RAID array for redundancy and performance, that is hosted on the local hypervisor.
+
+## Storage Area Networks (SANs)
+
+A Storage Area Network (SAN) consists of interconnected machines, network infrastructure and storage devices designed for performance and high-availability. Unlike a Network Attached Storage (NAS) which stores all data on a [file level](https://www.scaleway.com/en/blog/understanding-the-different-types-of-storage/#what-is-file-storage), the SAN stores all data on [block level](https://www.scaleway.com/en/blog/understanding-the-different-types-of-storage/#what-is-block-storage), this makes SAN a perfect solution for business critical applications and input/output intense operations like relational databases. The SAN is a network-connected solution, that operates independently from the local hypervisor hosting the virtual Instance. The storage capacity of the block devices on the SAN can be tailored towards your requirements.
+
+## Volumes
+
+A volume is a storage space used by your Instances. Several volumes can be [attached to an Instance](/block-storage/how-to/attach-a-volume/). In addition, they can be [snapshotted](/block-storage/how-to/create-a-snapshot/), [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) or [unmounted](/block-storage/api-cli/unmounting-a-volume/).
\ No newline at end of file
diff --git a/pages/block-storage/how-to/assets/scaleway-attach-volume.webp b/pages/block-storage/how-to/assets/scaleway-attach-volume.webp
new file mode 100644
index 0000000000..fa10e81fed
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-attach-volume.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-block-delete-volume.webp b/pages/block-storage/how-to/assets/scaleway-block-delete-volume.webp
new file mode 100644
index 0000000000..aa5757dbeb
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-block-delete-volume.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-block-storage-attach-instance.webp b/pages/block-storage/how-to/assets/scaleway-block-storage-attach-instance.webp
new file mode 100644
index 0000000000..ed5a01e2fd
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-block-storage-attach-instance.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-choose-region.webp b/pages/block-storage/how-to/assets/scaleway-choose-region.webp
new file mode 100644
index 0000000000..c7451e930c
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-choose-region.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-configure-block-volume.webp b/pages/block-storage/how-to/assets/scaleway-configure-block-volume.webp
new file mode 100644
index 0000000000..02ff6b0e70
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-configure-block-volume.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-create-volume.webp b/pages/block-storage/how-to/assets/scaleway-create-volume.webp
new file mode 100644
index 0000000000..fd31de6593
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-create-volume.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-detach-volume.webp b/pages/block-storage/how-to/assets/scaleway-detach-volume.webp
new file mode 100644
index 0000000000..66a3be2e1b
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-detach-volume.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-increase-volume-modal.webp b/pages/block-storage/how-to/assets/scaleway-increase-volume-modal.webp
new file mode 100644
index 0000000000..5b46e2c0aa
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-increase-volume-modal.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-volume-created.webp b/pages/block-storage/how-to/assets/scaleway-volume-created.webp
new file mode 100644
index 0000000000..c38ec81795
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-volume-created.webp differ
diff --git a/pages/block-storage/how-to/assets/scaleway-volumes-list.webp b/pages/block-storage/how-to/assets/scaleway-volumes-list.webp
new file mode 100644
index 0000000000..80a29448c9
Binary files /dev/null and b/pages/block-storage/how-to/assets/scaleway-volumes-list.webp differ
diff --git a/pages/block-storage/how-to/attach-a-volume.mdx b/pages/block-storage/how-to/attach-a-volume.mdx
new file mode 100644
index 0000000000..e13465979d
--- /dev/null
+++ b/pages/block-storage/how-to/attach-a-volume.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: How to attach a Block Storage volume to an Instance
+ description: This guide explains how to attach a Block Storage volume to a Scaleway Instance. Follow simple steps to manage your storage efficiently.
+content:
+ h1: How to attach a Block Storage volume to an Instance
+ paragraph: This guide explains how to attach a Block Storage volume to a Scaleway Instance. Follow simple steps to manage your storage efficiently.
+tags: attach block storage volume
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+You can attach a Block Storage volume to your Instance at any time, as long as they are both in the same [Availability Zone](/instances/concepts/#availability-zone).
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/)
+- At least one [Instance](/instances/how-to/create-an-instance/)
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. Your volumes display.
+2. Click > **Attach to Instance** next to the volume of your choice. A pop-up displays.
+3. Select the Instance to which you want to attach your volume from the drop-down.
+4. Click **Attach volume to Instance**.
+
+Alternatively, you can attach a Block Storage volume the following way:
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays.
+2. Click **Attach an Instance** under the **Linked Instance** section.
+
+3. Select the Instance to which you want to attach your volume from the drop-down.
+4. Click **Attach volume to Instance**.
+
+
+ You can attach up to 15 volumes at a time to a single Instance.
+
+
+ To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
+
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
+ This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+
+
+
diff --git a/pages/block-storage/how-to/create-a-snapshot.mdx b/pages/block-storage/how-to/create-a-snapshot.mdx
new file mode 100644
index 0000000000..0d889058cd
--- /dev/null
+++ b/pages/block-storage/how-to/create-a-snapshot.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to create a snapshot of a Block Storage volume
+ description: Discover how to easily create a snapshot of a Block Storage volume. Follow our step-by-step guide to efficiently manage your storage resources.
+content:
+ h1: How to create a snapshot of a Block Storage volume
+ paragraph: Discover how to easily create a snapshot of a Block Storage volume. Follow our step-by-step guide to efficiently manage your storage resources.
+tags: create snapshot block storage volume
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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
+- A [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu.
+2. Click > **Create snapshot** next to the volume of your choice. A pop-up displays.
+3. Enter a name for the new snapshot.
+4. Click **Create snapshot** to confirm.
+
+The new snapshot can be found in the **Snapshots** tab.
+
+Alternatively, you can create a snapshot the following way:
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu.
+2. Click the **Snapshots** tab.
+3. Click **Create snapshot**.
+4. Enter a name for the new snapshot.
+5. Select the volume you want to snapshot from the drop-down.
+6. Click **Create snapshot**.
\ No newline at end of file
diff --git a/pages/block-storage/how-to/create-a-volume.mdx b/pages/block-storage/how-to/create-a-volume.mdx
new file mode 100644
index 0000000000..e1c3869364
--- /dev/null
+++ b/pages/block-storage/how-to/create-a-volume.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: How to create a Block Storage low latency volume
+ description: Learn how to efficiently create a low-latency Block Storage volume with our detailed step-by-step guide. Enhance your storage performance seamlessly.
+content:
+ h1: How to create a Block Storage low latency volume
+ paragraph: Learn how to efficiently create a low-latency Block Storage volume with our detailed step-by-step guide. Enhance your storage performance seamlessly.
+tags: create block storage volume add
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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
+
+
+ This procedure refers to low latency block volumes. To create legacy block volumes, refer the [dedicated documentation](/instances/how-to/create-a-block-volume/).
+
+
+1. Click **Block Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com) side menu. The Block Storage page displays.
+2. Click **+ Create volume**.
+3. Follow the steps in the creation wizard:
+ - Choose an [Availability Zone](/instances/concepts/#availability-zone).
+ - Configure the volume:
+ - Enter a name for your volume or leave the automatically generated name.
+ - Select an [IOPS](/block-storage/concepts/#iops).
+
+ You cannot edit the IOPS after you create your volume.
+
+
+ To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
+
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
+ This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+
+
+ - Define a volume size.
+
+ The volume size must be at least 5GB.
+
+ - Select an Instance from the drop-down to attach your volume. This step is optional.
+ - Check the estimated cost.
+4. Click **Create volume**. The volumes overview page displays.
+
+ The volume must be in the same Availability Zone as the Instance you want to connect it to.
+
+
+
diff --git a/pages/block-storage/how-to/create-volume-from-snapshot.mdx b/pages/block-storage/how-to/create-volume-from-snapshot.mdx
new file mode 100644
index 0000000000..08019da6b1
--- /dev/null
+++ b/pages/block-storage/how-to/create-volume-from-snapshot.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to create a Block Storage volume from a snapshot
+ description: Discover how to efficiently create a Block Storage volume from a snapshot with our comprehensive step-by-step guide. Optimize your storage workflow effortlessly.
+content:
+ h1: How to create a Block Storage volume from a snapshot
+ paragraph: Discover how to efficiently create a Block Storage volume from a snapshot with our comprehensive step-by-step guide. Optimize your storage workflow effortlessly.
+tags: create snapshot block storage volume
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/)
+- Created a [snapshot](/block-storage/how-to/create-a-snapshot/)
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays.
+2. Click the **Snapshots** tab.
+3. Click > **Volume from snapshot** next to the snapshot of your choice. A pop-up displays.
+4. Enter a name for the new volume, or leave the suggested name.
+5. Select an [IOPS](/block-storage/concepts/#iops).
+
+ You cannot edit the IOPS after you create your volume.
+
+6. Click **Create volume from snapshot**.
+
+The new volume appears in your volumes list.
+
+
diff --git a/pages/block-storage/how-to/delete-a-snapshot.mdx b/pages/block-storage/how-to/delete-a-snapshot.mdx
new file mode 100644
index 0000000000..cf0e3f5e28
--- /dev/null
+++ b/pages/block-storage/how-to/delete-a-snapshot.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to delete a volume snapshot
+ description: This guide explains the steps to safely delete a volume snapshot from your Scaleway account.
+content:
+ h1: How to delete a volume snapshot
+ paragraph: This guide explains the steps to safely delete a volume snapshot from your Scaleway account.
+tags: delete snapshot block volume storage
+dates:
+ validation: 2024-12-06
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. A list of your volumes displays.
+2. Click the **Snapshots** tab.
+3. Click > **Delete** next to the snapshot of your choice. A pop-up displays.
+4. Type `DELETE` to confirm.
+5. Click **Delete this snapshot**.
+
+ This action permanently deletes your snapshot and all the data it contains. If you do not want to lose this data, make a backup before deleting the snapshot.
+
+
+
diff --git a/pages/block-storage/how-to/delete-a-volume.mdx b/pages/block-storage/how-to/delete-a-volume.mdx
new file mode 100644
index 0000000000..8f8057beca
--- /dev/null
+++ b/pages/block-storage/how-to/delete-a-volume.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to delete a Block Storage volume
+ description: This guide explains the steps to safely delete a Block Storage volume from your Scaleway account.
+content:
+ h1: How to delete a Block Storage volume
+ paragraph: This guide explains the steps to safely delete a Block Storage volume from your Scaleway account.
+tags: delete cancel terminate block volume storage
+dates:
+ validation: 2024-12-19
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+
+ - You must detach your volume from the Instance it is attached to before deleting the volume. Refer to our documentation to find out [how to do so](/block-storage/how-to/detach-a-volume/).
+ - We highly recommend that you [unmount](/block-storage/api-cli/unmounting-a-volume/) your volume from the operating system before detaching it, to avoid data loss.
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. A list of your volumes displays.
+2. Click the icon next to the volume of your choice, then click **Delete**. A pop-up displays.
+3. Type `DELETE` to confirm.
+4. Click **Delete volume**.
+
+ This action permanently deletes your volume and all the data it contains. If you do not want to lose this data, make a backup before deleting the volume.
+
+
+
diff --git a/pages/block-storage/how-to/detach-a-volume.mdx b/pages/block-storage/how-to/detach-a-volume.mdx
new file mode 100644
index 0000000000..a00e0c970b
--- /dev/null
+++ b/pages/block-storage/how-to/detach-a-volume.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to detach a Block Storage volume
+ description: Learn how to safely detach a Block Storage volume from your Scaleway Instance.
+content:
+ h1: How to detach a Block Storage volume
+ paragraph: Learn how to safely detach a Block Storage volume from your Scaleway Instance.
+tags: detach unlock disconnect block storage volume
+dates:
+ validation: 2024-12-19
+ posted: 2020-01-10
+categories:
+ - block-storage
+ - storage
+---
+
+You can detach a Block Storage volume from your Instance at any time. It is important to [unmount the volume](/block-storage/api-cli/unmounting-a-volume/) from the operating system before detaching it to avoid data loss.
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/) that is [attached](/block-storage/how-to/attach-a-volume/) to an Instance
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays.
+2. Click > **Detach from Instance** next to the volume of your choice. A pop-up displays.
+3. Click **Detach volume from Instance** to confirm.
+
+
diff --git a/pages/block-storage/how-to/increase-block-volume.mdx b/pages/block-storage/how-to/increase-block-volume.mdx
new file mode 100644
index 0000000000..e53b1c2a93
--- /dev/null
+++ b/pages/block-storage/how-to/increase-block-volume.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to increase the size of your Block Storage volumes
+ description: Learn how to easily increase the size of your Scaleway Block Storage volumes for more storage capacity.
+content:
+ h1: How to increase the size of your Block Storage volumes
+ paragraph: Learn how to easily increase the size of your Scaleway Block Storage volumes for more storage capacity.
+tags: block storage block-storage increase maximize expand volume size
+dates:
+ validation: 2024-12-19
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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 [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+
+1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays.
+2. Click the icon next to the volume of your choice, then click **Increase size**. A pop-up displays.
+3. Increase the size according to your preference with the button.
+4. Click **Update volume size** to confirm.
+
+ The maximum size of a Block volume is 10 TB.
+
+
+
+ Refer to our [dedicated documentation](/block-storage/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase your volume's partition size.
+
+
+
diff --git a/pages/block-storage/how-to/index.mdx b/pages/block-storage/how-to/index.mdx
new file mode 100644
index 0000000000..21ee4f5e06
--- /dev/null
+++ b/pages/block-storage/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Block Storage - How Tos
+ description: Block Storage How Tos
+content:
+ h1: Block Storage - How Tos
+ paragraph: Block Storage How Tos
+---
diff --git a/pages/block-storage/how-to/unmount-a-volume.mdx b/pages/block-storage/how-to/unmount-a-volume.mdx
new file mode 100644
index 0000000000..1e37a869b3
--- /dev/null
+++ b/pages/block-storage/how-to/unmount-a-volume.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: How to unmount a Block Storage volume
+ description: This guide explains how to safely unmount a Block Storage volume from your Scaleway Instance to avoid data loss.
+content:
+ h1: How to unmount a Block Storage volume
+ paragraph: This guide explains how to safely unmount a Block Storage volume from your Scaleway Instance to avoid data loss.
+tags: unmount umount disconnect unlink block volume
+dates:
+ validation: 2024-12-06
+ posted: 2019-11-29
+categories:
+ - block-storage
+ - storage
+---
+
+Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command.
+
+
+
+- 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 an [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume
+
+
+1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console.
+ ```
+ ssh root@
+ ```
+2. Use `lsblk` to check where your volume is mounted. You should see an output similar to the following:
+
+ ```
+ root@scw-heuristic-shtern:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sdb 8:0 0 18.6G 0 disk /mnt/block-volume
+ ```
+3. Unmount the volume to remove it from your current setup. Replace `/mnt/block-volume` with your mount point.
+ ```
+ umount /mnt/block-volume
+ ```
+4. Check that the volume is no longer mounted in the system with `lsblk`.
+ ```
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sdb 8:0 0 18.6G 0 disk
+ ```
+
+ Do not forget to edit the `/etc/fstab` file and delete the line corresponding to your block volume.
+
+
+Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes.
+
+
diff --git a/pages/block-storage/index.mdx b/pages/block-storage/index.mdx
new file mode 100644
index 0000000000..fe074692b9
--- /dev/null
+++ b/pages/block-storage/index.mdx
@@ -0,0 +1,84 @@
+---
+meta:
+ title: Block Storage Low Latency Documentation
+ description: Explore Scaleway Block Storage Low Latency with quickstart guides, how-tos, and more.
+---
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+## API/CLI
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/block-storage/quickstart.mdx b/pages/block-storage/quickstart.mdx
new file mode 100644
index 0000000000..534647fff7
--- /dev/null
+++ b/pages/block-storage/quickstart.mdx
@@ -0,0 +1,172 @@
+---
+meta:
+ title: Block Storage - Quickstart
+ description: Get started with Scaleway Block Storage. This guide covers creating, attaching, and mounting Block Storage volumes to your Instances for efficient data management.
+content:
+ h1: Block Storage - Quickstart
+ paragraph: Get started with Scaleway Block Storage. This guide covers creating, attaching, and mounting Block Storage volumes to your Instances for efficient data management.
+tags: block storage overview get started
+dates:
+ validation: 2025-01-07
+ posted: 2023-11-23
+categories:
+ - block-storage
+ - storage
+---
+
+Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone).
+
+From the user's point of view, once [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk.
+
+
+
+
+
+- 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 an [Instance](/instances/how-to/create-an-instance/)
+
+## How to create a Block Storage volume
+
+1. Click **Block Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com) side menu. The Block Storage page displays.
+2. Click **+ Create volume**.
+3. Follow the steps in the creation wizard:
+ - Choose an [Availability Zone](/instances/concepts/#availability-zone).
+ - Configure the volume:
+ - Enter a name for your volume or leave the automatically generated name.
+ - Select an [IOPS](/block-storage/concepts/#iops).
+
+ You cannot edit the IOPS after you create your volume.
+
+
+ - Define a volume size.
+
+ The volume size must be at least 5GB.
+
+ - Select an Instance from the drop-down to attach your volume. This step is optional.
+ - Check the estimated cost.
+4. Click **Create volume**. The volume's **Overview** page displays.
+
+
+ The volume must be in the same Availability Zone as the Instance you want to connect it to.
+
+
+
+## How to attach a Block Storage volume to an Instance
+
+1. Click **Block Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com) side menu. Your volumes display.
+2. Click > **Attach to Instance** next to the volume of your choice. A pop-up displays.
+3. Select the Instance to which you want to attach your volume from the drop-down.
+4. Click **Attach volume to Instance**.
+
+## How to mount and use a Block Storage volume
+
+In order to mount and use your Block Storage volume, you need to [connect to the Instance it is attached to via SSH](/instances/how-to/connect-to-instance/#troubleshooting-connection-problems).
+Then, check that the volume is available, format it, and mount it, following the instructions below.
+
+### How to verify device availability
+
+1. Open a terminal and use the following command to connect to your Instance. Replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console.
+ ```
+ ssh root@
+ ```
+2. Use the `lsblk` command to confirm that your volume is available:
+ ```
+ lsblk
+ ```
+
+
+ You should see an output similar to the following. The root Block volume `sda`, runs your OS. The Block volume named `sdb` is the one we will be mounting to the Instance.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk
+ ```
+
+
+ The Scaleway ecosystem uses [GB](https://en.wikipedia.org/wiki/Gigabyte) to define storage sizes and not [GiB](https://en.wikipedia.org/wiki/Gibibyte) as the default on linux.
+
+
+
+### How to format the Block Storage volume
+
+Formatting your volume prepares it for storing files.
+
+1. In the same terminal as the steps above, create a file system with the following command. This command uses the `ext4` file system, though you can choose another if you prefer.
+ ```
+ # Make sure that you replace `/dev/sdX` with the name of your volume
+ mkfs.ext4 /dev/sdX
+ ```
+2. Run the following command to check if your file system is correctly created:
+ ```
+ lsblk -f
+ ```
+
+ You should see an output like the following. Check that the `FSTYPE` field matches `ext4` for your Block volume. In this example, we have formatted the `sdb` volume.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk -f
+ NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
+ sda
+ ├─sda1
+ │ ext4 1.0 cloudimg-rootfs
+ │ cf5b092b-9a8b-49e9-980c-b44b5e3ed197 14.5G 18% /
+ ├─sda14
+ │
+ └─sda15
+ vfat FAT32 UEFI D590-3FD4 98.3M 6% /boot/efi
+ sdb ext4 1.0 d36bdf8b-b2ff-4e2b-9736-cc05940aea35
+ ```
+
+
+### How to mount the Block Storage volume
+
+Once you have created your file system, you need to define where you want to mount your volume, and create a mount point (directory) for it.
+
+1. Create the mount point. Feel free to replace `block-volume` with another name for your mount point.
+ ```
+ mkdir /mnt/block-volume
+ ```
+2. Mount the volume. We recommend that you use the `defaults` option, as in the command below.
+ ```
+ # Make sure that you replace sdX with the name of your volume
+ mount -o defaults /dev/sdX /mnt/block-volume
+ ```
+
+ If you want to see all available options, you can run `man mount` on your Instance.
+
+3. Make sure your file system is properly mounted by running the `lsblk` command.
+ ```
+ lsblk
+ ```
+
+ You should see an output like the following. Check the `MOUNTPOINT` field.
+
+ ```sh no-copy
+ root@scw-festive-agnesi:~# lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sda 8:0 0 18.6G 0 disk
+ ├─sda1 8:1 0 18.5G 0 part /
+ ├─sda14 8:14 0 4M 0 part
+ └─sda15 8:15 0 106M 0 part /boot/efi
+ sdb 8:16 0 27.9G 0 disk /mnt/block-volume
+ ```
+
+The `sdb` volume is mounted at `/mnt/block-volume`
+
+### How to use fstab for Persistent Mounting
+
+With the current configuration, your volume will not be mounted automatically upon reboot. Use the `/etc/fstab` file to ensure the reboot does not impact your file system.
+
+Run the following command to make sure your volume is automatically mounted to your Instance upon reboot. You must replace `sdX` with your volume.
+
+```
+echo "UUID=$(blkid --output value /dev/sdX | head -n1) /mnt/block-volume ext4 defaults 0 0" >> /etc/fstab
+```
+
+You can now use your Block Storage volume like a regular disk of your Instance, and store data on it as you wish.
\ No newline at end of file
diff --git a/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx b/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx
new file mode 100644
index 0000000000..ac09e40abc
--- /dev/null
+++ b/pages/block-storage/reference-content/advantages-migrating-to-sbs.mdx
@@ -0,0 +1,101 @@
+---
+meta:
+ title: Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots
+ description: Learn the key advantages of migrating to the Block Storage API for managing your Block Storage volumes and snapshots.
+content:
+ h1: Advantages of migrating from the Instance API to the Block Storage API for managing block volumes and snapshots
+ paragraph: Learn the key advantages of migrating to the Block Storage API for managing your Block Storage volumes and snapshots.
+tags: volumes block-storage 5kiops 10kiops sbs low-latency migration
+dates:
+ validation: 2025-01-14
+ posted: 2025-01-14
+categories:
+ - storage
+---
+
+This page explains why **Instance users** should migrate from the Instance API to the Block Storage API to create and manage block volumes and snapshots.
+
+
+
+## Transitioning from the Instance API to the Block Storage API for volume and snapshot management
+
+Scaleway is transitioning the management of all Block Storage volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/).
+
+This change streamlines how storage resources are managed by consolidating them under the Block Storage API, providing enhanced management features and clearer storage class distinctions.
+
+Local volumes will remain exclusively supported by the Instance API.
+
+## What is required from you in the context of the migration?
+
+If you have created volumes and snapshots via the Instance API, you **must transition to the Block Storage API** to align with the latest management practices.
+
+This entails [migrating your existing volumes and snapshots to the Block Storage API](/instances/how-to/migrate-volumes-snapshots-to-sbs/), and **switching to using only the Block Storage API for Block Storage volumes and snapshots creation and management**.
+
+
+ Unified volume creation and management will no longer be available via the Block Storage API and will no longer be supported by the Instance API at the end of the migration. For this reason, it is also necessary to convert your existing unified volumes and snapshots to either local or block volumes.
+
+
+## What will happen at the end of the migration?
+
+From **April 30th 2025, it will no longer be possible to create Block volumes through the Instance API**.
+
+From **June 2nd, 2025, all block volumes and snapshots that you have not migrated manually will be automatically switched behind the Block Storage API**.
+
+What's more, creating and managing block volumes and snapshots through the Instance API will no longer be possible. The Instance API will only allow you to create and manage local volumes and snapshots.
+
+Creating and managing block volumes and snapshots will **only be available via the Block Storage API**.
+
+## Differences between the Instance API and the Block Storage API
+
+The key differences between the Instance API and the Block Storage API lie in the storage classes they manage, rather than just the APIs themselves. The [Block Storage API](https://www.scaleway.com/en/developers/api/block/) is the only API to use to create and manage all types of volumes, including high performance ones.
+
+### Storage classes
+
+The Instance API handles only **BSSD (Basic SSD)** volumes.
+The Block Storage API supports a broader range of storage classes, including:
+
+ - **BSSD volumes**
+ - **Scaleway Block Storage (SBS) 5K IOPS volumes**
+ - **Scaleway Block Storage (SBS) 15K IOPS volumes**
+
+### Underlying hardware
+
+**BSSD volumes** (managed by both APIs) are built on **older-generation SSDs**, offering reliable performance but with limitations in speed and latency.
+
+**Scaleway Block Storage 5K and 15K volumes** (managed only by the Block Storage API) are powered by **modern NVMe (Non-Volatile Memory Express) disks**. They are optimized for **low-latency and high-speed operations**.
+
+### Performance and latency
+
+**BSSD volumes**:
+
+ - **Performance**: Limited IOPS and slower data processing speed due to older SSD technology.
+ - **Latency**: Higher latency, less suitable for applications requiring rapid data retrieval.
+
+**Scaleway Block Storage 5K and 15K volumes**:
+
+ - **Performance**: Enhanced performance with up to 5K IOPS (SBS 5K) and 15K IOPS (SBS 15K).
+ - **Latency**: Lower latency, ideal for workloads demanding rapid and reliable data access.
+
+## Why transition to the Block Storage API?
+
+By transitioning to the Block Storage API, you align with Scaleway's consolidated storage management approach and gain access to advanced storage features and flexibility. While migrating to the Block Storage API does not inherently change the performance of BSSD volumes, you benefit from:
+
+- **Unified management**: Simplified volume and snapshot management through a dedicated API.
+- **Access to advanced storage classes**: You can create new Scaleway Block Storage 5K or 15K volumes for workloads needing higher performance and lower latency.
+- **Ongoing support**: Enhanced support and updates tailored for Block Storage API-managed resources.
+
+## Impact on volume names in virtual machines
+
+When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, refer to [our documentation on identifying devices on a Scaleway Instance](/instances/reference-content/identify-devices/).
+
+## How to transition?
+
+- For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/instances/how-to/migrate-volumes-snapshots-to-sbs/).
+
+- To identify which API manages your volumes and snapshots, refer to the [dedicated documentation](/block-storage/api-cli/identifying-volume-snapshot-api/).
+
+- To find out how to convert a Block Storage legacy volume into a Block Storage Low Latency volume, read [the dedicated documentation](/faq/blockstorage/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume).
+
+---
+
+This transition ensures Scaleway can continue to provide robust, scalable, and high-performance storage solutions tailored to your needs. If you have questions or need assistance, [contact our support team](https://console.scaleway.com/support/tickets/create).
\ No newline at end of file
diff --git a/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx
new file mode 100644
index 0000000000..44779b2043
--- /dev/null
+++ b/pages/block-storage/reference-content/differences-between-5kiops-volumes.mdx
@@ -0,0 +1,65 @@
+---
+meta:
+ title: Understand the difference between Block Storage volumes and Block Storage Low Latency volumes
+ description: Learn the key differences between Block Storage and Block Storage Low Latency 5K IOPS volumes to choose the optimal storage solution for your needs.
+content:
+ h1: Understand the difference between Block Storage volumes and Block Storage Low Latency volumes
+ paragraph: Learn the key differences between Block Storage and Block Storage Low Latency 5K IOPS volumes to choose the optimal storage solution for your needs.
+tags: differences-5kiops volumes block-storage 5kiops
+dates:
+ validation: 2024-09-05
+ posted: 2024-09-05
+categories:
+ - storage
+---
+
+When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/instances/concepts/#volumes).
+
+This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/block-storage/concepts/#iops) volumes.
+
+Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes.
+
+## Underlying hardware
+
+ - **Block Storage 5K IOPS volumes**:
+
+ - They are built using older-generation SSDs. This means that the hardware is slower, as it uses older SSD technology.
+ - The 5K IOPS is split between read and write operations, resulting in a total of 10K IOPS (5K for reads and 5K for writes).
+
+ - **Block Storage Low Latency 5K IOPS volumes**:
+
+ - They are powered by modern NVMe (Non-Volatile Memory Express) disks.
+ - NVMe technology provides better performance and is optimized for high-speed storage operations.
+
+## Performance
+
+ - **Block Storage 5K IOPS volumes**:
+
+ - Their performance is limited by the older SSD hardware, which can result in slower data access and higher latency.
+ - The older technology may impact overall speed and responsiveness.
+
+ - **Block Storage Low Latency 5K IOPS volumes**:
+
+ - Delivers better performance thanks to NVMe disks, which handle 5K IOPS for both read and write operations combined.
+ - This provides a significant boost in data processing speed and efficiency.
+
+## Latency
+
+ - **Block Storage 5K IOPS volumes**:
+
+ - Higher latency due to the use of older SSDs.
+ - This can lead to slower application response times, especially in scenarios requiring rapid data access.
+
+ - **Block Storage Low Latency 5K IOPS volumes**:
+
+ - Offers lower latency and faster access times, making it ideal for applications that require quick data retrieval.
+ - The use of NVMe technology ensures a smoother and more responsive experience.
+
+
+## Summary
+
+- **Block Storage 5K IOPS volumes** rely on older, slower SSD technology, leading to higher latency and lower overall performance.
+
+- **Block Storage Low Latency 5K IOPS volumes** use advanced NVMe disks, offering improved performance, lower latency, and faster data access.
+
+For tasks where performance and low latency are crucial, Block Storage Low Latency volumes provide a more effective solution due to the modern hardware and technological improvements.
\ No newline at end of file
diff --git a/pages/block-storage/reference-content/index.mdx b/pages/block-storage/reference-content/index.mdx
new file mode 100644
index 0000000000..d4ee4be997
--- /dev/null
+++ b/pages/block-storage/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Block Storage - Additional Content
+ description: Block Storage Additional Content
+content:
+ h1: Block Storage - Additional Content
+ paragraph: Block Storage Additional Content
+---
diff --git a/pages/classic-hosting/assets/scaleway_create_email.webp b/pages/classic-hosting/assets/scaleway_create_email.webp
new file mode 100644
index 0000000000..7b39e7e6b3
Binary files /dev/null and b/pages/classic-hosting/assets/scaleway_create_email.webp differ
diff --git a/pages/classic-hosting/assets/scaleway_ftp_tab.webp b/pages/classic-hosting/assets/scaleway_ftp_tab.webp
new file mode 100644
index 0000000000..46095dfcdc
Binary files /dev/null and b/pages/classic-hosting/assets/scaleway_ftp_tab.webp differ
diff --git a/pages/classic-hosting/concepts.mdx b/pages/classic-hosting/concepts.mdx
new file mode 100644
index 0000000000..1bec03c521
--- /dev/null
+++ b/pages/classic-hosting/concepts.mdx
@@ -0,0 +1,61 @@
+---
+meta:
+ title: Webhosting Classic - Concepts
+ description: This page explains all the concepts related to Webhosting Classic
+content:
+ h1: Webhosting Classic - Concepts
+ paragraph: This page explains all the concepts related to Webhosting Classic
+tags: webhosting alias cloud-hosting ftp-account ftp htaccess php
+dates:
+ validation: 2024-08-19
+categories:
+ - webhosting
+---
+
+## Alias
+
+An email alias is an additional email address for an email account with which a user can send and receive emails or set forwards to. A single user account can have multiple email aliases with the same or different domains.
+
+## Cloud hosting
+
+Cloud hosting uses Scaleway cloud Instances for your hosting needs. With this option, you can benefit from all the technologies and features of the cloud. Cloud hosting solutions work with all CMS and PHP frameworks. Storage is via SSD, giving better performance.
+
+## Email account
+
+An email account is an email address in which mail is stored (unlike an alias / catchall). You can check your mail accounts via two protocols: POP3 and IMAP.
+
+## FTP account
+
+FTP, or File Transfer Protocol, is a protocol that allows you to transfer files between different computers over the internet. With our Webhosting service, you can transfer your files from your computer to Scaleway.com - for example, to update your website. It also works vice versa: you can recover the files stored on Scaleway.com and transfer them to your personal computer, for example to make a backup.
+
+## Filtering
+
+Filtering allows you to sort your emails depending on different criteria (the sender, the subject, the object and much more). If the email meets one or more criteria, you can define different actions (delete the email, move it into a folder, etc.).
+
+## htaccess
+
+`.htaccess` is a simple text file containing commands for the Apache web server configuration. It allows you to personalize the server dynamically and per folder. The configuration values are inherited through directories. Common applications for setting up a `.htaccess` file are switching between PHP4 and PHP5, partial website protection, website redirectioning, or error messages customization. Once on the server, its name must be `.htaccess` with a point ahead.
+
+## PHP
+
+PHP is a server-side scripting language designed for web development, but also used as a general-purpose programming language. While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext Preprocessor, which is a recursive backronym.
+
+## php.ini
+
+The `php.ini` file is the configuration file used for applications that require PHP. It contains the configuration of variables such as upload sizes, file timeouts, and resource limits. At Scaleway, we provide PHP with the most common values preconfigured for each webhosting. If required, you can [customize the configuration of PHP](/classic-hosting/how-to/configure-php/) towards your needs.
+
+## Redirection
+
+A redirection is an alternative email address for one or multiple email accounts of the same domain. For example, you can create the alias `[contact@example.com](mailto:contact@example.com)`, which will redirect the mail to the personal email account `[firstname.lastname@example.com](mailto:firstname.lastname@example.com)`.
+This allows you to not only have multiple email addresses without needing multiple email accounts, but also to deliver the email to multiple recipients.
+
+## Webhosting
+
+Webhosting is a service provided by Scaleway which offers storage space and access for your websites. Our Webhosting services include:
+
+- A domain name,
+- A configurable Webhosting service,
+- The management of your emails, including anti-spam, antivirus and filter systems,
+- Unlimited subdomains,
+- An FTP account to upload your website,
+- At least one database.
\ No newline at end of file
diff --git a/pages/classic-hosting/how-to/access-logcenter.mdx b/pages/classic-hosting/how-to/access-logcenter.mdx
new file mode 100644
index 0000000000..af8774a60a
--- /dev/null
+++ b/pages/classic-hosting/how-to/access-logcenter.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to access the logcenter
+ description: This page explains how to access the logcenter of a Webhosting Classic
+content:
+ h1: How to access the logcenter
+ paragraph: This page explains how to access the logcenter of a Webhosting Classic
+tags: webhosting logcenter
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+The logcenter allows you to visualize real-time error logs of your hosting. That way, you can quickly troubleshoot potential issues linked to your code.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+
+## How to create or reset a password for the logcenter
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Statistics and logs** in the side menu. The statistics and logs overview page displays.
+4. Go to the **Logs** section and click **Define password**. If you want to reset your password, click **Reset password**.
+
+5. Enter a password and its confirmation, then click **Edit account**.
+
+ For a strong password, combine lowercase, uppercase, numbers, and special characters.
+
+
+## How to access the logcenter
+
+1. Access the [logcenter](https://logcenter.online.net/).
+2. Enter your domain name as login and the password set in the previous step. Then click **Connexion**. The logs of your webhosting displays in real-time.
+
+## How to download the log files
+
+We provide full access to your website's logs (access.log). This allows interested parties to have access to the raw data regarding visits to your website.
+
+You can find the connection details on the statistics overview page in your console.
+
+The log files can be downloaded via FTP access. Enter the required connection details to download them using an FTP client:
+
+FTP host: `stats.online.net`
+User: `webmaster@domain.tld`
+Password: The statistics password | see above
+
+Remember to replace `domain.tld` with your own domain (for example: `mydomain.com`).
+
+
+ Keep in mind that even if the username is the same, the log access account is different from the main FTP account. The password is therefore different too.
+
+
+
diff --git a/pages/classic-hosting/how-to/access-statistics.mdx b/pages/classic-hosting/how-to/access-statistics.mdx
new file mode 100644
index 0000000000..44d452b977
--- /dev/null
+++ b/pages/classic-hosting/how-to/access-statistics.mdx
@@ -0,0 +1,71 @@
+---
+meta:
+ title: How to access the website statistics
+ description: This page explains how to access the website statistics of a Webhosting Classic
+content:
+ h1: How to access the website statistics
+ paragraph: This page explains how to access the website statistics of a Webhosting Classic
+tags: webhosting statistics webhosting-classic
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+With each of our Webhosting Classic offers, we provide the possibility to visualize the statistics of your website (number of visits, number of unique visitors, bandwidth used, etc…).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+
+## How to create or reset a password for the statistics
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Statistics and logs** in the side menu. The statistics and logs overview page displays.
+4. Go to the **Statistics** section and click **Define password**. If you want to reset your password, click **Reset password**.
+5. Enter a password and its confirmation, then click **Edit account**.
+
+ For a strong password, combine lowercase, uppercase, numbers, and special characters.
+
+
+## How to access the statistics
+
+1. Open the following URL in your web browser: `https://stats.online.net/domain/example.com/` (replace `example.com` with your domain name) to access the statistics.
+2. Enter the password set in the previous step. Then press Enter. The statistics dashboard displays.
+
+
+ The dashboard contains the following information:
+
+ * **A:** Choice of the analysis period. The analysis period is a month of your choice (by default the current month). It allows you to display the statistics of a specific month.
+ * **B:** The current analysis period. This will indicate which period the current statistics analysis refers to.
+ * **C:** Details of the visits/visitors. You can see:
+ * Number of visits,
+ * Number of different visitors,
+ * Number of page views,
+ * Number of hits,
+ * Amount of bandwidth consumed.
+ * **D:** Monthly history. This information shows you a summary of the activity of your site over all the months of the current year (see **C**), with the possibility of having the cumulative total of these statistics.
+
+ This information is only part of the data provided by our statistics page. Below is a complete list of the other information available:
+
+ * Detailed statistics on the days of the selected analysis period,
+ * Detailed statistics on the days of the week of the selected analysis period,
+ * Detailed statistics on the hours of the selected analysis period,
+ * Most frequent visitors,
+ * Most frequent robots (referencing, etc.,),
+ * Duration of the visits,
+ * Most used file types,
+ * Most downloaded files,
+ * Most viewed pages,
+ * Most used operating systems to consult your site,
+ * Most used browsers to consult your site,
+ * Origin of the users,
+ * Keywords/key phrases used to access the site,
+ * Most returned HTTP codes.
+
+
diff --git a/pages/classic-hosting/how-to/assets/scaleway-filezilla-newsite.webp b/pages/classic-hosting/how-to/assets/scaleway-filezilla-newsite.webp
new file mode 100644
index 0000000000..6db4017813
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway-filezilla-newsite.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway-outlook2013-mutu.webp b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-mutu.webp
new file mode 100644
index 0000000000..a3500d047c
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-mutu.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway-outlook2013-ports.webp b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-ports.webp
new file mode 100644
index 0000000000..423e9e4dfb
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-ports.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway-outlook2013-smtp.webp b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-smtp.webp
new file mode 100644
index 0000000000..5bf3c975dc
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway-outlook2013-smtp.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_add_email_redirection.webp b/pages/classic-hosting/how-to/assets/scaleway_add_email_redirection.webp
new file mode 100644
index 0000000000..9c5b0ff02f
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_add_email_redirection.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_auto_reply1.webp b/pages/classic-hosting/how-to/assets/scaleway_auto_reply1.webp
new file mode 100644
index 0000000000..37696f947d
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_auto_reply1.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_backups_emails.webp b/pages/classic-hosting/how-to/assets/scaleway_backups_emails.webp
new file mode 100644
index 0000000000..93f9e12769
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_backups_emails.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_backups_filezilla.webp b/pages/classic-hosting/how-to/assets/scaleway_backups_filezilla.webp
new file mode 100644
index 0000000000..04e07c2081
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_backups_filezilla.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_connection_failed.webp b/pages/classic-hosting/how-to/assets/scaleway_connection_failed.webp
new file mode 100644
index 0000000000..23f9ca8215
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_connection_failed.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_delete_email.webp b/pages/classic-hosting/how-to/assets/scaleway_delete_email.webp
new file mode 100644
index 0000000000..0e78969da7
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_delete_email.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_example_password.webp b/pages/classic-hosting/how-to/assets/scaleway_example_password.webp
new file mode 100644
index 0000000000..9b5ec9279c
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_example_password.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_ftp_sslcertificate_2022.webp b/pages/classic-hosting/how-to/assets/scaleway_ftp_sslcertificate_2022.webp
new file mode 100644
index 0000000000..3485455380
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_ftp_sslcertificate_2022.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_ftpaccounts.webp b/pages/classic-hosting/how-to/assets/scaleway_ftpaccounts.webp
new file mode 100644
index 0000000000..76f965e013
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_ftpaccounts.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_generate_import_key.webp b/pages/classic-hosting/how-to/assets/scaleway_generate_import_key.webp
new file mode 100644
index 0000000000..24e3c6d0e6
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_generate_import_key.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_hosting_webhosting_classic.webp b/pages/classic-hosting/how-to/assets/scaleway_hosting_webhosting_classic.webp
new file mode 100644
index 0000000000..915008ed3f
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_hosting_webhosting_classic.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_insecure_connection.webp b/pages/classic-hosting/how-to/assets/scaleway_insecure_connection.webp
new file mode 100644
index 0000000000..6a9ce5400f
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_insecure_connection.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_key_password.webp b/pages/classic-hosting/how-to/assets/scaleway_key_password.webp
new file mode 100644
index 0000000000..70cbae212d
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_key_password.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_logcenter_define_password.webp b/pages/classic-hosting/how-to/assets/scaleway_logcenter_define_password.webp
new file mode 100644
index 0000000000..9880c580d4
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_logcenter_define_password.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_mysql_phpmyadmin.webp b/pages/classic-hosting/how-to/assets/scaleway_mysql_phpmyadmin.webp
new file mode 100644
index 0000000000..54dad6a994
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_mysql_phpmyadmin.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_once_generated.webp b/pages/classic-hosting/how-to/assets/scaleway_once_generated.webp
new file mode 100644
index 0000000000..c0d501714f
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_once_generated.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_send_email.webp b/pages/classic-hosting/how-to/assets/scaleway_send_email.webp
new file mode 100644
index 0000000000..71a798287c
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_send_email.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_subdomain_01.webp b/pages/classic-hosting/how-to/assets/scaleway_subdomain_01.webp
new file mode 100644
index 0000000000..08954a5204
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_subdomain_01.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_subdomain_02.webp b/pages/classic-hosting/how-to/assets/scaleway_subdomain_02.webp
new file mode 100644
index 0000000000..758a6509ae
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_subdomain_02.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_subdomain_03.webp b/pages/classic-hosting/how-to/assets/scaleway_subdomain_03.webp
new file mode 100644
index 0000000000..5196b145e9
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_subdomain_03.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_subdomain_ftp.webp b/pages/classic-hosting/how-to/assets/scaleway_subdomain_ftp.webp
new file mode 100644
index 0000000000..7635418eef
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_subdomain_ftp.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_webhosting_statistics.webp b/pages/classic-hosting/how-to/assets/scaleway_webhosting_statistics.webp
new file mode 100644
index 0000000000..c9d080b73a
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_webhosting_statistics.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_webhostingc_manage.webp b/pages/classic-hosting/how-to/assets/scaleway_webhostingc_manage.webp
new file mode 100644
index 0000000000..d1a4486257
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_webhostingc_manage.webp differ
diff --git a/pages/classic-hosting/how-to/assets/scaleway_website_php.webp b/pages/classic-hosting/how-to/assets/scaleway_website_php.webp
new file mode 100644
index 0000000000..3d7f4722b9
Binary files /dev/null and b/pages/classic-hosting/how-to/assets/scaleway_website_php.webp differ
diff --git a/pages/classic-hosting/how-to/change-email-account-password.mdx b/pages/classic-hosting/how-to/change-email-account-password.mdx
new file mode 100644
index 0000000000..98f0a4a9e9
--- /dev/null
+++ b/pages/classic-hosting/how-to/change-email-account-password.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to change the password of an email account on Web Hosting Classic
+ description: This page shows you how to change the password of an email account on Scaleway Web Hosting Classic
+content:
+ h1: How to change the password of an email account on Web Hosting Classic
+ paragraph: This page shows you how to change the password of an email account on Scaleway Web Hosting Classic
+tags: password email-account email account webhosting
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+
+1. Click **Hosting**, then click **Manage**.
+2. Scroll down to **E-mail accounts** and click **Manage**.
+3. Click the settings icon next to the email account you wish to update.
+4. Click **Update password**. A window displays.
+5. Type in your new password and confirm it, then click **Update Password**.
+ Your new password is now registered.
+
+
+ - The status of the account changes to **Waiting for update**. During this time, no other change to the email account is possible.
+ - The new password will be set in a maximum delay of one hour.
+
+
+
diff --git a/pages/classic-hosting/how-to/change-ftp-account-password.mdx b/pages/classic-hosting/how-to/change-ftp-account-password.mdx
new file mode 100644
index 0000000000..9cbbc51776
--- /dev/null
+++ b/pages/classic-hosting/how-to/change-ftp-account-password.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to change the password of an FTP account for Scaleway Web Hosting Classic
+ description: This page shows you how to change the password of an FTP account
+content:
+ h1: How to change the password of an FTP account for Scaleway Web Hosting Classic
+ paragraph: This page shows you how to change the password of an FTP account
+tags: webhosting ftp-account ftp account password
+dates:
+ validation: 2024-08-12
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+
+1. Click **Hosting**, then click **Manage**.
+2. Click the **FTP accounts** tab under **HOSTING**.
+3. Click the settings icon under **Actions**, then click **Reset password**. A window displays.
+4. Type in your new password and confirm it.
+5. Click **Edit account** to confirm your changes.
+
+ The status of your account changes and displays **Currently updating**. Updating takes up to one hour.
+
+
+
diff --git a/pages/classic-hosting/how-to/change-password-mysql-database.mdx b/pages/classic-hosting/how-to/change-password-mysql-database.mdx
new file mode 100644
index 0000000000..ebedc9950c
--- /dev/null
+++ b/pages/classic-hosting/how-to/change-password-mysql-database.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to change the password of a MySQL database
+ description: This page explains how to change the password of a MySQL database
+content:
+ h1: How to change the password of a MySQL database
+ paragraph: This page explains how to change the password of a MySQL database
+tags: webhosting password mysql database
+dates:
+ validation: 2024-11-18
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **MySQL databases** in the side menu. The list of your databases displays.
+4. Click the **cogwheel** > **Update password**. A pop-up displays.
+5. Enter the new password for your MySQL database and its confirmation. Then click **Edit password**.
+
+ The status of your database has changed to **Waiting for update**. Your password will be updated within one hour.
+
+
diff --git a/pages/classic-hosting/how-to/change-password-postgresql-database.mdx b/pages/classic-hosting/how-to/change-password-postgresql-database.mdx
new file mode 100644
index 0000000000..173dfbadcf
--- /dev/null
+++ b/pages/classic-hosting/how-to/change-password-postgresql-database.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to change the password of a PostgreSQL database
+ description: This page explains how to change the password of a PostgreSQL database
+content:
+ h1: How to change the password of a PostgreSQL database
+ paragraph: This page explains how to change the password of a PostgreSQL database
+tags: webhosting password postgresql database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **PostgreSQL databases** in the side menu. The list of your databases displays.
+4. Click the **cogwheel** > **Update password**. A pop-up displays.
+5. Enter the new password for your PostgreSQL database and its confirmation. Then click **Edit password**.
+
+ The status of your database has changed to **Waiting for update**. Your password will be updated within one hour.
+
+
diff --git a/pages/classic-hosting/how-to/check-emails.mdx b/pages/classic-hosting/how-to/check-emails.mdx
new file mode 100644
index 0000000000..3ae7104731
--- /dev/null
+++ b/pages/classic-hosting/how-to/check-emails.mdx
@@ -0,0 +1,72 @@
+---
+meta:
+ title: How to check your emails
+ description: This page shows you how to check your emails
+content:
+ h1: How to check your emails
+ paragraph: This page shows you how to check your emails
+tags: email configuration account webmail pop3 webhosting
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+- Configured an email account
+
+## How to configure your email account
+
+We recommend choosing a protocol adapted to your usage habits:
+- **POP3**: ideal for use on a single device;
+- **IMAP**: the best option for a multi-device usage (computer, mobile phone, tablet etc.).
+
+
+| Protocol | Server -WEB- | Port | TLS | SSL | Authentication |
+|:--------:|:---------------:|:---------------:|:---:|:---:|:--------------:|
+| IMAP | imap.online.net | 143 (recommend) | Yes | No | Yes |
+| IMAPS | imap.online.net | 993 | No | Yes | Yes |
+| POP3 | pop.online.net | 110 (recommend) | Yes | No | Yes |
+| POP3 | pop.online.net | 995 | No | Yes | Yes |
+| SMTP | smtp.online.net | 25 | Yes | No | Yes |
+| SMTP | smtp.online.net | 587 (recommend) | Yes | No | Yes |
+| SMTP | smtp.online.net | 2525 | Yes | No | Yes |
+| SMTPS | smtp.online.net | 465 | No | Yes | Yes |
+
+
+
+
+ The authenticated SMTP service has some limitations for security reasons:
+ - No more than 5 simultaneous SMTP connections.
+ - No more than 60 mails / hour / per recipient / per SMTP account.
+ - No more than 500 mails / day / per recipient / domain.
+ - The maximum size of an email is 20 MB (Attachment included).
+ - You should instead use another service using FTP or HTTP to transfer larger files - for example: [Free Transfert](https://transfert.free.fr/).
+
+
+## How to check your emails using a webmail interface
+
+1. Go to the [Scaleway webmail interface](https://webmail.online.net/).
+2. Log in by entering the following information:
+ * The **Login** which corresponds to your complete email address ([you@domain.ex](mailto:you@domain.ex) for example).
+ * The **Password** which is related to your email account.
+
+
+ - If you do not know your password, you can recover it from the [Dedibox console](https://console.online.net).
+ - Log into the [Dedibox console](https://console.online.net).
+ - Click **Hosting** > **Manage** > **E-mail accounts**. A list of your email addresses displays.
+ - Click the settings icon (cogwheel) next to your email address and click **Update password** to change it.
+
+
+
+ - If you use a messaging client (Outlook, Thunderbird, etc.) on your computer, configured to use POP, it is normal that you can only see the newly arrived mails, as POP downloads mail onto your computer.
+ - If you want to check your emails using the webmail, you should configure your client to use IMAP.
+
+
+
diff --git a/pages/classic-hosting/how-to/configure-backup-option.mdx b/pages/classic-hosting/how-to/configure-backup-option.mdx
new file mode 100644
index 0000000000..bd773b4a90
--- /dev/null
+++ b/pages/classic-hosting/how-to/configure-backup-option.mdx
@@ -0,0 +1,76 @@
+---
+meta:
+ title: How to configure the backup option for webhosting
+ description: This page shows you how to configure the backup option for wehbosting
+content:
+ h1: How to configure the backup option for webhosting
+ paragraph: This page shows you how to configure the backup option for wehbosting
+tags: webhosting backup
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+Because you can never be safe against human failure, a hardware fault, or piracy of your data we offer a secured storage space, accessible by FTP, containing the backups of your webhosting and your databases.
+
+The offer includes:
+* A daily backup of your website and your databases
+* Retention of all of your backups for 3 days
+* Retention of a full weekly backup of your site for two months
+
+
+ * More information about this option and its pricing is available on our [website](https://www.scaleway.com/en/web-hosting/#sauvegarde).
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic** plan
+
+## How to subscribe to the backup option for webhosting
+
+1. Log into the [Dedibox console](https://console.online.net).
+2. Click **Hosting** then click **Manage** next to the webhosting you wish to backup. The **Configure hosting** page displays.
+3. Click **Backup** then click **Order the backup option to be safe**. You are redirected to the **Change hosting offer** page.
+4. Check the **Option Hosting backup** box and click **Confirm your offer**.
+5. Select your payment mode, then check the mandatory boxes.
+
+ * We recommend you activate automatic renewal 62 days before the expiration date by checking the corresponding box.
+
+6. Click **Confirm my order** to subscribe to the backup option.
+
+ * Your backup will be set up within the hour of your order.
+
+
+## How to configure your FTP/SQL backup
+
+
+
+- Set up the backup option for your webhosting
+
+1. Log into the [Dedibox console](https://console.online.net).
+2. Click **Hosting** then click **Manage** next to your webhosting.
+3. Click **Backup** to find the data required to configure your backup. A page displays your identifier and password to access your backup with an FTP client.
+4. Launch [FileZilla](https://filezilla-project.org/) on your computer and enter your credentials to connect to the backup.
+
+
+
+ * The backups are placed in the root directory and are named by the date of their creation. SQL backups can be found in the subdirectory `database_backup`.
+
+
+## How to configure your email backup
+
+
+ * There is no standardized format for the export of emails. Therefore, we offer a second dedicated [webmail](https://backup-mail.online.net/) for accessing your emails.
+
+
+1. Log into the [webmail](https://backup-mail.online.net/) using your email address and usual password.
+2. You can access your current mailbox and your backups.
+
+3. Click and drag the backup folders to your current mailbox to restore your old emails.
+
+
diff --git a/pages/classic-hosting/how-to/configure-htaccess-file.mdx b/pages/classic-hosting/how-to/configure-htaccess-file.mdx
new file mode 100644
index 0000000000..7c0d8ee664
--- /dev/null
+++ b/pages/classic-hosting/how-to/configure-htaccess-file.mdx
@@ -0,0 +1,157 @@
+---
+meta:
+ title: How to configure an .htaccess file on Web Hosting Classic
+ description: Learn how to configure an .htaccess file on Scaleway Web Hosting Classic.
+content:
+ h1: How to configure an .htaccess file on Web Hosting Classic
+ paragraph: This guide explains how to configure an .htaccess file on Scaleway Web Hosting Classic.
+tags: htaccess, error-message, directory, authentication, php, html
+dates:
+ validation: 2024-08-05
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+`.htaccess` is a simple text file containing commands for configuring the Apache web server. It allows you to customize the server dynamically and per folder.
+
+
+ - When transferring your `.htaccess` file, ensure the FTP transfer mode is set to "ASCII/TEXT" and not "BINARY". Transferring the file in binary mode will cause an HTTP error 500, blocking access to your websites. Also, ensure your `.htaccess` file ends with an empty line to prevent this error. Double-check the file syntax before transferring it in text mode.
+ - You can create the `.htaccess` file on Windows only using **Notepad**.
+
+
+### How to configure personalized error messages
+
+You can replace the default **404 error (Not Found)** message with a more user-friendly text or a redirection to another URL, either local or external.
+
+1. Use the `ErrorDocument` command to configure personalized messages. Here are some examples:
+ ```
+ ErrorDocument 404 /myfile404.html
+ ErrorDocument 404 http://URLexample.tld
+ ErrorDocument 403 /accessrefused.html
+ ```
+2. Place this command in an `.htaccess` file in the directory where you want to redirect the error messages. Typically, this is the root of your website.
+
+### How to disable directory listing
+
+1. Create an `.htaccess` file by opening your text editor.
+2. Add the following line:
+ ```
+ Options -Indexes
+ ```
+3. Upload the file using FTP, place it in the desired directory, and rename it to `.htaccess`.
+
+### How to prevent access to a directory
+
+1. Open your text editor and create a file with the following lines:
+ ```
+ # We authorize access from the IP 213.228.62.50
+ Allow from 213.228.62.50
+ # We authorize access from the IP 213.228.62.51
+ Allow from 213.228.62.51
+ # We deny access from all other IPs
+ Deny from All
+ ```
+2. Upload the file using FTP, place it in the desired directory, and rename it to `.htaccess`.
+
+### How to secure a directory with HTTP authentication
+
+1. Create a user table with usernames and encrypted passwords. Here is an example:
+ ```
+ martin:$apr1$tQqqRlvz$70soamNFTNl54OnSV.RWr.
+ jean:$apr1$yMWZ093W$DKAVAi5.XRx1ofwF5T..E0
+ sophie:$apr1$92x5vRxN$vivxTZtZfcqRmRBvL1ASF/
+ ```
+
+
+ - The first part is the username, and the second part after ":" is the encrypted password. You can use this [website](https://hostingcanada.org/htpasswd-generator/) to encrypt your passwords if needed.
+
+2. Name this file **passlist.txt**.
+3. Create an `.htaccess` file in the directory you want to protect, with the following content:
+ ```
+ AuthUserFile /flex/domain/DOMAIN.TLD/site/www/secret/password/mylist.txt
+ AuthName "Access Restricted"
+ AuthType Basic
+ require valid-user
+ ```
+
+
+ - Replace `PATH` with `/flex/domain/DOMAIN.TLD/site/www/`.
+ - Replace `DOMAIN.TLD` with your domain name.
+
+4. Upload the file using FTP, place it in the desired directory, and name it `.htaccess`. For more details, refer to the [Apache user guide](https://httpd.apache.org/docs/).
+
+
+ - It is not possible to create an `.htaccess` file directly on Windows. Create the file with another name (e.g., `htaccess.txt`) and rename it after uploading to your server.
+ - Transfer the file in ASCII mode to preserve 'line break' characters.
+ - Protect your password list by storing it in a subdirectory and securing it with an `.htaccess` file.
+
+
+### How to configure HTTP redirections
+
+1. Create an `.htaccess` file with the following content:
+ ```
+ # Redirection to the site Scaleway.com
+ RedirectPermanent / https://www.scaleway.com/en/
+ ```
+2. Upload the file using FTP to the folder of the concerned subdomain (e.g., `www` for `www.URLexample`, `blog` for `blog.URLexample`) and rename it to `.htaccess`.
+
+ For more information, refer to the [Apache documentation](http://httpd.apache.org/docs/2.0/mod/mod_alias.html).
+
+
+### How to configure an HTML redirection
+
+
+ This method is simpler but less efficient. It uses the HTML document itself to indicate the redirection and should be used only when HTTP redirects are not possible.
+
+
+Here is an example of redirecting `http://old.address.fr/dossier1/URLexample/page1.html` to `http://new.address.fr/dossier2/URLexample/page2.html`:
+
+```html
+
+
+
+
+
+
+ Redirection
+
+
+
+ Redirection
+
+
+```
+
+### How to configure PHP redirections
+
+Create a PHP file with the following content to redirect `http://URLexample/index.php/` to `http://newsite.com/`:
+
+```php
+
+```
+
+
+ - By default, the redirection returns the HTTP 301 status code. Modify it if required.
+
+
+### How to configure rewrite rules
+
+
+ - The Apache module `mod_rewrite` is activated on our web hosting servers and works by default with `.htaccess` files.
+ - The directive `FollowSymlinks` is activated and must not be modified, as doing so will result in an HTTP 500 error.
+
+
+For example, to rewrite the URL `http://www.URLexample/index.php/` with the page name as an argument:
+
+1. Create an `.htaccess` file with the following content:
+ ```
+ RewriteEngine On
+ RewriteRule ^([^\.]+)\.html /index.php?page=$1 [L]
+ ```
+2. Upload the file using FTP to the folder of the concerned subdomain (e.g., `www` for `www.URLexample`, `blog` for `blog.URLexample`) and rename it `.htaccess`.
+3. Open the `http://www.URLexample/test.html/` file in your web browser. The `index.php` file will be executed with the argument “test”.
\ No newline at end of file
diff --git a/pages/classic-hosting/how-to/configure-outlook.mdx b/pages/classic-hosting/how-to/configure-outlook.mdx
new file mode 100644
index 0000000000..22c4070a3b
--- /dev/null
+++ b/pages/classic-hosting/how-to/configure-outlook.mdx
@@ -0,0 +1,49 @@
+---
+meta:
+ title: How to configure Outlook to receive and send email on Web Hosting Classic
+ description: This page shows you how to Outlook to receive and send email on Scaleway Web Hosting Classic
+content:
+ h1: How to configure Outlook to receive and send email on Web Hosting Classic
+ paragraph: This page shows you how to configure Outlook to receive and send emails on Scaleway Web Hosting Classic
+tags: configuration outlook email webhosting
+dates:
+ validation: 2024-08-12
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+You can read and send your emails using the Microsoft Outlook client.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created an email account](/classic-hosting/how-to/create-email-account/)
+
+
+ We recommend using the IMAP protocol if you access your mailbox from different devices (PC, Mobile phone, Tablet, …).
+
+
+You can [configure](https://support.microsoft.com/en-us/office/add-an-email-account-to-outlook-6e27792a-9267-4aa4-8bb6-c84ef146101b) Microsoft Outlook to [check your emails](/classic-hosting/how-to/check-emails/).
+
+1. Set the following parameters in the configuration wizard to access your Webhosting Classic mailbox:
+ * IMAP server (incoming mail):
+ * Hostname: imap.online.net
+ * TCP port: 993
+
+ * Connection type: SSL
+ * SMTP server (outgoing mail)
+ * Hostname: smtpauth.online.net
+ * TCP port: 587 or 465
+ * Connection type TLS
+
+
+2. Click **More settings**, then select **Advanced** to configure the ports:
+
+3. Click **Outgoing server** and tick the box **My outgoing server requires authentication**. Then click **OK** to validate.
+
+
+
diff --git a/pages/classic-hosting/how-to/configure-php.mdx b/pages/classic-hosting/how-to/configure-php.mdx
new file mode 100644
index 0000000000..50e0ae22a3
--- /dev/null
+++ b/pages/classic-hosting/how-to/configure-php.mdx
@@ -0,0 +1,324 @@
+---
+meta:
+ title: How to configure PHP
+ description: This page explains how to configure PHP.
+content:
+ h1: How to configure PHP
+ paragraph: This page explains how to configure PHP.
+tags: webhosting php antispam
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+## How to configure PHP at Scaleway
+
+`phpinfo` is a function of the PHP language, that allows you to see the active modules, the configuration of the server, the restrictions, and the compilation parameters of the language:
+
+```php
+
+```
+
+
+ - The default version of PHP for all webhostings is PHP 5. During the creation of your webhosting, a `phpinfo.php` file will be created.
+
+
+## How to use sessions
+
+Sessions are a method to save certain information when you are browsing, (your shopping cart during a pending order, for example). The session system is a default feature of PHP.
+
+
+ - Refer to the [official documentation](https://www.php.net/manual/en/ref.session.php) for more information about sessions.
+
+
+Let us see how to use sessions with PHP4:
+
+1. Log into your PHP session using FTP and go to the folder `www/` in which you will add the code of your website.
+2. Create a new file and name it `start.php` containing the following lines:
+ ```php
+ ";
+ ?>
+
+ To go to the next page click here
+ ```
+3. Create a new file and name it `nextpage.php` containing the following lines:
+ ```php
+ ";
+ ?>
+ ```
+4. Upload the files to your website and open the file `start.php` in your browser.
+
+## How to configure a root directory (DocumentRoot)
+
+
+ Never use the absolute path `hard` coded in your site, because the path is likely to change, and your site will be inaccessible.
+
+
+
+1. Use the variable `$DOCUMENT_ROOT` that points to the root of the website in which your script is being hosted.
+2. Use `$path = “$DOCUMENT_ROOT/afolder/anotherfolder/”;` if you want to know the path of your website `http://www.mysite.ext/afolder/anotherfolder`.
+
+## How to configure a directory inclusion (IncludePath)
+
+As part of the creation of a large website, it is possible to centralize frequently included files by adding a default directory to the search list of included files. You must create it, as it is not created by default.
+
+1. Create a directory `include` (all lowercase letters) in the website's folder (for example: www/include).
+
+ - Such directory can only be used within the website it was created in. This means the main website's directory, which is named `www/include`, is not accessible from a secondary website (such as `blog.domain.ext`).
+
+2. Below is an example of a directory-inclusion:
+ - Let us suppose you created a file `global.php` including different information or methods.
+ - You want to access it from anywhere on your website without copying it in each subdirectory or entering the relative path to that file in each program.
+ - Let us assume that your `.php` files are located on the main website `www.mydomain.ext>`.
+ - You have to create `www/include` and store your file `global.php` in it (it is therefore in `www/include/global.php` seen in FTP).
+ - Call it from a `.php` file regardless of where it is located inside the main website by writing:
+ ```php
+
+ ```
+ - You can also use:
+ ```php
+
+ ```
+
+## How to connect to a database
+
+
+ - Persistent connections are not possible due to the architecture of the webhosting platform and are performed as a standard connection.
+
+
+Refer to the [documentation](/classic-hosting/how-to/manage-mysql-database-phpmyadmin/) on how to configure the connection to a database using PHP.
+
+## How to upload files
+
+
+ - The maximum file size you can upload is 10 MB.
+
+
+1. Rename an uploaded file using the function `move_updloaded_file` before the end of your script.
+2. The temporary file `phpXXXXX` will be deleted at the end of the receiving PHP script. Below is an example:
+ ```php
+
+
+
+ ```
+
+## How to send emails
+
+The email function of PHP is available, but it has some limitations:
+ - No more than 35 recipients per call of the function,
+ - Maximum 500 outgoing mails per day, with a limitation of 60 mails/hour,
+ - Size of the mails is limited to 2 MB,
+ - Antispam detection,
+ - The mail function returns TRUE on success and FALSE if one of these conditions is not met.
+
+Here is an example:
+ - Let us suppose that the domain is `domain.ext`.
+
+```php
+\n"; // Adding the From field
+ // $headers = $headers."MIME-Version: 1.0\n"; // Adding the MIME version
+ $headers = $headers."Content-type: text/plain; charset=iso-8859-1\n"; // Add the type of encoding
+
+ // Call the mail function
+ if ( mail($to, $subject, $message, $headers) == TRUE )
+ {
+ echo "Mail sent.";
+ }
+ else
+ {
+ echo "Error: The message could not be sent.";
+ }
+
+?>
+```
+
+
+ A malicious individual can use contact forms to send you spam. By calling several times a second, it will eventually saturate the `contact@domain.ext` email address you specified. The addition of a captcha can help you avoid this kind of hacking, and thus the suspension or cancellation of your account.
+
+
+## How to create a contact form (form2mail)
+
+Let us suppose that the domain in this example is `domain.ext`.
+
+1. Create a file `form.html` and upload it using FTP. Your file should be similar to:
+ ```php
+
+
+
+
+
+ ```
+2. Create a second file `form2mail.php` and upload it using FTP. Your file should be similar to:
+ ```php
+ \n";
+ $headers .= "To: Contact <$to>\n";
+ /* $headers .= "MIME-Version: 1.0\n";
+ $headers .= "Content-type: text/plain; charset=iso-8859-15\n";
+
+ /* Call of the mail function */
+ if (!mail($to, $subject, $message, $headers)){
+ echo "Error: Impossible to send the mail";
+ } else {
+ echo "Email sent";
+ }
+ }
+ else {
+ echo "Error: You need to specify a mail address and a message.\n";
+ }
+
+ ?>
+ ```
+
+## How to configure PHP versions
+
+Scaleway offers different PHP versions:
+
+* The version 5.5
+* The version 5.6
+* The version 7.0
+* The version 7.1
+* The version 7.2
+* The version 7.3
+
+
+ Versions prior to PHP 5.6 are deprecated, so we recommend you update the code of your website. If you need an older version, you must contact the support and request it.
+
+
+The default version for `.php` is 7.3 for current webhosting accounts. For older accounts the version can be changed directly from the [Dedibox console](https://console.online.net):
+
+1. Log into your account.
+2. Click **Hosting**, then **Manage**, next to your webhosting.
+3. Click **Manage** in the menu on the right. The **Website configuration** page displays.
+4. Click the **Edit** action.
+
+5. Select the PHP version of your choice.
+6. Click **Submit** to update your PHP version.
+
+## How to configure PHP
+
+
+ Configuring PHP is possible for all our offers. However, ensure you are running at least PHP version 5.3 and above.
+
+
+1. Upload a `.user.ini`file to the folder corresponding to your subdomain (folder `/www` for example).
+
+ The majority of options are configurable, except for those with an impact on the resources of the server.
+
+2. You can modify all values with `PHP_INI_ALL` changeable option you can find by clicking this [link](https://www.php.net/manual/en/ini.list.php).
+
+ - chown: modifications of the owner of a file are prohibited. Files uploaded using PHP or FTP already belong to your user.
+ - system/exec/popen: the execution of binaries or CGI files is not possible for security reasons.
+ - ASP is not supported. The execution of CGI scripts (cgi-bin) and other programs is disabled.
+
+
+## How to solve an HTTP error 500 in the htaccess file
+
+You can get this error because your `.htaccess` file has errors, such as:
+
+- Presence of unauthorized directive,
+- Presence of a syntax error,
+- `.htaccess` file transferred in binary, instead of a transfer as text,
+- Lack of a final blank line.
+
+1. Rename the `.htaccess` file to `htaccessX.txt`to solve these errors.
+2. Create an empty `.htaccess` file.
+3. Add the lines one by one until you find the lines that caused the error 500.
+
+## How to solve an error in a PHP Script
+
+An error 500 can come from an error in the PHP code.
+
+Change the `error_reporting` and `display_errors` in a `user.ini` file as described in [How to configure PHP](#how-to-configure-php-at-scaleway).
+
+## How to solve email problems
+
+1. Update your CMS if it uses the `phpmailer` class (XOOPS, WAnewsletter for example).
+2. Replace the `phpmailer` directory present in your CMS with the latest version proposed here https://github.com/PHPMailer/PHPMailer.
+
+
diff --git a/pages/classic-hosting/how-to/connect-via-ftp.mdx b/pages/classic-hosting/how-to/connect-via-ftp.mdx
new file mode 100644
index 0000000000..0baddf64ea
--- /dev/null
+++ b/pages/classic-hosting/how-to/connect-via-ftp.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to connect via FTP on Web Hosting Classic
+ description: Learn how to connect to your website via FTP on Scaleway Web Hosting Classic using FileZilla.
+content:
+ h1: How to connect via FTP on Web Hosting Classic
+ paragraph: This guide explains how to connect to your website via FTP using FileZilla on Scaleway Web Hosting Classic.
+tags: webhosting, ftp
+dates:
+ validation: 2024-08-05
+ posted: 2022-02-24
+categories:
+ - webhosting
+---
+
+
+
+**F**ile **T**ransfer **P**rotocol (FTP) is a standard method for transferring files between a client (e.g., your local computer) and a server (e.g., your Scaleway web hosting server) via the internet. This guide shows you how to configure the popular and free FTP client [FileZilla](https://filezilla-project.org/) to connect to your web hosting site using FTP. You will then be able to transfer files from your local computer to your Scaleway web hosting server. For additional help, refer to the [FileZilla Client Tutorial](https://wiki.filezilla-project.org/FileZilla_Client_Tutorial_(en)).
+
+In this example, we assume your domain name is `example.com` and your FTP account is `webmaster@example.com`. Ensure you have [created an FTP account](/classic-hosting/how-to/create-ftp-account/) before proceeding.
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A **Web Hosting Classic** plan and a domain name
+- An [FTP account created](/classic-hosting/how-to/create-ftp-account/)
+
+### Installing FileZilla
+
+1. Open the [FileZilla website](https://filezilla-project.org/) in your browser.
+2. Click **Download FileZilla Client**.
+ The FileZilla website detects your operating system and suggests the correct version of the FileZilla client to download.
+3. Click **Download FileZilla Client** and follow the on-screen prompts to complete the installation.
+
+ Depending on your operating system, you may prefer to download FileZilla from the command line of your terminal. On Ubuntu Linux, use the command `sudo apt update && sudo apt install filezilla`.
+
+
+### Configuring the FTP Account
+
+1. Open FileZilla on your local machine.
+2. Click on **File** in the top menu, and select **Site Manager**.
+3. Enter the following information in the form that displays. Remember to replace the **User** and **Password** values with [those of your FTP account](/classic-hosting/how-to/create-ftp-account/).
+
+
+ - **Protocol**: FTP - File Transfer Protocol
+ - **Host**: `ftp.online.net`
+ - **Port**: `21`
+ - **Encryption**: `Require explicit FTP over TLS`
+ - **Logon Type**: `Normal`
+ - **User**: `webmaster@example.com`
+ - **Password**: `your-ftp-password`
+
+
+ The form may display slightly differently depending on your operating system, but the fields and their values should remain the same.
+
+4. Click **Connect**. If a confirmation window appears, check and validate the certificate.
+
+
+ You are now connected via FTP to your web hosting site. Remember that all files for your website must be stored in the `www` folder.
+
+ Refer to the official [FileZilla documentation](https://wiki.filezilla-project.org/Documentation) for more help with using FileZilla to connect to your site and transfer files via FTP.
diff --git a/pages/classic-hosting/how-to/create-alias.mdx b/pages/classic-hosting/how-to/create-alias.mdx
new file mode 100644
index 0000000000..c5f17bb62c
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-alias.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to add a domain name as an alias on Web Hosting Classic
+ description: This page explains how to add a domain name as an alias on Scaleway Web Hosting Classic
+content:
+ h1: How to add a domain name as an alias on Web Hosting Classic
+ paragraph: This page explains how to add a domain name as an alias on Scaleway Web Hosting classic
+tags: webhosting domain alias domain-name
+dates:
+ validation: 2024-08-05
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+On our web hosting offers, you can link an additional domain name as an alias to your website. For example, you have the domain names `mydomainname.fr` and `mydomainname.com`, and want the same website to be visible for both domains.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Add Domain** in the **Additional domain names** section of the overview page.
+4. Enter the domain name you wish to add to your hosting in the search bar and click **Search**. The search result displays.
+
+ If your domain name is not registered yet, you can order it. If it is already registered and with another registrar, you can transfer it to Scaleway.
+
+5. Click the **Order** button to continue. The list of hosting offers displays.
+6. Select **Hosting alias** from the list of offers. Select the hosting you want to link the domain name to from the drop-down list. Then click **Order**. An order summary displays.
+7. Select your preferred payment method from the drop-down list and tick the checkboxes to agree to the terms of service, the specific terms for shared hosting. Then click **Confirm my command** to validate your order. The payment form for your order displays.
+8. Complete your payment and validate your order.
+
+ The domain name is now linked as an alias to your existing webhosting.
+
+
+
diff --git a/pages/classic-hosting/how-to/create-email-account.mdx b/pages/classic-hosting/how-to/create-email-account.mdx
new file mode 100644
index 0000000000..e927ba966f
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-email-account.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to create an email account on Web Hosting Classic
+ description: This page shows you how to create an email account on Scaleway Web Hosting Classic
+content:
+ h1: How to create an email account on Web Hosting Classic
+ paragraph: This page shows you how to create an email account on Scaleway Web Hosting Classic
+tags: email-account email account webhosting
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. Click **Hosting**, then click **Manage**.
+
+
+ The **Configure hosting** page displays.
+2. Scroll to **E-mail accounts** and click **Manage**.
+3. Click **Add account** to create a new mailbox.
+4. Enter the details of the email address you are adding and click **Add account**.
+5. Your account will be "active" and ready to use within an hour.
+
+
diff --git a/pages/classic-hosting/how-to/create-email-redirection.mdx b/pages/classic-hosting/how-to/create-email-redirection.mdx
new file mode 100644
index 0000000000..93fd72ad5f
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-email-redirection.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to create an email redirection
+ description: This page shows you how to create an email redirection
+content:
+ h1: How to create an email redirection
+ paragraph: This page shows you how to create an email redirection
+tags: webhosting email-redirection email redirect
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+A redirection is an alternative email address for one or multiple email accounts of the same domain. For example, you can create the alias [contact@example.com](mailto:contact@example.com), which will redirect the email to the personal email account [firstname.lastname@example.com](mailto:firstname.lastname@example.com).
+
+This allows you to have multiple email addresses without needing to have multiple email accounts. It is also possible to deliver the email to multiple recipients. This means, for our example, we can get the email sent to “contact” delivered to the email accounts “firstname.lastname” and also to “firstname2.lastname2”.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. Click **Hosting**, then click **Manage** next to your webhosting.
+2. Scroll down to **E-mail accounts**, then click **E-mail redirections**.
+3. Click **Add e-mail redirection**.
+
+
+4. Enter the required information for the alias (the name of the redirection and the recipient) to create the redirection. This may take up to one hour.
+5. Once the redirection is activated, the yellow dot next to your alias will turn green.
+
+ To add more than one recipient to a redirection, repeat the steps above for each recipient.
+
+
+
diff --git a/pages/classic-hosting/how-to/create-email-transfer.mdx b/pages/classic-hosting/how-to/create-email-transfer.mdx
new file mode 100644
index 0000000000..f91823c7a4
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-email-transfer.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to create an email transfer
+ description: This page shows you how to create an email transfer
+content:
+ h1: How to create an email transfer
+ paragraph: This page shows you how to create an email transfer
+tags: webhosting email-transfer email transfer
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+Emails transfer allow you to forward the incoming mail of an existing account to another address of your choice.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+
+ In some cases, the forwarded mails are considered spam and are not properly received. If that happens, we recommend importing the mails received at your existing address from your other provider instead of forwarding them.
+
+
+1. Click **Hosting**, then click **Manage** next to your webhosting.
+2. Scroll down to **E-mail accounts**, then click **E-mail forwarding**.
+3. Click **Add E-mail Forward**.
+4. Select the existing address and enter the email address of your choice. Your transfer is created.
+
+
diff --git a/pages/classic-hosting/how-to/create-ftp-account.mdx b/pages/classic-hosting/how-to/create-ftp-account.mdx
new file mode 100644
index 0000000000..60fa0f9ffc
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-ftp-account.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: How to create an FTP account on Web Hosting Classic
+ description: This page shows you how to create an FTP account on Scaleway Web Hosting Classic
+content:
+ h1: How to create an FTP account on Web Hosting Classic
+ paragraph: This page shows you how to create an FTP account on Scaleway Web Hosting Classic
+tags: webhosting ftp account ftp-account
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+**F**ile **T**ransfer **P**rotocol is a standard way to transfer files between a client (such as your local computer) and a server (such as your Scaleway webhosting server) via the internet. In order to [use FTP](/classic-hosting/how-to/connect-via-ftp/), you must first create an account.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+## How to create an FTP account
+
+1. Click **Hosting**, then **Manage**.
+2. Click the **FTP accounts** tab.
+ A form displays.
+3. Fill in the form to create your FTP account, entering the following values:
+ * a **username** (eg `webmaster`)
+ * a **password** of your choice
+ * a **path**, which has to be an existing directory on your FTP. Enter `/` to create an account with access to the whole directory, or a specific path to limit access to certain directories.
+4. Validate your entries.
+
+ Your FTP account appears in the account list with the status **Waiting to create**. Your account will be activated in approximately one hour.
+
+
+ When you [connect to your FTP account](/classic-hosting/how-to/connect-via-ftp/), the following folders display:
+ * `awffull` (contains your old access statistics, if they were activated).
+ * `www` (should contain your website).
+ * `logs` (contains your old access statistics, if they were activated).
+ * `UPLOADER_VOTRE_SITE_DANS_LE_REPERTOIRE_WWW` (this directory serves simply as a reminder as to where to upload your website files).
+
+
+ - Keep in mind that your website is located in the folder `/www` on the FTP server.
+ - Upload all your website's content into this folder.
+
+
+## How to limit the access to an FTP account
+
+To limit access to an FTP account, create the folder you want to access (example: `client`) in the folder `www` (the one containing your website). Then follow these steps:
+
+1. Log into the [Dedibox console](https://console.online.net).
+2. Click **Hosting**, then click **Manage**.
+3. Click the **FTP accounts** tab.
+4. Enter **/www/client/** in the **Directory** field of your new account.
+
+ Ensure that you follow the syntax `/www/directory/` in order for your account to work.
+
+
+
diff --git a/pages/classic-hosting/how-to/create-mysql-database.mdx b/pages/classic-hosting/how-to/create-mysql-database.mdx
new file mode 100644
index 0000000000..145df4aebe
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-mysql-database.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: How to create a MySQL database
+ description: This page explains how to create a MySQL database
+content:
+ h1: How to create a MySQL database
+ paragraph: This page explains how to create a MySQL database
+tags: webhosting mysql database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **MySQL databases** in the side menu. The list of your databases displays.
+4. Click **Add database**. A pop-up displays.
+5. Enter the database name, the database password, and its confirmation. Then click **Create MySQL database**.
+
+ For a strong password, combine lowercase, uppercase, numbers, and special characters.
+
+
+Your database is created and displays in the list of your MySQL databases.
+
+## Limitations
+
+Databases are not hosted in the local storage of Webhosting services.
+
+However, to ensure the best performance of the SQL servers, we have defined limits for the sizes of the databases:
+
+ - Maximum size of a table: 1 GB for all offers.
+ - Maximum number of tables in a database: 2,000 for all offers.
+ - Number of simultaneous requests: 3 requests for the **Personal** offer, 50 requests for the **Pro** offer, 75 requests for the **Business** offer.
+
+
+ Databases that exceed these quotas are automatically blocked. You will not be able to add additional data or update them. Only the options to view and delete data remain active.
+
+
+If you reach these limits and are unable to use your database, you can connect to the MySQL shell in the administration interface to check the size of your databases and manage your data to reduce usage.
+
+
diff --git a/pages/classic-hosting/how-to/create-postgresql-database.mdx b/pages/classic-hosting/how-to/create-postgresql-database.mdx
new file mode 100644
index 0000000000..6547714f5f
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-postgresql-database.mdx
@@ -0,0 +1,53 @@
+---
+meta:
+ title: How to create a PostgreSQL database
+ description: This page explains how to create a PostgreSQL database
+content:
+ h1: How to create a PostgreSQL database
+ paragraph: This page explains how to create a PostgreSQL database
+tags: webhosting postgresql database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+PostgreSQL is an object-relational database management system that uses the SQL language. It is open source and well known for its stability, reliability and strong community.
+
+Compared with MySQL, PostgreSQL has the following advantages:
+
+* Better compliance with SQL standards,
+* Stricter data integrity,
+* More native data types,
+* Much more customizable/extensible (define custom data types and functions),
+* More advanced support of transactions, stored procedures, triggers, and views,
+* Asynchronous notifications and treatments,
+* Better scalability.
+
+However, it has the following limitations:
+
+* More complex to understand,
+* Replication is harder to implement,
+* Generally less well-supported than MySQL in current projects (CMS, for example).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **PostgreSQL databases** in the side menu. The list of your databases displays.
+4. Click **Add database**. A pop-up displays.
+5. Enter the database name, the database password, and its confirmation. Then click **Create PostgreSQL database**.
+
+ For a strong password, combine lowercase, uppercase, numbers, and special characters.
+
+
+Your database is being created and displays in the list of your PostgreSQL databases.
+
+
diff --git a/pages/classic-hosting/how-to/create-subdomain.mdx b/pages/classic-hosting/how-to/create-subdomain.mdx
new file mode 100644
index 0000000000..9b70abc1da
--- /dev/null
+++ b/pages/classic-hosting/how-to/create-subdomain.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: How to create subdomains
+ description: This page explains how to create subdomains
+content:
+ h1: How to create subdomains
+ paragraph: This page explains how to create subdomains
+tags: webhosting subdomain
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+Subdomains are an additional part to extend your main domain name. Mostly, they are created to organize and navigate to different sections of your website. For example, you can host your main website at `www.example.com` and your blog at `blog.example.com`.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+## How to create a subdomain from the Dedibox console
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Subdomains** in the side menu. The list of your subdomains displays.
+4. Click **Add subdomain**. A pop-up displays.
+5. Enter the name of your subdomain and click **Add subdomain**. The new subdomain will appear in the list of your subdomains.
+
+## How to upload content to your subdomain
+
+1. Connect to your webhosting using your [FTP account](/classic-hosting/concepts/#ftp-account). A listing of your remote files and folders displays in the right part of the FTP client:
+
+2. Double-click on the folder named like your subdomain to enter it. Then upload your files into this directory.
+
+ The directory where you usually upload your files on the server is `www`. To upload your files into the folder for your subdomain, you have to choose the one named after it.
+
+
+## How to create subdomains using the FTP client (advanced mode)
+
+It is also possible to create subdomains directly using your FTP client, without needing to create them via the Dedibox console.
+
+1. Log into your webhosting using an FTP client. Your remote files are listed in the right part of the FTP client.
+
+2. Create a new folder in the document root of your hosting, named after your subdomain:
+
+3. Enter the newly created directory and upload your files into it:
+
+
+You now can access the files located in this directory as a subdomain of your webhosting.
+
+
diff --git a/pages/classic-hosting/how-to/delete-email-account.mdx b/pages/classic-hosting/how-to/delete-email-account.mdx
new file mode 100644
index 0000000000..b907fb6ae0
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-email-account.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to delete your email account on Web Hosting Classic
+ description: This page shows you how to delete your email account on Scaleway Web Hosting Classic
+content:
+ h1: How to delete your email account on Web Hosting Classic
+ paragraph: This page shows you how to delete your email account on Scaleway Web Hosting Classic
+tags: webhosting email-account
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+
+ An email account deletion is irreversible and erases all emails stored on the servers.
+
+
+1. Click **Hosting**, then **Manage**.
+2. Scroll down to **E-mail accounts** and click **Manage**. A list of your email accounts displays.
+3. Click the settings icon next to the email account you wish to delete.
+4. Click **Delete**.
+5. Click **Delete** to confirm the deletion.
+
+
+ The email account is now scheduled to be deleted within the hour.
+
+
+
diff --git a/pages/classic-hosting/how-to/delete-email-redirection.mdx b/pages/classic-hosting/how-to/delete-email-redirection.mdx
new file mode 100644
index 0000000000..5c4bbc824e
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-email-redirection.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: How to delete an email redirection
+ description: This page shows you how to delete an email redirection
+content:
+ h1: How to delete an email redirection
+ paragraph: This page shows you how to delete an email redirection
+tags: webhosting email redirect email-redirection
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. Click **Hosting**, then click **Manage** next to your webhosting.
+2. Scroll down to **E-mail accounts**, then click **E-mail redirections**.
+3. Click **Delete** next to the email redirection you wish to delete.
+4. Click **Delete** to confirm. The redirection is scheduled for deletion.
+
+ Once the redirection is deleted, it will no longer be visible in the list of your aliases.
+
+
+
diff --git a/pages/classic-hosting/how-to/delete-email-transfer.mdx b/pages/classic-hosting/how-to/delete-email-transfer.mdx
new file mode 100644
index 0000000000..126ef425e8
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-email-transfer.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: How to delete an email transfer
+ description: This page shows you how to delete an email transfer
+content:
+ h1: How to delete an email transfer
+ paragraph: This page shows you how to delete an email transfer
+tags: webhosting email-transfer email transfer
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. Click **Hosting**, then click **Manage** next to your web hosting.
+2. Scroll down to **E-mail accounts**, then click **E-mail forwarding**.
+3. Click **Delete** next to the email transfer you wish to delete.
+4. Confirm the deletion.
+ Your transfer is now deleted.
+
+
diff --git a/pages/classic-hosting/how-to/delete-ftp-account.mdx b/pages/classic-hosting/how-to/delete-ftp-account.mdx
new file mode 100644
index 0000000000..918a60b1ac
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-ftp-account.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: How to delete an FTP account
+ description: This page shows you how to delete an FTP account
+content:
+ h1: How to delete an FTP account
+ paragraph: This page shows you how to delete an FTP account
+tags: ftp-account ftp webhosting
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- An [FTP account](/classic-hosting/how-to/create-ftp-account/)
+
+1. Click **Hosting** then click **Manage**.
+2. Click the **FTP accounts** tab.
+3. Click **Delete** next to the settings icon (cogwheel). The deletion will take up to one hour.
+
+ This will not delete the data on the FTP server.
+
+
+
diff --git a/pages/classic-hosting/how-to/delete-mysql-database.mdx b/pages/classic-hosting/how-to/delete-mysql-database.mdx
new file mode 100644
index 0000000000..4ae4625db8
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-mysql-database.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to delete a MySQL database
+ description: This page explains how to delete a MySQL database
+content:
+ h1: How to delete a MySQL database
+ paragraph: This page explains how to delete a MySQL database
+tags: webhosting mysql database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **MySQL databases** in the side menu. The list of your databases displays.
+4. Click **Delete** next to the database you want to delete. A pop-up displays.
+5. Confirm the database deletion by clicking on **Delete**.
+
+ All data stored in your database will be deleted. This operation cannot be undone. Make sure you have a backup of your data before deleting your MySQL database.
+
+
+
diff --git a/pages/classic-hosting/how-to/delete-postgresql-database.mdx b/pages/classic-hosting/how-to/delete-postgresql-database.mdx
new file mode 100644
index 0000000000..b074df6585
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-postgresql-database.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to delete a PostgreSQL database
+ description: This page explains how to delete a PostgreSQL database
+content:
+ h1: How to delete a PostgreSQL database
+ paragraph: This page explains how to delete a PostgreSQL database
+tags: webhosting postgresql database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **PostgreSQL databases** in the side menu. The list of your databases displays.
+4. Click **Delete** next to the database you want to delete. A pop-up displays.
+5. Confirm the database deletion by clicking on **Delete**.
+
+ All data stored in your database will be deleted. This operation cannot be undone. Make sure you have a backup of your data before deleting your PostgreSQL database.
+
+
+
diff --git a/pages/classic-hosting/how-to/delete-subdomain.mdx b/pages/classic-hosting/how-to/delete-subdomain.mdx
new file mode 100644
index 0000000000..3209478b2a
--- /dev/null
+++ b/pages/classic-hosting/how-to/delete-subdomain.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to delete subdomains
+ description: This page explains how to delete subdomains
+content:
+ h1: How to delete subdomains
+ paragraph: This page explains how to delete subdomains
+tags: webhosting subdomain
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Subdomains** in the side menu. The list of your subdomains displays.
+4. Click **Delete** next to the subdomain you want to remove from your webhosting. A pop-up displays.
+5. Click **Delete subdomain** to remove the subdomain.
+
+ This action is irreversible and permanently deletes all data stored in your subdomain. Make sure you have a backup of your data before deleting subdomains.
+
+
+
diff --git a/pages/classic-hosting/how-to/enable-https.mdx b/pages/classic-hosting/how-to/enable-https.mdx
new file mode 100644
index 0000000000..794933463c
--- /dev/null
+++ b/pages/classic-hosting/how-to/enable-https.mdx
@@ -0,0 +1,103 @@
+---
+meta:
+ title: How to enable HTTPS for Webhosting Classic
+ description: This page explains how to enable HTTPS for Webhosting Classic
+content:
+ h1: How to enable HTTPS for Webhosting Classic
+ paragraph: This page explains how to enable HTTPS for Webhosting Classic
+tags: webhosting https webhosting-classic ios
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+Scaleway Dedibox offers HTTPS on all its webhosting services by default. HTTPS allows you to secure the exchanges between the client (visitor of your site) and the server (our platform).
+
+It is usually preferred for online shops, but HTTPS is becoming more and more a standard on the web.
+
+The certificate is issued by [Let's Encrypt](https://letsencrypt.org), an initiative that allows the generation of free SSL certificates known by all browsers.
+
+
+ TLS/SSL is enabled by default for all webhostings and does not require any configuration from you.
+
+
+
+ TLS/SSL is only compatible with OS/browsers that support [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication). This means that the following clients cannot connect to sites hosted in HTTPS:
+ * Windows XP (IE6/IE7)
+ * Android 2.x
+ * Versions below iOS 4 (iPhone)
+
+
+## How to force HTTPS for the whole website
+
+To force a site to accept SSL, such as a CMS, simply add the following code to the `.htaccess` file:
+
+```
+RewriteEngine On
+RewriteCond %{HTTP:HTTPS} !on
+RewriteRule (.*) https://%{SERVER_NAME}/$1 [QSA,L,R=301]
+```
+
+## How to disable HTTPS for the whole website
+
+To disable SSL, you need to put the following code in the `.htaccess` file
+
+```
+RewriteEngine On
+RewriteCond %{HTTP:HTTPS} on
+RewriteRule (.*) http://%{SERVER_NAME}/$1 [QSA,L,R=301]
+```
+
+## How to troubleshoot HTTPS issues
+
+### How to fix the mixed content issue
+
+When using HTTPS, it needs to be used everywhere.
+It means that all the loaded elements on the webpage (pictures, CSS, JavaScripts) have to be loaded through HTTPS as well.
+
+A website that loads, for example, JavaScript scripts or external images by HTTP, will display an HTTPS alert in the browser (e.g.: “non Secure Content”).
+
+In some cases, it could not display it (Chrome did that in some cases).
+
+### How to fix the "insecure connection" issue
+
+
+
+This may happen for example if the subdomain does not exist in the certificate.
+
+In this case, you need to add the subdomain in the console, or if it exists already to add/delete it - or to create another subdomain (this will force the regeneration of the certificate).
+
+### How to fix the "connection error" issue
+
+
+
+This error message means that there is no certificate for this domain. You need to verify the DNS records and force the regeneration by creating a subdomain from the Dedibox console.
+
+### How to fix the "too many redirections" issue
+
+When using WordPress, you may encounter **Too many redirections** errors in your web browser.
+
+This can be fixed by installing the [Really Simple HTTPS](https://wordpress.org/plugins/really-simple-ssl/) plugin.
+
+When using the plugin, make sure that the following lines are not present in your `.htaccess` file:
+
+```
+RewriteEngine On
+RewriteCond %{HTTP:HTTPS} !on
+RewriteRule (.*) https://%{SERVER_NAME}/$1 [QSA,L,R=301]
+```
+
+
+ If you have installed WordPress according to the WordPress documentation, simply replace in the table `(prefix)_options` the `siteurl` and `home` entries from _https_ to _http_ before installing the aforementioned plugin.
+
+
+
diff --git a/pages/classic-hosting/how-to/encrypt-emails-with-pgp-using-webmail.mdx b/pages/classic-hosting/how-to/encrypt-emails-with-pgp-using-webmail.mdx
new file mode 100644
index 0000000000..0b99f7372d
--- /dev/null
+++ b/pages/classic-hosting/how-to/encrypt-emails-with-pgp-using-webmail.mdx
@@ -0,0 +1,74 @@
+---
+meta:
+ title: How to encrypt your emails with PGP using the Scaleway webmail
+ description: This page shows you how to encrypt your emails with PGP using the Scaleway webmail
+content:
+ h1: How to encrypt your emails with PGP using the Scaleway webmail
+ paragraph: This page shows you how to encrypt your emails with PGP using the Scaleway webmail
+tags: webhosting pgp webmail encryption encrypt
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+The [webmail](https://webmail.online.net/) used at Scaleway to read your emails, offers options to encrypt your mails with PGP, helping to ensure:
+
+- Confidentiality of emails
+- That the sender is who they claim to be
+
+
+ PGP encryption of your email includes a non-repudiation character. This means once the email is sent and received, you cannot deny having sent it.
+
+
+The [Scaleway webmail interface](https://webmail.online.net) currently offers one way of encrypting your emails: `Mailvelope`.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- Configured an email account
+
+## How to configure Mailvelope
+
+`Mailvelope` works on the client side and requires you to install an extension in your browser:
+
+* [Extension for Chrome](https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke).
+* [Extension for Firefox](https://download.mailvelope.com/releases/latest/mailvelope.firefox.xpi).
+
+1. Install the `Mailvelope` extension depending on the browser you use.
+2. Once the extension is installed, click **Options**.
+3. **Generate** or **import** an already existing key. You can keep the advanced parameters in their default values.
+
+4. Once generated or imported, the key appears in the list of available keys in the extension.
+
+5. Enter your Scaleway webmail interface and click the logo of the extension, then **Add**.
+
+## How to write a PGP signed or encrypted email
+
+1. Once you have configured the extension, go back to your webmail and open the interface for writing new emails.
+2. Click the **icon of the extension** to write an email with PGP. A pop-up displays.
+3. Write your email and click **sign** or **encrypt** the email.
+4. Enter your key password:
+
+5. Click **OK**.
+
+## How to encrypt and sign an email
+
+1. Choose your identity in the drop-down box.
+2. Choose the addressee of your email to be able to encrypt it with their public key.
+
+ To sign an email, you must choose your identity in both the drop-down box and **Encrypt for** section.
+
+
+## How to send an email
+
+1. Once you have been redirected after encrypting and/or signing, your email will appear in its final form in the window of the extension displaying:
+
+2. Click **Transfer** to transfer your email into your webmail's interface.
+3. Once transferred, you can send the email from your interface.
+
+
diff --git a/pages/classic-hosting/how-to/index.mdx b/pages/classic-hosting/how-to/index.mdx
new file mode 100644
index 0000000000..87d4b7c1a0
--- /dev/null
+++ b/pages/classic-hosting/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Webhosting Classic - How Tos
+ description: Webhosting Classic How Tos
+content:
+ h1: Webhosting Classic - How Tos
+ paragraph: Webhosting Classic How Tos
+---
diff --git a/pages/classic-hosting/how-to/manage-email-filter.mdx b/pages/classic-hosting/how-to/manage-email-filter.mdx
new file mode 100644
index 0000000000..4a62550186
--- /dev/null
+++ b/pages/classic-hosting/how-to/manage-email-filter.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: How to manage your email filters on Web Hosting Classic
+ description: This page shows you how to manage your email filters on Scaleway Web Hosting Classic.
+content:
+ h1: How to manage your email filters on Web Hosting Classic
+ paragraph: This page shows you how to manage your email filters on Scaleway Web Hosting Classic.
+tags: webhosting email-filter filter email
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+Email filters allow you to sort your emails based on the sender, subject, and more. If an email meets one or more criteria, you can define different actions, such as deleting or moving it into a folder. Email filters only work on email accounts.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+
+## How to configure your email filters?
+
+1. Log into your [Scaleway webmail](https://webmail.online.net/) account.
+2. Click **Settings** in the upper right corner of your screen, then click **Filters**. You can create filter groups, and activate or deactivate your filters by groups to easily manage your emails.
+
+
+ - Ensure no filter is active. If you activate a new filter group, the previous one will be disabled.
+ - We do not recommend naming your filter group console, as this is the name for default filters.
+
+
+
+## How to add new filter groups?
+
+1. Log into your [Scaleway webmail](https://webmail.online.net/) account.
+2. Click **Settings** in the upper right corner of your screen, then click **Filters**.
+3. Click **+** under the **Filter sets** column.
+4. Enter the name of your filter group in **Filters set name**.
+5. You can either import filters from a file or from another filter group.
+
+## How to add a filter?
+
+1. Log into your [Scaleway webmail](https://webmail.online.net/) account.
+2. Click **Settings** in the upper right corner of your screen, then click **Filters**.
+3. Click **+** under the **Filters** column.
+4. Enter the name of your filter in **Filter name**.
+5. Two input fields display. **For incoming mail** defines the requirements so that the mails undergo the action selected in the **execute the following actions** field.
+6. Once you have added your filter, click **Save**.
+
+## How to configure an automatic response?
+
+
+ - Setting up an automatic response on incoming mails can be useful when you will not have access to your mails for a while.
+
+
+1. Log into your [Scaleway webmail](https://webmail.online.net/) account.
+2. [Add a new filter](#how-to-add-a-filter) and name it **Auto Reply**. It should appear at the bottom of your filter list, under **antispam** and **antivirus**.
+3. Select **all messages** in the **For incoming mail** input field.
+4. Select **Reply with message** in the **execute the following actions** input field.
+5. Write your message in **Message body**.
+6. Type in **[Auto reply]** in **Message subject**.
+
+7. Click **Save**.
+
+
diff --git a/pages/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx b/pages/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx
new file mode 100644
index 0000000000..0c2ddcd7aa
--- /dev/null
+++ b/pages/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to manage MySQL databases with phpMyAdmin
+ description: This page explains how to manage MySQL databases with phpMyAdmin
+content:
+ h1: How to manage MySQL databases with phpMyAdmin
+ paragraph: This page explains how to manage MySQL databases with phpMyAdmin
+tags: webhosting mysql phpmyadmin database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **MySQL databases** in the side menu. The list of your databases displays.
+4. Click on the **Server** link for your database to access the phpMyAdmin interface. The phpMyAdmin interface displays in a new browser tab:
+
+
+ You can access phpMyAdmin directly at [https://phpmyadmin.online.net](https://phpmyadmin.online.net).
+
+5. Enter your MySQL database login as user and the database password to connect.
+
+
diff --git a/pages/classic-hosting/how-to/manage-postgresql-database-adminer.mdx b/pages/classic-hosting/how-to/manage-postgresql-database-adminer.mdx
new file mode 100644
index 0000000000..6641a367f3
--- /dev/null
+++ b/pages/classic-hosting/how-to/manage-postgresql-database-adminer.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to manage PostgreSQL databases with Adminer
+ description: This page explains how to manage PostgreSQL databases with Adminer
+content:
+ h1: How to manage PostgreSQL databases with Adminer
+ paragraph: This page explains how to manage PostgreSQL databases with Adminer
+tags: webhosting postgresql adminer database
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-05
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **PostgreSQL databases** in the side menu. The list of your databases displays.
+4. Click on the **Server** link for your database to access the Adminer interface. The Adminer interface displays in a new browser tab:
+
+
+ You can access Adminer directly at [https://adminer.online.net](https://adminer.online.net).
+
+5. Enter your PostgreSQL database login as user and the database password to connect.
\ No newline at end of file
diff --git a/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx b/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx
new file mode 100644
index 0000000000..d994f90779
--- /dev/null
+++ b/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: How to retrieve the header of an email
+ description: This guide shows you how to retrieve the header of an email on Scaleway Web Hosting using different email clients like Thunderbird, Gmail, Outlook, and Mail for Mac.
+content:
+ h1: How to retrieve the header of an email
+ paragraph: This guide shows you how to retrieve the header of an email on Scaleway Web Hosting using different email clients like Thunderbird, Gmail, Outlook, and Mail for Mac.
+tags: webhosting email header thunderbird
+dates:
+ validation: 2024-08-12
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+The header of an email contains essential information about the path and origins of the email before it arrives in your mailbox. It is comparable to the postmark and routing information on a physical envelope sent through the mail.
+
+## Why email headers are important
+
+Email headers can provide crucial information about the origin of an email, the servers it passed through, and various technical details that may help in troubleshooting or verifying the authenticity of the email.
+Email headers are often required when reporting spam, investigating delivery issues, or diagnosing potential security threats. In some cases, email headers may contain information required by technical support to diagnose issues or verify the authenticity of an email. The method for retrieving this information varies depending on the email client you use.
+
+## Retrieving email headers
+
+### How to retrieve email headers in Thunderbird
+
+1. Select the email in your inbox that you need to investigate.
+2. In the preview pane, click **Others**, then select **View Source**. A new window will open displaying the email's source code, including its headers.
+3. Copy the relevant header information from this window.
+
+### How to retrieve email headers in Gmail
+
+1. Log in to your Gmail account.
+2. Open the email containing the desired headers.
+3. Click the **downward arrow** in the upper-right corner of the email (next to the reply button).
+4. Select **Show original** from the dropdown menu. The headers will be displayed in a new window.
+5. Copy the header information as needed.
+
+### How to retrieve email headers in Outlook
+
+1. Navigate to your list of messages and double-click the email you wish to view. This will open the message in a new window.
+2. Click on **File** > **Properties**. A new window will appear showing the email properties.
+3. Copy the headers from the "Internet headers" section.
+
+### How to retrieve email headers in Outlook Web Mail
+
+1. Log in to your Microsoft account.
+2. Open the email for which you want to retrieve the headers.
+3. Click the **downward arrow** in the email's top right corner. A menu appears.
+4. Click **View Message Source**. This will open a new window showing the message's source code, including the headers.
+5. Copy the header information from the "Internet Headers" section.
+
+### How to retrieve email headers in Mail for Mac
+
+1. Open the Mail application on your Mac, then select the email you need.
+2. Press **Cmd + Shift + H**. A new window will open, displaying the email's header.
+3. Copy the relevant header information from this window.
\ No newline at end of file
diff --git a/pages/classic-hosting/how-to/solve-email-account-connection-problems.mdx b/pages/classic-hosting/how-to/solve-email-account-connection-problems.mdx
new file mode 100644
index 0000000000..8e004fc8fb
--- /dev/null
+++ b/pages/classic-hosting/how-to/solve-email-account-connection-problems.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to solve connection problems to your email account
+ description: Learn how to resolve connection problems with your email account on Web Hosting Classic quickly and easily.
+content:
+ h1: How to solve connection problems to your email account
+ paragraph: Learn how to resolve connection problems with your email account on Web Hosting Classic quickly and easily.
+tags: webhosting connection problem error email
+dates:
+ validation: 2024-12-23
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a **Webhosting Classic**
+- Created an [email account](/classic-hosting/how-to/create-email-account/)
+
+1. Log into the [Scaleway webmail interface](https://webmail.online.net/).
+2. Verify if your emails are available from the Scaleway webmail interface.
+
+ - If you can connect to your email account using the Scaleway webmail, the problem you are experiencing might come from the configuration of your computer.
+
+3. Verify the [configuration of your client](/classic-hosting/how-to/check-emails/).
+
+ - Some email clients cut the domain part of your email address in the username by default. For example, with the email address “[firstname.lastname@example.com](mailto:firstname.lastname@example.com)”, your client cuts it to “firstname.lastname”. Make sure to enter your complete email address as your username.
+
+4. Verify your username and make sure to use your entire email address (for example "[firstname.lastname@example.com](mailto:firstname.lastname@example.com)").
+
+
diff --git a/pages/classic-hosting/how-to/terminate-online-classic-hosting.mdx b/pages/classic-hosting/how-to/terminate-online-classic-hosting.mdx
new file mode 100644
index 0000000000..8e5f2b3318
--- /dev/null
+++ b/pages/classic-hosting/how-to/terminate-online-classic-hosting.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to terminate an Online Web Hosting plan
+ description: Learn how to terminate a Online Web Hosting plan
+content:
+ h1: How to terminate an Online Web Hosting plan
+ paragraph: This guide explains how to terminate a Online Web Hosting plan
+ tags: hosting webhosting terminate online-console dedibox delete
+dates:
+ posted: 2024-12-17
+ validation: 2024-12-17
+categories:
+ - dedibox-console
+---
+
+This page shows you how to terminate an Online (Dedibox) Web Hosting plan.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- An active Online Web Hosting plan
+
+## How to terminate your Online Web Hosting plan
+
+1. Click your username, next to _logged in as_, in the top right corner of the [Online console](https://console.online.net/). From the drop-down menu, select **Services**. The service page displays.
+2. Click **Detail** next to the Web Hosting plan you want to terminate. The **Hosting plan information** page displays.
+3. Click **Terminate**. A pop-up displays.
+4. Click **Confirm Termination**. The Web Hosting plan and all associated options display.
+5. Check the **Reason for termination** box which best suits your case.
+6. Click **TERMINATE THIS SERVICE AND OPTION ASSOCIATED** to confirm the termination.
+
+
+Your Online Web Hosting plan will be terminated immediately.
+Before terminating, ensure that you have saved all your files from FTP and all emails from webmail or your mail client.
+
diff --git a/pages/classic-hosting/index.mdx b/pages/classic-hosting/index.mdx
new file mode 100644
index 0000000000..34f1dd208c
--- /dev/null
+++ b/pages/classic-hosting/index.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Webhosting Classic Documentation
+ description: Dive into Scaleway Webhosting Classic with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
diff --git a/pages/classic-hosting/quickstart.mdx b/pages/classic-hosting/quickstart.mdx
new file mode 100644
index 0000000000..ac27a96be3
--- /dev/null
+++ b/pages/classic-hosting/quickstart.mdx
@@ -0,0 +1,103 @@
+---
+meta:
+ title: Webhosting Classic - Quickstart
+ description: This page shows you how to get started with Scaleway Webhosting Classic.
+content:
+ h1: Webhosting Classic - Quickstart
+ paragraph: This page shows you how to get started with Scaleway Webhosting Classic.
+tags: webhosting webhosting-classic ftp-account webmail
+dates:
+ validation: 2024-08-19
+ posted: 2021-08-11
+categories:
+ - webhosting
+---
+
+
+
+Scaleway Webhosting Classic is our historical Webhosting service. It allows you to host your personal website and create personalized email addresses using your domain name.
+
+
+ * Webhosting Classic reached its end of life and is no longer available for new customers. We recommend our [Cloud Hosting](https://www.scaleway.com/en/web-hosting/) offers for new subscriptions.
+ * Existing customers of Webhosting Classic can continue to use and configure their hosting as usual.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A **Webhosting Classic** and a domain name
+
+## How to create an email account
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **Manage** in the **E-mail accounts** section of the side menu. The email accounts overview page displays.
+4. Click **Add account**. A pop-up displays.
+
+5. Enter the login (the part before the @) for your email address, a password and its confirmation. Then click **Add account**.
+
+ - The status of the account changes to **Waiting for update**. During this time, no other change to the email account is possible.
+ - The new email account will be created within one hour maximum.
+
+
+
+## How to access your email using the webmail client
+
+1. The webmail client is available at [https://webmail.online.net](https://webmail.online.net). Open it in a browser.
+2. Log into the webmail client by entering your complete email address and its password in the form.
+
+ The webmail interface displays. You can now read and send your emails from your web browser.
+
+## How to change the password of my email account
+
+1. Click **Hosting** then click **Manage**.
+2. Scroll down to **E-mail accounts** and click **Manage**.
+3. Click the settings icon next to the email account you wish to update.
+4. Click **Update password**. A window displays.
+5. Type in your new password and confirm it, then click **Update Password**. Your new password is now registered.
+
+
+ - The status of the account changes to **Waiting for update**. During this time, no other change to the email account is possible.
+ - The new password will be set within one hour maximum.
+
+
+## How to create an FTP account
+
+1. Click **Hosting** then click **Manage**.
+2. Click the **FTP accounts** tab.
+3. A form displays. Fill it out to create your FTP account.
+4. Enter the following values:
+ * Your username
+ * Your password
+ * The path which has to be an already existing directory on your FTP
+5. Validate your entries.
+
+ - Your FTP account appears in the account list with the status **Waiting to create**. Your account will be activated in about one hour.
+
+6. When you connect to your FTP account, the following folders display:
+* `awffull` (contains your old access statistics, if they were activated)
+* `www` (should contain your website)
+* `logs` (contains your old access statistics, if they were activated)
+* `UPLOAD_YOUR_SITE_IN_THE_REPERTORY_WWW` (this directory only serves as a reminder)
+
+
+ - Keep in mind that your website is located in the folder `/www` on the FTP server.
+ - Upload all your website's content into this folder.
+
+
+## How to create a MySQL database
+
+1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays.
+2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays.
+3. Click **MySQL databases** in the side menu. The list of your databases displays.
+4. Click **Add database**. A pop-up displays.
+5. Enter the database name, the database password, and its confirmation. Then click **Create MySQL database**.
+
+ For a strong password, combine lowercase, uppercase, numbers, and special characters.
+
+
+Your database is being created and displays in the list of your MySQL databases.
+
+
+ For MySQL databases, [size limitations apply](/classic-hosting/how-to/create-mysql-database/#limitations).
+
\ No newline at end of file
diff --git a/pages/cockpit/api-cli/assets/scaleway-data-source-url.webp b/pages/cockpit/api-cli/assets/scaleway-data-source-url.webp
new file mode 100644
index 0000000000..316d2255ef
Binary files /dev/null and b/pages/cockpit/api-cli/assets/scaleway-data-source-url.webp differ
diff --git a/pages/cockpit/api-cli/configuring-grafana-agent.mdx b/pages/cockpit/api-cli/configuring-grafana-agent.mdx
new file mode 100644
index 0000000000..b9fbb39d09
--- /dev/null
+++ b/pages/cockpit/api-cli/configuring-grafana-agent.mdx
@@ -0,0 +1,268 @@
+---
+meta:
+ title: Configuring the Grafana agent
+ description: This page provides information on how to configure the Grafana agent, push data sources, and visualize them in Grafana
+content:
+ h1: Configuring the Grafana agent
+ paragraph: This page provides information on how to configure the Grafana agent, push data sources, and visualize them in Grafana
+tags: cockpit observability grafana-agent
+dates:
+ validation: 2024-10-15
+ posted: 2023-01-10
+categories:
+ - observability
+---
+
+This page explains how to configure the Grafana agent and the Zipkin collector to push your metrics, logs, and traces. You can use it to **push your data from Scaleway resources or external resources**.
+
+
+ [The Grafana agent has been deprecated by Grafana](https://grafana.com/docs/agent/latest/). Find out [how to configure Grafana Alloy](/cockpit/how-to/send-metrics-with-grafana-alloy/#configuring-grafana-alloy) which is Grafana's new telemetry collector.
+
+
+
+
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - Installed [Docker](https://www.docker.com/) and [Docker compose](https://docs.docker.com/compose/install/)
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## Configuring and running the Grafana agent
+
+
+ It is not currently possible to collect logs if you are using OSX.
+
+
+1. [Create a token](/cockpit/how-to/create-token/) and select the push permission for metrics, traces, and logs.
+2. Create a folder where you will keep your configuration files.
+3. Create a configuration file inside your folder and name it `config.yaml`. This file will contain the Grafana agent configuration.
+4. Copy the following YAML template.
+
+
+ - Make sure you replace `` with `https://metrics.cockpit.fr-par.scw.cloud/api/v1/push`, `` with `https://logs.cockpit.fr-par.scw.cloud/loki/api/v1/push` and `` with `https://traces.cockpit.fr-par.scw.cloud/otlp`
+ - Make sure you replace ``, `` and `` with the token you created in step 1
+
+
+ ```
+ metrics:
+ wal_directory: /tmp/agent
+ global:
+ scrape_interval: 60s
+ remote_write:
+ - url:
+ headers:
+ "X-Token":
+
+ logs:
+ positions_directory: /tmp/positions/
+ configs:
+ - name: scw
+ clients:
+ - url:
+ tenant_id:
+ scrape_configs:
+ - job_name: varlogs
+ static_configs:
+ - targets: [localhost]
+ labels:
+ job: varlogs
+ __path__: /host/root/var/log/*.log
+
+ traces:
+ configs:
+ - name: default
+ remote_write:
+ - endpoint:
+ headers:
+ X-TOKEN:
+ protocol: http
+ format: otlp
+ receivers:
+ otlp:
+ protocols:
+ grpc:
+ http:
+ zipkin:
+ endpoint: 0.0.0.0:9411
+
+ integrations:
+ node_exporter:
+ enabled: true
+ rootfs_path: /host/root
+ sysfs_path: /host/sys
+ procfs_path: /host/proc
+ # Anything not provided in the list below will be disabled by default
+ set_collectors:
+ - uname
+ - cpu
+ - loadavg
+ - meminfo
+ - filesystem
+ - netdev
+ - boottime
+ - time
+ - stat
+ ```
+
+ Your configuration file should look like the following:
+
+ ```
+ metrics:
+ wal_directory: /tmp/agent
+ global:
+ scrape_interval: 60s
+ remote_write:
+ - url: https://metrics.cockpit.fr-par.scw.cloud/api/v1/push
+ headers:
+ "X-Token": B6GI9xwdtWBxNcFlSxAWOM65R2aGpbTIbS4THIE4JmYZ6eQfj9upxPk5SfhdBm3
+
+ logs:
+ positions_directory: /tmp/positions/
+ configs:
+ - name: scw
+ clients:
+ - url: https://logs.cockpit.fr-par.scw.cloud/loki/api/v1/push
+ tenant_id: B6GI9xwdtWBxNcFlSxAWOM65R2aGpbTIbS4THIE4JmYZ6eQfj9upxPk5SfhdBm3
+ scrape_configs:
+ - job_name: varlogs
+ static_configs:
+ - targets: [localhost]
+ labels:
+ job: varlogs
+ __path__: /host/root/var/log/*.log
+
+ traces:
+ configs:
+ - name: default
+ remote_write:
+ - endpoint: https://traces.cockpit.fr-par.scw.cloud/otlp
+ headers:
+ X-TOKEN: B6GI9xwdtWBxNcFlSxAWOM65R2aGpbTIbS4THIE4JmYZ6eQfj9upxPk5SfhdBm3
+ protocol: http
+ format: otlp
+ receivers:
+ otlp:
+ protocols:
+ grpc:
+ http:
+ zipkin:
+ endpoint: 0.0.0.0:9411
+
+ integrations:
+ node_exporter:
+ enabled: true
+ rootfs_path: /host/root
+ sysfs_path: /host/sys
+ procfs_path: /host/proc
+ # Anything not provided in the list below will be disabled by default
+ set_collectors:
+ - uname
+ - cpu
+ - loadavg
+ - meminfo
+ - filesystem
+ - netdev
+ ```
+5. You can also specify the [data source](/cockpit/concepts/#data-sources) containing your [data types](/cockpit/concepts/#data-types) by:
+ - Adding the ID of the data source to the endpoint. You can retrieve the ID of the data source you want to configure using the `ListDataSources` API command, or
+ - Adding the `X-Datasource-Id` header in the `headers` section, under `X-Token`.
+
+ If you do not specify a data source, your data will automatically be pushed to the default data source for the concerned data type.
+
+
+ Below is an example of what your **Traces** configuration should look like if you add the `X-Datasource-Id` header:
+
+ ```
+ traces:
+ configs:
+ - name: default
+ remote_write:
+ - endpoint: https://traces.cockpit.fr-par.scw.cloud/otlp
+ headers:
+ X-TOKEN: B6GI9xwdtWBxNcFlSxAWOM65R2aGpbTIbS4THIE4JmYZ6eQfj9upxPk5SfhdBm3
+ X-Datasource-Id:
+ protocol: http
+ format: otlp
+ receivers:
+ otlp:
+ protocols:
+ grpc:
+ http:
+ zipkin:
+ endpoint: 0.0.0.0:9411
+ ```
+
+6. In the same folder, create another file and name it `docker-compose.yaml`.
+7. Copy the following template and paste it into your file:
+
+ ```
+ version: "3"
+ services:
+ agent:
+ image: grafana/agent:latest
+ restart: always
+ ports:
+ - "9411:9411"
+ volumes:
+ - "./config.yaml:/etc/agent-config/agent.yaml:ro"
+ - "/:/host/root:ro"
+ - "/sys:/host/sys:ro"
+ - "/proc:/host/proc:ro"
+ - "/tmp/agent:/etc/agent"
+ entrypoint:
+ - /bin/grafana-agent
+ - -config.file=/etc/agent-config/agent.yaml
+ - -metrics.wal-directory=/tmp/agent/wal
+ network_mode: "host"
+ pid: "host"
+ ```
+
+8. Run the following command to open your folder containing your configuration files:
+
+ ```
+ cd
+ ```
+9. Run the following command to bring the Grafana Agent container up:
+
+ ```
+ docker compose up
+ ```
+
+ Run `sudo docker compose up` if you are using Linux and your user is not in the docker group.
+
+
+## Visualizing metrics in Grafana
+
+1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+2. Click the **Toggle menu** icon.
+3. Click **Dashboards**.
+4. Click **New** then click **Import** to import your Grafana dashboard.
+5. Enter `1860`, which is the ID of the [Node Exporter Full](https://grafana.com/grafana/dashboards/1860-node-exporter-full/) dashboard, in the **Import via grafana.com** field and click **Load**.
+
+6. Enter a name for your dashboard in the **Name** field.
+7. Select the **Metrics** data source and click **Import**. Your dashboard displays with your metrics.
+
+## Visualizing logs in Grafana
+
+1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+2. Click **Explore**.
+
+3. Select the **Scaleway logs** data source in the drop-down.
+4. Configure a query using the instructions that display on your screen.
+5. Click **Run query**. Your logs display.
+6. Optionally, click the **Live** button on the top right corner of your screen to see your logs arriving in real time.
+
+## Visualizing traces in Grafana
+
+1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+2. Click the **Toggle menu** icon.
+3. Click **Explore** next to the compass icon.
+4. Select the **Traces** data source from the drop-down.
+5. Configure the queries you wish to apply to your traces. Your traces display.
+
+
+ Refer to the [Grafana documentation](https://grafana.com/docs/grafana/latest/panels-visualizations/visualizations/traces/#add-a-panel-with-tracing-visualizations) to learn more about how to visualize your traces.
+
diff --git a/pages/cockpit/api-cli/index.mdx b/pages/cockpit/api-cli/index.mdx
new file mode 100644
index 0000000000..9e06f1c177
--- /dev/null
+++ b/pages/cockpit/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Cockpit - API/CLI Documentation
+ description: Cockpit API/CLI Documentation
+content:
+ h1: API/CLI Documentation
+ paragraph: Cockpit API/CLI Documentation
+---
diff --git a/pages/cockpit/api-cli/querying-logs-with-logcli.mdx b/pages/cockpit/api-cli/querying-logs-with-logcli.mdx
new file mode 100644
index 0000000000..487fe7f9bf
--- /dev/null
+++ b/pages/cockpit/api-cli/querying-logs-with-logcli.mdx
@@ -0,0 +1,88 @@
+---
+meta:
+ title: Retrieving logs programmatically using LogCLI
+ description: Learn how to programmatically retrieve logs stored in Cockpit using LogCLI. Explore efficient querying methods to automate log retrieval from various data sources like Kubernetes clusters and Object Storage buckets.
+content:
+ h1: Retrieving logs programmatically using LogCLI
+ paragraph: Learn how to programmatically retrieve logs stored in Cockpit using LogCLI. Explore efficient querying methods to automate log retrieval from various data sources like Kubernetes clusters and Object Storage buckets.
+tags: cockpit observability logs logcli
+dates:
+ validation: 2024-09-19
+ posted: 2024-05-22
+categories:
+ - observability
+---
+
+
+This documentation page shows you how to retrieve your Scaleway and custom logs stored in Cockpit programmatically, using [LogCLI](https://grafana.com/docs/loki/latest/query/logcli/).
+
+Retrieving your logs programmatically can be useful in environments where automation, scalability, and integration with other systems are crucial. It enables advanced analytics, greater efficiency, and deeper insights than manual log retrieval through a user interface such as Grafana.
+
+
+
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - [Created a token](/cockpit/how-to/create-token/) with the `query` permission for logs
+ - Custom and/or Scaleway logs to query
+ - [Installed LogCLI](https://grafana.com/docs/loki/latest/query/logcli/#installation)
+
+
+## Exporting your environment variables
+
+Open a terminal and run the following command to export your environment variables. Make sure that you replace `` and `` with your values.
+
+ ```
+ export LOKI_ADDR=
+ export LOKI_BEARER_TOKEN=
+ ```
+
+
+ You can retrieve your data source URL in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) under the **API URL** section.
+
+
+
+## Retrieving logs
+
+### Retrieving an Object Storage bucket's logs
+
+Open a terminal and paste the following command to retrieve logs from your desired data source. For the sake of this documentation, we are retrieving logs from a Scaleway Object Storage bucket. You can replace `object_storage_bucket` with any other Scaleway resource type, provided that the resource has logs available.
+
+ ```
+ logcli query '{resource_type="object_storage_bucket"}'
+ ```
+An output similar to the following should display:
+
+```
+2024/05/20 17:04:33 _range?direction=BACKWARD&end=1716390273303145000&limit=30&query=%7Bresource_type%3D%22object_storage_bucket%22%7D&start=1716386673303145000
+```
+
+### Retrieving a Kubernetes Kapsule cluster's logs
+
+Open a terminal and paste the following command to retrieve logs from your Kapsule cluster.
+
+ ```
+ logcli query '{resource_type="kubernetes_cluster"}'
+ ```
+
+An output similar to the following should display:
+
+ ```
+ 2024/05/22 17:33:19 _range?direction=BACKWARD&end=1716391999461784000&limit=30&query=%7Bresource_type%3D%22kubernetes_cluster%22%7D&start=1716388399461784000
+ 2024/05/22 17:33:19 Common labels: {level="I", log_type="control-plane", region="fr-par", resource_id="36f08aaf-f208-4d58-9385-5064cde63792", resource_name="k8s-sharp-robinson", resource_type="kubernetes_cluster"}
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 legacy.go:727] No candidates for scale down
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 static_autoscaler.go:544] Starting scale down
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 static_autoscaler.go:535] Scale down status: lastScaleUpTime=2024-05-22 14:20:23.13076564 +0000 UTC m=-3598.920416647 lastScaleDownDeleteTime=2024-05-22 14:20:23.13076564 +0000 UTC m=-3598.920416647 lastScaleDownFailTime=2024-05-22 14:20:23.13076564 +0000 UTC m=-3598.920416647 scaleDownForbidden=false scaleDownInCooldown=false
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 pre_filtering_processor.go:57] Node scw-k8s-sharp-robinson-default-e110ac268b5546d should not be processed by cluster autoscaler (no node group config)
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 pre_filtering_processor.go:57] Node scw-k8s-sharp-robinson-default-7cefec16593342e should not be processed by cluster autoscaler (no node group config)
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 pre_filtering_processor.go:57] Node scw-k8s-sharp-robinson-default-bfb90f82c4b949c should not be processed by cluster autoscaler (no node group config)
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 static_autoscaler.go:492] Calculating unneeded nodes
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 static_autoscaler.go:445] No unschedulable pods
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 filter_out_schedulable.go:87] No schedulable pods
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 filter_out_schedulable.go:177] 0 pods marked as unschedulable can be scheduled.
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 filter_out_schedulable.go:176] 0 pods were kept as unschedulable based on caching
+ 2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522 1 filter_out_schedulable.go:137] Filtered out 0 pods using hints
+ ```
+
+
+ You can tailor your `logcli query` command according to your needs using the [LogCLI flags and commands](https://grafana.com/docs/loki/latest/query/logcli/#logcli-command-reference). Enter `logcli help` in your terminal to see the available flags and commands, and examples of how to use them.
+
diff --git a/pages/cockpit/assets/scaleway-instance-grafana-alert.webp b/pages/cockpit/assets/scaleway-instance-grafana-alert.webp
new file mode 100644
index 0000000000..73cf74a49b
Binary files /dev/null and b/pages/cockpit/assets/scaleway-instance-grafana-alert.webp differ
diff --git a/pages/cockpit/assets/scaleway-traces-concept.webp b/pages/cockpit/assets/scaleway-traces-concept.webp
new file mode 100644
index 0000000000..374167036b
Binary files /dev/null and b/pages/cockpit/assets/scaleway-traces-concept.webp differ
diff --git a/pages/cockpit/assets/scaleway_obs_dashboards_browse.webp b/pages/cockpit/assets/scaleway_obs_dashboards_browse.webp
new file mode 100644
index 0000000000..3a1555b8d5
Binary files /dev/null and b/pages/cockpit/assets/scaleway_obs_dashboards_browse.webp differ
diff --git a/pages/cockpit/assets/scaleway_obs_import_dashboard.webp b/pages/cockpit/assets/scaleway_obs_import_dashboard.webp
new file mode 100644
index 0000000000..f23b28db7d
Binary files /dev/null and b/pages/cockpit/assets/scaleway_obs_import_dashboard.webp differ
diff --git a/pages/cockpit/assets/scaleway_obs_logs_compass.webp b/pages/cockpit/assets/scaleway_obs_logs_compass.webp
new file mode 100644
index 0000000000..b97fb91b07
Binary files /dev/null and b/pages/cockpit/assets/scaleway_obs_logs_compass.webp differ
diff --git a/pages/cockpit/concepts.mdx b/pages/cockpit/concepts.mdx
new file mode 100644
index 0000000000..d42eb72576
--- /dev/null
+++ b/pages/cockpit/concepts.mdx
@@ -0,0 +1,216 @@
+---
+meta:
+ title: Cockpit - Concepts
+ description: Explore Scaleway Observability concepts including metrics, logs, and alerts management through Cockpit. Learn about agents, alerting rules, Grafana integration, and data types for comprehensive monitoring.
+content:
+ h1: Cockpit - Concepts
+ paragraph: Explore Scaleway Observability concepts including metrics, logs, and alerts management through Cockpit. Learn about agents, alerting rules, Grafana integration, and data types for comprehensive monitoring.
+tags: observability alert-manager contact-points endpoint grafana loki logql prometheus promql tokens
+dates:
+ validation: 2024-12-26
+categories:
+ - observability
+---
+
+## Active series
+
+Active series refer to [time series](#time-series) for which the latest [samples](#samples) received by your Cockpit are less than 10 minutes old.
+
+## Agent
+
+An agent is a software component that runs on your systems to gather [data types](#data-types) from the host system or applications running on it. The agent then forwards this data to Cockpit for analysis and visualization.
+
+
+ Find out how to [configure the Grafana Alloy agent to collect and send your data to Cockpit](/cockpit/how-to/send-metrics-with-grafana-alloy/).
+
+
+## Alerting
+
+Alerting detects complex conditions defined by a rule and keeps you aware of issues in your environments. When a condition defined by a rule is met, the rule tracks it as an alert and responds by triggering one or more actions.
+
+
+ The **Grafana alert manager** on the Grafana interface is inactive. We strongly recommend that you select the **Scaleway Alerting** alert manager if you want to manage your alerts using Grafana.
+
+
+## Alert manager
+
+Scaleway's regionalized alert manager allows you to manage and respond to alerts according to the regions you have enabled it in. It handles alerts sent when the alerting rules we run are firing. The alert manager triggers alerts (e.g. emails or texts) if a criteria you have configured on your applications' metrics and logs is activated.
+
+
+ The **Grafana alert manager** on the Grafana interface is inactive. We strongly recommend that you select the **Scaleway Alerting** alert manager if you want to manage your alerts using Grafana.
+
+
+## Alerting rules
+
+Alerting rules allow you to define criteria that determine whether an alert is triggered. The rule consists of queries and expressions, a condition, the frequency of evaluation, and the duration over which the condition is met. They act as alarm sensors: when an alert is triggered, a notification is sent to the alert manager, which forwards the notification to receivers.
+
+
+ If you plan on setting up alerting rules with Grafana, use the Mimir or Loki alerts rather than the Grafana managed alert.
+
+
+## Cockpit
+
+A Cockpit is an instance of the Observability product that stores metrics, logs, and traces and provides a dedicated dashboarding system on Grafana to visualize them. A Scaleway Project can have only one Cockpit, which is automatically activated when you are using [Scaleway resources that are integrated into Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit).
+
+## Contact points
+
+Contact points define who is notified when an alert fires, according to the region in which you have added them. Contact points include emails, Slack, on-call systems, and texts. When an alert fires, all contact points are notified.
+
+## Data sources
+
+Data sources are regionalized backends that allow you to store and fetch your metrics, logs, and traces. By default, **Scaleway data sources** are enabled if you are using [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) on your Project.
+
+Scaleway data sources are **read-only**.
+
+You can [create](/cockpit/how-to/create-external-data-sources/) additional **custom data sources** in the Paris, Amsterdam, and Warsaw regions, from your own external resources.
+
+## Data types
+
+Data types refer to the categories of data you can collect for monitoring and observability. There are three data types:
+
+- [Metrics](#metric), which are numeric measurements. They are used for performance monitoring.
+- [Logs](#logs), which are textual records of events generated by your applications. They are used for event and error monitoring.
+- [Traces](#traces), which are data structures that represent the path of a request. They are used for request-behavior-monitoring.
+
+## Endpoints
+
+An endpoint is the point of entry in a communication channel when two systems are interacting. The endpoint is the means from which the API can access the resources they need from a server to perform their task. An endpoint can include a URL of a server or service. The Observability Cockpit provides four endpoints:
+
+- A Prometheus-compatible endpoint responsible for dealing with metrics
+- A Loki-compatible endpoint responsible for dealing with logs
+- A Prometheus-compatible endpoint responsible for configuring your alert manager
+- A Tempo-compatible endpoint responsible for dealing with traces
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month.
+ - Sending metrics, logs and traces for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## Grafana users
+
+A Grafana user is any individual who can log in to [Grafana](https://grafana.com). Each user is associated with a role. There are two types of roles a user can have:
+
+- a viewer: can only view dashboards
+- an editor: can build and view dashboards
+
+
+ - Managed dashboards in the "Scaleway" folder are always read-only, regardless of your role.
+ - The `admin` user is not yet available for creation.
+
+
+## Loki
+
+Loki is the log aggregation system used by [Grafana](https://grafana.com/docs/grafana/latest/introduction/) to store and query your logs.
+
+## Loki Remote Write
+
+`Loki Remote Write` is the protocol used to push your logs to your Cockpit's logs' endpoint.
+
+## LogQL
+
+LogQL is [Grafana Loki’s language](https://grafana.com/docs/loki/latest/logql/) for querying logs. LogQL uses labels and operators for filtering.
+
+## Logs
+
+Logs are a data type that provides a record of all events and errors taking place during the lifecycle of your resources. They represent an excellent source of visibility if you want to know when a problem occurred, or which events correlate with it.
+
+You can push logs with any Loki-compatible agent such as [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/), [Fluentd](https://docs.fluentd.org/), [Fluent Bit](https://docs.fluentbit.io/manual/) or [Logstash](https://www.elastic.co/guide/en/logstash/current/introduction.html).
+
+## Preconfigured alerts
+
+Preconfigured alerts are regionalized alerting rules that Scaleway defines for you. They are active in all the regions where you have enabled the [alert manager](#alert-manager). You can think of them as alarm sensors. They allow you to receive alerts for behaviors that we deem abnormal on your resources. Preconfigured alerts only apply to the metrics and logs of your Scaleway resources.
+
+
+ You must enable the alert manager to enable preconfigured alerts. Preconfigured alerts will only be active in the regions where you have enabled the alert manager.
+
+
+
+## Managed dashboards
+
+A managed dashboard is a set of one or more panels that Scaleway sets up and updates for you to visualize the metrics and logs associated with your Scaleway products.
+
+## Metric
+
+A metric is a lifecycle-related numerical representation of data (e.g. disk usage and CPU usage) measured over intervals of time. Metrics give you a bird's eye view of your infrastructure.
+
+You can push metrics with any Prometheus-compatible agent such as [Prometheus](https://prometheus.io/docs/introduction/overview/), [Grafana](https://grafana.com/docs/agent/latest/) or [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/).
+
+## Mimir
+
+[Grafana Mimir](https://github.com/grafana/mimir) is an open source software project that allows you to store your metrics by providing long-term storage for [Prometheus](https://prometheus.io/docs/introduction/overview/#what-is-prometheus).
+
+## Prometheus Remote Write
+
+`Prometheus Remote Write` is the protocol used to push your metrics to your Cockpit's metrics' endpoint.
+
+## PromQL
+
+PromQL, short for Prometheus Querying Language, is the main way to query metrics within Prometheus. It is designed for building queries for graphs and alerts.
+
+## Receivers
+
+Receivers are hubs consisting of contact points. You can associate one or several alerts with one or more receivers. This allows you to diversify your alerts.
+
+## Recording rules
+
+Recording rules allow you to precompute frequently needed or computationally expensive expressions and save their results as a new set of time series.
+
+## Region
+
+A region is the geographical area in which your Cockpit data is stored. They are duplicated on all Availability Zones of the selected regions (Paris, Amsterdam, or Warsaw).
+
+You can decide in which region to enable the [alert manager](#alert-manager) and your [preconfigured alerts](#preconfigured-alerts). You can also choose the regions in which to create your [data types](#data-types), [data sources](#data-sources), and [tokens](#tokens).
+
+## Retention
+
+Retention or data retention refers to the duration for which data, such as metrics, logs, or traces, is stored before being automatically deleted. Retention allows you to manage the lifecycle of your Scaleway and custom data by selecting storage periods that align with your needs.
+
+The minimum and maximum retention periods for each data source type are as follows:
+
+| Custom metrics | Custom logs/traces | Scaleway metrics | Scaleway logs/traces |
+|------------------------------------------------|---------------------------------------------|------------------------------------------------|---------------------------------------------|
+| Minimum retention period: 1 day | Minimum retention period: 1 day | Minimum retention period: 31 days | Minimum retention period: 1 day |
+| Maximum retention period: 365 days (12 months) | Maximum retention period: 31 days (1 month) | Maximum retention period: 365 days (12 months) | Maximum retention period: 31 days (1 month) |
+| Default retention period: 31 days | Default retention period: 7 days | Default retention period: 31 days | Default retention period: 7 days |
+
+## Samples
+
+A sample is a unique measuring point on a time series.
+
+## Tempo
+
+Tempo is [Grafana's open source](https://grafana.com/docs/tempo/latest/) tracing tool that allows you to search for traces, generate metrics from them, and link your tracing data with logs and metrics. Tempo can be used with open-source tracing protocols such as [Jaeger](https://www.jaegertracing.io/docs/1.50/), [Zipkin](https://zipkin.io/), and [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/).
+
+
+ During the beta of the traces feature, only the [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) HTTP push path is supported. Scaleway is working on implementing the [Open Telemetry gRPC](https://opentelemetry.io/docs/specs/semconv/rpc/grpc/), [Zipkin](https://zipkin.io/) and [Jaeger](https://www.jaegertracing.io/docs/1.50/) protocols.
+
+
+## Time series
+
+A time series is a sequence of numerical data points in successive order, that tracks the value of a parameter over time. Example of parameter: the disk usage of a machine hosting a database, expressed in percentage.
+
+## Tokens
+
+Tokens are regionalized secret keys that allow you to authenticate against your Cockpit's endpoints (metrics, logs, alerts). You can generate new tokens and select token permissions such as:
+
+- **Push**: allows you to send your metrics, logs, and traces to your Cockpit.
+- **Query**: allows you to fetch your metrics, logs, and traces from your Cockpit.
+- **Rules**: allow you to configure alerting and recording rules.
+- **Alerts**: allow you to set up the alert manager.
+
+## TraceQL
+
+[TraceQL](https://grafana.com/docs/tempo/latest/traceql/) is Grafana Tempo's query language designed for searching and extracting traces.
+
+## Traces
+
+Traces are detailed records of your **requests' behavior**, as they move through distributed systems such as microservices and containers.
+
+Traces are an effective way to identify performance issues and bottlenecks in your environments, as they break down what happens within a request and provide information such as the moment a request starts and finishes, the events that occur, and their duration, as well as additional context.
+
+You can push traces with the Tempo-compatible agent supported by Scaleway: [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/).
+
+
+
+
+Scaleway only supports the [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) agent for pushing traces.
diff --git a/pages/cockpit/how-to/access-grafana-and-managed-dashboards.mdx b/pages/cockpit/how-to/access-grafana-and-managed-dashboards.mdx
new file mode 100644
index 0000000000..f94ee2db2f
--- /dev/null
+++ b/pages/cockpit/how-to/access-grafana-and-managed-dashboards.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to access Grafana and your managed dashboards
+ description: Learn to access your Grafana managed dashboards, including steps to log in, navigate, and view your resources.
+content:
+ h1: How to access Grafana and your managed dashboards
+ paragraph: Learn to access your Grafana managed dashboards, including steps to log in, navigate, and view your resources.
+tags: observability cockpit grafana managed-dashboard
+categories:
+ - observability
+dates:
+ validation: 2024-12-26
+ posted: 2022-10-31
+---
+
+Scaleway provides you with managed dashboards you can access in Grafana, for [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit).
+
+This page shows you how to access [managed dashboards](/cockpit/concepts/#managed-dashboards).
+
+
+
+ - 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
+ - [Retrieved your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/)
+
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website.
+3. Enter your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+4. Click **Log in**. The Grafana overview page displays.
+5. Click the **Home** icon at the top left of your screen.
+6. Click **Dashboard**. The Scaleway folder appears, with a list of all available managed dashboards for Scaleway resources.
+7. Click the dashboard you want to view.
+
+
+ Managed dashboards in the “Scaleway” folder are always read-only.
+
diff --git a/pages/cockpit/how-to/activate-managed-alerts.mdx b/pages/cockpit/how-to/activate-managed-alerts.mdx
new file mode 100644
index 0000000000..9ba7a2e388
--- /dev/null
+++ b/pages/cockpit/how-to/activate-managed-alerts.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to activate Scaleway preconfigured alerts
+ description: Learn how to activate preconfigured alerts for your Cockpit resources using the Scaleway console.
+content:
+ h1: How to activate Scaleway preconfigured alerts
+ paragraph: Learn how to activate preconfigured alerts for your Cockpit resources using the Scaleway console.
+categories:
+ - observability
+dates:
+ validation: 2024-10-03
+ posted: 2024-04-05
+---
+
+This page shows you how to activate [preconfigured alerts](/cockpit/concepts/#preconfigured-alerts) for your Cockpit resources using the [Scaleway console](https://console.scaleway.com/).
+
+
+
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+
+2. Click the **Alerts** tab.
+
+3. Click **Enable** under the **Scaleway preconfigured alerts** section. Select the regions you want to enable the alerts in.
+
+
+ You can only enable preconfigured alerts in the regions you have enabled the alert manager.
+
diff --git a/pages/cockpit/how-to/activate-push-traces.mdx b/pages/cockpit/how-to/activate-push-traces.mdx
new file mode 100644
index 0000000000..8f2a5f9bb2
--- /dev/null
+++ b/pages/cockpit/how-to/activate-push-traces.mdx
@@ -0,0 +1,65 @@
+---
+meta:
+ title: How to create and push traces
+ description: Learn how to create traces, retrieve trace push paths, and push traces.
+content:
+ h1: How to create and push traces
+ paragraph: Learn how to create traces, retrieve trace push paths, and push traces.
+categories:
+ - observability cockpit traces push
+dates:
+ validation: 2024-12-26
+ posted: 2023-10-31
+---
+
+This page shows you how to create [traces](/cockpit/concepts/#traces) from the Scaleway console, retrieve traces push paths, configure the OpenTelemetry HTTP agent, and push traces.
+
+
+
+ - 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
+
+## Create a trace
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Data sources** tab.
+3. Click **+ Create custom data source**. A pop-up displays.
+4. Complete the required steps to create your trace:
+ - Enter a name
+ - Choose the **Traces** data type
+ - Select a region to create your trace in
+5. Check the estimated cost, then click **Create custom data source**.
+
+### Retrieve traces push paths
+
+
+ Only the [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) HTTP push path is supported. Scaleway is working on implementing the [Open Telemetry gRPC](https://opentelemetry.io/docs/specs/semconv/rpc/grpc/), [Zipkin](https://zipkin.io/) and [Jaeger](https://www.jaegertracing.io/docs/1.50/) protocols.
+
+
+Scaleway provides the following push path for the OpenTelemetry agent: `/otlp/v1/traces`.
+The complete endpoint is `https://traces.cockpit.fr-par.scw.cloud/otlp/v1/traces`.
+
+Alternatively, you can retrieve your trace's push path from the Scaleway console:
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Data sources** tab.
+3. Click the trace of which you want to retrieve the path. The trace's information displays.
+4. Retrieve the push path under the **URL** section.
+
+## Push traces
+
+1. [Create a token](/cockpit/how-to/create-token/) with **Push** permissions for traces.
+
+ Your token's secret key displays only once. Make sure that you copy and save it before you exit the page.
+
+2. Configure your applications to send traces to your [preferred endpoint](/cockpit/concepts/#endpoints) using your newly-created token to authenticate.
+
+ You can also configure an agent to push your trace(s). Find out [how to configure the Grafana Alloy agent and push your data](/cockpit/how-to/send-metrics-with-grafana-alloy/)
+
+3. [Create your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+4. [Log in to your Grafana account](/cockpit/how-to/access-grafana-and-managed-dashboards/).
+5. Create your [Grafana dashboard](/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data.
+
+
+ Find out more information about pushing traces and visualizing them in Grafana, in the [official documentation](https://grafana.com/docs/grafana/latest/panels-visualizations/visualizations/traces/#add-a-panel-with-tracing-visualizations)
+
diff --git a/pages/cockpit/how-to/add-contact-points.mdx b/pages/cockpit/how-to/add-contact-points.mdx
new file mode 100644
index 0000000000..f1e57aadaa
--- /dev/null
+++ b/pages/cockpit/how-to/add-contact-points.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to add contact points
+ description: Learn how to add contact points to the default receiver using the Scaleway console. Follow the steps to enter email addresses, select regions, and optionally send test alerts.
+content:
+ h1: How to add contact points
+ paragraph: Learn how to add contact points to the default receiver using the Scaleway console. Follow the steps to enter email addresses, select regions, and optionally send test alerts.
+categories:
+ - observability
+dates:
+ validation: 2024-12-26
+ posted: 2024-04-05
+---
+
+This page shows you how to associate [contact points](/cockpit/concepts/#contact-points) with the default [receiver](/cockpit/concepts/#receivers) using the [Scaleway console](https://console.scaleway.com/).
+
+
+
+ - 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
+ - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager
+
+## Add contact points
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Alerts** tab.
+3. Click **+ Add email** in the **Default receiver’s contact points** section. A pop-up displays.
+4. Enter the email address you wish to add as a contact point.
+5. Choose the regions in which you want to add the contact point.
+
+ Make sure that you choose the same regions as the data sources for which you want to receive alerts.
+
+6. Click **Add email address**. The email address appears in the list of your contact points.
+7. Optionally, if you have [activated preconfigured alerts](/cockpit/how-to/activate-managed-alerts/), click **Send test alert** to ensure that your alerts are sent to your contact points.
diff --git a/pages/cockpit/how-to/assets/scaleway-alloy-dashboard.webp b/pages/cockpit/how-to/assets/scaleway-alloy-dashboard.webp
new file mode 100644
index 0000000000..41f41f66e8
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-alloy-dashboard.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway-alloy-datasource.webp b/pages/cockpit/how-to/assets/scaleway-alloy-datasource.webp
new file mode 100644
index 0000000000..a48253048a
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-alloy-datasource.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway-explore-python-logs.webp b/pages/cockpit/how-to/assets/scaleway-explore-python-logs.webp
new file mode 100644
index 0000000000..7f97b2b609
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-explore-python-logs.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway-logs-python.webp b/pages/cockpit/how-to/assets/scaleway-logs-python.webp
new file mode 100644
index 0000000000..72b54bb46d
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-logs-python.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway-traces-concept.webp b/pages/cockpit/how-to/assets/scaleway-traces-concept.webp
new file mode 100644
index 0000000000..374167036b
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway-traces-concept.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway_endpoints.webp b/pages/cockpit/how-to/assets/scaleway_endpoints.webp
new file mode 100644
index 0000000000..495097cfb7
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway_endpoints.webp differ
diff --git a/pages/cockpit/how-to/assets/scaleway_grafana_browse.webp b/pages/cockpit/how-to/assets/scaleway_grafana_browse.webp
new file mode 100644
index 0000000000..18851948f8
Binary files /dev/null and b/pages/cockpit/how-to/assets/scaleway_grafana_browse.webp differ
diff --git a/pages/cockpit/how-to/change-data-retention.mdx b/pages/cockpit/how-to/change-data-retention.mdx
new file mode 100644
index 0000000000..f610f02c7f
--- /dev/null
+++ b/pages/cockpit/how-to/change-data-retention.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: How to change your data retention period
+ description: Discover how to adjust data retention settings for metrics, logs, and traces in Cockpit.
+content:
+ h1: How to change your data retention period
+ paragraph: Discover how to adjust data retention settings for metrics, logs, and traces in Cockpit.
+tags: cockpit data-retention retention-period edit-retention
+categories:
+ - observability
+dates:
+ validation: 2024-11-25
+ posted: 2024-11-25
+---
+
+This page shows you how to change the [retention](/cockpit/concepts/#retention) period for your data sources.
+
+
+
+ **Cockpit pricing plans were deprecated on January 1st 2025**
+
+ The [retention](/cockpit/concepts/#retention) period previously set for your Scaleway and custom logs, metrics and traces remains the same.
+ You can change the retention period for your metrics, logs, and traces for free during the retention period edition beta (starting January 1st 2025).
+
+
+
+
+ - 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
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Data sources** tab.
+3. Click the icon next to the data source you want to change the retention period for.
+
+ You can change the retention period for both Scaleway and custom data sources. Each data source can have a different retention period.
+
+4. Click **More info**. The **Data source information** page displays.
+5. Click the **Edit retention** button and drag the slider to adjust the retention period:
+ - Drag the slider to the **right to increase** your retention period, or
+ - Drag the slider to the **left to decrease** the retention period.
+
+
+ - Reducing the retention period of a data source will permanently delete all observability data in that data source beyond the selected timeframe. This deletion is irreversible and takes effect a few minutes after the retention period is reduced, even if the retention period is later increased.
+ - Find out about the [retention periods available for each data source type](/cockpit/concepts/#retention).
+
+6. Click **Edit retention period** to confirm.
+
+
+ Adjusting data retention is free of charge during Beta.
+
\ No newline at end of file
diff --git a/pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx b/pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx
new file mode 100644
index 0000000000..db79d0a1f2
--- /dev/null
+++ b/pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: How to configure alerts for Scaleway resources in Grafana
+ description: Learn how to configure alerts for Scaleway resources in Grafana. Follow the steps to create alert rules, define conditions, and set up notifications for your monitored resources.
+content:
+ h1: How to configure alerts for Scaleway resources in Grafana
+ paragraph: Learn how to configure alerts for Scaleway resources in Grafana. Follow the steps to create alert rules, define conditions, and set up notifications for your monitored resources.
+categories:
+ - observability cockpit
+dates:
+ validation: 2024-10-03
+ posted: 2023-11-06
+---
+
+This page shows you how to configure alerts for Scaleway resources in Grafana using the `Scaleway Metrics` data source.
+
+
+
+ - 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
+ - Scaleway resources you can monitor
+ - [Created Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) with the **Editor** role
+ - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager, and [activated preconfigured alerts](/cockpit/how-to/activate-managed-alerts/)
+ - [Created](/cockpit/how-to/add-contact-points/) at least one contact point
+ - Selected the **Scaleway Alerting** alert manager in Grafana
+
+1. [Log in to Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your credentials.
+2. Click the **Toggle menu** then click **Alerting**.
+3. Click **Alert rules** and **+ New alert rule**.
+4. Scroll down to the **Define query and alert condition** section and click **Switch to data source-managed alert rule**.
+
+ This allows you to configure alert rules managed by the data source of your choice, instead of using Grafana's managed alert rules.
+
+5. Type in a name for your alert.
+6. Select the data source you want to configure alerts for. For the sake of this documentation, we are choosing the **Scaleway Metrics** data source.
+7. In the **Metrics browser** drop-down, select the metric you want to configure an alert for. For the sake of this documentation, we are choosing the `instance_server_cpu_seconds_total` metric.
+8. Select labels that apply to the metric you have selected in the previous step, to target your desired resources and fine-tune your alert.
+9. Select one or more values for your labels.
+10. Click **Use query** to generate your alert based on the conditions you have defined. For example, the alert below will be triggered whenever **the rate of our Instance's total CPU usage per second exceeds 10%**.
+
+11. In the **Set alert evaluation behavior** field, configure the amount of time during which the alert can be in breach of the condition(s) you have defined until it fires.
+
+ For example, if you wish to be alerted after your alert has been in breach of the condition for 2 minutes without interruption, type `2` and select `minutes` in the drop-down.
+
+12. Enter a namespace for your alert in the **Namespace** field and click **Enter**.
+13. Enter a name for your alert's group in the **Group** field and click **Enter**.
+14. Optionally, add a summary and a description.
+15. Click **Save rule** at the top right corner of your screen to save your alert. Once your alert meets the requirements you have configured, you will receive an email to inform you that your alert is firing.
+
+
+ You can configure up to a maximum of 10 alerts for the `Scaleway Metrics` data source.
+
diff --git a/pages/cockpit/how-to/create-external-data-sources.mdx b/pages/cockpit/how-to/create-external-data-sources.mdx
new file mode 100644
index 0000000000..10c119d1f6
--- /dev/null
+++ b/pages/cockpit/how-to/create-external-data-sources.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to create a custom data source
+ description: Learn how to create a custom data source and its data type using the Scaleway console. Follow the steps to choose a data type, select a region, and finalize the creation process.
+content:
+ h1: How to create a custom data source
+ paragraph: Learn how to create a custom data source and its data type using the Scaleway console. Follow the steps to choose a data type, select a region, and finalize the creation process.
+categories:
+ - observability
+dates:
+ validation: 2024-09-19
+ posted: 2024-04-05
+---
+
+This page shows you how to create a **custom** [data source](/cockpit/concepts/#data-sources) and its [data type](/cockpit/concepts/#data-types), from the Scaleway console.
+
+
+
+ - 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
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Data sources** tab.
+3. Click **+ Create custom data source**.
+4. Enter a name for the data source.
+5. Choose the [data type](/cockpit/concepts/#data-types) you want to create in the data source.
+6. Select the region for your data source.
+
+ We recommend that you create your data sources in the same regions as the alert manager if you want to receive alerts for them.
+
+7. Click **Create custom data source**.
+
+
+ If you are using Scaleway resources integrated with Cockpit, you can also view your Scaleway data sources in the **Data sources** tab. Scaleway data sources are **read-only**.
+
diff --git a/pages/cockpit/how-to/create-token.mdx b/pages/cockpit/how-to/create-token.mdx
new file mode 100644
index 0000000000..af7ef0bae7
--- /dev/null
+++ b/pages/cockpit/how-to/create-token.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: How to create a token
+ description: Learn how to create tokens to grant services and platforms access to your Scaleway Cockpit. Follow the steps to choose a region, select token permissions, and save the token's secret key.
+content:
+ h1: How to create a token
+ paragraph: Learn how to create tokens to grant services and platforms access to your Scaleway Cockpit. Follow the steps to choose a region, select token permissions, and save the token's secret key.
+tags: cockpit observability token
+categories:
+ - observability
+dates:
+ validation: 2024-12-26
+ posted: 2022-10-31
+---
+
+This page shows you how to create [tokens](/cockpit/concepts/#tokens), to grant other cloud providers’ services and platforms access to your [Cockpit](/cockpit/concepts/#cockpit).
+
+
+
+- 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
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Tokens** tab.
+3. Click **+ Create token**. A pop-up displays.
+4. Choose a region to create the token in.
+
+ Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for.
+
+5. Choose a name for your token or use the already-generated name.
+6. Select the permissions you wish to apply to your token.
+
+ You must select at least one permission.
+ Permissions include:
+ - **Push**: allows you to send your metrics, logs, and traces to your Cockpit.
+ - **Query**: allows you to fetch your metrics, logs, and traces from your Cockpit.
+ - **Rules**: allow you to configure alerting and recording rules.
+ - **Alerts**: allow you to set up the alert manager.
+
+7. Click **Create token** to confirm. A pop-up displays with your token's secret key. Make sure that you save the secret key before closing the pop-up.
+
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing page](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
diff --git a/pages/cockpit/how-to/delete-external-data-sources.mdx b/pages/cockpit/how-to/delete-external-data-sources.mdx
new file mode 100644
index 0000000000..29351c0469
--- /dev/null
+++ b/pages/cockpit/how-to/delete-external-data-sources.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to delete a custom data source
+ description: Learn how to delete a custom data source from the Scaleway console. Follow the steps to navigate to the data sources tab, select the data source, and confirm its deletion.
+content:
+ h1: How to delete a custom data source
+ paragraph: Learn how to delete a custom data source from the Scaleway console. Follow the steps to navigate to the data sources tab, select the data source, and confirm its deletion.
+categories:
+ - observability
+dates:
+ validation: 2024-09-19
+ posted: 2024-04-13
+---
+
+This page shows you how to delete a custom [data source](/cockpit/concepts/#data-sources) from the Scaleway console.
+
+
+
+ - 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](/cockpit/how-to/create-external-data-sources/) custom data sources
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Data sources** tab.
+3. Click the icon next to the data source you wish to delete.
+4. Click **Delete**. A deletion confirmation pop-up displays.
+5. Click **Delete data source** to confirm the data source deletion.
+
+
+ Deleting a data source is permanent. Any data associated with it will be lost.
+
+
diff --git a/pages/cockpit/how-to/enable-alert-manager.mdx b/pages/cockpit/how-to/enable-alert-manager.mdx
new file mode 100644
index 0000000000..382ff0c679
--- /dev/null
+++ b/pages/cockpit/how-to/enable-alert-manager.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to enable the alert manager
+ description: Learn how to enable Scaleway's regionalized alert manager to configure preconfigured alerts for your resources. Follow the steps to navigate to the Alerts tab, select regions, and confirm the alert manager activation.
+content:
+ h1: How to enable the alert manager
+ paragraph: Learn how to enable Scaleway's regionalized alert manager to configure preconfigured alerts for your resources. Follow the steps to navigate to the Alerts tab, select regions, and confirm the alert manager activation.
+categories:
+ - observability
+dates:
+ validation: 2024-10-03
+ posted: 2024-04-05
+---
+
+This page shows you how to enable Scaleway's regionalized alert manager to configure preconfigured alerts for your Scaleway resources.
+
+
+
+ - A Scaleway account logged into the [Scaleway 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
+
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Alerts** tab.
+3. Click **Enable** under the **Alert manager** section.
+4. Choose the regions where you want to enable the alert manager.
+
+ Make sure that you enable the alert manager in the same regions as the [data sources](/cockpit/concepts/#data-sources) you want to be alerted for.
+
+5. Click **Enable alert manager** to confirm.
diff --git a/pages/cockpit/how-to/index.mdx b/pages/cockpit/how-to/index.mdx
new file mode 100644
index 0000000000..e367cafe14
--- /dev/null
+++ b/pages/cockpit/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Observability How Tos
+ description: Observability How Tos
+content:
+ h1: Observability How Tos
+ paragraph: Observability How Tos
+---
diff --git a/pages/cockpit/how-to/retrieve-grafana-credentials.mdx b/pages/cockpit/how-to/retrieve-grafana-credentials.mdx
new file mode 100644
index 0000000000..7be72086c1
--- /dev/null
+++ b/pages/cockpit/how-to/retrieve-grafana-credentials.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to retrieve your Grafana credentials
+ description: Learn how to retrieve your Grafana credentials to access your Grafana dashboards from the Scaleway console. Follow the steps to navigate to the Grafana users tab, add a user, and retrieve the automatically generated password for login.
+content:
+ h1: How to retrieve your Grafana credentials
+ paragraph: Learn how to retrieve your Grafana credentials to access your Grafana dashboards from the Scaleway console. Follow the steps to navigate to the Grafana users tab, add a user, and retrieve the automatically generated password for login.
+tags: cockpit observability grafana credentials
+categories:
+ - observability
+dates:
+ validation: 2024-12-26
+ posted: 2022-10-31
+---
+
+This page shows you how to retrieve your Grafana credentials to access your Grafana [dashboards](/cockpit/concepts/#managed-dashboards) using the [Scaleway console](https://console.scaleway.com/).
+
+
+
+ - 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
+
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Grafana users** tab.
+3. Click **+ Add user**.
+4. Enter a username.
+5. Select a [role](/cockpit/concepts/#grafana-users) for the user.
+6. Click **Add user**. Your automatically generated password to log in to Grafana displays. Make sure to copy and save it before closing the pop-up.
+
+
+ The `admin` user is not yet available for creation.
+
+
+
diff --git a/pages/cockpit/how-to/send-metrics-logs-to-cockpit.mdx b/pages/cockpit/how-to/send-metrics-logs-to-cockpit.mdx
new file mode 100644
index 0000000000..bdf6f82f5b
--- /dev/null
+++ b/pages/cockpit/how-to/send-metrics-logs-to-cockpit.mdx
@@ -0,0 +1,123 @@
+---
+meta:
+ title: How to send metrics and logs to your Cockpit
+ description: Learn how to send metrics and logs to your Cockpit using Scaleway's comprehensive guide. This tutorial covers sending Python logs to Scaleway's Cockpit for centralized monitoring and analysis using Grafana, ensuring efficient data management and analysis in your infrastructure.
+content:
+ h1: How to send metrics and logs to your Cockpit
+ paragraph: Learn how to send metrics and logs to your Cockpit using Scaleway's comprehensive guide. This tutorial covers sending Python logs to Scaleway's Cockpit for centralized monitoring and analysis using Grafana, ensuring efficient data management and analysis in your infrastructure.
+tags: metrics cockpit logs observability
+categories:
+ - observability
+dates:
+ validation: 2024-12-26
+ posted: 2022-10-31
+---
+
+This page shows you how to send data such as [metrics](/cockpit/concepts/#metric) and [logs](/cockpit/concepts/#logs) to your [Cockpit](/cockpit/concepts/#cockpit). You can push metrics with any `Prometheus Remote Write` compatible agent such as the [Prometheus](https://prometheus.io/docs/introduction/overview/), [Grafana](https://grafana.com/docs/agent/latest/) or [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) agents.
+You can push logs with any Loki compatible agent such as the [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/), [Fluentd](https://docs.fluentd.org/), [Fluent Bit](https://docs.fluentbit.io/manual/) or [Logstash](https://www.elastic.co/guide/en/logstash/current/introduction.html) agents.
+
+
+
+ - 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
+ - Configured an agent. Read our dedicated [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure the Grafana Alloy agent
+ - [Created](/iam/how-to/create-api-keys/) an API key and retrieved your API secret key
+
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## Send metrics and logs to your Cockpit
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. [Create a token](/cockpit/how-to/create-token/) with the **Push** permission for metrics and logs.
+
+ - Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for.
+ - Make sure that you copy your token's secret key and save it before you exit the page.
+
+3. Configure your applications to send metrics and logs to your Cockpit [endpoints](/cockpit/concepts/#endpoints), using your token's secret key for authentication.
+
+
+ Retrieve your metrics' and logs' push endpoints in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console.
+
+4. [Log in to your Grafana account](/cockpit/how-to/access-grafana-and-managed-dashboards/).
+5. Create your [Grafana dashboard](/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data.
+
+---
+
+
+ ## Sending Python logs to Cockpit
+
+
+ You need custom logs in the `fr-par` region to follow the procedure below. Find out [how to create custom logs](/cockpit/how-to/create-external-data-sources/).
+
+
+ 1. Open a terminal and run `pip install python-logging-loki` or `pip3 install python-logging-loki` if you are using Python 3, to install the [logging_loki](https://pypi.org/project/python-logging-loki/) package to send your Python logs.
+ 2. [Create a token](/cockpit/how-to/create-token/) with the **Push** permission for logs.
+ 3. Create a `python_logs.py` Python file and paste the following code snippet into it. Make sure that you replace `$SCW_SECRET_KEY` with your API secret key and `$COCKPIT_TOKEN_SECRET_KEY` with your Cockpit token's secret key.
+
+ ```
+ import logging
+ import logging_loki
+ import time
+
+ handler = logging_loki.LokiHandler(
+ url="https://logs.cockpit.fr-par.scw.cloud/loki/api/v1/push",
+ tags={"job": "logs_from_python"},
+ auth=("$SCW_SECRET_KEY", "$COCKPIT_TOKEN_SECRET_KEY"),
+ version="1",
+
+ )
+
+ logger = logging.getLogger("my-first-python-logger")
+ logger.addHandler(handler)
+
+ def main():
+ # Start generating log messages
+ for i in range(10):
+ logger.error(f"Error message {i}")
+ time.sleep(1)
+
+ if __name__ == "__main__":
+ main()
+
+
+ ```
+
+ This script sets up a logger that sends error log messages to the Loki endpoint in Cockpit. It then generates 10 error log messages with a one-second delay between each message. These log messages are sent to Cockpit and can be viewed and analyzed via the Grafana dashboard we will create in the next part.
+
+
+ If you are using the Scaleway Loki API, you can `POST` through the `Authorization: Bearer ` header, or `POST` using the following endpoint: `https://api_key:YOUR_COCKPIT_TOKEN@logs.cockpit.fr-par.scw.cloud/loki/api/v1/push`.
+
+
+ ### Creating a Grafana dashboard and visualizing your Python logs
+
+ 1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+ 2. Click **Toggle menu**, then click **Dashboards**.
+ 3. Click **New** in the top right corner of your screen, then **Import**.
+ 4. Upload the JSON file of the [Grafana Log Viewer dashboard for Loki](https://grafana.com/grafana/dashboards/13639-logs-app/) or enter `13639` in the **Import via grafana.com** field.
+ 5. Click **Load**.
+ 6. Enter a name for the dashboard or leave the default name.
+ 7. Select a folder in which to store the dashboard.
+ 8. Select your custom logs data source in the **Loki** drop-down. Make sure that the data source you select is in the `fr-par` region.
+ 9. Click **Import**.
+ 10. Open a terminal and enter the following command.
+ ```
+ python3 python_logs.py
+ ```
+ 11. Click the **Home** icon > **Dashboards**. Your **Logs / App** dashboard should display.
+ 12. Click the **Logs / App** dashboard. Your log lines from the Python snippet should appear.
+
+ If your logs do not display, try changing the time range to match the time at which you ran your Python file.
+
+
+ 13. Click the **View in Explore** button for more configuration options.
+
+
+
+ Read our more in depth-documentation on [how to configure the Grafana alloy agent](/cockpit/how-to/send-metrics-with-grafana-alloy/) to push your Scaleway metrics, and visualize them in a Grafana dashboard.
+
+
+
diff --git a/pages/cockpit/how-to/send-metrics-with-grafana-alloy.mdx b/pages/cockpit/how-to/send-metrics-with-grafana-alloy.mdx
new file mode 100644
index 0000000000..054db0fbb3
--- /dev/null
+++ b/pages/cockpit/how-to/send-metrics-with-grafana-alloy.mdx
@@ -0,0 +1,117 @@
+---
+meta:
+ title: Send metrics to Cockpit using Grafana Alloy
+ description: Learn to configure Grafana Alloy to push metrics and visualize them in your Grafana dashboard with this step-by-step tutorial.
+content:
+ h1: Send metrics to Cockpit using Grafana Alloy
+ paragraph: Learn to configure Grafana Alloy to push metrics and visualize them in your Grafana dashboard with this step-by-step tutorial.
+tags: cockpit observability grafana-alloy agent push-metrics
+dates:
+ validation: 2025-01-07
+ posted: 2024-06-28
+categories:
+ - observability
+---
+
+
+The Grafana Alloy agent is a component used in observability and monitoring setups, to collect and send metrics, logs, and traces from your applications, services, and infrastructure to observability platforms, such as Cockpit.
+
+This page explains how to configure the Grafana Alloy agent to push your metrics and visualize them in Grafana. You can use it to **push your data from Scaleway resources or external/custom resources**.
+
+For the sake of this documentation, we are using Grafana Alloy on macOS. Refer to the [official Grafana documentation](https://grafana.com/docs/alloy/latest/get-started/) to find the commands to use depending on your operating system of choice.
+
+
+
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - [Retrieved your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/)
+ - [Installed Grafana Alloy](https://grafana.com/docs/alloy/latest/get-started/install/)
+ - [Created a custom data source of the metrics type](/cockpit/how-to/create-external-data-sources/)
+ - A [token](/cockpit/how-to/create-token/) with push permissions for metrics in the **same region as your metrics**
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month.
+
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## Configuring Grafana Alloy
+
+1. Create a folder named `config` on your local machine.
+2. Create a file named `cockpit.alloy` inside the `config` folder.
+3. Paste the following template inside `cockpit.alloy`:
+ ```
+ prometheus.exporter.unix "node" {
+ set_collectors = [
+ "uname",
+ "cpu",
+ "cpufreq",
+ "loadavg",
+ "meminfo",
+ "filesystem",
+ "netdev",
+ ]
+ }
+
+ prometheus.scrape "node" {
+ scrape_interval = "60s"
+ scrape_timeout = "4s"
+
+ targets = prometheus.exporter.unix.node.targets
+ forward_to = [prometheus.remote_write.cockpit.receiver]
+ }
+
+ prometheus.remote_write "cockpit" {
+ endpoint {
+ url = "https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.metrics.cockpit.fr-par.scw.cloud/api/v1/push"
+ headers = {
+ "X-TOKEN" = "COCKPIT_TOKEN_SECRET_KEY",
+ }
+ }
+ }
+ ```
+3. Replace `https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.metrics.cockpit.fr-par.scw.cloud/api/v1/push` with your metrics' URL. You can retrieve it in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console.
+4. Replace `COCKPIT_TOKEN_SECRET_KEY` with your Cockpit token's secret key, then save your changes.
+
+ Make sure that your token and your metrics data source were both created in the same region.
+
+5. Open a terminal and [start Alloy](https://grafana.com/docs/alloy/latest/get-started/run/):
+ ```
+ brew services start alloy
+ ```
+6. In the same terminal, run the following command.
+ ```
+ alloy run config/cockpit.alloy
+ ```
+ The two last lines of your output should look similar to the following.
+ ```
+ ts=2024-06-27T14:23:05.542081Z level=info msg="now listening for http traffic" service=http addr=127.0.0.1:12345
+ ts=2024-06-27T14:23:13.432896Z level=info msg="Done replaying WAL" component_path=/ component_id=prometheus.remote_write.cockpit subcomponent=rw remote_name=aa0551 url=https://xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.metrics.cockpit.fr-par.scw.cloud/api/v1/push duration=12.900498616s
+ ```
+
+## Visualizing your metrics
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website.
+3. Enter your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+4. Click **Log in**. The Grafana overview page displays.
+5. Click the **Toggle menu** icon in the top left corner of your screen.
+6. Click **Dashboards**, then click **New** in the top right corner of your screen. A drop-down displays.
+7. Click **Import** to import a dashboard.
+8. In the **Import via grafana.com** field, enter `1860`, then click **Load**
+
+
+ `1860` is the ID of the [Node Exporter Full dashboard](https://grafana.com/grafana/dashboards/1860-node-exporter-full/) provided by Grafana.
+
+
+9. Enter a name for your dashboard or leave the default one.
+10. In the **Folder** field select a folder in which to store your dashboard.
+11. In the **Prometheus** field, select your metrics data source in the drop-down.
+12. Click **Import**. Your dashboard should load and display.
+13. In the drop-down next to **Datasource**, select your metrics data source. By default, your dashboard retrieves your data source's data from the last 24 hours.
+
+14. If your data source was created less than 24 hours ago, click the clock icon and adjust the time range to match its creation time.
+
+ Your dashboard should look similar to the one in the image below.
+
+
diff --git a/pages/cockpit/index.mdx b/pages/cockpit/index.mdx
new file mode 100644
index 0000000000..47f7b6f743
--- /dev/null
+++ b/pages/cockpit/index.mdx
@@ -0,0 +1,85 @@
+---
+meta:
+ title: Cockpit Documentation
+ description: Explore Scaleway Cockpit with our quickstart guides, how-tos, tutorials, and more for efficient monitoring.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/cockpit/quickstart.mdx b/pages/cockpit/quickstart.mdx
new file mode 100644
index 0000000000..7e7fbeba2e
--- /dev/null
+++ b/pages/cockpit/quickstart.mdx
@@ -0,0 +1,71 @@
+---
+meta:
+ title: Cockpit - Quickstart
+ description: Discover how to begin with the Scaleway Observability Cockpit. Learn to set up Grafana credentials, create push tokens, and leverage Grafana agents for monitoring metrics, logs, and traces.
+content:
+ h1: Cockpit - Quickstart
+ paragraph: Discover how to begin with the Scaleway Observability Cockpit. Learn to set up Grafana credentials, create push tokens, and leverage Grafana agents for monitoring metrics, logs, and traces.
+tags: observability cockpit
+dates:
+ validation: 2024-12-26
+ posted: 2022-10-31
+categories:
+ - observability
+---
+
+Scaleway's Observability Cockpit allows you to monitor your applications and their infrastructure by giving you insights and context into their behavior. With Cockpit, you can visualize your resources' and applications' metrics, logs, and traces in Grafana dashboards. Cockpit is automatically activated when you are using [Scaleway resources that are integrated into it](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit).
+
+The Observability Cockpit provides you with [endpoints](/cockpit/concepts/#endpoints) to push [metrics](/cockpit/concepts/#metric), [logs](/cockpit/concepts/#logs), and [traces](/cockpit/concepts/#traces).
+
+Learn [how to reduce extra costs and understand Cockpit pricing](/cockpit/reference-content/understanding-cockpit-usage/).
+
+In this documentation, we show you how to retrieve your Grafana credentials to access your Grafana, and how to create a push token to send metrics and logs to your Cockpit. We include tips to go further at the end of this Quickstart, to show you how you can configure the Grafana Alloy agent to push your metrics, logs, and traces to Cockpit and visualize your data in Grafana.
+
+
+
+ - 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
+
+
+ - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month.
+ - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## How to retrieve your Grafana credentials
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Grafana users** tab.
+3. Click **Add user**.
+4. Enter a username.
+5. Select a [role](/cockpit/concepts/#grafana-users) for the user.
+6. Click **Add a user**. Your automatically generated password to log in to Grafana displays. Make sure to copy and save it before closing the pop-up.
+
+## How to create a token to push your metrics and logs
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Tokens** tab.
+3. Click **Create token**. A pop-up displays prompting you to create a token.
+4. Choose the region to create the token in.
+
+ Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for.
+
+5. Choose a name for your token or use the already-generated name.
+6. Select the permissions you wish to apply to your token.
+
+ You must select at least one permission.
+ Permissions include:
+ - **Push**: allows you to send your metrics, logs and traces to your Cockpit.
+ - **Query**: allows you to fetch your metrics, logs and traces from your Cockpit.
+ - **Rules**: allow you to configure alerting and recording rules.
+ - **Alerts**: allow you to set up the alert manager.
+
+7. Click **Create token** to confirm. A pop-up displays with your secret key. Make sure that you save the secret key before closing the pop-up.
+
+
+**Going further**
+
+ If you have not set up an agent yet, check out our [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure Grafana Alloy, push your metrics, and visualize them in Grafana.
+ You must have created resources to monitor to push your data to Cockpit.
+
+
+
diff --git a/pages/cockpit/reference-content/cockpit-limitations.mdx b/pages/cockpit/reference-content/cockpit-limitations.mdx
new file mode 100644
index 0000000000..758f14752b
--- /dev/null
+++ b/pages/cockpit/reference-content/cockpit-limitations.mdx
@@ -0,0 +1,106 @@
+---
+meta:
+ title: Cockpit capabilities and limits
+ description: Discover the capabilities and limits of Cockpit, including retention periods, Loki and Mimir limits, and product integrations for comprehensive infrastructure monitoring and management efficiency.
+content:
+ h1: Cockpit capabilities and limits
+ paragraph: Discover the capabilities and limits of Cockpit, including retention periods, Loki and Mimir limits, and product integrations for comprehensive infrastructure monitoring and management efficiency.
+tags: observability cockpit retention metrics logs
+dates:
+ validation: 2024-11-25
+ posted: 2023-09-05
+categories:
+ - observability
+---
+
+
+
+This page provides information about the capabilities and limits of Scaleway's Observability Cockpit.
+
+## Retention period of your data
+
+Scaleway offers several retention periods, depending on your [data types](/cockpit/concepts/#data-types).
+
+Find out more information about how Cockpit is billed depending on your data types in the [FAQ](/faq/cockpit/#how-am-i-billed-for-using-cockpit-with-my-scaleway-data).
+
+## Limits for Loki
+
+The following table provides information about [Loki](/cockpit/concepts/#loki)'s limits.
+
+| Parameter | Default value | Value for the user | Description |
+|------------------------------------|---------------|--------------------|--------------------------------------------------------------------------------------|
+| `ingestion_rate_mb` | 4 | 4 | Maximum number of samples accepted in megabytes. Any further samples are rejected |
+| `max_label_name_length` | 1024 | 1024 | Maximum character size for a label name |
+| `max_label_value_length` | 2048 | 2048 | Maximum character size for a label value |
+| `max_label_names_per_series` | 30 | 30 | Maximum number of label names per series |
+| `max_line_size` | 0B | 0B | Maximum size in bytes for a log row |
+| `max_line_size_truncate` | false | false | No line truncation |
+| `unordered_writes` | true | true | Accept out-of-order samples |
+| `max_chunks_per_query` | 2000000 | 2000000 | Number of chunks that can be queried in a single request |
+| `max_query_length` | **30d1h** | **30d1h** | Maximum period over which a request can be made |
+| `cardinality_limit` | 100000 | 100000 | Cardinality limit |
+| `max_entries_limit_per_query` | 5000 | 5000 | Maximum number of rows that can be returned per query |
+| `query_timeout` | 1 minute | 1 minute | Query timeout |
+
+**30d1h**: 30 days + 1 hour.
+
+## Limits for Mimir
+
+The following table provides information about [Mimir](/cockpit/concepts/#mimir)'s limits.
+
+| Parameter | Default value | Value for the user | Description |
+|------------------------------------|---------------|--------------------|-----------------------------------------------------------------------------------|
+| `ingestion_rate` | 10000 | 10000 | Maximum number of samples accepted per second. Any further samples are rejected |
+| `ingestion_burst_size` | 200000 | 200000 | Ability to exceed `ingestion_rate` for a short period of time (still undefined) |
+| `accept_ha_samples` | false | false | High availability function (not supported at this time) |
+| `max_label_name_length` | 1024 | 1024 | Maximum character size for a label name |
+| `max_label_value_length` | 2048 | 2048 | Maximum character size for a label value |
+| `max_label_names_per_series` | 30 | 30 | Maximum number of label names per series |
+| `max_metadata_length` | 1024 | 1024 | Maximum size of the metadata, in characters |
+| `max_global_series_per_user` | 150000 | 250000 | Maximum number of series in memory on the Project ID, in the last 10 minutes |
+| `max_global_series_per_metric` | 0 | 25000 | Maximum number of series in memory for a metric, in the last 10 minutes |
+| `ruler_max_rules_per_rule_group` | 20 | 20 | Number of rules per rule group |
+| `ruler_max_rule_groups_per_tenant` | 70 | 70 | Number of rule groups for a Project ID |
+
+## Product integration into Cockpit
+
+The following table provides details about the products that are integrated into Cockpit. This means that you can have metrics and/or logs and/or alerts in your Cockpit for the products mentioned below.
+
+**Sending metrics and logs using an external path is a billable feature**. As such, any additional data that you may push yourself will be billed, even if you send data from Scaleway products that are **not integrated into Cockpit**. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+| **Product Name** | **Metrics** | **Logs** | **Alerts** |
+|----------------------------|-----------------|-----------------|-----------------|
+| Instances | **Integrated*** | Not integrated | Not integrated |
+| Managed Inference | **Integrated*** | **Integrated*** | Not integrated |
+| Generative APIs | **Integrated*** | Not integrated | Not integrated |
+| Elastic Metal | Not integrated | Not integrated | Not integrated |
+| Apple silicon | Not integrated | Not integrated | Not integrated |
+| Kubernetes Kapsule | **Integrated*** | **Integrated*** | **Integrated** |
+| Kubernetes Kosmos | **Integrated*** | **Integrated*** | **Integrated** |
+| Container Registry | Not integrated | Not integrated | Not integrated |
+| Serverless Containers | **Integrated*** | **Integrated*** | Not integrated |
+| Serverless Functions | **Integrated*** | **Integrated*** | Not integrated |
+| Serverless Jobs | **Integrated*** | **Integrated*** | Not integrated |
+| NATS | **Integrated*** | Not integrated | Not integrated |
+| Queues | **Integrated*** | Not integrated | Not integrated |
+| Topics and Events | **Integrated*** | Not integrated | Not integrated |
+| Block Storage | **Integrated*** | Not integrated | Not integrated |
+| Object Storage | **Integrated*** | **Integrated*** | Not integrated |
+| Database RDB PostgreSQL | **Integrated*** | **Integrated*** | **Integrated** |
+| Database RDB MySQL | **Integrated*** | **Integrated*** | **Integrated** |
+| Serverless SQL Database | **Integrated*** | **Integrated*** | **Integrated** |
+| Redis | **Integrated*** | **Integrated*** | **Integrated** |
+| MongoDB | Planned | Not integrated | Not integrated |
+| Private Networks | **Integrated*** | Not integrated | Not integrated |
+| Public Gateways | **Integrated*** | **Integrated*** | Not integrated |
+| Load Balancers | **Integrated*** | **Integrated*** | Not integrated |
+| Domains and DNS | Not integrated | Not integrated | Not integrated |
+| Edge Services | **Integrated*** | Not integrated | Not integrated |
+| Transactional Email | **Integrated*** | Not integrated | **Integrated** |
+| IoT Hub | **Integrated*** | Not integrated | Not integrated |
+| Web Hosting | Not integrated | Not integrated | Not integrated |
+| Cockpit | **Integrated*** | Not integrated | Not integrated |
+| IAM | Not integrated | Not integrated | Not integrated |
+| Secret Manager | **Integrated*** | **Integrated** | Not integrated |
+
+*: Including data and dashboards
diff --git a/pages/cockpit/reference-content/index.mdx b/pages/cockpit/reference-content/index.mdx
new file mode 100644
index 0000000000..592bb49823
--- /dev/null
+++ b/pages/cockpit/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Cockpit - Additional content
+ description: Cockpit additional content
+content:
+ h1: Cockpit - Additional content
+ paragraph: Cockpit additional content
+---
diff --git a/pages/cockpit/reference-content/understanding-cockpit-usage.mdx b/pages/cockpit/reference-content/understanding-cockpit-usage.mdx
new file mode 100644
index 0000000000..cb42ed10c9
--- /dev/null
+++ b/pages/cockpit/reference-content/understanding-cockpit-usage.mdx
@@ -0,0 +1,124 @@
+---
+meta:
+ title: Understanding Cockpit usage and pricing
+ description: Explore Cockpit's usage and pricing details, including how to manage and optimize costs by controlling the amount of metrics ingested. Learn to adjust scrape intervals and filter metrics effectively, ensuring efficient resource monitoring without unnecessary expenses.
+content:
+ h1: Understanding Cockpit usage and pricing
+ paragraph: Explore Cockpit's usage and pricing details, including how to manage and optimize costs by controlling the amount of metrics ingested. Learn to adjust scrape intervals and filter metrics effectively, ensuring efficient resource monitoring without unnecessary expenses.
+tags: observability cockpit retention metrics logs
+dates:
+ validation: 2024-11-04
+ posted: 2023-06-07
+categories:
+ - observability
+---
+
+
+Cockpit allows you to [push custom metrics](/cockpit/how-to/send-metrics-logs-to-cockpit/) for various resources. The pricing of our service is based on the number of samples that are ingested per month.
+Using Cockpit costs €0.15 per million samples ingested per month.
+
+## Importance of controlling the rate
+
+If you wish to avoid extra costs, you can define a limit to the number of samples you send to Cockpit.
+The following table shows an estimate of the pricing (€0.00000015 per sample) based on the push rate of the sample:
+
+
+| Sample ingestion rate per seconds | Samples ingested per day | Price per day | Samples ingested per month | Price per month |
+|:---------------------------------:|:------------------------:|:-------------:|:--------------------------:|:---------------:|
+| 1 | 86 400 | €0.01296 | 2 678 400 | €0.4017 |
+| 10 | 864 000 | €0.1296 | 26 784 000 | €4.0176 |
+| 100 | 8 640 000 | €1.296 | 267 840 000 | €40.176 |
+| 1000 | 86 400 000 | €12.96 | 2 678 400 000 | €401.76 |
+
+## How to know my current ingestion rate?
+
+Within the Cockpit dashboard on Grafana, click **Cockpit Overview**. The panel named **Metrics ingestion rate** displays the ingestion rate for samples coming from Scaleway products, and the ingestion rate for your own samples if you look at "Other Metrics".
+
+If you are [using your own Grafana](/tutorials/using-own-grafana/) to visualize metrics, use the following query `sum(rate(observability_cockpit_ingestion_samples_total{is_from_scaleway="false"}[5m])) OR on() vector(0)` to know what your current ingestion rate is.
+
+## How to control the number of samples sent to Cockpit?
+
+### Control the interval between scrapes
+
+A common good practice to control the number of samples you send to Cockpit, is to have a `scrape_interval` of 1 minute.
+
+Let us say you have 1000 samples exposed and a `scrape_interval` of 10s. This means you will have a rate of 100 sample/s and pay around €40 per month.
+If you increase the `scrape_interval` to 60s, you will have a rate of 1,66 sample/s, which amounts to around €6.69 per month.
+
+#### Change the scrape interval using Prometheus
+
+If you are using Prometheus to remote write metrics to your Cockpit, you can tweak the `scrape_interval` using the following configuration:
+
+ ```yaml
+ global:
+ scrape_interval: 60s
+
+ scrape_configs:
+ ...
+
+ remote_write:
+ - url: https://metrics.cockpit.fr-par.scw.cloud/api/v1/push
+ headers:
+ "X-Token":
+ ```
+
+#### Change the scrape interval using the Grafana agent
+
+Here is an example of a Grafana agent configuration file with a scrape interval of 60 seconds:
+
+ ```yaml
+ metrics:
+ global:
+ scrape_interval: 60s
+ remote_write:
+ - url: https://metrics.cockpit.fr-par.scw.cloud/api/v1/push
+ headers:
+ "X-Token":
+ integrations:
+ ...
+ ```
+### Control the metrics you are sending
+
+Another good practice to control the number of samples you send to Cockpit, is to only send metrics that you want into your Cockpit, by filtering what you send.
+
+Here is a configuration example with Prometheus:
+
+ ```yaml
+ ...
+
+ remote_write:
+ - url: https://metrics.cockpit.fr-par.scw.cloud/api/v1/push
+ headers:
+ "X-Token":
+ write_relabel_configs:
+ - source_labels: [__name__]
+ regex: 'my_app_metrics(.*)'
+ action: keep
+ ```
+
+This configuration will only send metrics starting with `my_app_metrics` to your Cockpit.
+
+For more information, refer to the [Prometheus documentation](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config).
+
+### Learn about the agents you are using
+
+Many agents, such as `cadvisor` and `node_exporter` expose a lot of metrics by default.
+
+The [following metrics collectors](https://github.com/prometheus/node_exporter#enabled-by-default) are enabled by default on a node_exporter. You can configure them to filter what is sent to your Cockpit.
+
+Use the following configuration example for a Grafana agent with the `node_exporter` integration:
+
+ ```yaml
+ ...
+ integrations:
+ node_exporter:
+ enabled: true
+ # Anything not provided in the list below will be disabled by default
+ set_collectors:
+ - uname
+ - cpu
+ - loadavg
+ - meminfo
+ - filesystem
+ - netdev
+ ```
diff --git a/pages/cockpit/troubleshooting/index.mdx b/pages/cockpit/troubleshooting/index.mdx
new file mode 100644
index 0000000000..c9f612715a
--- /dev/null
+++ b/pages/cockpit/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Cockpit - Troubleshooting
+ description: Cockpit Troubleshooting
+content:
+ h1: Cockpit - Troubleshooting
+ paragraph: Cockpit Troubleshooting
+---
diff --git a/pages/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx b/pages/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx
new file mode 100644
index 0000000000..631cccca7f
--- /dev/null
+++ b/pages/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: My Pusher does not support custom HTTP headers
+ description: Discover solutions to handle pushers that do not support custom HTTP headers.
+content:
+ h1: My Pusher does not support custom HTTP headers
+ paragraph: Discover solutions to handle pushers that do not support custom HTTP headers.
+tags: pusher token header
+dates:
+ validation: 2024-12-26
+ posted: 2023-04-03
+categories:
+ - observability
+---
+
+
+
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+
+If your pusher does not support the `X-Token` header, there are other ways to pass it:
+
+- Through the `X-Scope-OrgID` header. This means that when using [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/), you can set the `tenant_id` field of the client's configuration to pass the token.
+- Through the `Authorization: Bearer ` header. This is for all clients who usually have support for these bearer tokens.
+- Through the `Authorization: Basic` header. With basic authentication, you will have to use the token as a password with any username.
+
+
+ If none of these methods were successful, reach out to us on the [#observability channel on Slack](https://slack.scaleway.com/).
+
\ No newline at end of file
diff --git a/pages/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx b/pages/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx
new file mode 100644
index 0000000000..2e61cd09cc
--- /dev/null
+++ b/pages/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx
@@ -0,0 +1,28 @@
+---
+meta:
+ title: Resetting a Grafana password
+ description: Reset your Grafana user password using the Scaleway API. Retrieve your Grafana user ID and reset the password with a simple curl command.
+ h1: Resetting a Grafana password
+ paragraph: Reset your Grafana user password using the Scaleway API. Retrieve your Grafana user ID and reset the password with a simple curl command.
+tags: grafana password credentials
+dates:
+ validation: 2024-12-26
+ posted: 2023-04-03
+categories:
+ - observability
+---
+
+This page shows you how to reset your Grafana user's password through the Scaleway console.
+
+
+
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - [Created](/iam/how-to/create-api-keys/) an API key with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page
+ - [Installed](https://curl.se/download.html) curl
+
+
+1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.
+2. Click the **Grafana users** tab.
+3. Click the icon next to the relevant Grafana user.
+4. Click **Generate password**.
+5. Click **Generate new password** to confirm. Your new password displays. Make sure that you copy it before leaving the page.
diff --git a/pages/containers/container-registry/concepts.mdx b/pages/container-registry/concepts.mdx
similarity index 100%
rename from pages/containers/container-registry/concepts.mdx
rename to pages/container-registry/concepts.mdx
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-namespace-push-instructions.webp b/pages/container-registry/how-to/assets/scaleway-namespace-push-instructions.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-namespace-push-instructions.webp
rename to pages/container-registry/how-to/assets/scaleway-namespace-push-instructions.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_delete_image.webp b/pages/container-registry/how-to/assets/scaleway-registry_delete_image.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_delete_image.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_delete_image.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_delete_namespace.webp b/pages/container-registry/how-to/assets/scaleway-registry_delete_namespace.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_delete_namespace.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_delete_namespace.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_home.webp b/pages/container-registry/how-to/assets/scaleway-registry_home.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_home.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_home.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_image_privacy.webp b/pages/container-registry/how-to/assets/scaleway-registry_image_privacy.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_image_privacy.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_image_privacy.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_list_images.webp b/pages/container-registry/how-to/assets/scaleway-registry_list_images.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_list_images.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_list_images.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_namespace_list.webp b/pages/container-registry/how-to/assets/scaleway-registry_namespace_list.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_namespace_list.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_namespace_list.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_namespace_privacy_policies.webp b/pages/container-registry/how-to/assets/scaleway-registry_namespace_privacy_policies.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_namespace_privacy_policies.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_namespace_privacy_policies.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_privacy_policy.webp b/pages/container-registry/how-to/assets/scaleway-registry_privacy_policy.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_privacy_policy.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_privacy_policy.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_pull_instructions.webp b/pages/container-registry/how-to/assets/scaleway-registry_pull_instructions.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_pull_instructions.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_pull_instructions.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_pull_instructions_popup.webp b/pages/container-registry/how-to/assets/scaleway-registry_pull_instructions_popup.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_pull_instructions_popup.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_pull_instructions_popup.webp
diff --git a/pages/containers/container-registry/how-to/assets/scaleway-registry_push_instructions.webp b/pages/container-registry/how-to/assets/scaleway-registry_push_instructions.webp
similarity index 100%
rename from pages/containers/container-registry/how-to/assets/scaleway-registry_push_instructions.webp
rename to pages/container-registry/how-to/assets/scaleway-registry_push_instructions.webp
diff --git a/pages/containers/container-registry/how-to/connect-docker-cli.mdx b/pages/container-registry/how-to/connect-docker-cli.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/connect-docker-cli.mdx
rename to pages/container-registry/how-to/connect-docker-cli.mdx
diff --git a/pages/containers/container-registry/how-to/create-namespace.mdx b/pages/container-registry/how-to/create-namespace.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/create-namespace.mdx
rename to pages/container-registry/how-to/create-namespace.mdx
diff --git a/pages/containers/container-registry/how-to/delete-image.mdx b/pages/container-registry/how-to/delete-image.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/delete-image.mdx
rename to pages/container-registry/how-to/delete-image.mdx
diff --git a/pages/containers/container-registry/how-to/delete-namespace.mdx b/pages/container-registry/how-to/delete-namespace.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/delete-namespace.mdx
rename to pages/container-registry/how-to/delete-namespace.mdx
diff --git a/pages/containers/container-registry/how-to/display-image-versions.mdx b/pages/container-registry/how-to/display-image-versions.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/display-image-versions.mdx
rename to pages/container-registry/how-to/display-image-versions.mdx
diff --git a/pages/containers/container-registry/how-to/index.mdx b/pages/container-registry/how-to/index.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/index.mdx
rename to pages/container-registry/how-to/index.mdx
diff --git a/pages/containers/container-registry/how-to/manage-image-privacy-settings.mdx b/pages/container-registry/how-to/manage-image-privacy-settings.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/manage-image-privacy-settings.mdx
rename to pages/container-registry/how-to/manage-image-privacy-settings.mdx
diff --git a/pages/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx b/pages/container-registry/how-to/manage-namespace-privacy-policies.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx
rename to pages/container-registry/how-to/manage-namespace-privacy-policies.mdx
diff --git a/pages/containers/container-registry/how-to/pull-images.mdx b/pages/container-registry/how-to/pull-images.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/pull-images.mdx
rename to pages/container-registry/how-to/pull-images.mdx
diff --git a/pages/containers/container-registry/how-to/push-images.mdx b/pages/container-registry/how-to/push-images.mdx
similarity index 100%
rename from pages/containers/container-registry/how-to/push-images.mdx
rename to pages/container-registry/how-to/push-images.mdx
diff --git a/pages/containers/container-registry/index.mdx b/pages/container-registry/index.mdx
similarity index 100%
rename from pages/containers/container-registry/index.mdx
rename to pages/container-registry/index.mdx
diff --git a/pages/containers/container-registry/quickstart.mdx b/pages/container-registry/quickstart.mdx
similarity index 100%
rename from pages/containers/container-registry/quickstart.mdx
rename to pages/container-registry/quickstart.mdx
diff --git a/pages/containers/index.mdx b/pages/containers/index.mdx
deleted file mode 100644
index 868c1c3e24..0000000000
--- a/pages/containers/index.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-meta:
- title: Discover Containers
- description: Discover Containers
-content:
- h1: Discover Containters
- paragraph: Discover Containers
----
diff --git a/pages/cpanel-hosting/assets/scaleway_dashboard_cpanel.webp b/pages/cpanel-hosting/assets/scaleway_dashboard_cpanel.webp
new file mode 100644
index 0000000000..90f50b2b38
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_dashboard_cpanel.webp differ
diff --git a/pages/cpanel-hosting/assets/scaleway_domain_cpanel1.webp b/pages/cpanel-hosting/assets/scaleway_domain_cpanel1.webp
new file mode 100644
index 0000000000..c513b5b6e8
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_domain_cpanel1.webp differ
diff --git a/pages/cpanel-hosting/assets/scaleway_hosting1.webp b/pages/cpanel-hosting/assets/scaleway_hosting1.webp
new file mode 100644
index 0000000000..dad7db0355
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_hosting1.webp differ
diff --git a/pages/cpanel-hosting/assets/scaleway_hosting_2.webp b/pages/cpanel-hosting/assets/scaleway_hosting_2.webp
new file mode 100644
index 0000000000..83abcfd705
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_hosting_2.webp differ
diff --git a/pages/cpanel-hosting/assets/scaleway_list_of_domains.webp b/pages/cpanel-hosting/assets/scaleway_list_of_domains.webp
new file mode 100644
index 0000000000..2a2afcd21f
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_list_of_domains.webp differ
diff --git a/pages/cpanel-hosting/assets/scaleway_status_of_domain_names.webp b/pages/cpanel-hosting/assets/scaleway_status_of_domain_names.webp
new file mode 100644
index 0000000000..49152ab84b
Binary files /dev/null and b/pages/cpanel-hosting/assets/scaleway_status_of_domain_names.webp differ
diff --git a/pages/cpanel-hosting/index.mdx b/pages/cpanel-hosting/index.mdx
new file mode 100644
index 0000000000..426ead1d92
--- /dev/null
+++ b/pages/cpanel-hosting/index.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: cPanel Webhosting Documentation
+ description: Dive into Scaleway cPanel Webhosting with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/cpanel-hosting/quickstart.mdx b/pages/cpanel-hosting/quickstart.mdx
new file mode 100644
index 0000000000..b1aa36011b
--- /dev/null
+++ b/pages/cpanel-hosting/quickstart.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: cPanel Webhosting - Quickstart
+ description: This page shows you how to get started with cPanel webhosting.
+content:
+ h1: cPanel Webhosting - Quickstart
+ paragraph: This page shows you how to get started with cPanel webhosting.
+tags: webhosting cpanel
+dates:
+ validation: 2024-12-23
+ posted: 2021-05-26
+categories:
+ - webhosting
+---
+
+
+
+cPanel is a website management control panel tool, providing users with a graphical interface and fast access icons which allow the configuration and monitoring of their hosting solutions. Features like publishing websites, launching databases, creating emails, and managing files are available through the cPanel interface with elevated performance.
+
+## Getting started
+
+Not sure where to begin? Take a look at our Frequently Asked Questions, which guide you to the relevant official cPanel documentation.
+
+* [How do I use cPanel?](https://docs.cpanel.net/cpanel/the-cpanel-interface/the-cpanel-interface/)
+* [How do I set up SSH Access?](https://docs.cpanel.net/cpanel/security/ssh-access/)
+* [How do I manage my e-mail accounts?](https://docs.cpanel.net/cpanel/email/email-accounts/#overview)
+* [How do I configure my FTP accounts (create, access & delete)?](https://docs.cpanel.net/cpanel/files/ftp-accounts/)
+* [How do I manage my databases?](https://docs.cpanel.net/cpanel/databases/)
+ * [With MySQL](https://docs.cpanel.net/cpanel/databases/mysql-databases/)
+ * [With PostgresQL](https://docs.cpanel.net/cpanel/databases/postgresql-databases/)
+* [How do I manage my domains?](https://docs.cpanel.net/cpanel/domains/domains/)
+
+## How to access cPanel via the console
+
+Click **Dashboard** to access the link to your cPanel administration interface which is available in your hosting homepage.
+
+
+
+
+
+## How to access the webmail
+
+The classic Scaleway Dedibox webmail interface will remain available via the [website](https://webmail.online.net). If you wish to manage your e-mails through cPanel, you can access the webmail platform directly via the cPanel dashboard.
+
+## How to configure the nameserver
+
+Nameservers are servers used to translate domain names into IP addresses. When you enter a URL in a browser, they show you where the website is located, instead of memorizing entire numerical sequences in the form of IP addresses.
+
+
+ If you are migrating from another Webhosting service to the new Cloud Hosting offer powered by cPanel, you might need to update your nameserver information with the following new addresses:
+ * ns1.whm.fr-par.scw.cloud
+ * ns2.whm.fr-par.scw.cloud
+
+
+1. From the console, click **Domain** on the upper menu of the Scaleway Dedibox console. A list of your domain names displays.
+
+2. Click the **Configure domain name** action of the domain you wish to set up. The **Status of domain name** page displays.
+
+
+3. Click the **Manage DNS Servers** tab to find a list of your nameservers.
+4. Erase the old addresses.
+5. Include the new cPanel nameservers.
+6. Click **Update DNS Servers** to update the information.
\ No newline at end of file
diff --git a/pages/cpanel-hosting/reference-content.mdx b/pages/cpanel-hosting/reference-content.mdx
new file mode 100644
index 0000000000..b8309c2af9
--- /dev/null
+++ b/pages/cpanel-hosting/reference-content.mdx
@@ -0,0 +1,139 @@
+---
+meta:
+ title: cPanel Webhosting - Additional content
+ description: This page provides useful links and information for the management and configuration of your Scaleway webhosting package, powered by cPanel
+content:
+ h1: cPanel Webhosting - Additional content
+ paragraph: This page provides useful links and information for the management and configuration of your Scaleway webhosting package, powered by cPanel.
+tags: webhosting cpanel jetbackup database mailing list mailing-list
+dates:
+ validation: 2024-08-12
+ posted: 2021-09-12
+categories:
+ - webhosting
+---
+
+
+ This documentation is for users who have a webhosting package powered by cPanel on [Scaleway Dedibox](https://www.scaleway.com/en/web-hosting/).
+
+
+Refer to our [Quickstart](/cpanel-hosting/quickstart/) which contains useful links that answer your frequently asked questions.
+
+If you need additional help setting up your webhosting solution, or have any questions, refer to the index below:
+
+## Creating a Website
+
+* [From WHM to Website](https://docs.cpanel.net/knowledge-base/accounts/from-whm-to-website/)
+* [Apache vs. PHP-FPM Bottleneck with Child Processes](https://docs.cpanel.net/knowledge-base/php-fpm/apache-vs-php-fpm-bottleneck-with-child-processes/)
+* [Configuration Values of PHP-FPM](https://docs.cpanel.net/knowledge-base/php-fpm/configuration-values-of-php-fpm/)
+* [PHP FastCGI Process Manager - PHP-FPM](https://docs.cpanel.net/knowledge-base/php-fpm/php-fastcgi-process-manager-php-fpm/)
+* [PHP-FPM Code and FileSystem Layout for EasyApache 4](https://docs.cpanel.net/knowledge-base/php-fpm/php-fpm-code-and-filesystem-layout-for-easyapache-4/)
+* [WP Toolkit](https://docs.cpanel.net/knowledge-base/cpanel-developed-plugins/wp-toolkit/)
+* [How to Install WordPress® With cPanel](https://docs.cpanel.net/knowledge-base/third-party/how-to-install-wordpress-with-cpanel/)
+
+## Files
+
+* [File Manager](https://docs.cpanel.net/cpanel/files/file-manager/)
+* [Images](https://docs.cpanel.net/cpanel/files/images/)
+* [Disk Usage](https://docs.cpanel.net/cpanel/files/disk-usage/)
+* [FTP Accounts](https://docs.cpanel.net/cpanel/files/ftp-accounts/)
+* [FTP Connections](https://docs.cpanel.net/cpanel/files/ftp-connections/)
+* [File and Directory Restoration for cPanel](https://docs.cpanel.net/cpanel/files/file-and-directory-restoration-for-cpanel/)
+
+## JetBackup
+
+* [Full Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/fullBackups.html)
+* [File Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/fileBackups.html)
+* [Cron Job Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/cronJobBackups.html)
+* [DNS Zone Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/dnsBackups.html)
+* [Database Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/dbBackups.html)
+* [Email Backups](https://docs.jetbackup.com/manual/cpanel/BackupTypes/emailBackups.html)
+* [Queue](https://docs.jetbackup.com/manual/cpanel/queue.html)
+* [Snapshots](https://docs.jetbackup.com/manual/cpanel/snapshots.html)
+* [Settings](https://docs.jetbackup.com/manual/cpanel/settings.html)
+
+## Databases
+
+* [phpMyAdmin](https://docs.cpanel.net/cpanel/databases/phpmyadmin/)
+* [MySQL® Databases](https://docs.cpanel.net/cpanel/databases/mysql-databases/)
+* [MySQL® Database Wizard](https://docs.cpanel.net/cpanel/databases/mysql-database-wizard/)
+* [PostgreSQL Databases](https://docs.cpanel.net/cpanel/databases/postgresql-databases/)
+* [PostgreSQL Database Wizard](https://docs.cpanel.net/cpanel/databases/postgresql-database-wizard/)
+* [phpPgAdmin](https://docs.cpanel.net/cpanel/databases/phppgadmin/)
+
+## Domains
+
+* [Site Publisher](https://docs.cpanel.net/cpanel/domains/site-publisher/)
+* [Domains](https://docs.cpanel.net/cpanel/domains/domains/)
+* [Addon Domains](https://docs.cpanel.net/cpanel/domains/domains/#create-a-new-domain)
+* [Redirects](https://docs.cpanel.net/cpanel/domains/redirects/)
+* [Zone Editor](https://docs.cpanel.net/cpanel/domains/zone-editor/)
+
+## Email
+
+* [Email Accounts](https://docs.cpanel.net/cpanel/email/email-accounts/)
+* [Forwarders](https://docs.cpanel.net/cpanel/email/forwarders/)
+* [Email Routing](https://docs.cpanel.net/cpanel/email/email-routing/)
+* [Autoresponders](https://docs.cpanel.net/cpanel/email/autoresponders/)
+* [Default Address](https://docs.cpanel.net/cpanel/email/default-address/)
+* [Mailing Lists](https://docs.cpanel.net/cpanel/email/mailing-lists/)
+* [Track Delivery](https://docs.cpanel.net/cpanel/email/track-delivery/)
+* [Global Email Filters](https://docs.cpanel.net/cpanel/email/global-email-filters/)
+* [Email Filters](https://docs.cpanel.net/cpanel/email/email-filters/)
+* [Email Deliverability](https://docs.cpanel.net/cpanel/email/email-deliverability-in-cpanel/)
+* [Address Importer](https://docs.cpanel.net/cpanel/email/address-importer/)
+* [Spam Filters](https://docs.cpanel.net/cpanel/email/spam-filters/)
+* [Encryption](https://docs.cpanel.net/cpanel/email/encryption/)
+* [BoxTrapper](https://docs.cpanel.net/cpanel/email/boxtrapper/)
+* [Calendars and Contacts](https://docs.cpanel.net/knowledge-base/webmail/how-to-set-up-calendars-and-contacts/)
+* [Email Disk Usage](https://docs.cpanel.net/cpanel/email/email-disk-usage/)
+
+## Metrics
+
+* [Visitors](https://docs.cpanel.net/cpanel/metrics/visitors/)
+* [Errors](https://docs.cpanel.net/cpanel/metrics/errors/)
+* [Raw Access](https://docs.cpanel.net/cpanel/metrics/raw-access/)
+* [Awstats](https://docs.cpanel.net/cpanel/metrics/awstats/)
+* [Analog Stats](https://docs.cpanel.net/cpanel/metrics/analog-stats/)
+* [Webalizer](https://docs.cpanel.net/cpanel/metrics/webalizer/)
+* [Webalizer FTP](https://docs.cpanel.net/cpanel/metrics/webalizer-ftp/)
+* [Metrics Editor](https://docs.cpanel.net/cpanel/metrics/metrics-editor/)
+* [CPU and Concurrent Connection Usage](https://docs.cpanel.net/cpanel/metrics/cpu-and-concurrent-connection-usage/)
+
+## Security
+
+* [SSH Access](https://docs.cpanel.net/cpanel/security/ssh-access/)
+* [IP Blocker](https://docs.cpanel.net/cpanel/security/ip-blocker/)
+* [SSL/TLS](https://docs.cpanel.net/cpanel/security/ssl-tls/)
+* [Hotlink Protection](https://docs.cpanel.net/cpanel/security/hotlink-protection/)
+* [Leech Protection](https://docs.cpanel.net/cpanel/security/leech-protection/)
+* [SSL/TLS Wizard](https://docs.cpanel.net/cpanel/security/ssl-tls-wizard/)
+* [ModSecurity®](https://docs.cpanel.net/cpanel/security/modsecurity/)
+* [SSL/TLS Status](https://docs.cpanel.net/cpanel/security/ssl-tls-status/)
+* [The Let's Encrypt™ Plugin](https://docs.cpanel.net/knowledge-base/third-party/the-lets-encrypt-plugin/)
+
+## Software
+
+* [PHP PEAR Packages](https://docs.cpanel.net/cpanel/software/php-pear-packages/)
+* [Perl Modules](https://docs.cpanel.net/cpanel/software/perl-modules/)
+* [Optimize Website](https://docs.cpanel.net/cpanel/software/optimize-website/)
+* [MultiPHP Manager](https://docs.cpanel.net/cpanel/software/multiphp-manager-for-cpanel/)
+* [Installing Softaculous in cPanel](https://www.softaculous.com/docs/admin/installing-softaculous-in-cpanel/)
+* [MultiPHP Manager](https://docs.cpanel.net/cpanel/software/multiphp-manager-for-cpanel/#set-the-php-version-for-a-domain)
+
+## Advanced
+
+* [Terminal](https://docs.cpanel.net/cpanel/advanced/terminal-in-cpanel/)
+* [Cron Jobs](https://docs.cpanel.net/cpanel/advanced/cron-jobs/)
+* [Track DNS](https://docs.cpanel.net/cpanel/advanced/track-dns/)
+* [Indexes](https://docs.cpanel.net/cpanel/advanced/indexes/)
+* [Error Pages](https://docs.cpanel.net/cpanel/advanced/error-pages/)
+* [Apache Handlers](https://docs.cpanel.net/cpanel/advanced/apache-handlers/)
+* [MIME Types](https://docs.cpanel.net/cpanel/advanced/mime-types/)
+
+## Preferences
+
+* [Password & Security](https://docs.cpanel.net/cpanel/preferences/password-and-security/)
+* [Change Language](https://docs.cpanel.net/cpanel/preferences/change-language/)
+* [Contact Information](https://docs.cpanel.net/cpanel/preferences/contact-information/)
+* [User Manager](https://docs.cpanel.net/cpanel/preferences/user-manager/)
\ No newline at end of file
diff --git a/pages/dedibox-account/concepts.mdx b/pages/dedibox-account/concepts.mdx
new file mode 100644
index 0000000000..155d0afe69
--- /dev/null
+++ b/pages/dedibox-account/concepts.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: Dedibox account - Concepts
+ description: This page explains all the concepts related to your Dedibox account
+content:
+ h1: Dedibox account - Concepts
+ paragraph: This page explains all the concepts related to your Dedibox account
+tags: dedibox dedibox-console account logs google authenticator authenticator
+dates:
+ validation: 2024-08-19
+categories:
+ - account
+---
+
+## Abuse
+
+[Abuse](https://www.scaleway.com/en/abuse-notice/) of Scaleway services includes cyber-crime, copyright violation, illegal or offensive content, spamming and malware distribution. Abuse should be [reported in the console](https://console.scaleway.com/support/abuses/create).
+
+Abuse reports on the same offending resource for the same reason within a given timeframe are grouped by case. An abuse report either creates a case if no case is currently open or joins an existing case. Scaleway clients are responsible for taking the appropriate security measures to solve the case and related abuses.
+
+## Authorized SSH key
+
+An SSH key (**S**ecure **Sh**ell key) allows passwordless authentication on SSH sessions. An SSH key is generated by creating an RSA key pair consisting of two elements:
+
+- a sensitive **identification key**, (i.e. private key) which must be stored securely,
+- a **public key** which is uploaded to the Scaleway Dedibox interface.
+
+The public key is kept in your Scaleway account and transferred to the Dedibox server during the installation, while the identification key is kept securely on your local computer. When connecting to the Instance via SSH, a trusted connection to the machine is established using the key pair.
+
+## Billing
+
+The billing section contains all information related to the payment of your invoices. You can update your billing method from this page and download your invoices. It also allows you to define an additional billing contact, who receives a copy of your monthly invoice by email.
+
+## Dedibox console
+
+The Dedibox console allows you to view and manage your Scaleway Dedibox products, billing information, support tickets and more. You can access the console at the address [console.online.net](https://console.online.net).
+
+## Logs
+
+On this page you can see a list of connections made to your account. Each connection attempt is tracked with its associated status. It can either be **Login** for successful connections or **Connection refused** for failed logins.
+
+* **Messages**: The messages section of the Scaleway Dedibox console contains important messages regarding your account or your services. You will find information regarding planned maintenance or other important information in this section of the console.
+
+* **Notifications**: The notification section lets you define for which services you want to receive notifications by email. By default, you receive notifications for all your services requiring renewal (domain names and Webhosting services). You can opt out if you do not want to receive renewal notifications for certain services.
+
+* **Outsourcing**: Outsourcing allows you to provide access to your services to third parties. You can define another Scaleway Dedibox user who will have access to specific resources of your account, without needing to provide access to your full account. Scaleway Dedibox maintains a portfolio of [certified outsourcing partners](https://www.scaleway.com/en/dedibox/outsourcing/) for webmastering and administration of your dedicated servers.
+
+* **Personal information**: The personal information section of the Scaleway Dedibox console allows you to view and update certain personal information related to your account. You can also update your password or email address from this section of the Dedibox console.
+
+* **Security**: The security section of the Scaleway Dedibox console allows you to configure optional multifactor authentication to increase the security of your account. You can configure MFA using authentications applications such as Authy or Google Authenticator. French residents cans optionally also configure MFA by SMS.
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/accept-outsourcing.mdx b/pages/dedibox-account/how-to/accept-outsourcing.mdx
new file mode 100644
index 0000000000..4a90379d00
--- /dev/null
+++ b/pages/dedibox-account/how-to/accept-outsourcing.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to accept a Dedibox outsourcing request
+ description: Learn how to accept a Scaleway Dedibox outsourcing request.
+content:
+ h1: How to accept a Dedibox outsourcing request
+ paragraph: This guide explains how to accept a Scaleway Dedibox outsourcing request.
+tags: dedibox, outsource, outsourcing-request
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+If you have a Scaleway Dedibox account, another user can grant you access to their dedicated servers and failover IPs by outsourcing them to you. This allows you to manage their services without gaining full access to their Dedibox account.
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+
+1. When another user [sends you an outsourcing request](/dedibox-account/how-to/outsource-dedibox/), you will receive a notification. Click the link provided in the outsourcing request email to open the Scaleway Dedibox console.
+
+2. The **Outsourcing** section of the Scaleway Dedibox console displays.
+3. Review the services the user wants to outsource to you.
+4. Check the **Accept** box for the service(s) you agree to take over.
+
+5. Click **Save changes** to confirm.
+
+After completing these steps, the outsourced services will be available in your Dedibox console, and you can begin managing them.
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/add-payment-method.mdx b/pages/dedibox-account/how-to/add-payment-method.mdx
new file mode 100644
index 0000000000..058dd193ca
--- /dev/null
+++ b/pages/dedibox-account/how-to/add-payment-method.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: How to add a Dedibox payment method
+ description: This page explains how to add a payment method to your Dedibox console.
+content:
+ h1: How to add a Dedibox payment method
+ paragraph: This page explains how to add a payment method to your Dedibox console.
+tags: dedibox dedibox-console payment billing
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+Follow these steps to change the payment mode on your Scaleway Dedibox account:
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. From the drop-down menu, select **Billing**. The billing page displays.
+2. Click **Change payment mode**. A list of available payment modes appear. Choose your preferred method, then click **Update payment mode**.
+
+ Some payment methods may not be available for your account.
+
+3. Enter the required information for your new payment mode and validate the changes to complete the process.
+
+
diff --git a/pages/dedibox-account/how-to/assets/scaleway-account.webp b/pages/dedibox-account/how-to/assets/scaleway-account.webp
new file mode 100644
index 0000000000..606f411b0e
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-account.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-2fa-activate.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-2fa-activate.webp
new file mode 100644
index 0000000000..9daa384f31
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-2fa-activate.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-list.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-list.webp
new file mode 100644
index 0000000000..80096b2688
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-list.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-menu.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-menu.webp
new file mode 100644
index 0000000000..b3e4176b6f
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-abuses-menu.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-confirm-new-email.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-confirm-new-email.webp
new file mode 100644
index 0000000000..c7d549f39f
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-confirm-new-email.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-dedibox-outsourcing.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-dedibox-outsourcing.webp
new file mode 100644
index 0000000000..d76f1e11e3
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-dedibox-outsourcing.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ip-failover-outsourcing.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ip-failover-outsourcing.webp
new file mode 100644
index 0000000000..56396f85ed
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ip-failover-outsourcing.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-accept.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-accept.webp
new file mode 100644
index 0000000000..df8fbe5881
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-accept.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-menu.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-menu.webp
new file mode 100644
index 0000000000..5f4ff0b49d
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-menu.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-request.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-request.webp
new file mode 100644
index 0000000000..3041e97a08
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-request.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-revoke.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-revoke.webp
new file mode 100644
index 0000000000..3857e90828
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-outsourcing-revoke.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-privacy-menu.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-privacy-menu.webp
new file mode 100644
index 0000000000..850e4176dc
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-privacy-menu.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-security-menu.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-security-menu.webp
new file mode 100644
index 0000000000..a54794f1e5
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-security-menu.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ssh-key-menu.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ssh-key-menu.webp
new file mode 100644
index 0000000000..449be5bd18
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-ssh-key-menu.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-email.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-email.webp
new file mode 100644
index 0000000000..db9f919eef
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-email.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-password.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-password.webp
new file mode 100644
index 0000000000..8d4bc4ef82
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-console-update-password.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-login.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-login.webp
new file mode 100644
index 0000000000..20292ba673
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-login.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-popup.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-popup.webp
new file mode 100644
index 0000000000..6c7801a06f
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-popup.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-signup.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-signup.webp
new file mode 100644
index 0000000000..6e52feeb56
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-signup.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-dedibox-subscribe.webp b/pages/dedibox-account/how-to/assets/scaleway-dedibox-subscribe.webp
new file mode 100644
index 0000000000..7755fd377a
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-dedibox-subscribe.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-elements-create-account.webp b/pages/dedibox-account/how-to/assets/scaleway-elements-create-account.webp
new file mode 100644
index 0000000000..28d942e9e4
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-elements-create-account.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-orga-dashboard-test.webp b/pages/dedibox-account/how-to/assets/scaleway-orga-dashboard-test.webp
new file mode 100644
index 0000000000..cee40082d8
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-orga-dashboard-test.webp differ
diff --git a/pages/dedibox-account/how-to/assets/scaleway-website.webp b/pages/dedibox-account/how-to/assets/scaleway-website.webp
new file mode 100644
index 0000000000..b088ed8cbb
Binary files /dev/null and b/pages/dedibox-account/how-to/assets/scaleway-website.webp differ
diff --git a/pages/dedibox-account/how-to/contact-support.mdx b/pages/dedibox-account/how-to/contact-support.mdx
new file mode 100644
index 0000000000..a7321cfd5c
--- /dev/null
+++ b/pages/dedibox-account/how-to/contact-support.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to contact the Dedibox support team
+ description: This page shows you how to contact the Scaleway Dedibox support team.
+content:
+ h1: How to contact the Dedibox support team
+ paragraph: This page shows you how to contact the Scaleway Dedibox support team.
+tags: contact support help assistance dedibox-console
+dates:
+ validation: 2024-08-05
+ posted: 2021-08-05
+categories:
+ - account
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. Log in to the [Dedibox console](https://console.online.net).
+2. Locate and click the **Support** link.
+3. From the drop-down menu, select **Technical assistance**. This opens a [support ticket form](https://console.online.net/en/assistance/ticket).
+4. Fill out the form with the required details, providing as much relevant information as possible to assist the support team.
+5. Once you have completed your ticket, submit it.
+
+ After submitting the ticket, you will have access to your conversation history with the technical assistance team. This allows you to track your previous and current tickets.
+
+
+ Check the [Scaleway Status](https://status.scaleway.com/) page for real-time updates on the status of our services and maintenance information.
+
diff --git a/pages/dedibox-account/how-to/create-a-dedibox-account.mdx b/pages/dedibox-account/how-to/create-a-dedibox-account.mdx
new file mode 100644
index 0000000000..65d6d7e4c2
--- /dev/null
+++ b/pages/dedibox-account/how-to/create-a-dedibox-account.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: How to create your Scaleway Dedibox account
+ description: Learn how to create a Scaleway Dedibox account.
+content:
+ h1: How to create your Scaleway Dedibox account
+ paragraph: This guide explains how to create a Scaleway Dedibox account.
+tags: dedibox, account, create, signup
+dates:
+ validation: 2024-08-12
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+By creating a Scaleway Dedibox account, you gain access to powerful servers with excellent reliability and redundancy, backed by over 15 years of industry experience.
+Scaleway Dedibox servers are ideal for hosting websites, applications, databases, and other services requiring robust infrastructure.
+Additionally, you benefit from Scaleway's dedicated support, flexible billing options, and easy scalability.
+
+Follow these steps to get started with Scaleway Dedibox:
+
+### How to create your Scaleway Dedibox account
+
+1. Go to the [Scaleway Dedibox](https://console.online.net/en/user/subscribe) website and click **Subscribe**.
+2. Complete the subscription form with your details, review the information, and accept the terms of service. Then, click **Create my account**.
+3. Check your email inbox for a verification email. Click the verification link to activate your account. This will take you to the [Dedibox console](https://console.online.net/en/login) login page.
+4. Enter the username and password you created during registration, then click **Sign in**.
+
+You are now connected to the Scaleway Dedibox console. You must add [a payment method](/dedibox-account/how-to/add-payment-method/) before ordering your [first Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/).
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx b/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx
new file mode 100644
index 0000000000..ed98405b80
--- /dev/null
+++ b/pages/dedibox-account/how-to/disable-two-factor-authentication.mdx
@@ -0,0 +1,43 @@
+---
+meta:
+ title: How to disable multifactor authentication
+ description: This page explains how to disable multifactor authentication for Scaleway Dedibox.
+content:
+ h1: How to disable multifactor authentication
+ paragraph: This page explains how to disable multifactor authentication for Scaleway Dedibox.
+tags: dedibox-console dedibox disable mfa 2fa multifactor authentication
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+You can disable the multifactor authentication of your Dedibox account if you want to register a new authentication device.
+
+
+For security reasons, it is **not recommended to disable** multifactor authentication permanently.
+
+
+## How to disable multifactor authentication
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. Then click **Security** in the pop-up menu.
+
+2. The security page displays. Click **Disable two factor authenticaton**.
+3. Enter a security token generated by your multifactor authentication application and click **Confirm**.
+
+Multifactor authentication is now disabled, and you can log in with your identifier and password only.
+
+## How to restore access to your account
+
+If you lose both your MFA app and backup codes, the only way to regain access to your account is through a manual identity verification. To do so, contact our support team with the following information:
+ * Email address,
+ * Postal address,
+ * Two different documents proving your identity (passport or local ID card, for individual accounts + certificate of incorporation, for companies),
+ * Your current phone number,
+ * A copy of your last Dedibox bill or, if you do not have it, details about the charged amount,
+ * A card statement showing the Scaleway bill debit.
+
+Once you have collected this information, send it to [document@scaleway.com](mailto:document@scaleway.com).
+
+
diff --git a/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx b/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx
new file mode 100644
index 0000000000..f0b5e9478d
--- /dev/null
+++ b/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to enable multifactor authentication (MFA) for Dedibox accounts
+ description: This page explains how to enable multifactor authentication on the Scaleway Dedibox console.
+content:
+ h1: How to enable multifactor authentication (MFA) for Dedibox accounts
+ paragraph: This page explains how to enable multifactor authentication on the Scaleway Dedibox console.
+tags: dedibox-console 2fa authentication enable multifactor
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+Multifactor authentication helps make your account safer. When enabled, after entering your password, a security code generated by your phone is required each time you log in. This authentication method ensures your account remains protected even in case of leaked passwords.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Downloaded a multi-factor authenticator application to your phone
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. Then click **Security** in the pop-up menu.
+
+2. The security page displays. Click **Show QR code** to display the QR code and add the Scaleway Dedibox console to your authenticator application.
+
+
+
+ If your phone does not have a camera, you can manually enter the registration key shown in the console.
+
+3. Open the authenticator application on your phone and scan the code using the application.
+4. A registration code is displayed on your phone's display. Enter this code in the activation form and click **Enable** to validate.
+
+Your account is now protected by multifactor authentication, and a security token will be requested upon your next login.
+
+
+Make sure to keep your authentication device secure, as you cannot log in without the authentication token.
+
+
+
diff --git a/pages/dedibox-account/how-to/index.mdx b/pages/dedibox-account/how-to/index.mdx
new file mode 100644
index 0000000000..5b201b4d7e
--- /dev/null
+++ b/pages/dedibox-account/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox account - How Tos
+ description: Dedibox Account How Tos
+content:
+ h1: Dedibox account - How Tos
+ paragraph: Dedibox Account How Tos
+---
diff --git a/pages/dedibox-account/how-to/manage-data-settings.mdx b/pages/dedibox-account/how-to/manage-data-settings.mdx
new file mode 100644
index 0000000000..287ad1f2b4
--- /dev/null
+++ b/pages/dedibox-account/how-to/manage-data-settings.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to manage your Dedibox data privacy settings
+ description: This page explains how to manage your Scaleway Dedibox data privacy settings.
+content:
+ h1: How to manage your Dedibox data privacy settings
+ paragraph: This page explains how to manage your Scaleway Dedibox data privacy settings.
+tags: manage data privacy dedibox-console
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+You can manage your data privacy settings from the Scaleway Dedibox console.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. Then, select **[Privacy](https://console.online.net/en/account/privacy)** from the pop-up menu.
+2. The data privacy section displays. You can:
+ - retain a copy of your personal data.
+ - retrieve information about your personal data processed by Scaleway Dedibox.
+ - rectify your personal data.
+ - erase your personal data.
+ - exercise your right to data portability.
+ - manage the use of your personal data.
+3. Check the corresponding checkboxes for the actions you want to take, and then click **Send** to confirm your choices.
+
+
diff --git a/pages/dedibox-account/how-to/outsource-dedibox.mdx b/pages/dedibox-account/how-to/outsource-dedibox.mdx
new file mode 100644
index 0000000000..4d8ec28352
--- /dev/null
+++ b/pages/dedibox-account/how-to/outsource-dedibox.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to outsource your Dedibox
+ description: Learn how to outsource your Scaleway Dedibox dedicated server.
+content:
+ h1: How to outsource your Dedibox
+ paragraph: This guide explains how to outsource your Scaleway Dedibox dedicated server.
+tags: dedibox, outsource
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+Outsourcing a Dedibox dedicated server means entrusting the technical management of your machines and services to another Scaleway Dedibox account while retaining control over your main account.
+
+By outsourcing your servers, you grant permission to a third party to handle management on your behalf. This allows the designated Dedibox account holder access to all the necessary technical details of your Dedibox. However, they will not be able to view your billing information or make any changes to the services within your primary account. This ensures you maintain full control over your billing and service configurations while benefiting from external technical expertise.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- At least one Dedibox server
+
+
+ If you have multiple machines, you can outsource each of them individually to different users, if required.
+
+
+### Steps to outsource your Dedibox
+
+1. In the top menu, click **Server** > **Server list** to display the list of your servers.
+2. Select the server you want to outsource and click **Manage** to view its details.
+3. Click **Outsourcing** in the side menu of your server's status page:
+
+
+ The outsourcing form displays
+4. Enter the identifier of the new technical contact for your server. The identifier is the login of the other user's console account. Click **Send request** to validate the form.
+
+ The other account holder will receive a notification to accept the outsourcing of your dedicated server into their Scaleway Dedibox account.
diff --git a/pages/dedibox-account/how-to/outsource-failover-ip.mdx b/pages/dedibox-account/how-to/outsource-failover-ip.mdx
new file mode 100644
index 0000000000..604d7a1936
--- /dev/null
+++ b/pages/dedibox-account/how-to/outsource-failover-ip.mdx
@@ -0,0 +1,27 @@
+---
+meta:
+ title: How to outsource a Scaleway Dedibox failover IP
+ description: Learn how to outsource a Scaleway Dedibox failover IP, allowing another user to manage it on your behalf.
+content:
+ h1: How to outsource a Scaleway Dedibox failover IP
+ paragraph: Learn how to outsource a Scaleway Dedibox failover IP, allowing another user to manage it on your behalf.
+tags: dedibox-console dedibox outsource failover failover-ip
+dates:
+ validation: 2024-08-12
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+Outsourcing a Dedibox dedicated server and its allocated failover IPs allows another Dedibox user to manage these resources on your behalf.
+
+1. In the [Dedibox console](https://console.online.net/), navigate to **Server** > **Network configuration** from the top menu. This will display a list of your allocated failover IPs.
+2. Locate the failover IP you intend to outsource. Click the settings icon (typically a gear icon) next to the selected IP. A drop-down menu will appear.
+3. Select **Outsourcing** from the drop-down menu. This will open the outsourcing form, where you can specify the new technical contact.
+4. Enter the **identifier** (login) of the Dedibox user who will manage the failover IP in the outsourcing form. Ensure that the identifier corresponds to the other user's Dedibox console account. Complete the form by providing any additional required details.
+5. Click **Send request** to submit the outsourcing request.
+6. The recipient of the failover IP will receive a notification, prompting them to accept or decline the outsourcing request. Once accepted, the management of the failover IP will be transferred to their account.
+
+
+ By outsourcing the failover IP, you are granting another user full management rights over the IP, including network configuration and troubleshooting.
+
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/recover-password-lost-email.mdx b/pages/dedibox-account/how-to/recover-password-lost-email.mdx
new file mode 100644
index 0000000000..0ef6152f15
--- /dev/null
+++ b/pages/dedibox-account/how-to/recover-password-lost-email.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to recover your Dedibox account password if your email is no longer valid
+ description: Learn how to recover the password of your account if your email address is no longer valid.
+content:
+ h1: How to recover your Dedibox account password if your email is no longer valid
+ paragraph: This guide explains how to recover the password of your account if your email address is no longer valid.
+tags: dedibox-console, recover, password, email, account
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+To ensure the security of your Scaleway Dedibox account, it is strongly advised that you regularly verify and update your contact details, especially your email address.
+This precaution helps prevent potential account lockouts if you lose access to both your console password and email account.
+
+In the unlikely event that you encounter such a situation, follow these steps to recover access to your Scaleway Dedibox account.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+### How to recover your password
+
+If you cannot access your email account, send us a contact update request with the following details:
+
+- Your current and new email addresses
+- Your postal address
+- Two distinct identity documents (e.g., passport or local ID card for individuals, incorporation certificate for companies)-
+- A reachable phone number for contact purposes
+- A copy of your most recent Scaleway Dedibox invoice (or the amount charged if you do not have the invoice)
+- A card statement displaying the Scaleway bill debit
+
+Submit the complete set of required documents via email to [document@scaleway.com](mailto:document@scaleway.com).
+
+Upon receiving your application, we will proceed with updating your email address, subject to validation.
+
+Once your email address is updated, you can submit a [lost password form](https://console.online.net/en/user/recovery) to request the recovery codes for your account.
diff --git a/pages/dedibox-account/how-to/report-incident.mdx b/pages/dedibox-account/how-to/report-incident.mdx
new file mode 100644
index 0000000000..35930e7e82
--- /dev/null
+++ b/pages/dedibox-account/how-to/report-incident.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: How to report a Dedibox incident
+ description: This page shows you how to submit an abuse report and to indicate how the report will be processed.
+content:
+ h1: How to report a Dedibox incident
+ paragraph: This page shows you how to submit an abuse report and to indicate how the report will be processed.
+tags: report incident dedibox-console
+dates:
+ validation: 2024-08-05
+ posted: 2021-08-05
+categories:
+ - account
+---
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+## How to report a Dedibox incident
+
+1. From the Scaleway [console](https://console.scaleway.com) or [website](https://www.scaleway.com/), click the [Report Abuse](https://console.scaleway.com/support/abuses/create/) page. A form displays.
+2. Enter the IP address, domain name or URL of the source you want to report.
+3. Enter the date of publication of the illegal content or the start date of the illegal behavior.
+4. Enter the time of the publication of the illegal content or the time the illegal behavior started.
+5. Select the type of abuse you wish to report in the drop-down box.
+
+ The different types of content or illegal behavior that can be reported are described in Scaleway’s [Abuse notice](https://www.scaleway.com/en/abuse-notice/).
+
+
+ Falsely reporting content or activity as illegal only to obtain its removal or to stop its distribution, is punishable by one year imprisonment and a €15,000 fine.
+
+6. Enter your email address and name, if required.
+7. Describe what you have observed in as much detail as possible. Provide information such as logs, time zones, headers, the precise location and, if applicable, the email addresses to which the content is made accessible.
+
+ This description will be directly forwarded to our customer. Therefore, refrain from including any confidential or personal information which you do not want them to have access to.
+ Scaleway denies all responsibility for the use which could be made by third parties of any information that you provide in this field.
+
+8. Check the box confirming that you are submitting this report in good faith.
+9. Once you have entered the information mentioned above, check the CAPTCHA form and click **Submit abuse report**.
+
+ If you encounter difficulties submitting an abuse report, you can contact [Scaleway’s abuse team](https://www.scaleway.com/fr/contact-trust-et-safety/).
+
+
+## How is my report processed?
+
+Once you have submitted the [report abuse form](https://abuse.scaleway.com/), you will receive an email confirming its reception by Scaleway’s abuse team.
+
+Scaleway’s abuse team will verify the exactness of the report, that all the necessary information has been provided for the report to be processed. They will also verify whether the report indeed relates to explicitly illegal behavior or content with regard to French regulations and the evidence and information you have provided. If your report meets the above criteria, it will be validated by the abuse team and sent to Scaleway’s customer so that the necessary corrective measures can be taken.
+
+1. You will receive updates regarding the resolution of the abuse via the email address provided in the form if you provided one.
+
+ Should Scaleway’s customer not respond, or should the transferred report not be processed correctly, appropriate measures will be taken by Scaleway. These measures may vary from a simple warning to termination of all services of said customer.
+
+2. If your report is rejected, you will be informed of the reasons why by email.
+
+ * Do not repeatedly report the same practices or content, as it forces the abuse team to carry out unnecessary actions and negatively impacts their work.
+ * Remain courteous when communicating with the abuse team. Abuse reports shall not contain any offensive, vulgar or threatening language.
+ * If you consider that your report has been unduly rejected, you can contact Scaleway’s abuse team.
+
+
+
diff --git a/pages/dedibox-account/how-to/resolve-abuse.mdx b/pages/dedibox-account/how-to/resolve-abuse.mdx
new file mode 100644
index 0000000000..62b09130d1
--- /dev/null
+++ b/pages/dedibox-account/how-to/resolve-abuse.mdx
@@ -0,0 +1,104 @@
+---
+meta:
+ title: How to resolve Dedibox abuse tickets and cases
+ description: This page explains how to resolve Abuse tickets.
+content:
+ h1: How to resolve Dedibox abuse tickets and cases
+ paragraph: This page explains how to resolve Abuse tickets.
+tags: resolve abuse complaint ticket dedibox-console
+dates:
+ validation: 2024-09-02
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+
+Abuse reports are complaints regarding the use of Scaleway services for illegal behavior or hosting of illegal content. Abuse reports for the same issue on the same resource within a given time frame are grouped by case.
+
+If you have been the subject of an abuse report, you are responsible for taking the appropriate security measures to solve the case. You must also prevent any further abuse from your resources to avoid your services being locked by Scaleway.
+
+However, Scaleway reserves the right to immediately suspend the infringing services if it is deemed necessary, and proportionate to keep Scaleway’s network safe or to abide by legal requirements.
+
+If you encounter any issue with the resolution of an abuse, ensure that you contact the abuse team by opening a [support ticket](https://console.scaleway.com/support/tickets/create) directly from your console.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+
+1. Click **Abuse** in the bottom left corner of the Scaleway console. A list of your open cases displays. You can also view the closed cases by clicking on **Closed cases**.
+2. Click the **case ID** to view the specifics of the complaint.
+3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue.
+
+ If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/).
+
+ If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly.
+ * For other types of abuse, here are some suggestions to help you to correct them:
+ * Backup all your server data
+ * Check for recent file changes
+ * Check log files on your server
+ * Check your PHP and CGI files for any backdoors
+ * Check if any software you use is vulnerable, and update them
+ * Reinstall your server after backup
+ * Change passwords of your server
+ * Backup your website and your email data
+ * Check for recent files changes, security holes in common CMS you may use (Joomla, SPIP, WordPress…)
+ * Check version in some software you may use on your computer (email client, FTP client)
+ * Change your FTP and email passwords
+ If you do not know how to solve the problem, you can contact our [outsourcing partners(https://www.scaleway.com/en/dedibox/outsourcing/)] or reach out to Scaleway’s abuse team by opening a ticket directly from your Scaleway console account.
+
+4. The case will be closed at the end of its lifetime by Scaleway’s abuse team, and so will the abuse tickets forming the case.
+ If you receive more abuse reports on the same resource within the case lifetime, it means that you did not take the appropriate measures to prevent further abuse from happening.
+ Therefore, we recommend that you take additional actions and contact our support team if you need assistance. Failure to take appropriate measures to solve the case may result in the locking of your service as per our [Terms of Services](https://www.scaleway.com/en/contracts/) and the legal framework in force.
+
+In specific instances, the case will be closed automatically:
+* abuse reports submitted by Scaleway’s abuse partners may be closed automatically after the automated locking of your services, if several complaints were received within the same case, or if Scaleway considers that the type of abuse reported requires immediate locking of your services.
+* cases regarding security holes will be closed automatically. Refer to the description of the abuse in order to find more details on patches and updates available.
+
+
+ Refer to our [abuse notice](https://www.scaleway.com/en/abuse-notice/) for further information about Scaleway’s abuse policy.
+
+
+Abuse tickets are complaints regarding the use of Scaleway Dedibox services for illegal behavior or hosting of illegal content. Abuse tickets for the same issue on the same resource within a given timeframe are grouped by case.
+
+Scaleway’s clients are responsible for taking the appropriate security measures in order to solve the case and prevent any further abuse from their resources in order to avoid the locking of their services.
+
+However, Scaleway reserves the right to immediately suspend the infringing services if it is deemed necessary and proportionate to keep Scaleway’s network safe or to abide by legal requirements.
+
+If you encounter any issue with the resolution of your abuse tickets, please contact the abuse team by opening a [support ticket](https://console.scaleway.com/support/tickets/create) directly from your console.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. Click your username, located next to “logged in as” in the top right corner of the Dedibox console. Then, select **Abuses** from the drop-down menu. A list of your abuse tickets and cases displays.
+2. Click **Details** to view the specifics of the complaint.
+3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue.
+
+ If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/).
+
+ If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly.
+ * For other types of abuse, here are some suggestions to help you to correct them:
+ * Backup all your server data
+ * Check for recent file changes
+ * Check log files on your server
+ * Check your PHP and CGI files for any backdoors
+ * Check if any software you use is vulnerable, and update them
+ * Reinstall your server after backup
+ * Change passwords of your server
+ * Backup your website and your email data
+ * Check for recent files changes, security holes in common CMS you may use (Joomla, SPIP, WordPress…)
+ * Check version in some software you may use on your computer (email client, FTP client)
+ * Change your FTP and email passwords
+ If you do not know how to solve the problem, you can contact our [outsourcing partners(https://www.scaleway.com/en/dedibox/outsourcing/)] or reach out to Scaleway’s abuse team by opening a ticket directly from your Scaleway console account.
+4. The case will be closed at the end of its lifetime by Scaleway’s abuse team, and so will the abuse tickets forming the case.
+ If you receive more abuse reports on the same resource within the case lifetime, it means that you did not take the appropriate measures to prevent further abuse from happening.
+ Therefore, we recommend you take additional actions and contact our support team if you need assistance. Failure to take appropriate measures to solve the case may result in the locking of your service as per our [Terms of Services](https://www.scaleway.com/en/contracts/) and the legal framework in force.
+
+In specific instances, the case will be closed automatically:
+* abuse reports submitted by Scaleway’s abuse partners may be closed automatically after the automated locking of your services, if several complaints were received within the same case, or if Scaleway considers that the type of abuse reported requires immediate locking of your services.
+* cases regarding security holes will be closed automatically. Refer to the description of the abuse in order to find more details on patches and updates available.
+
+
+ Refer to our [abuse notice](https://www.scaleway.com/en/abuse-notice/) for further information about Scaleway’s abuse policy.
+
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/revoke-outsourcing.mdx b/pages/dedibox-account/how-to/revoke-outsourcing.mdx
new file mode 100644
index 0000000000..d089b3c1ba
--- /dev/null
+++ b/pages/dedibox-account/how-to/revoke-outsourcing.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to revoke a Dedibox outsourcing agreement
+ description: Learn how to revoke an existing Scaleway Dedibox outsourcing agreement.
+content:
+ h1: How to revoke a Dedibox outsourcing agreement
+ paragraph: This guide explains how to revoke an existing Scaleway Dedibox outsourcing agreement.
+tags: dedibox, revoke, outsourcing
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+Outsourced services refer to services managed by a different technical contact than the owner of the service. This technical contact, who is another Scaleway Dedibox account holder, can manage these services without requiring full access to the owner's Scaleway Dedibox account.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+### How to revoke an outsourcing agreement
+
+1. Log in to the [Dedibox console](https://console.online.net).
+2. Click your username next to _logged in as_ in the top right corner of the console. Then select **Outsourcing** from the pop-up menu.
+3. On the outsourcing page, navigate to the **Outsourced** tab to view a list of your outsourced services. Select the checkbox next to each service you want to revoke the outsourcing for:
+
+4. Click **Remove selected roles** to confirm and initiate the revocation of outsourcing for the selected services.
+
+ Once you complete these steps, the services will no longer be associated with the outsourced account, and the technical management will revert to the owner of the service.
+
+ Revoking the outsourcing of a service does not cancel its subscription. The service will remain active, but management control will revert to the owner.
+
\ No newline at end of file
diff --git a/pages/dedibox-account/how-to/update-email.mdx b/pages/dedibox-account/how-to/update-email.mdx
new file mode 100644
index 0000000000..4caec247a7
--- /dev/null
+++ b/pages/dedibox-account/how-to/update-email.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to update the email address associated with your account
+ description: This page explains how to update the email address associated with your Scaleway Dedibox account.
+content:
+ h1: How to update the email address associated with your account
+ paragraph: This page explains how to update the email address associated with your Scaleway Dedibox account.
+tags: dedibox update account email
+dates:
+ validation: 2024-08-19
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+Every Scaleway Dedibox account is associated with a specific email address. In the event that your email address undergoes any changes, you have the option to update this information directly within your account settings.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. Then click **Account information** in the pop-up menu. The account information page displays.
+2. Click **Update** next to your email address:
+
+
+ A link will be sent to the email address registered in the account.
+3. Click the link sent to your registered email address, to access the email update form.
+4. Enter your new email address and its confirmation. Then click **Update my mail** to submit.
+
+
+You have now linked your new email address to your Scaleway Dedibox account.
+
+
diff --git a/pages/dedibox-account/how-to/update-password.mdx b/pages/dedibox-account/how-to/update-password.mdx
new file mode 100644
index 0000000000..12fa85b732
--- /dev/null
+++ b/pages/dedibox-account/how-to/update-password.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to update your Dedibox account password
+ description: This page explains how to update the password of your account.
+content:
+ h1: How to update your Dedibox account password
+ paragraph: This page explains how to update the password of your account.
+tags: dedibox account password security
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+For security reasons, we recommend changing your passwords regularly. You can update your Dedibox password anytime from the [Scaleway Dedibox console](https://console.online.net/).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. Click your username, next to _logged in as_, in the top right corner of the console. Then click **Account information** in the pop-up menu. The account information page displays.
+2. Click **Update** next to your (hidden) password:
+
+3. Click the link sent to your registered email address to access the update form.
+4. Enter your current password, your new password, and its confirmation. Click **Update my password** to submit the form.
+
+ Your new password is validated, and you can use it to log in to your Scaleway Dedibox console.
+
+
diff --git a/pages/dedibox-account/how-to/upload-an-ssh-key.mdx b/pages/dedibox-account/how-to/upload-an-ssh-key.mdx
new file mode 100644
index 0000000000..927faa703b
--- /dev/null
+++ b/pages/dedibox-account/how-to/upload-an-ssh-key.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to upload and use an SSH key for Dedibox
+ description: Learn how to upload and use an SSH key for Scaleway Dedibox servers.
+content:
+ h1: How to upload and use an SSH Key for Dedibox
+ paragraph: This guide explains how to upload and use an SSH key for Scaleway Dedibox servers.
+tags: upload, ssh-key, ssh, dedibox
+dates:
+ validation: 2024-08-05
+ posted: 2020-03-12
+categories:
+ - account
+---
+
+SSH keys offer a more secure method of identity authentication on computer systems compared to passwords. Each SSH key comprises a private and a public part, which can be generated on your computer. The public part serves the purpose of passwordless authentication and can be uploaded to the Scaleway Dedibox console and then transferred to your dedicated server during installation.
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+
+1. In the top right corner of the console, click on your username to open the pop-up menu. From there, select **SSH keys**.
+
+ You will be taken to a page displaying all your existing SSH keys (if you have not created any key yet, the list will be empty).
+2. Click **Add SSH key** to open the SSH key form.
+3. Provide a description of your choice (e.g., your computer's name) and paste the public key into the designated field.
+4. Click **Add SSH key** to upload the public key to your Scaleway Dedibox account.
+
+ With the SSH key now uploaded, you can select it during the [Dedibox installation process](/dedicated-servers/how-to/install-a-server/) and use it for authentication on your server.
+
+ If you upload another key or change the existing one, you must manually replace it on your Dedibox. The **keys are transferred from the console to your server solely during installation**.
+
diff --git a/pages/dedibox-account/index.mdx b/pages/dedibox-account/index.mdx
new file mode 100644
index 0000000000..c7647a334f
--- /dev/null
+++ b/pages/dedibox-account/index.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Dedibox - Account Documentation
+ description: Dive into Scaleway Dedibox - Account with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/dedibox-account/quickstart.mdx b/pages/dedibox-account/quickstart.mdx
new file mode 100644
index 0000000000..bcb6e50d9b
--- /dev/null
+++ b/pages/dedibox-account/quickstart.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: Dedibox Account - Quickstart
+ description: Learn how to get started with the Scaleway Dedibox console.
+content:
+ h1: Dedibox Account - Quickstart
+ paragraph: This guide shows you how to get started with the Dedibox console.
+tags: dedibox, account, quickstart
+dates:
+ validation: 2024-08-05
+ posted: 2021-07-13
+categories:
+ - account
+---
+
+[Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) offers high-quality dedicated servers. With almost 20 years of experience, our Dedibox servers are recognized for their extreme reliability and best-in-class redundancy. We manage a continuously growing park of more than 100,000 servers in our data centers in France, Poland, and the Netherlands - offering up to 99.95% SLA.
+
+## How to create a Scaleway Dedibox account
+
+1. Open the [Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) website in a web browser.
+2. Click [Create Dedibox account](https://console.online.net/en/user/subscribe). The subscription form
+3. Fill in all the required information, agree to the terms of service, and click **Create my account**. You will receive an email containing a link to complete your registration.
+4. Click the link in the email to validate your email address and activate your account. The [Dedibox console](https://console.online.net) login screen displays.
+5. Enter your username and password and click **Sign in**.
+
+ You are now connected to the Scaleway Dedibox console and can order your first dedicated server.
+
+## How to add a payment method to your Dedibox account
+
+You will need to add a payment method when ordering your first Dedibox. If you want to add a payment method beforehand, follow these steps:
+
+1. Click on your username in the top right corner of the Dedibox console, then click **Billing** in the pop-up menu. The billing page displays.
+2. Click **Change payment mode**.
+3. Choose your preferred payment method from the list and click **Update payment mode**.
+
+ Some payment methods may not be available for your account.
+
+4. Enter the details of your new payment method and validate.
diff --git a/pages/dedibox-dns/concepts.mdx b/pages/dedibox-dns/concepts.mdx
new file mode 100644
index 0000000000..7b5a083501
--- /dev/null
+++ b/pages/dedibox-dns/concepts.mdx
@@ -0,0 +1,77 @@
+---
+meta:
+ title: Dedibox DNS - Concepts
+ description: This page explains all the concepts related to the Dedibox DNS services
+content:
+ h1: Dedibox DNS - Concepts
+ paragraph: This page explains all the concepts related to DNS
+tags: mx-record txt-record dedibox dns
+dates:
+ validation: 2024-08-19
+categories:
+ - dedibox-network
+---
+
+## Domain Name / Domain
+
+See [Domains](/dedibox-domains/concepts/#domain-name).
+
+## DNS
+
+The **D**omain **N**ame **S**ystem is a name management system for computing devices connected to a network, be it public (Internet) or private. It translates text-based [domain names](/dedibox-domains/concepts/#domain-name) to numerical [IP addresses](#ip-address).
+
+## DNS Delegation
+
+DNS delegation is when a [DNS Name Server](#dns-name-servers) delegates authority over a part of its [namespace](#dns-namespace) to one or more other DNS servers. Delegation can be seen as a pointer to the authoritative name servers for a subdomain. With Dedibox, this can be useful to edit the reverse of IPv4/27 blocks and the IPv6 blocks (/48 - /56 - /64), as that cannot be done directly in the console. You can, alternatively, delegate those subnets to your name servers, who will then take on the task of propagating the DNS reverses of your IPs on the internet.
+
+## DNS Name Servers
+
+A DNS Name Server stores the [DNS Records](#dns-record) for a given domain(s).
+
+## DNS Record
+
+A [DNS](#dns) Record holds information translating a domain or subdomain to an IP address, mail server or other domain/subdomain. DNS records for each [DNS Zone](#dns-zone) are stored within files called [DNS Zone Files](#dns-zone-file). These are hosted on [DNS Name Servers](#dns-name-servers). DNS records act as instructions for the DNS servers, so they know which domain names and IP addresses are associated with each other. DNS records can be of multiple types, called [Resource Records](#resource-records).
+
+## DNS Zone
+
+A DNS zone hosts the [DNS records](#dns-record) for a distinct part of the global domain namespace, and is managed by a specific organization or administrator.
+
+## DNS Zone File
+
+A DNS Zone File describes a [DNS Zone](#dns-zone), containing DNS records which constitute mappings between domain names, IP addresses and other resources.
+
+## DNS Namespace
+
+DNS domains are all organized in a hierarchy called the DNS namespace. The hierarchy consists of:
+
+ - **Top Level Domains**: .com or .net, for example.
+ - **Second-level domains**: example.com
+ - **Subdomains**: mysite.example.com or sub.domain.example.com.
+
+## IP Address
+
+An Internet Protocol address is a unique address that identifies a device on the internet or a local network. Generally, when we talk about IP addresses, we are referring to IPv4 addresses. However, due to the global shortage of IPv4 addresses, IPv6 addresses have also been in deployment since the mid-2000s.
+
+## Resource Records
+
+Information in [DNS zones](#dns-zone) is categorized and organized through a list of [DNS record](#dns-record) types, called Resource Records (RRs). Each of these records has a type, an expiration time (Time to Live - TTL), a name, and type-specific data for certain types of records.
+
+The most common records are:
+
+- **A record**: Address record, it is mostly used to map domain names to the IPv4 address of a specific server
+- **AAAA record**: IPv6 Address record, it returns an IPv6 address and is mostly used to map domain names to the IPv6 address of a specific server.
+- **CNAME record**: Canonical name record, an alias of one name to another. The DNS lookup will continue by looking up the new name.
+- **MX record**: Mail exchange record, it maps a domain name to a list of one or several mail servers for that domain.
+- **TXT record**: Text record, it is often used to carry machine-readable data such as information for automated domain validation.
+
+## Reverse DNS
+
+Reverse DNS, or rDNS, is exactly the opposite of classic [forward DNS](#dns) as we know it. Forward DNS maps a hostname to an IP address. Reverse DNS means we are mapping the IP address to a hostname. This can be very useful, especially if you want to send emails from your server.
+
+## Root Server
+
+Root Servers are a type of [DNS Name Server](#dns-name-servers) pertaining to [Top Level domains](/dedibox-domains/concepts/#tld). They are the first step in the resolution of any domain name, since they contain information about the authoritative DNS servers for each Top Level Domain.
+
+## Secondary DNS
+
+Secondary DNS uses zone transfer to automatically transfer DNS zones from a primary DNS server to a secondary DNS server. The secondary server is useful for redundancy, resiliency, and load balancing. The zone files on a secondary DNS server are read-only copies of the files on the primary server, and are automatically updated if a file changes on the primary server.
\ No newline at end of file
diff --git a/pages/dedibox-dns/how-to/add-dns-delegation.mdx b/pages/dedibox-dns/how-to/add-dns-delegation.mdx
new file mode 100644
index 0000000000..4f39362814
--- /dev/null
+++ b/pages/dedibox-dns/how-to/add-dns-delegation.mdx
@@ -0,0 +1,96 @@
+---
+meta:
+ title: How to add a DNS delegation
+ description: This page explains how to add a DNS delegation to IPv6 and IPv4 on Scaleway Dedibox
+content:
+ h1: How to add a DNS delegation
+ paragraph: This page explains how to add a DNS delegation to IPv6 and IPv4 on Scaleway Dedibox
+tags: dns dedibox delegation IPv6 IPv4
+dates:
+ validation: 2024-08-12
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+You cannot edit the reverse of IPv4 /27 blocks nor the IPv6 blocks (/48 - /56 - /64) directly in the console. Therefore, you will have to delegate your subnet to your nameservers. This will delegate the task of propagating the DNS reverses of your IPs on the internet to your servers. You will need two DNS servers for redundancy and can delegate the subnets directly to your account.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a corresponding **A record** for your reverse DNS at least 24 hours ago
+
+## How to add a DNS delegation in the console
+
+1. From the [console](https://console.online.net), click **Server** in the top menu, then select **Network configuration**.
+
+2. Click the settings icon (cogwheel) next to the relevant IP block, then select **Edit nameserver delegation**. The **Edit nameserver delegation** page displays.
+
+3. Enter details for the two name servers, and click **Update delegation**.
+
+ - You can have a minimum of two and a maximum of five name servers. To add more name servers, use the **Add nameserver** button.
+ - Ensure that your DNS configuration complies with [RFC 4183](https://datatracker.ietf.org/doc/html/rfc4183).
+
+
+ You will need to repeat this for all your /27 IPv4 blocks. For IPv6, once you delegate your /48 all subnets will be automatically configured to the same name servers.
+
+## Example BIND configurations
+
+### IPv4
+
+Here is an example BIND configuration for the block `62.4.10.0/27`:
+
+```
+0-27.10.4.62.in-addr.arpa. 86400 IN SOA ns1.mydns.net. hostmaster.mydns.net. (
+ 2013121407 ; Serial
+ 10800 ; Refresh
+ 1800 ; Retry
+ 604800 ; Expire
+ 86400 ) ; Minimum TTL
+0-27.10.4.62.in-addr.arpa. 86400 IN NS ns1.mydns.net.
+0-27.10.4.62.in-addr.arpa. 86400 IN NS ns2.mydns.net.
+1.0-27.10.4.62.in-addr.arpa. 86400 IN PTR toto.domaine.com.
+```
+
+- The line **SOA** indicates the authoritative server for the IP block,
+- The lines **NS** indicate the propagating DNS servers for the concerned IP block.
+- The lines **PTR** indicate the reverse of the indicated IP, here 62.4.10.1.
+
+
+ If your IP block is a size other than /27, you will need to adapt your configuration accordingly.
+
+
+### IPv6
+
+Here is an example BIND configuration for the zone `001:bc8::3398::/48`:
+
+```
+;
+; 2001:bc8:3398::/48
+;
+;
+$TTL 1h ; Default TTL
+8.9.3.3.8.c.b.0.1.0.0.2.ip6.arpa. IN SOA ns1.domain.fr webmaster.domain.fr (
+ 2016071503 ; serial
+ 1h ; secondary refresh interval
+ 15m ; secondary retry interval
+ 1w ; secondary copy expire time
+ 1h ; NXDOMAIN cache time
+ )
+
+;
+; domain name servers
+;
+@ IN NS ns1.domain.fr.
+@ IN NS ns2.domain.fr.
+
+
+; IPv6 PTR entries
+1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.9.3.3.8.c.b.0.1.0.0.2.ip6.arpa. IN PTR toto.domain.fr.
+```
+
+
+ You can use the utilities available at [whatsmydns.net](https://www.whatsmydns.net/reverse-dns-generator) to facilitate the generation of your zones.
+
+
+
diff --git a/pages/dedibox-dns/how-to/assets/scaleway-dedibox-server-list.webp b/pages/dedibox-dns/how-to/assets/scaleway-dedibox-server-list.webp
new file mode 100644
index 0000000000..d21a3cf8a4
Binary files /dev/null and b/pages/dedibox-dns/how-to/assets/scaleway-dedibox-server-list.webp differ
diff --git a/pages/dedibox-dns/how-to/assets/scaleway-edit-delegation.webp b/pages/dedibox-dns/how-to/assets/scaleway-edit-delegation.webp
new file mode 100644
index 0000000000..bab360413a
Binary files /dev/null and b/pages/dedibox-dns/how-to/assets/scaleway-edit-delegation.webp differ
diff --git a/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-button.webp b/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-button.webp
new file mode 100644
index 0000000000..39c1ec0fd3
Binary files /dev/null and b/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-button.webp differ
diff --git a/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-panel.webp b/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-panel.webp
new file mode 100644
index 0000000000..b982371535
Binary files /dev/null and b/pages/dedibox-dns/how-to/assets/scaleway-edit-reverse-panel.webp differ
diff --git a/pages/dedibox-dns/how-to/configure-reverse-dns.mdx b/pages/dedibox-dns/how-to/configure-reverse-dns.mdx
new file mode 100644
index 0000000000..cd5dcccb75
--- /dev/null
+++ b/pages/dedibox-dns/how-to/configure-reverse-dns.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to configure reverse DNS on Dedibox
+ description: This page explains how to configure reverse DNS on your Scaleway Dedibox server
+content:
+ h1: How to configure reverse DNS on Dedibox
+ paragraph: This page explains how to configure reverse DNS on your Scaleway Dedibox server
+tags: dedibox dns
+dates:
+ validation: 2024-09-30
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+Reverse DNS is the opposite of classic "forward" DNS, and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your server. If you are using the default reverse (`*.poneytelecom.eu`), you may experience problems with deliverability of your mails and during the subscription of certain tools like [JMRP](https://postmaster.live.com/snds/JMRP.aspx).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Created a corresponding **A record** for your reverse DNS at least 24 hours ago
+
+1. From the [console](https://console.online.net), click **Server** in the top menu, then select **Server list**.
+
+2. Click **Manage** next to the relevant server.
+3. Under **Network**, click **Edit Reverses**.
+
+4. Enter the new reverse DNS of your IP (generally this corresponds to your hostname) and click **Update**.
+
+
+ Your reverse DNS is now updated.
+
+
diff --git a/pages/dedibox-dns/how-to/configure-secondary-dns.mdx b/pages/dedibox-dns/how-to/configure-secondary-dns.mdx
new file mode 100644
index 0000000000..1630209731
--- /dev/null
+++ b/pages/dedibox-dns/how-to/configure-secondary-dns.mdx
@@ -0,0 +1,114 @@
+---
+meta:
+ title: How to configure secondary DNS
+ description: This page explains how to configure secondary DNS on your Scaleway Dedibox server
+content:
+ h1: How to configure secondary DNS
+ paragraph: This page explains how to configure secondary DNS on your Scaleway Dedibox server
+tags: dedibox dns
+dates:
+ validation: 2024-09-30
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+Secondary DNS allows you to have your domain's zone file automatically backed up on a second set of name servers. This backup is a read-only copy of the zone file, containing the DNS records.
+
+This how-to assumes that you want to manage your domains exclusively with BIND. It shows you how to configure your Dedibox as your primary DNS and nssec.online.net as your secondary DNS.
+
+
+ Be aware that there is a delay of 24 hours upon completing this procedure before it takes effect.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- Ports 53/TCP and 53/UDP open on your server, enabling it to respond to DNS requests
+- Ownership of a domain name, which is configured on your server with a valid SOA
+
+## How to configure BIND
+
+1. If you use a management panel for your server, add the domain in your panel.
+2. Log in to your server as root [via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh).
+3. Use your favorite text editor to edit the general BIND configuration file, located at `/etc/bind/named.conf`. The configuration of your domain should be as follows (replace `domain.fr` with your domain):
+ ```
+ zone "domain.fr" {
+ type master;
+ notify yes;
+ allow-transfer { 62.210.16.8; };
+ file "/etc/bind/domain.fr.db";
+ };
+ ```
+4. Edit the file pointed to in the configuration carried out in step 3. In this example, you can see that the content of the zone is located in the file `/etc/bind/domain.fr.db`. Use your favorite text editor to edit the file as follows:
+ ```
+ $TTL 86400
+ @ IN SOA sd-xxxx.dedibox.fr. root.domain.fr. (
+ 2006081720
+ 8H
+ 2H
+ 4W
+ 1D )
+ IN NS sd-xxxx.dedibox.fr.
+ IN NS nssec.online.net.
+ IN MX 10 mail.domain.fr.
+
+ domain.fr. A 195.154.xx.xx
+ ns IN A 62.210.xx.xx
+ mail IN A 62.210.xx.xx
+ www CNAME domain.fr.
+ ftp CNAME domain.fr.
+ ```
+
+ Ensure that you do the following:
+ - Replace `domain.fr` with your own domain name.
+ - Replace `sd-xxxx.dedibox.fr` with the name of your Dedibox.
+ - Replace `62.210.xx.xx` with the IP of your Dedibox.
+ - Pay special attention to keep the “.” as they are indicated.
+ - Update the serial number (here `2006081720`) using the format `YearMonthDateNumber`.
+5. Restart BIND for the changes to take effect:
+ ```
+ /etc/init.d/bind9 reload
+ ```
+
+## How to declare the domain name
+
+1. From the [console](https://console.online.net/), click **Server** in the top menu, and select **Server List**.
+2. Click **Manage** next to the relevant server.
+3. Click **Secondary DNS** on the left side menu. The **Create a new entry** form displays.
+4. Enter your domain name, and next to **IP** select your primary DNS server.
+5. Click **Create**.
+
+ The initial installation of a new domain name takes about 24 hours (restart of the server each night at 2:45 CET), and then updates are made according to the “refresh” indicated in the SOA of the primary DNS of your domain.
+
+
+## How to test your domain
+
+[AFNIC](https://www.afnic.fr/) is the association tasked with managing the domain name registry in France. Before you carry out your test:
+ - Wait 24 hours after finishing the configuration steps above.
+ - Remember to create a postmaster mailbox (postmaster@domain.fr) for your domain.
+
+1. Use a zonecheck service such as this one: [https://zonemaster.net/en/](https://zonemaster.net/en/):
+ - In **zone**, enter your domain without www or http
+ - In **primaire**, enter the reverse (sd-xxxx.dedibox.fr) of your server and its IP
+ - In **secondaire** enter nssec.online.net and 62.210.16.8 as the IP
+2. Click **Vérifier!**.
+ - If the test generates errors, correct the problems identified in the error messages.
+ - If the test result is `SUCCÈS`, this means everything is working. You can update the DNS servers of your domain at your registrar.
+
+## How to deal with a failed zone transfer
+
+If the transfer of your zone does not work, it may be that:
+ - Your DNS server does not accept requests of the type AXFR.
+ - You forgot to update the serial of your zone (`YearMonthDayNumber`).
+
+To test the transfer of your zone, authorize the transfer to your personal IP (allow-transfer) and test the transfer from your personal IP, using the following command:
+
+```
+dig @ip_of_my_dedibox mydomain.tld axfr
+```
+
+The serial of your zone **must** be up-to-date (2010112402, for example, for the 2nd modification on 24/11/2010).
+
+
diff --git a/pages/dedibox-dns/how-to/index.mdx b/pages/dedibox-dns/how-to/index.mdx
new file mode 100644
index 0000000000..2154e2bcfb
--- /dev/null
+++ b/pages/dedibox-dns/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: DNS - How Tos
+ description: Dedibox Network DNS How Tos
+content:
+ h1: Dedibox DNS - How Tos
+ paragraph: Dedibox Network DNS How Tos
+---
diff --git a/pages/dedibox-dns/index.mdx b/pages/dedibox-dns/index.mdx
new file mode 100644
index 0000000000..1bdf2512bd
--- /dev/null
+++ b/pages/dedibox-dns/index.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: Dedibox - DNS Documentation
+ description: Dive into Scaleway Dedibox - DNS with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
diff --git a/pages/dedibox-domains/concepts.mdx b/pages/dedibox-domains/concepts.mdx
new file mode 100644
index 0000000000..84cb108c8b
--- /dev/null
+++ b/pages/dedibox-domains/concepts.mdx
@@ -0,0 +1,57 @@
+---
+meta:
+ title: Scaleway Dedibox Domains - Concepts
+ description: This page explains all the concepts related to Scaleway Dedibox Domains
+content:
+ h1: Scaleway Dedibox Domains - Concepts
+ paragraph: This page explains all the concepts related to Scaleway Dedibox Domains
+tags: dedibox domain-name dns-server dns tld dnssec waps authcode
+dates:
+ validation: 2024-08-26
+categories:
+ - dedibox-network
+---
+
+## Domain name
+
+A domain name is a unique alphanumeric name used to identify a computer (web or email server) on the internet. It translates the numeric address of the computer to a more memorable name.
+
+## DNS server
+
+A DNS server is a program that responds to requests for DNS zones configured by the administrator. DNS servers typically operate in pairs, each consisting of a primary and secondary server.
+
+## DNS zone
+
+Computers connected to an IP network, such as the internet, all have a unique IP address.
+These addresses are numeric because it is easier to handle for a machine. With IPv4 these addresses have the form of `xxx.yyy.zzz.aaa`, where `xxx`, `yyy`, `zzz` and `aaa` are four numbers in the range of 0 to 255 (in the decimal system). Whilst these numbers are easy to handle for a computer, it is impossible for a human.
+
+Therefore, a mechanism was deployed to associate an IP address with a more memorable name, called a domain name.
+The DNS zone links these memorable names with their IP addresses.
+If you want to connect to our website **www.scaleway.com**, your computer sends a request to a DNS server, hosting the DNS zone.
+This is a file that has information about the IP addresses linked to a domain name.
+
+## IP address
+
+An Internet Protocol address is a unique address that identifies a device on the internet or a local network. Generally, when we talk about IP addresses, we are referring to IPv4 addresses. However, due to the global shortage of IPv4 addresses, IPv6 addresses have also been in deployment since the mid-2000s.
+
+## TLD
+
+TLD is the acronym used for top-level domains. It is the last segment of a domain name after the final dot. The most common example is `.com`, but there is a whole wide world of different TLDs.
+
+## DNSSEC
+
+DNSSEC cryptographically ensures that DNS content cannot be modified from its source without being detected. It works by digitally signing each DNS record so that any tampering of that record can be detected.
+
+## TLD specifications at Scaleway
+
+Some TLDs have special requirements that can block you from ordering or renewing a domain. Registry may also ask for some verifications.
+
+- **.eu**: the owner's postal address must be located within the European community. Following Brexit, the UK is [no longer considered part of the European community](https://eurid.eu/en/register-a-eu-domain/brexit-notice/).
+- **.be**: your authcode is only available directly from the registry. The phone number must be linked to the country declared in the postal address.
+- **.de**: administrative contact and technical contact must be an individual located within the European community.
+- **.la**: administrative contact and technical contact must be an individual.
+- **.li**: administrative contact and technical contact must be an individual.
+
+## WAPS
+
+WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system introduced by the [ICANN](https://www.icann.org/) to validate the contact information of a domain name. ICANN requires that all registrars validate their identity and keep the domain’s contact information up-to-date.
\ No newline at end of file
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec-ext.webp b/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec-ext.webp
new file mode 100644
index 0000000000..fe51c151c6
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec-ext.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec.webp b/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec.webp
new file mode 100644
index 0000000000..0029114354
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-activate-dnssec.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-authcode.webp b/pages/dedibox-domains/how-to/assets/scaleway-authcode.webp
new file mode 100644
index 0000000000..37205fb3f0
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-authcode.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-change-dns.webp b/pages/dedibox-domains/how-to/assets/scaleway-change-dns.webp
new file mode 100644
index 0000000000..4da2c98188
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-change-dns.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-domain-configure.webp b/pages/dedibox-domains/how-to/assets/scaleway-domain-configure.webp
new file mode 100644
index 0000000000..017e00f0d1
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-domain-configure.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-domain-handles.webp b/pages/dedibox-domains/how-to/assets/scaleway-domain-handles.webp
new file mode 100644
index 0000000000..b4798f4b47
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-domain-handles.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-edit-dns-zone.webp b/pages/dedibox-domains/how-to/assets/scaleway-edit-dns-zone.webp
new file mode 100644
index 0000000000..f66b5a7145
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-edit-dns-zone.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-order-domain-contact.webp b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-contact.webp
new file mode 100644
index 0000000000..ac7d7b5124
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-contact.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-order-domain-hosting.webp b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-hosting.webp
new file mode 100644
index 0000000000..ceee48371c
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-hosting.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-order-domain-summary.webp b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-summary.webp
new file mode 100644
index 0000000000..716f01bed1
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-order-domain-summary.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-order-domain.webp b/pages/dedibox-domains/how-to/assets/scaleway-order-domain.webp
new file mode 100644
index 0000000000..bc98c0a722
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-order-domain.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-renew-domain.webp b/pages/dedibox-domains/how-to/assets/scaleway-renew-domain.webp
new file mode 100644
index 0000000000..7a49408010
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-renew-domain.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-trade-domain-2.webp b/pages/dedibox-domains/how-to/assets/scaleway-trade-domain-2.webp
new file mode 100644
index 0000000000..8817b882a7
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-trade-domain-2.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-trade-domain.webp b/pages/dedibox-domains/how-to/assets/scaleway-trade-domain.webp
new file mode 100644
index 0000000000..db8654c491
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-trade-domain.webp differ
diff --git a/pages/dedibox-domains/how-to/assets/scaleway-transfer-domain.webp b/pages/dedibox-domains/how-to/assets/scaleway-transfer-domain.webp
new file mode 100644
index 0000000000..20f98eecf6
Binary files /dev/null and b/pages/dedibox-domains/how-to/assets/scaleway-transfer-domain.webp differ
diff --git a/pages/dedibox-domains/how-to/change-ownership.mdx b/pages/dedibox-domains/how-to/change-ownership.mdx
new file mode 100644
index 0000000000..551ece1775
--- /dev/null
+++ b/pages/dedibox-domains/how-to/change-ownership.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: How to change the ownership of a domain name
+ description: This page explains how to change the ownership of a domain name at Scaleway Dedibox
+content:
+ h1: How to change the ownership of a domain name
+ paragraph: This page explains how to change the ownership of a domain name at Scaleway Dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+You must always keep the contact details relating to the owner of your domain name accurate and up to date. This can be done by [following the instructions here](/dedibox-domains/how-to/file-contact-info/). If you wish to change details about the owner’s identity, such as full name(s) or corporate name, this must be done by the change of ownership process described below.
+
+
+Before changing the ownership of the domain, you must [ensure that all contact email addresses of the domain are up to date](#how-to-check-and-update-the-contact-email).
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A Scaleway domain you want to transfer to a new owner, who must have [created a Dedibox account](/dedibox-account/how-to/create-a-dedibox-account/)
+
+## How to check and update the contact email
+
+1. From the console, click **Domain** near the top right of the screen.
+2. Click **Configure domain name** next to the relevant domain.
+3. Click the link next to **Handle**. You are directed to the contact details page.
+4. Check the details (particularly the email address), rectifying any that are incorrect.
+5. Ensure the **anti spam** feature is set to **Inactive**.
+6. If you have made changes, scroll to the bottom of the page and click **Update handle data**.
+
+## How to change the ownership of a domain
+
+1. From the console, click **Domain** at the top right of the screen.
+2. Click **Trades**. Trading is the procedure that allows you to change the ownership of a domain.
+
+3. Click **Initiate a domain trade**.
+4. Select the relevant domain name and click **Order**.
+5. Select the account of the new owner, searching for it via the account login if necessary, and click **Confirm**.
+
+6. Create a handle for the new owner, including all their contact details, and click **Confirm**.
+7. Confirm the ownership trade and pay the administrative fee.
+8. For the extensions `.fr`, `.eu`, and `.be`, emails will be sent to both the old and new owners of the domain. Both parties are required to validate the trade by clicking the enclosed link. Without this action, the change of ownership will not be validated.
+
+ The validation link you will receive by email is valid for one month. To obtain a new validation link, you will need to restart the ownership change process, which leads to an administrative fee.
+
+ For the extensions `.com`, `.net` and `.org`, the validation is done directly once your change of ownership request is confirmed.
+You can check if the change of ownership was successful on [Who.is](http://who.is/).
+
+
diff --git a/pages/dedibox-domains/how-to/enable-dnssec.mdx b/pages/dedibox-domains/how-to/enable-dnssec.mdx
new file mode 100644
index 0000000000..ad96698e71
--- /dev/null
+++ b/pages/dedibox-domains/how-to/enable-dnssec.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: How to enable DNSSEC
+ description: This page explains how to enable DNSSEC for domains at Scaleway Dedibox
+content:
+ h1: How to enable DNSSEC
+ paragraph: This page explains how to enable DNSSEC for domains at Scaleway Dedibox
+tags: dedibox dnssec domain
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+Since its design in 1983, DNS has been vulnerable to attacks. Attackers can falsify responses to DNS queries, which allows them to redirect end users to websites under their control. In response to these threats, [DNSSEC](https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en) was deployed. DNSSEC cryptographically ensures that DNS content cannot be modified from its source without being detected. It works by digitally signing each DNS record so that any tampering of that record can be detected.
+
+DNSSEC therefore involves:
+
+ - the domain's DNS server
+ - the registrar
+ - the registry
+ - the provider's DNS server
+
+DNSSEC should only be used by experienced users, due to the propagation time of the DNS cache. If you do want to configure DNSSEC yourself, bear in mind that:
+
+ - You should always use external tools such as https://dnssec-analyzer.verisignlabs.com/ or http://dnsviz.net/
+ - Not all registries support the same algorithms
+ - Not all DNS servers (clients) verify DNSSEC, you can achieve responses on them despite bad DNSSEC configuration
+
+
+ This page shows you how to enable DNSSEC for **Online.net domains only**. Find out how to enable DNSSEC for Domains and DNS domains via [the API](https://www.scaleway.com/en/developers/api/domains-and-dns/registrar-api/#path-domains-update-domain-dnssec) or the [Scaleway console](/domains-and-dns/how-to/configure-dnssec-internal-domain/).
+
+
+
+
+- A Dedibox account logged in to the [Online console](https://console.online.net)
+- An Online domain name
+
+## How to activate and deactivate DNSSEC if your domain and DNS are managed by Scaleway
+
+Although DNSSEC should generally only be configured by experienced users, this simple activation/deactivation is easy to carry out.
+
+1. Log in to the [Online console](https://console.online.net).
+2. Click **Domain**. A list of your domains displays.
+
+3. Click **Configure domain name** next to the relevant domain.
+4. Click the **Activate DNSSEC** button to activate DNSSEC, if allowed by your domain extension. If DNSSEC is already activated, the **Deactivate DNSSEC** button displays, allowing you to deactivate it if you wish.
+
+ If you deactivate DNSSEC, it is advised to wait 48 hours before activating it again.
+
+
+## How to activate and deactivate DNSSEC if your domain is managed by Scaleway with your own DNS server
+
+1. Log in to the [Online console](https://console.online.net).
+2. Click **Domain**. A list of your domains displays.
+3. Click **Configure domain name** next to the relevant domain.
+4. Click the **Manage DNSSEC** tab.
+
+5. Depending on whether you want to activate or deactivate DNSSEC:
+ - **Activation**: A key is generated for you. Complete the rest of the configuration fields, and click **Update DNS Records** to transfer them to the registrar. In case of error, you can modify this information at a later date.
+ - **Deactivation**: Click **Delete DNS Records** to request deletion from the registry. You will then need to delete the records from the DNS server yourself.
+
+
diff --git a/pages/dedibox-domains/how-to/file-contact-info.mdx b/pages/dedibox-domains/how-to/file-contact-info.mdx
new file mode 100644
index 0000000000..dbe6033e6d
--- /dev/null
+++ b/pages/dedibox-domains/how-to/file-contact-info.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to file contact information
+ description: This page explains how to file contact information for a domain at Scaleway Dedibox
+content:
+ h1: How to file contact information
+ paragraph: This page explains how to file contact information for a domain at Scaleway Dedibox
+tags: dedibox contact-information domain
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+You must always ensure that the contact information for the domain owner is accurate and correct. You are prompted to provide and/or check contact details when you are ordering or renewing your domain. It is your responsibility to keep this information up-to-date after that. This document shows you how to check and modify this information.
+
+
+ If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade).
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A domain registered with Scaleway
+
+1. From the [Dedibox console](https://console.online.net), click **Domain**. A list of your domains displays.
+2. Click the **Domain handles** tab. A list of all your handles and their associated domains displays.
+
+3. Click **Edit** next to the handle whose contact details you wish to edit.
+4. Check and update the contact details as necessary, then click **Update handle data** at the bottom of the page.
+
+
diff --git a/pages/dedibox-domains/how-to/index.mdx b/pages/dedibox-domains/how-to/index.mdx
new file mode 100644
index 0000000000..43f083ef2b
--- /dev/null
+++ b/pages/dedibox-domains/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Domains - How Tos
+ description: Domains How Tos
+content:
+ h1: Domains - How Tos
+ paragraph: Domains How Tos
+---
diff --git a/pages/dedibox-domains/how-to/manage-dns-servers.mdx b/pages/dedibox-domains/how-to/manage-dns-servers.mdx
new file mode 100644
index 0000000000..401f8355ec
--- /dev/null
+++ b/pages/dedibox-domains/how-to/manage-dns-servers.mdx
@@ -0,0 +1,85 @@
+---
+meta:
+ title: How to manage a domain's DNS servers
+ description: This page explains how to manage a domain's DNS servers at Scaleway Dedibox
+content:
+ h1: How to manage a domain's DNS servers
+ paragraph: This page explains how to manage a domain's DNS server at Scaleway Dedibox
+tags: domain dns-server dns dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+A DNS server is a program that responds to requests for DNS zones configured by the administrator. DNS servers typically operate in pairs, each consisting of a primary and secondary server.
+
+Scaleway Dedibox's DNS servers are as follows:
+
+ * Primary server: ns0.online.net (`195.154.228.249`)
+ * Secondary server: ns1.online.net (`62.210.16.9`)
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A domain name
+
+## How to find the nameservers and the registrar of your domain
+
+1. Go to [http://who.is](http://who.is).
+2. Enter your domain name in the format **yourdomain.ext** (no www).
+3. In the results, look at the **Registrar Info** and **Name Servers**.
+
+## How to configure Dedibox DNS servers for your domain
+
+### If you ordered your domain name with Scaleway
+
+If you ordered your domain name with Scaleway, your domain automatically configures to our DNS servers. No further action is required from you.
+
+### If your domain name is registered elsewhere
+
+You can still use your Dedibox web hosting, and ask your registrar to change your domain’s DNS zones.
+
+#### For a WEB offer
+
+For the website (depending on your choice):
+```
+"A"-Record: 62.210.16.61
+"A"-Record: 62.210.16.62
+```
+
+For email:
+```
+"MX"-Record, Priority "10": mx.online.net
+"MX"-Record, Priority "20": mx-cache.online.net
+```
+
+#### For a CLOUD offer
+
+[Open a support ticket](https://console.online.net/en/assistance/ticket) to ask for the required information.
+
+## How to change your DNS servers
+
+
+ Changing DNS servers or zones must be done by experts.
+
+ We do not provide support for Scaleway webhostings and domain names if the DNS servers have been modified by the user.
+
+
+1. From the [Dedibox console](https://console.online.net), click **Domain**. A list of your domains displays.
+2. Click **Configure domain name** next to the relevant domain.
+
+3. Click the **Manage DNS servers** tab.
+
+4. Modify the DNS servers to your requirements.
+
+ The DNS zone must be configured on the new server before the change in the console.
+ If you have an error such as “SOA not found”, we invite you to check this with your provider.
+
+
+
diff --git a/pages/dedibox-domains/how-to/manage-dns-zones.mdx b/pages/dedibox-domains/how-to/manage-dns-zones.mdx
new file mode 100644
index 0000000000..8684e7bef9
--- /dev/null
+++ b/pages/dedibox-domains/how-to/manage-dns-zones.mdx
@@ -0,0 +1,100 @@
+---
+meta:
+ title: How to manage a domain's DNS zones
+ description: This page explains how to manage a domain's DNS zones at Scaleway Dedibox
+content:
+ h1: How to manage a domain's DNS zones
+ paragraph: This page explains how to manage a domain's DNS zones at Scaleway Dedibox
+tags: dedibox domain dns dns-zone
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+The [DNS zone](/dedibox-domains/concepts/#dns-zone) is the roadmap of the domain name and contains all the required information to operate it on the internet.
+
+For example, **A** records indicate where to find the website and **MX** records indicate where emails should be sent.
+
+This document shows you how to manage your domain's DNS zones.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A domain name
+
+## How to understand DNS records/entries
+
+The most common types of DNS entries are as follows:
+
+| Type | Description |
+| ----------- | --------------- |
+| **A** | Allows you to link a domain name with an IP address (IPv4) (`www.online.net.` IN A 212.27.35.195). |
+| **AAAA** | Allows you to link a domain name with an IP address (IPv6) (irc.online.net. IN AAAA 2a01:e0b:1:f:2d0:b7ff:fea9:4da8). |
+| **CNAME** | Allows the mapping between a DNS name and another DNS name (sql.domain.ext. IN CNAME mysql1.online.net.). |
+| **MX** | Allows to set the responsible mail server for a domain (online.net. IN mx.online.net.). The DNS name MUST be an IPv4 and can not be an IP address or a CNAME. Priority defines the time in which the servers are contacted if there are more than one. |
+| **TXT** | This record can store a string of 1024 characters. |
+| **SRV** | This registration enables automatic discovery services. This type of record is reserved for expert users only. |
+
+
+ - DNS zone modifications should be done **exclusively by experts**.
+ - Errors in the configuration of a DNS zone may lead to the unavailability of your website or emails.
+ - We do not provide support for web hostings or domain names with DNS zones modified by the user.
+
+
+## How to manage your DNS zones
+
+You can manage multiple versions of your DNS zones at Scaleway.
+
+Each modification on an existing DNS zone will launch the creation of a new temporary zone. Once you have finished your modifications, you will be able to create a permanent zone from the temporary zone and to set it as active to allow its usage on the internet.
+
+1. From the [Dedibox console](https://console.online.net), click **Domain**. A list of your domains displays.
+2. Click **Configure domain name** next to the relevant domain.
+
+3. Click the **Edit DNS zone** tab.
+
+4. Note the following parts of the interface:
+ - At the top of the screen, the **Select a zone version** drop-down menu lets you navigate between your different zone versions to modify them and set them as active.
+ - The pen icon next to the zone name in the **Active Version** panel lets you manage the zone's options. Click the pen to edit the zone name or set it as active.
+ - The list of zone entries in the lower part of the screen lets you add, modify or delete DNS entries in your zone.
+
+## How to modify a DNS zone
+
+1. From the **Edit DNS zone** tab, make your changes (eg adding or deleting an entry) in the current zone shown to you.
+2. Click **Create a new version**.
+3. Click **Set as active** and wait for propagation of the zone.
+
+ * **Provisioning time**: The provisioning of your DNS zone on the Dedibox side is done instantly. If you want to verify that your changes have been taken into account, you can directly query the servers `ns0.online.net` and `ns1.online.net`.
+ * **Propagation time**: The time it takes to propagate a DNS zone depends on the TTL (or Time To Live). This is the default refresh information during which other DNS servers on the internet keep the information about your DNS zone in their cache. By default, this value is 24 hours (86400 seconds). You can edit the TTL to your convenience, knowing that the new TTL will not be applied until the next reload, at the end of the current TTL. On the internet it is generally recommended to set a minimum TTL of one hour (3600 seconds). Many DNS servers will not respect your values if your TTL is below that value.
+
+
+## How to use BIND configuration mode (Advanced)
+
+To facilitate the management of your zones, reserved for experts, we provide you with the option of sending and downloading your DNS zone in the BIND format. This is the format mostly used for the configuration of a BIND DNS Server, and allows you to re-import your zones if they were previously in this format, or if you are used to it.
+
+1. From the **Edit DNS zone** tab, click the arrow in the middle panel next to **Open BIND file options**.
+2. Enter the desired content in the text box that displays. Alternatively, if you want to recover your current zone, click the **Download** button.
+
+ Here is an example of a DNS zone in the BIND format:
+
+ ```
+ ;; Zone dump from zone version "Zone 1"
+ $ORIGIN mutu-essentiel.com.
+ @ 3600 IN SOA ns0.online.net. hostmaster.online.net. 20170209060437 10800 3600 604800 3600
+ @ 86400 IN A 212.47.231.228
+ * 86400 IN CNAME pf114.mutu-perf.online.net.
+ @ 86400 IN MX 10 mxproxy-1.cloud.online.net.
+ @ 86400 IN MX 20 mxproxy-2.cloud.online.net.
+ autoconfig 86400 IN CNAME mail-autoconfig.cloud.online.net.
+ @ 86400 IN TXT "v=spf1 include:spf.online.net ?all"
+ db93577 86400 IN CNAME pf114.mutu-perf.online.net.
+ phpmyadmin 14400 IN CNAME pf114.mutu-perf.online.net.
+ ```
+3. Click **Submit your zone**.
+
+
diff --git a/pages/dedibox-domains/how-to/purchase-domain.mdx b/pages/dedibox-domains/how-to/purchase-domain.mdx
new file mode 100644
index 0000000000..3c695068f1
--- /dev/null
+++ b/pages/dedibox-domains/how-to/purchase-domain.mdx
@@ -0,0 +1,56 @@
+---
+meta:
+ title: How to buy a domain name at Scaleway
+ description: This page explains how to buy a domain name at Scaleway Dedibox
+content:
+ h1: How to buy a domain name
+ paragraph: This page explains how to buy a domain name at Scaleway Dedibox
+tags: dedibox domain domain-name
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+A domain name is the equivalent of your postal address on the web, and allows your users to find your website. Scaleway offers you the possibility of buying a domain name with or without web hosting. Depending on availability, you can buy the domain name and extension (.com, .fr, .net etc.) of your choice.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+1. In your browser, navigate to [the domain name order page](https://www.scaleway.com/en/domain/).
+
+2. Enter the domain name of your choice in the search bar and click **search a domain**. The **Domain name choice** page displays, showing whether the domain is available and for which extensions.
+
+ If the domain name is not available because you are already the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-domains/how-to/transfer-domain/) for more information.
+
+3. Select an available domain-name/extension combination from the list by clicking the checkbox next to it.
+
+ Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-domains/concepts/#tld-specifications-at-scaleway).
+
+4. Scroll to the bottom of the page and click **Order**. The **Hosting** page displays.
+5. Select a web hosting package, or choose to proceed with no hosting. You can additionally choose to add a hosting backup if you wish.
+
+ If you purchase web hosting, you get your domain name for free with purchase/renewal.
+
+6. Scroll down to the bottom of the page and click **Order**.
+7. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays.
+8. Select the domain owner from your existing contacts, or choose to create a new contact.
+
+
+
+ You must always keep the contact details relating to the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade).
+
+9. Scroll down to the bottom of the page and click **Confirm**.
+
+ If you chose to create a new contact, you will be required to enter their details. Do so, and click **Create Handle**. Once completed, the **Summary** page displays.
+10. Check the summary of your order and select a payment mode from the drop-down menu. You must also agree to the terms of service and web hosting specific terms, and choose whether to activate automatic renewal of your domain.
+
+11. Scroll down to the bottom of the page and click **Confirm my command**. You are redirected to the payment gateway to complete your payment.
+
+
diff --git a/pages/dedibox-domains/how-to/renew-domain.mdx b/pages/dedibox-domains/how-to/renew-domain.mdx
new file mode 100644
index 0000000000..af51781703
--- /dev/null
+++ b/pages/dedibox-domains/how-to/renew-domain.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to renew a domain name
+ description: This page explains how to renew a domain name at Scaleway Dedibox
+content:
+ h1: How to renew a domain name
+ paragraph: This page explains how to renew a domain name at Scaleway Dedibox
+tags: dedibox domain-name domain
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+When you buy a domain name, you can use it for the period of time you registered it for, which is typically from one to ten years. When this period is nearing its end, you must renew your domain if you wish to keep using it.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A domain registered with Scaleway
+
+1. In your browser, navigate to [the domain name renewal page](https://console.online.net/en/order/renew). A list of your hosting packages and domain names displays.
+
+2. Select the domain name you want to renew, select a renewal period, and click **Renew**. You are directed to the Summary page.
+3. Check the summary of your renewal order and select your payment mode from the drop-down list. Agree to the terms and conditions, and click **Confirm my order**.
+
+ You can also choose to activate automatic renewal of your web hosting and domain names. To do so, check the **Activate automatic renewal** box on the Summary page. Your services automatically renew 62 days before their expiry dates. As such, automatic renewal can only be activated 62 days before the expiration date of the service.
+
+
+ You are redirected to the payment gateway to complete your payment.
+
+
diff --git a/pages/dedibox-domains/how-to/transfer-domain.mdx b/pages/dedibox-domains/how-to/transfer-domain.mdx
new file mode 100644
index 0000000000..bda84135ed
--- /dev/null
+++ b/pages/dedibox-domains/how-to/transfer-domain.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to transfer a domain name
+ description: This page explains how to transfer a domain name at Scaleway Dedibox
+content:
+ h1: How to transfer a domain name
+ paragraph: This page explains how to transfer a domain name at Scaleway Dedibox
+tags: dedibox domain transfer domain-name authcode antispam
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+You can transfer any domain bought or renewed at another registrar to Scaleway as long as you meet the conditions shown below.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- An unlocked domain at an external registrar (not Scaleway) and access to its authorization key
+- A domain name that:
+ - Has at least 15 days until its expiration
+ - Was created at least 60 days ago or renewed at least 45 days ago
+- Up-to-date contact information with your current registrar
+- A domain that is not a premium domain
+- An email address provided in the whois of the domain that is not protected with an antispam
+
+1. In your browser, navigate to [the Scaleway domain name order page](https://www.scaleway.com/en/domain/).
+2. Enter your domain name in the search bar, and click **search a domain**. The **Domain name choice** page displays, showing that the domain is not available for buy.
+
+3. Scroll to the **Are you the owner of this domain name?** section, and under **Transfer**, click **Transfer yourdomain.ext**. You are directed to the transfer form.
+
+4. Enter the Authcode provided by your current registrar (if it is required: this depends on the domain extension).
+
+ By default, Scaleway's DNS servers are not activated after the transfer. However, you can choose to activate these by ticking the box if you wish.
+
+5. Read the information about the conditions of the transfer, and click **Confirm** to state that you comply with them. You are directed to the hosting page.
+6. Select a hosting package, or click **No hosting**. You can also add a hosting backup, if you wish.
+
+ If you buy web hosting, you get your domain name for free with your order or renewal.
+
+7. Scroll down to the bottom of the page and click **Order**.
+8. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays.
+9. Complete the contact information for the domain name.
+
+ You must always keep the domain owner’s contact details accurate and up-to-date. If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade).
+
+10. Scroll down to the bottom of the page and click **Confirm**. The **Summary** page displays.
+11. Check the summary of your order and select a payment mode from the drop-down menu. You must also agree to the terms of service as well as the web hosting specific terms, and choose whether to activate automatic renewal of your domain.
+12. Scroll down to the bottom of the page and click **Confirm my command**. You are redirected to the payment gateway to complete your payment.
+
+ You will generally receive one or more emails to confirm the transfer. However, since the General Data Protection Regulation (GDPR) came into force, it is possible that the process will be completed without the use of email. This depends on your registrar and registry. If you receive no email, the transfer will be validated after 14 days.
+
+
+
diff --git a/pages/dedibox-domains/how-to/validate-waps-info.mdx b/pages/dedibox-domains/how-to/validate-waps-info.mdx
new file mode 100644
index 0000000000..cdf78ea154
--- /dev/null
+++ b/pages/dedibox-domains/how-to/validate-waps-info.mdx
@@ -0,0 +1,77 @@
+---
+meta:
+ title: How to validate WAPS information
+ description: This page explains how to validate WAPS information at Scaleway Dedibox
+content:
+ h1: How to validate WAPS information
+ paragraph: This page explains how to validate WAPS information at Scaleway Dedibox
+tags: dedibox waps
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system introduced by the [ICANN](https://www.icann.org/) to validate the contact information of a domain name. ICANN requires that all registrars validate the identity and the continuity of the information entered in the contact of a domain name in order to have up-to-date information about the owners.
+
+Domain owners are responsible for the use of their domain.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A domain registered with Scaleway
+
+1. Scaleway validates the information by sending an email to the owner's email address:
+ ```
+ Hello,
+
+ You received this message because you are the current owner of
+ domain names.
+
+ As part of a mandatory process that is required by ICANN,
+ we need to verify if your e-mail address is still being used as a domain name holder once a year and for each modification
+ of your e-mail validity use as a domain name holder.
+
+ WARNING: Without a response from your end within 15 days, the verification fails and your domain names may get suspended.
+ fail and you risk the suspension of domain names.
+
+ You have 15 days to confirm your e-mail address
+ by simply clicking the following link.
+
+ http://registrar.online.net/waps.cgi?
+
+ We remind you the information when opening your account:
+
+ Your e-mail : xxxxxxxx@yyyyyyy.com
+ Your telephone : +33.xxxxxxxxxx
+
+ This procedure is about the following domain names:
+
+ xxxxxx.com
+
+ If you have questions about this process you can contact our
+ helpdesk team at https://console.online.net/en/assistance/commercial
+ but do not reply to this message. Messages received to this
+ address are not read and therefore receive no answer
+
+ --
+ https://console.online.net
+ ```
+2. Click on the link in the email within 15 days to confirm that your email address is valid.
+
+ If you do not carry out this validation, you will not be able to renew your domain name. You may end up with a renewed hosting package, and no domain name. Since the domain is not renewed and no longer responds correctly on the Internet, the site will not be available.
+
+
+
+ If you are expecting a validation email (e.g. if you have modified your domain owner's contact information) but cannot find the email, try the following steps:
+ - Check your spam folder.
+ - Check and update, if necessary, the email address of your domain name contact from the [console](https://console.online.net/).
+ - [Open a ticket](https://console.online.net/en/assistance/ticket) They will be able to check to which address the validation email has been sent and whether it has been validated.
+
+
+
diff --git a/pages/dedibox-domains/index.mdx b/pages/dedibox-domains/index.mdx
new file mode 100644
index 0000000000..67a6b658e9
--- /dev/null
+++ b/pages/dedibox-domains/index.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: Dedibox - Domains Documentation
+ description: Dive into Scaleway Dedibox - Domains with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+
diff --git a/pages/dedibox-domains/quickstart.mdx b/pages/dedibox-domains/quickstart.mdx
new file mode 100644
index 0000000000..566109a258
--- /dev/null
+++ b/pages/dedibox-domains/quickstart.mdx
@@ -0,0 +1,105 @@
+---
+meta:
+ title: Domains - Quickstart
+ description: This page shows you how to get started with Scaleway Dedibox Domains.
+content:
+ h1: Domains - Quickstart
+ paragraph: This page shows you how to get started with Scaleway Dedibox Domains.
+tags: dedibox domains domain waps whois
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+
+ This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service.
+
+
+A domain name is the equivalent of your postal address on the web, and allows your users to find your website. Scaleway offers you the possibility of purchasing a domain name with or without web hosting. Depending on availability, you can buy the domain name and extension (`.com`, `.fr`, `.net`, etc.) of your choice.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+## How to buy a domain
+
+1. Click **DNS** in the **Network** section of the console side menu to access the [domain name order page](https://www.scaleway.com/en/domain/).
+2. Enter the domain name of your choice in the search bar, and click **search a domain**. The **Domain name choice** page displays, showing whether the domain is available, and for which extensions.
+
+ If the domain name is not available because you already are the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-domains/how-to/transfer-domain/) for more information.
+
+3. Select an available domain-name/extension combination from the list by clicking the checkbox next to it.
+
+ Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-domains/concepts/#tld-specifications-at-scaleway).
+
+4. Scroll to the bottom of the page and click **Order**. The **Hosting** page displays.
+5. Select a web hosting package, or choose to proceed with no hosting. You can additionally choose to add a hosting backup if you wish.
+
+ If you buy web hosting, you get your domain name for free with your order or renewal.
+
+6. Scroll down to the bottom of the page and click **Order**.
+7. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays.
+8. Select the domain owner from your existing contacts, or choose to create a new contact.
+
+ You must always keep the contact details regarding the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade).
+
+9. Scroll down to the bottom of the page and click **Confirm**.
+
+ If you chose to create a new contact, you will be required to enter their details. Do so, and click **Create Handle**. Once completed, the **Summary** page displays.
+
+10. Check the summary of your order and select a payment mode from the drop-down menu. You must also agree to the terms of service and web hosting specific terms, and choose whether to activate automatic renewal of your domain.
+11. Scroll down to the bottom of the page and click **Confirm my command**. You are redirected to the payment gateway to complete your payment.
+
+## How to validate WAPS information
+
+WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system introduced by the [ICANN](https://www.icann.org/) to validate the contact information of a domain name. ICANN requires that all registrars validate the identity and the continuity of the information entered in the contact of a domain name in order to have up-to-date information about the owners.
+
+1. Scaleway validates the information by sending an email to the owner's email address:
+ ```
+ Hello,
+
+ You received this message because you are the current owner of
+ domain names.
+
+ As part of a mandatory process that is required by ICANN,
+ we need to verify if your e-mail address is still being used as a domain name holder once a year and for each modification.
+ of your e-mail validity use as a domain name holder.
+
+ WARNING: Without a response from your end within 15 days the verification fails and your domain names may get suspended.
+ fail and you risk the suspension of domain names.
+
+ You have 15 days to verify your e-mail address
+ by simply clicking the following link.
+
+ http://registrar.online.net/waps.cgi?
+
+ We remind you the information when opening your account:
+
+ Your e-mail : xxxxxxxx@yyyyyyy.com
+ Your telephone : +33.xxxxxxxxxx
+
+ This procedure is about the following domain names:
+
+ xxxxxx.com
+
+ If you have questions about this process you can contact our
+ helpdesk team at https://console.online.net/en/assistance/commercial
+ but do not reply to this message. Messages received to this
+ address are not read and therefore receive no answer
+
+ --
+ https://console.online.net
+ ```
+2. Click on the link in the email within 15 days to confirm that your email address is valid.
+
+ If you do not carry out this validation, you will not be able to renew your domain name. You may end up with a renewed hosting package, and no domain name. Since the domain is not renewed and no longer responds correctly on the Internet, the site will not be available.
+
+
+
+ If you are expecting a validation email (e.g. if you have modified your domain owner's contact information) but cannot find the email, try the following steps:
+ - Check your spam folder
+ - Check and update, if necessary, the email address of your domain name contact from the [console](https://console.online.net/).
+ - [Open a ticket](https://console.online.net/en/assistance/ticket) or contact the support team directly. They will be able to check to which address the validation email has been sent and whether it has been validated.
+
\ No newline at end of file
diff --git a/pages/dedibox-hardware/concepts.mdx b/pages/dedibox-hardware/concepts.mdx
new file mode 100644
index 0000000000..ca5bc89c27
--- /dev/null
+++ b/pages/dedibox-hardware/concepts.mdx
@@ -0,0 +1,48 @@
+---
+meta:
+ title: Hardware - Concepts
+ description: This page explains all the concepts related to your servers Hardware
+content:
+ h1: Hardware - Concepts
+ paragraph: This page explains all the concepts related to your servers Hardware
+tags: dedibox hardware cpu hdd nvme ssd raid raid 0 raid-0 raid 1 raid-1 raid-5
+dates:
+ validation: 2024-09-02
+categories:
+ - dedibox-servers
+---
+
+## CPU
+
+A Central Processing Unit (CPU) is the computer's main processor. The CPU executes instructions comprising a computer program. The choice for a specific CPU depends on your product's computing requirements.
+
+## HDD
+
+A Hard disk drive (HDD) uses rotating magnetic disks to store data. HDDs provide larger storage capacity but slower read/write speed compared to SSDs. They are perfect for storing large volumes of data.
+
+## NVMe
+
+NVM Express (NVMe) disks are SSDs that use the PCI Express bus for communication with the host.
+
+## SSD
+
+A Solid state disk (SSD) uses flash memory to store your data. Since there are no rotating parts, they provide faster read/write speed than HDDs.
+
+## RAID
+
+RAID is a data storage technology used for data redundancy, performance improvement, or both by combining multiple physical hard drives into one or more logical drives.
+
+The different RAID schemes are referenced as levels and are named by the word RAID itself, followed by a number (For example, [RAID 0](#raid-0), [RAID 1](#raid-1) or [RAID 5](#raid-5)). Depending on the RAID level, data is distributed and stored across the disks in one or several ways.
+
+## RAID 0
+
+RAID 0 uses [data striping](https://en.wikipedia.org/wiki/Data_striping). This increases the storage capacity of the virtual disk to the sum of all available disks in the RAID. The write and read performances of the machine are increased in RAID 0 to concurrent read and write operations. There is zero fault tolerance in RAID 0, as the contents of each file are distributed among all disks in the set, the failure of any single disk in the RAID array causes the entire RAID 0 volume to break down.
+The minimum number of disks in a RAID 0 set is two.
+
+## RAID 1
+
+RAID 1 uses [disk mirroring](https://en.wikipedia.org/wiki/Disk_mirroring), meaning data is written identically to any of the two disks in the set. File requests are broadcasted to any drive in the array and can be served by the drive that accesses the data at first, improving read performance. Write performance can be slower than using a single drive, as any write request has to be sent to all drives in the set, limiting write performances to the speed of the slowest disk. A fault tolerance is provided using this RAID level, as data can be restored from the second disk in case one disk fails. The minimum number of disks available in a RAID 1 set is two, and the number can be increased in odd pairs (For example, 2, 4, 6, …).
+
+## RAID 5
+
+RAID 5 uses block-level [data striping](https://en.wikipedia.org/wiki/Data_striping) with distributed [parity](https://en.wikipedia.org/wiki/Parity_drive). This means parity information is distributed among all available drives, resulting in a fault tolerance where all drives but one need to be present to operate. If a single drive fails, subsequent reads can be calculated from the distributed parity available on the other drives, so that no data is lost. This RAID level requires a minimum of three disks in the set, and the total available space of the virtual disk is the sum of all drives minus one.
\ No newline at end of file
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_01.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_01.webp
new file mode 100644
index 0000000000..4d10c85797
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_01.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_02.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_02.webp
new file mode 100644
index 0000000000..928ccd17a4
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_02.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_03.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_03.webp
new file mode 100644
index 0000000000..8970bc3774
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_03.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_04.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_04.webp
new file mode 100644
index 0000000000..e81f6ebe4c
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_04.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_05.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_05.webp
new file mode 100644
index 0000000000..a099742c34
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_05.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_06.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_06.webp
new file mode 100644
index 0000000000..b89627bcd1
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_06.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h200_enter_config.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h200_enter_config.webp
new file mode 100644
index 0000000000..4171c9ce5e
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h200_enter_config.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_01.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_01.webp
new file mode 100644
index 0000000000..42a7b3b25a
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_01.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_02.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_02.webp
new file mode 100644
index 0000000000..a3c371f6b5
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_02.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_03.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_03.webp
new file mode 100644
index 0000000000..e0449d9932
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_03.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_04.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_04.webp
new file mode 100644
index 0000000000..121e55eea1
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_04.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_05.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_05.webp
new file mode 100644
index 0000000000..5837ad33ba
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_05.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_h310_06.webp b/pages/dedibox-hardware/how-to/assets/scaleway_h310_06.webp
new file mode 100644
index 0000000000..76b9c8f1ec
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_h310_06.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p410_01.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p410_01.webp
new file mode 100644
index 0000000000..2c9ad8386b
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p410_01.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p410_02.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p410_02.webp
new file mode 100644
index 0000000000..c6cae6b906
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p410_02.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p410_03.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p410_03.webp
new file mode 100644
index 0000000000..19a2941500
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p410_03.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p410_04.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p410_04.webp
new file mode 100644
index 0000000000..722af6a813
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p410_04.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_01.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_01.webp
new file mode 100644
index 0000000000..84d7dbb5f0
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_01.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_02.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_02.webp
new file mode 100644
index 0000000000..375a478c15
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_02.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_03.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_03.webp
new file mode 100644
index 0000000000..1497c8c037
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_03.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_04.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_04.webp
new file mode 100644
index 0000000000..8ee2784f2f
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_04.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_05.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_05.webp
new file mode 100644
index 0000000000..4e7c94e599
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_05.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_06.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_06.webp
new file mode 100644
index 0000000000..b15c08101c
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_06.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_07.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_07.webp
new file mode 100644
index 0000000000..74d4ae0d4a
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_07.webp differ
diff --git a/pages/dedibox-hardware/how-to/assets/scaleway_p420_08.webp b/pages/dedibox-hardware/how-to/assets/scaleway_p420_08.webp
new file mode 100644
index 0000000000..1497c8c037
Binary files /dev/null and b/pages/dedibox-hardware/how-to/assets/scaleway_p420_08.webp differ
diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx
new file mode 100644
index 0000000000..526bc5e633
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h200.mdx
@@ -0,0 +1,150 @@
+---
+meta:
+ title: How to configure the DELL PERC H200 RAID controller
+ description: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox
+content:
+ h1: How to configure the DELL PERC H200 RAID controller
+ paragraph: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox
+tags: dedibox h200 raid dell perc controller
+dates:
+ validation: 2024-08-27
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H200](https://www.dell.com/support/kbdoc/en-us/000134280/perc-dell-perc-h200-and-6gbps-sas-hba-features) RAID controller
+
+## How to install the required packages
+
+We recommend you use the packages provided by [HWraid](http://hwraid.le-vert.net/) to configure your DELL PERC H200 RAID controller. Install them as follows:
+
+### Debian 12 (Bookworm)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 11 (Bullseye)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 10 (Buster)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian buster main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 9 (Stretch)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian stretch main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Unbuntu 20.04 (Focal Fossa)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu focal main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Unbuntu 18.04 (Bionic Beaver)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu bionic main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Ubuntu 16.04 (Xenial Xerus)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu xenial main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+## How to check the status of the RAID controller
+
+Run the following command to check the status of the DELL PERC H200 RAID controller:
+
+```
+sas2ircu LIST
+```
+
+An output like the following example displays:
+
+```
+ LSI Corporation SAS2 IR Configuration Utility.
+ Version 5.00.00.00 (2010.02.09)
+ Copyright (c) 2009 LSI Corporation. All rights reserved.
+
+ Adapter Vendor Device SubSys SubSys
+ Index Type ID ID Pci Address Ven ID Dev ID
+ ----- ------------ ------ ------ ----------------- ------ ------
+ 0 SAS2008 1000h 72h 00h:01h:00h:00h 1028h 1f1dh
+ SAS2IRCU: Utility Completed Successfully.
+```
+
+## How to check the status of the RAID
+
+Run the following command to check the status of the hardware RAID on your Dell PERC H200:
+
+```
+sas2ircu-status
+```
+
+It displays information about the state of the RAID array:
+
+```
+-- Controller informations --
+-- ID | Model
+c0 | SAS2008
+
+-- Arrays informations --
+-- ID | Type | Size | Status
+c0u0 | RAID1 | 1907G | Okay (OKY)
+
+-- Disks informations
+-- ID | Model | Status
+c0u0p0 | ST32000444SS (9WM3NAR0) | Optimal (OPT)
+c0u0p1 | ST32000444SS (9WM3MZL2) | Optimal (OPT)
+```
+
+## How to optimize the performance of your hardware RAID
+
+For maximum performance, you can activate the cache of your SATA disks. After creating a virtual disk, the cache of SATA disks is disabled by default. Restore maximum performance by re-enabling the cache using rescue mode.
+
+
+ This step can be performed on Dedibox servers equipped with a DELL PERC H200 RAID controller and SATA hard disk drives.
+
+
+1. Boot your server into [rescue mode](/dedicated-servers/how-to/use-rescue-mode/) using a 64-bit Ubuntu operating system.
+2. Log into the server using the provided SSH credentials and run the following commands to re-enable the disk cache:
+ ```sh
+ sudo su
+
+ echo 'deb http://linux.dell.com/repo/community/deb/latest /' | sudo tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list
+
+ apt-get update && apt-get install -y --force-yes srvadmin-base
+
+ service dataeng start
+
+ /opt/dell/srvadmin/sbin/omconfig storage vdisk action=changepolicy controller=0 vdisk=0 diskcachepolicy=enabled
+ ```
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h310.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h310.mdx
new file mode 100644
index 0000000000..68c16f3686
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h310.mdx
@@ -0,0 +1,119 @@
+---
+meta:
+ title: How to configure the DELL PERC H310 RAID controller
+ description: This page explains how to configure the DELL PERC H310 RAID controller on a Scaleway Dedibox
+content:
+ h1: How to configure the DELL PERC H310 RAID controller
+ paragraph: This page explains how to configure the DELL PERC H310 RAID controller
+tags: dell perc h310 raid controller dedibox
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H310](https://www.dell.com/support/kbdoc/fr-fr/000102394/dell-poweredge-perc-h310-h810-configuration-and-faq) RAID controller
+
+## How to install the required packages
+
+We recommend you use the packages provided by [HWraid](http://hwraid.le-vert.net/) to configure your DELL PERC H310 RAID controller. Install them as follows:
+
+### Debian 12 (Bookworm)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 11 (Bullseye)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 10 (Buster)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian buster main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 9 (Stretch)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian stretch main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Unbuntu 20.04 (Focal Fossa)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu focal main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Unbuntu 18.04 (Bionic Beaver)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu bionic main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Ubuntu 16.04 (Xenial Xerus)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu xenial main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+## How to check the status of the RAID controller
+
+Run the following command to check the status of the DELL PERC H310 RAID controller:
+
+```
+megaclisas-status
+```
+
+An output like the following example displays:
+
+```
+-- Controller information --
+-- ID | Model
+c0 | PERC H310 Mini
+
+-- Arrays informations --
+-- ID | Type | Size | Status | InProgress
+c0u0 | RAID0 | 2728G | Optimal | None
+c0u1 | RAID0 | 2728G | Optimal | None
+
+-- Disks informations
+-- ID | Model | Status
+c0u0p0 | SEAGATE ST3000NM0023 GS0FZ1Y25K8M | Online, Spun Up
+c0u1p0 | SEAGATE ST3000NM0023 GS0FZ1Y25L0X | Online, Spun Up
+```
+
+## How to check the status of the disks
+
+Run the following command to check the health status of the disks in your RAID:
+
+```
+DEVICE=/dev/sda
+for i in $(megacli -pdlist -a0 | grep Id | cut -d":" -f2); do
+ echo "============================== $i =============================="
+ smartctl -s on -a -d megaraid,${i} ${DEVICE} -T permissive
+done
+```
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h700.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h700.mdx
new file mode 100644
index 0000000000..41ff2c6b15
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h700.mdx
@@ -0,0 +1,122 @@
+---
+meta:
+ title: How to configure the DELL PERC H700/H710/H730/H730P RAID controller
+ description: This page explains how to configure the DELL PERC H700/H710/H730/H730P RAID controller
+content:
+ h1: How to configure the DELL PERC H700/H710/H730/H730P RAID controller
+ paragraph: This page explains how to configure the DELL PERC H700/H710/H730/H730P RAID controller
+tags: dell perc h700 h710 h730 h730p raid controller dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H700/H710/H730/H730P](https://i.dell.com/sites/csdocuments/Shared-Content_data-Sheets_Documents/en/perc-technical-guidebook.pdf) RAID controller
+
+## How to install the required packages
+
+We recommend using the packages provided by [HWraid](http://hwraid.le-vert.net/) to configure your DELL PERC H700/H710/H730/H730P RAID controller. Install them as follows:
+
+### Debian 12 (Bookworm)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 11 (bullseye)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 10 (Buster)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian buster main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Debian 9 (Stretch)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian stretch main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Unbuntu 20.04 (Focal Fossa)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu focal main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Unbuntu 18.04 (Bionic Beaver)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu bionic main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+### Ubuntu 16.04 (Xenial Xerus)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu xenial main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install megaclisas-status
+```
+
+## How to check the status of the RAID controller
+
+Run the following command to check the status of the DELL PERC H700/H710/H730/H730P RAID controller:
+
+```
+megaclisas-status
+```
+
+An output like the following example displays:
+```
+-- Controller informations --
+-- ID | Model
+c0 | PERC H710
+
+-- Arrays informations --
+-- ID | Type | Size | Status | InProgress
+c0u0 | RAID0 | 2728G | Optimal | None
+c0u1 | RAID0 | 2728G | Optimal | None
+
+-- Disks informations
+-- ID | Model | Status
+c0u0p0 | SEAGATE ST3000NM0023 GS0FZ1Y25K8M | Online, Spun Up
+c0u1p0 | SEAGATE ST3000NM0023 GS0FZ1Y25L0X | Online, Spun Up
+```
+
+## How to check the status of the disks
+
+Run the following command to check the health status of the disks in your RAID:
+
+```
+DEVICE=/dev/sda
+for i in $(megacli -pdlist -a0 | grep Id | cut -d":" -f2); do
+ echo "============================== $i =============================="
+ smartctl -s on -a -d megaraid,${i} ${DEVICE} -T permissive
+done
+```
+
+
+ Note that you will need to replace `/dev/sda`with the correct disk that represents your Logical Volume, if you have multiple of them.
+
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-dell-perc-h800.mdx b/pages/dedibox-hardware/how-to/configure-dell-perc-h800.mdx
new file mode 100644
index 0000000000..a3b1eb86f0
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-dell-perc-h800.mdx
@@ -0,0 +1,132 @@
+---
+meta:
+ title: How to configure the DELL PERC H800 RAID controller
+ description: This page explains how to configure the DELL PERC H800 RAID controller
+content:
+ h1: How to configure the DELL PERC H800 RAID controller
+ paragraph: This page explains how to configure the DELL PERC H800 RAID controller
+tags: dedibox dell perc h800 raid controller
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H800](https://i.dell.com/sites/csdocuments/Shared-Content_data-Sheets_Documents/en/perc-technical-guidebook.pdf) RAID controller
+
+## How to install the required packages
+
+We recommend you use the packages provided by [HWraid](http://hwraid.le-vert.net/) to configure your DELL PERC H800 RAID controller. Install them as follows:
+
+### Debian 12 (Bookworm)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 11 (Bullseye)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian bullseye main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 10 (Buster)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian buster main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Debian 9 (Stretch)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/debian stretch main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Unbuntu 20.04 (Focal Fossa)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu focal main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Unbuntu 18.04 (Bionic Beaver)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu bionic main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+### Ubuntu 16.04 (Xenial Xerus)
+
+```sh
+sudo echo "deb http://hwraid.le-vert.net/ubuntu xenial main" >> /etc/apt/sources.list
+sudo apt update
+sudo apt install sas2ircu-status
+```
+
+## How to check the status of the RAID controller
+
+Run the following command to check the status of the DELL PERC H800 RAID controller:
+
+```
+sas2ircu LIST
+```
+
+An output like the following example displays:
+
+```
+-- Controller informations --
+-- ID | Model
+c0 | PERC H800 Integrated
+
+-- Arrays informations --
+-- ID | Type | Size | Status | InProgress
+c0u0 | RAID6 | 18188G | Optimal | None
+
+-- Disks informations
+-- ID | Model | Status
+c0u0p0 | SEAGATE ST32000444SS KS689WM3P15W | Online
+c0u0p1 | SEAGATE ST32000444SS KS689WM495G6 | Online
+c0u0p2 | SEAGATE ST32000444SS KS689WM3P1BM | Online
+c0u0p3 | SEAGATE ST32000444SS KS689WM41PYG | Online
+c0u0p4 | SEAGATE ST32000444SS KS689WM47H0J | Online
+c0u0p5 | SEAGATE ST32000444SS KS689WM3YWVT | Online
+c0u0p6 | SEAGATE ST32000444SS KS689WM3HEP6 | Online
+c0u0p7 | SEAGATE ST32000444SS KS689WM3QGBJ | Online
+c0u0p8 | SEAGATE ST32000444SS KS689WM3EN4J | Online
+c0u0p9 | SEAGATE ST32000444SS KS689WM3QG7G | Online
+c0u0p10 | SEAGATE ST32000444SS KS689WM3V3ML | Online
+c0u0p11 | SEAGATE ST32000444SS KS689WM3QGTG | Online
+```
+
+## How to check the status of the disks
+
+Run the following command to check the health status of the disks in your RAID:
+
+```
+DEVICE=/dev/sda
+for i in $(megacli -pdlist -a0 | grep Id | cut -d":" -f2); do
+ echo "============================== $i =============================="
+ smartctl -s on -a -d megaraid,${i} ${DEVICE} -T permissive
+done
+```
+
+
+ Note that you will need to replace `/dev/sda`with the correct disk that represents your Logical Volume, if you have multiple of them.
+
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx b/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx
new file mode 100644
index 0000000000..6df164b6d0
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-hardware-raid-console.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to configure your Scaleway Dedibox hardware RAID from the console
+ description: This page explains how to configure your Scaleway Dedibox hardware RAID from the console
+content:
+ h1: How to configure your Scaleway Dedibox hardware RAID from the console
+ paragraph: This page explains how to configure your Scaleway Dedibox hardware RAID from the console
+tags: dedibox raid
+dates:
+ validation: 2024-08-27
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+A hardware RAID is a type of [RAID](/hardware/concepts/#raid) implementation where construction and management of the RAID is performed on dedicated hardware, independently of the operating system.
+
+The logical disks of the RAID array are managed by a physical controller, sitting on the PCI bus, which presents only the logical volumes to the operating system. The RAID controller manages the RAID using its own CPU and RAM, without delegating tasks to the main CPU of the machine.
+
+
+
+- A [Dedibox account](https://console.online.net)
+
+1. Log in to the [Scaleway Dedibox console](https://console.online.net/en/login).
+2. Click on **Server** > **Server list** to display a list of available servers in the account.
+3. Select the server to install and click **Manage**.
+4. Click **RAID configuration** in the menu.
+5. Choose the RAID level for the server from the drop-down list and confirm by clicking **Erase all my data and proceed to RAID level changes**.
+
+ This will delete all the data in the server's disks. Make sure to back up your data before changing the RAID level of the machine.
+
+6. Proceed with the reinstallation of the operating system from the console.
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-hp-smart-array-p410.mdx b/pages/dedibox-hardware/how-to/configure-hp-smart-array-p410.mdx
new file mode 100644
index 0000000000..6bdfc2ac86
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-hp-smart-array-p410.mdx
@@ -0,0 +1,69 @@
+---
+meta:
+ title: How to configure the HP SMART ARRAY P410/P222 RAID controller
+ description: This page explains how to configure the HP SMART ARRAY P410/P222 RAID RAID controller
+content:
+ h1: How to configure the HP SMART ARRAY P410/P222 RAID controller
+ paragraph: This page explains how to configure the HP SMART ARRAY P410/P222 RAID RAID controller
+tags: dedibox hp smart array p410 p222 raid controller
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with an HP SMART ARRAY P410 or P222 RAID controller
+
+## How to check the status of the RAID
+
+1. Log into your server using SSH.
+2. Run the following command to display the status of the RAID:
+ ```
+ ssacli ctrl all show config
+ ```
+
+ An output similar to the following example displays:
+
+ ```
+ Smart Array P410 in Slot 1 (sn: PACCRID111003N3)
+
+ array A (SATA, Unused Space: 0 MB)
+
+ logicaldrive 1 (1.8 TB, RAID 1, OK)
+
+ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SATA, 2 TB, OK)
+ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SATA, 2 TB, OK)
+ ```
+3. Run the following commands to display the SMART values of the disks:
+ ```
+ smartctl -a -d cciss,0 /dev/sg0
+ ```
+
+ then run:
+
+ ```
+ smartctl -a -d cciss,1 /dev/sg0
+ ```
+
+## How to check the battery state of a P410 RAID controller with cache and battery
+
+Run the following command to check the battery state of an HP SMART ARRAY P410 RAID controller:
+
+ ```
+ ssacli ctrl all show config detail
+ ```
+
+ It returns the state of the cache and the battery of the controller:
+
+ ```
+ Total Cache Size: 256 MB
+ Cache Backup Power Source: Batteries
+ Battery/Capacitor Count: 1
+ Battery/Capacitor Status: OK
+ ```
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-hp-smart-array-p420.mdx b/pages/dedibox-hardware/how-to/configure-hp-smart-array-p420.mdx
new file mode 100644
index 0000000000..8285dbed97
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-hp-smart-array-p420.mdx
@@ -0,0 +1,69 @@
+---
+meta:
+ title: How to configure the HP SMART ARRAY P420 RAID controller
+ description: This page explains how to configure the HP SMART ARRAY P420 RAID controller
+content:
+ h1: How to configure the HP SMART ARRAY P420 RAID controller
+ paragraph: This page explains how to configure the HP SMART ARRAY P420 RAID controller
+tags: hp smart array p420 kvm hp-smart-array dedibox raid controller
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with an HP SMART ARRAY P420 RAID controller
+
+## How to check the status of the RAID
+
+1. Log into your server using SSH.
+2. Run the following command to display the status of the RAID:
+ ```
+ ssacli ctrl all show config
+ ```
+
+ An output as the following example displays:
+
+ ```
+ Smart Array P420 in Slot 1 (sn: PACCRID1XXXXXX)
+
+ array A (SATA, Unused Space: 0 MB)
+
+ logicaldrive 1 (1.8 TB, RAID 1, OK)
+
+ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SATA, 2 TB, OK)
+ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SATA, 2 TB, OK)
+ ```
+3. Run the following commands to display the SMART values of the disks:
+ ```
+ smartctl -a -d cciss,0 /dev/sg0
+ ```
+
+ Then run:
+
+ ```
+ smartctl -a -d cciss,1 /dev/sg0
+ ```
+
+## How to check the battery state of a P420 RAID controller with cache and battery
+
+Run the following command to check the battery state of an HP SMART ARRAY P420 RAID controller:
+
+ ```
+ ssacli ctrl all show config detail
+ ```
+
+ It resets the cache and battery of the controller:
+
+ ```
+ Total Cache Size: 256 MB
+ Cache Backup Power Source: Batteries
+ Battery/Capacitor Count: 1
+ Battery/Capacitor Status: OK
+ ```
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx
new file mode 100644
index 0000000000..305a28bc99
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-h200.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to configure the DELL PERC H200 RAID controller from the KVM
+ description: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox from the KVM
+content:
+ h1: How to configure the DELL PERC H200 RAID controller from the KVM
+ paragraph: This page explains how to configure the DELL PERC H200 RAID controller on a Scaleway Dedibox from the KVM
+tags: dedibox dell perc h200 raid kvm
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a [DELL PERC H200](https://www.dell.com/support/kbdoc/en-us/000134280/perc-dell-perc-h200-and-6gbps-sas-hba-features) RAID controller
+
+1. Click **Server** > **Server list** to display the list of your servers. Click the identifier of the server you want to configure. The server information page displays.
+2. Click **IDRAC** in the menu on the right and validate the terms. Then enter your connection IP address and click **Create**. Your iDRAC session credentials display. Login to iDRAC using the credentials shown.
+3. The iDRAC dashboard displays. Click **Launch** in the **Virtual Console Preview** section to launch the Java-based KVM-over-IP applet. Once the server's screen output is visible in the KVM applet, reboot the machine.
+
+ Set your Java security settings to **low** to avoid connection problems.
+
+4. Press **CTRL** + **C** during the boot process to enter the RAID configuration utility:
+
+5. The RAID configuration utility main screen displays. Select the RAID controller to configure and press Enter.
+
+6. Select **RAID Properties** and press enter. The RAID configuration displays. Select **Manage volume** and press **Enter**.
+
+7. Create a new volume and select the RAID type for the volume:
+
+
+
+ By creating a new RAID volume **all data** on volume disks will be **deleted**.
+
+8. Select the drives for the volume and save your settings:
+
+
+
+ Select a disk using the arrow keys on your keyboard. You can change **NO** to **YES** by pressing the spacebar.
+
+9. Press **C** to validate your edits. Then select **Save changes** and then **Exit menu** to finalize the RAID configuration and reboot your server.
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx
new file mode 100644
index 0000000000..47902d11dc
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to configure the DELL PERC H310 / H710 / H730 RAID controller from the KVM
+ description: This page explains how to configure the DELL PERC H310 / H710 / H730 RAID controller on a Scaleway Dedibox from the KVM
+content:
+ h1: How to configure the DELL PERC H310 / H710 / H730 RAID controller from the KVM
+ paragraph: This page explains how to configure the DELL PERC H310 / H710 / H730 RAID controller on a Scaleway Dedibox from the KVM
+tags: dell perc h310 h710 h730 raid controller kvm
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+The personalized RAID configuration allows you to create a RAID mode that cannot be created via the management console of Online.net (RAID10, for example).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with a DELL PERC H310, H710, or H730 RAID controller
+
+1. Click **Server** > **Server list** to display the list of your servers. Click the identifier of the server you want to configure. The server information page displays.
+2. Click **IDRAC** in the menu on the right and validate the terms. Then enter your connection's IP address and click **CREATE**. Your iDRAC session credentials display. Login to iDRAC using the credentials shown.
+3. The iDRAC dashboard displays. Click **Launch** in the **Virtual Console Preview** section to launch the Java-based KVM-over-IP applet. Once the server's screen output is visible in the KVM applet, reboot the machine.
+
+ Set your Java security settings to **low** to avoid connection problems.
+
+4. Press **CTRL** + **C** during the boot process to enter the RAID configuration utility:
+
+5. The RAID configuration tool's main interface displays. Select the virtual disk to delete:
+
+6. Press **F2**, then select **Delete VD** and press enter to delete the virtual disk:
+
+7. Create a new virtual disk by selecting **No configuration present**. The following screen displays, allowing you to configure a new virtual disk:
+
+8. Return to the main menu and select the virtual disk. Then press **F2**, and select **Fast Init.** and press enter to initialize the virtual disk:
+
+7. Press **OK** once the initialization is completed on the virtual drive. Then press **Strg** + **ALT** + **CTRL** to reboot the machine:
+
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx
new file mode 100644
index 0000000000..f02b23455d
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to configure the HP Smart Array P410 RAID controller from the KVM
+ description: This page explains how to configure the HP Smart Array P410 RAID controller on a Scaleway Dedibox from the KVM
+content:
+ h1: How to configure the HP Smart Array P410 RAID controller from the KVM
+ paragraph: This page explains how to configure the HP Smart Array P410 RAID controller on a Scaleway Dedibox from the KVM
+tags: dedibox hp smart array p410 raid kvm
+dates:
+ validation: 2024-08-16
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+The personalized RAID configuration allows you to create a RAID mode that cannot be created via the management console of Online.net (RAID10, for example).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with an HP Smart Array P410 RAID controller
+
+1. Click **Server** > **Server list** to display the list of your servers. Click the identifier of the server you want to configure. The server information page displays.
+2. Click **iLO** in the menu on the right and validate the terms. Then enter your connection's IP address and click **CREATE**. Your iDRAC session credentials display. Login to iDRAC using the credentials shown.
+3. The iDRAC dashboard displays. Click **Launch** in the **Virtual Console Preview** section to launch the Java-based KVM-over-IP applet. Once the server's screen output is visible in the KVM applet, reboot the machine.
+
+ Set your Java security settings to **low** to avoid connection problems.
+
+4. Press **F8** during the boot process to enter the RAID configuration utility:
+
+5. Select **Delete Logical Drive** with the error keys and press **Enter** to select.
+
+6. Press **F3** to confirm the deletion of the local drive:
+
+
+
+ This will result in complete data loss for this logical drive.
+
+7. Select **Create Logical Drive** in the main menu. Then use the **Tab** key on your keyboard to navigate and configure your RAID:
+
+
+
diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx
new file mode 100644
index 0000000000..fd20ae7170
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to configure the HP Smart Array P420 RAID controller from the KVM
+ description: This page explains how to configure the HP Smart Array P420 RAID controller on a Scaleway Dedibox from the KVM
+content:
+ h1: How to configure the HP Smart Array P420 RAID controller from the KVM
+ paragraph: This page explains how to configure the HP Smart Array P420 RAID controller on a Scaleway Dedibox from the KVM
+tags: dedibox hp smart array p420 raid kvm
+dates:
+ validation: 2024-08-16
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+The personalized RAID configuration allows you to create a RAID mode that cannot be created via the management console of Online.net (RAID10, for example).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) with an HP Smart Array P420 RAID controller
+
+1. Click **Server** > **Server list** to display the list of your servers. Click the identifier of the server you want to configure. The server information page displays.
+2. Click **iLO** in the menu on the right and validate the terms. Then enter your connection's IP address and click **CREATE**. Your iDRAC session credentials display. Login to iDRAC using the credentials shown.
+3. The iDRAC dashboard displays. Click **Launch** in the **Virtual Console Preview** section to launch the Java-based KVM-over-IP applet. Once the server's screen output is visible in the KVM applet, reboot the machine.
+
+ Set your Java security settings to **low** to avoid connection problems.
+
+4. Press **F8** during the boot process to enter the RAID configuration utility:
+
+5. Select the RAID controller from the drop-down menu. The current array configuration displays:
+
+6. Click **Delete** to delete the existing virtual disk. A pop-up displays. Click **OK** to confirm deletion of the logical drive:
+
+
+
+ Deleting your logical drive will erase all data stored on it.
+
+7. Create a new logical array once the previous one is deleted. To do so, click **Create Array**:
+
+8. Select the physical disks you want to use for the virtual device and confirm by clicking **OK**:
+
+9. Select the parameters for the array and click **Save** to write the changes to the disks:
+
+10. Click **Exit ACU** to quit the array configuration and reboot your server.
+
+
diff --git a/pages/dedibox-hardware/how-to/index.mdx b/pages/dedibox-hardware/how-to/index.mdx
new file mode 100644
index 0000000000..76ad796e43
--- /dev/null
+++ b/pages/dedibox-hardware/how-to/index.mdx
@@ -0,0 +1,10 @@
+---
+meta:
+ title: Hardware - How Tos
+ description: Hardware How Tos
+content:
+ h1: Hardware - How Tos
+ paragraph: Hardware How Tos
+---
+
+
diff --git a/pages/dedibox-hardware/index.mdx b/pages/dedibox-hardware/index.mdx
new file mode 100644
index 0000000000..14e3a83d8b
--- /dev/null
+++ b/pages/dedibox-hardware/index.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: Dedibox - Hardware Documentation
+ description: Dive into Scaleway Dedibox - Hardware with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/dedibox-hardware/reference-content/index.mdx b/pages/dedibox-hardware/reference-content/index.mdx
new file mode 100644
index 0000000000..48da79bf2b
--- /dev/null
+++ b/pages/dedibox-hardware/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Hardware - Additional content
+ description: Hardware additional content
+content:
+ h1: Hardware - Additional content
+ paragraph: Hardware additional content
+---
diff --git a/pages/dedibox-hardware/reference-content/server-comparison-table.mdx b/pages/dedibox-hardware/reference-content/server-comparison-table.mdx
new file mode 100644
index 0000000000..1800686cb4
--- /dev/null
+++ b/pages/dedibox-hardware/reference-content/server-comparison-table.mdx
@@ -0,0 +1,144 @@
+---
+meta:
+ title: Hardware - Server comparison table
+ description: This page shows you our previous Dedibox offers and their equivalent current offers.
+content:
+ h1: Server comparison table
+ paragraph: This page shows you our previous Dedibox offers and their equivalent current offers.
+tags: dedibox server
+dates:
+ validation: 2024-11-15
+ posted: 2021-09-05
+categories:
+ - dedibox-servers
+---
+
+These comparison tables display our Dedibox machines, grouped by categories.
+
+
+ The information provided below is for informative purposes only and has no contractual value.
+
+
+## Start range
+
+| Offer Name | CPU | RAM | Storage | Hardware RAID | NIC bandwidth | Included bandwidth | RPN speed | RPN Business speed |
+|:-------------------|:----------------------|:------|:------------------|:-----------------|:----------------|:---------------------|:-------------|:---------------------|
+| Start-1-L | Intel® Xeon E3 1220v2 | 16 GB | 2 x 1 TB | No hardware RAID | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Start-1-M-SATA | Intel® C2750 (Avoton) | 8 GB | 1 x 1 TB | None | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Start-1-M-SSD | Intel® C2750 (Avoton) | 8 GB | 1 x 120 GB SSD | None | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Start-1-M-SSD-160G | Intel® C2750 (Avoton) | 8 GB | 1 x 160 GB SSD | None | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Start-2-L | Intel® Xeon® D-1531 | 32 GB | 2 x 250 GB SSD | None | 1 Gbit/sec | 300 Mbit/sec | No RPN | No RPN |
+| Start-2-M-SATA | Intel® C2750 (Avoton) | 16 GB | 1 x 1 TB | None | 1 Gbit/sec | 250 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Start-2-M-SSD | Intel® C2750 (Avoton) | 16 GB | 1 x 250 GB SSD | None | 1 Gbit/sec | 250 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Start-2-XS-SATA | Intel® C2350 (Avoton) | 4 GB | 1 x 500 GB | None | 1 Gbit/sec | 250 Mbit/sec | No RPN | No RPN |
+| Start-2-S-SATA | Intel® C2350 (Avoton) | 4 GB | 1 x 1 TB | None | 1 Gbit/sec | 250 Mbit/sec | No RPN | No RPN |
+| Start-2-S-SSD | Intel® C2350 (Avoton) | 4 GB | 1 x 120 GB SSD | None | 1 Gbit/sec | 250 Mbit/sec | No RPN | No RPN |
+| Start-3-L | Intel® Xeon® D-1531 | 32 GB | 2 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Start-3-S-SSD | Intel® C2350 (Avoton) | 4 GB | 1 x 250 GB SSD | None | 1 Gbit/sec | 250 Mbit/sec | No RPN | No RPN |
+| Start-9-M | AMD Ryzen™ 5 PRO 3600 | 32 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Start-9-S | AMD Ryzen™ 5 PRO 3600 | 16 GB | 2 x 1 TB | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+
+## Core range
+
+| Offer Name | CPU | RAM | Storage | Hardware RAID | NIC bandwidth | Included bandwidth | RPN speed | RPN Business speed |
+|:------------------|:----------------------------|:--------|:---------------------|:---------------------------|:----------------|:---------------------|:--------------|:---------------------|
+| Core-1-L-SATA | 2 x Intel® Xeon E5 2670 | 128 GB | 3 x 3 TB SAS | No hardware RAID | 1 Gbit/sec | 100 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-1-M-SATA | 2 x Intel® Xeon E5 2640 | 128 GB | 3 x 3 TB | P420 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Core-1-M-SSD | 2 x Intel® Xeon E5 2620 | 128 GB | 3 x 120 GB SSD | P420 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-1-S-SATA | 2 x Intel® Xeon E5 2640 | 64 GB | 3 x 2 TB | No hardware RAID | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Core-2-L-SATA | 2 x Intel® Xeon E5 2670 | 256 GB | 3 x 3 TB | P420 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-2-M-SSD | 2 x Intel® Xeon E5 2650v2 | 192 GB | 3 x 160 GB SSD | H710 (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-2-S-SATA | Intel® Xeon E5 1650 | 64 GB | 2 x 3 TB | P420 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Core-2-S-SSD | 2 x Intel® Xeon E5 2620v2 | 128 GB | 2 x 160 GB SSD | P420 or H310 (RAID 0,1,5) | 1 Gbit/sec | 400 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-3-L-SSD | 2 x Intel® Xeon E5 2670v2 | 256 GB | 3 x 160 GB SSD | H710 or H730P (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-3-M-SATA | 2 x Intel® Xeon E5 2640v3 | 192 GB | 3 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-3-S-SSD | 2 x Intel® Xeon E5 2620v2 | 128 GB | 2 x 500 GB SSD | H310 or H730 (RAID 0,1,5) | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Core-4-L-SATA | 2 x Intel® Xeon E5 2660v4 | 256 GB | 3 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 750 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-4-L-SSD | 2 x Intel® Xeon E5 2660v4 | 256 GB | 5 x 500 GB SSD | H730P (RAID 0,1,5) | 1 Gbit/sec | 750 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-4-M-SATA | 2 x Intel® Xeon E5 2640v4 | 192 GB | 3 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 750 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-4-M-SSD | 2 x Intel® Xeon E5 2640v4 | 192 GB | 5 x 500 GB SSD | H730P (RAID 0,1,5) | 1 Gbit/sec | 750 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-4-S-SATA | 2 x Intel® Xeon E5 2620v4 | 128 GB | 2 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 400 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-4-S-SSD | 2 x Intel® Xeon E5 2620v4 | 128 GB | 3 x 500 GB SSD | H730P (RAID 0,1,5) | 1 Gbit/sec | 400 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-5-L | 2 x Intel® Xeon Gold 5120 | 384 GB | 4 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-5-M | AMD EPYC™ 7401P | 256 GB | 3 x 1 TB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-5-S | 2 x Intel® Xeon Silver 4114 | 128 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-5-XL | 2 x Intel® Xeon Gold 6140 | 768 GB | 8 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-6-M | 2 x Intel® Xeon Silver 4114 | 192 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-6-XS | 2 x Intel® Xeon Silver 4114 | 96 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-7-L-A | AMD EPYC™ 7532 | 256 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-7-L-I | 2 x Intel Xeon Silver 4214R | 576 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-7-M-A | AMD EPYC™ 7302P | 256 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-7-M-A-F | AMD EPYC™ 7302P | 256 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | No RPN | No RPN |
+| Core-7-M-I | 2 x Intel Xeon Silver 4214R | 192 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-7-XL-I | 2 x Intel Xeon Gold 6242R | 384 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-7-XXL-A | 2 x AMD EPYC™ 7532 | 1024 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec | 25 Gbit/sec |
+| Core-9-L | AMD EPYC™ 7313P | 256 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-9-M | AMD EPYC™ 7401P | 256 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-9-S | AMD EPYC™ 7401P | 128 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Core-10-L | AMD EPYC™ 8324P | 256 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Core-10-M | AMD EPYC™ 8224P | 192 GB | 2 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Core-10-S | AMD EPYC™ 8124P | 128 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Core-10-XL | AMD EPYC™ 8434P | 384 GB | 2 x 3.84 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Core-10-XS | AMD EPYC™ 8024P | 64 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Core-10-XXL | AMD EPYC™ 8534P | 576 GB | 2 x 3.84 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+
+## Pro range
+
+| Offer Name | CPU | RAM | Storage | Hardware RAID | NIC bandwidth | Included bandwidth | RPN speed | RPN Business speed |
+|:---------------|:------------------------|:-------|:--------------------|:--------------------------|:----------------|:---------------------|:--------------|:---------------------|
+| Pro-1-L-SATA | Intel® Xeon E5 1650 | 32 GB | 2 x 3 TB | P420 (RAID 0,1,5) | 1 Gbit/sec | 200 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-1-M-SATA | Intel® Xeon E3 1240 | 24 GB | 2 x 2 TB | P410 (RAID 0,1,5) | 1 Gbit/sec | 200 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-2-M-SATA | Intel® Xeon E3 1230v3 | 32 GB | 2 x 2 TB | P222 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-2-S | Intel® Xeon E3 1230v2 | 16 GB | 2 x 1 TB | H200 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-3-L-SATA | Intel® Xeon E5 1410v2 | 96 GB | 2 x 4 TB | H310 or H710 (RAID 0,1,5) | 1 Gbit/sec | 400 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-3-M-SATA | Intel® Xeon E5 1410v2 | 64 GB | 2 x 2 TB | H310 or H710 (RAID 0,1,5) | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-3-M-SSD | Intel® Xeon E5 1410v2 | 64 GB | 2 x 500 GB SSD | H310 or H710 (RAID 0,1,5) | 1 Gbit/sec | 300 Mbit/sec | No RPN | No RPN |
+| Pro-4-L | Intel® Xeon E5 1650v3 | 96 GB | 3 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Pro-4-M | Intel® Xeon E3 1245v5 | 64 GB | 3 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-4-S | Intel® Xeon E3 1245v5 | 32 GB | 3 x 250 GB SSD | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-5-L | AMD EPYC™ 7281 | 96 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 1 Gbit/sec | 750 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Pro-5-M | Intel® Xeon E3 1240v6 | 64 GB | 3 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-5-S | Intel® Xeon E3 1240v6 | 32 GB | 3 x 250 GB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 1 Gbit/sec |
+| Pro-5-S-LE | Intel® Xeon E3 1240v6 | 32 GB | 2 x 250 GB SSD | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | No RPN | No RPN |
+| Pro-6-M | Intel® Xeon E3 1240v6 | 64 GB | 3 x 1 TB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-6-S | Intel® Xeon E3 1240v6 | 64 GB | 2 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 300 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-6-XS | Intel® Xeon® D-1531 | 32 GB | 2 x 500 GB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-7-M | Intel Xeon E-2246G | 64 GB | 2 x 960 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 750 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-7-S | Intel Xeon E-2246G | 32 GB | 2 x 480 GB SSD NVMe | No hardware RAID | 1 Gbit/sec | 750 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-8-M | 2 x Intel® Xeon E5 2670 | 256 GB | 2 x 1 TB SSD | No hardware RAID | 1 Gbit/sec | 750 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-8-S | 2 x Intel® Xeon E5 2620 | 192 GB | 2 x 1 TB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-8-XS | Intel® Xeon E5 1410v2 | 96 GB | 3 x 1 TB SSD | No hardware RAID | 1 Gbit/sec | 750 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-8-XS-LE | Intel® Xeon E5 1410v2 | 64 GB | 2 x 1 TB SSD | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Pro-9-L | AMD EPYC™ 7272 | 256 GB | 2 x 2 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Pro-9-M | AMD EPYC™ 7272 | 128 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Pro-9-XS | AMD EPYC™ 7281 | 32 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Pro-9-S | AMD EPYC™ 7281 | 96 GB | 2 x 1 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+
+## Store range
+
+| Offer Name | CPU | RAM | Storage | Hardware RAID | NIC bandwidth | Included bandwidth | RPN speed | RPN Business speed |
+|:-------------|:--------------------------|:-------|:---------------------|:------------------------|:----------------|:---------------------|:--------------|:---------------------|
+| Store-1-L | AMD Opteron 4386 | 64 GB | 12 x 4 TB | H700 (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-1-S | Intel® Xeon E3 1220 | 32 GB | 2 x 4 TB | No hardware RAID | 1 Gbit/sec | 150 Mbit/sec | No RPN | No RPN |
+| Store-1-XL | Intel® Xeon E3 1220 | 8 GB | 3 x 4 TB | P410 (RAID 0,1,5) | 1 Gbit/sec | 100 Mbit/sec | No RPN | No RPN |
+| Store-1-XXL | Intel Xeon E5620 2.40GHz | 64 GB | 12 x 6 TB | H700 (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | No RPN | 10 Gbit/sec |
+| Store-2-L | Intel® Xeon E5 1620v4 | 64 GB | 12 x 4 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 300 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-2-M | Intel® Xeon E5 1410v2 | 64 GB | 3 x 6 TB | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Store-2-XXL | AMD Opteron 4386 | 64 GB | 12 x 6 TB | H700 (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 10 Gbit/sec | 10 Gbit/sec |
+| Store-4-L | 2 x Intel® Xeon E5 2660v3 | 192 GB | 5 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-4-M | 2 x Intel® Xeon E5 2620v3 | 128 GB | 4 x 6 TB | H730P (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-4-XL | 2 x Intel® Xeon E5 2620v3 | 96 GB | 24 x 500 GB SSD | LSI9361-8i (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-4-XXL | 2 x Intel® Xeon E5 2620v3 | 96 GB | 24 x 1 TB SSD | LSI9361-8i (RAID 0,1,5) | 1 Gbit/sec | 500 Mbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-8-S | Intel® Xeon E5 1410v2 | 96 GB | 4 x 12 TB | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Store-8-XS | Intel® Xeon E5 1410v2 | 96 GB | 4 x 6 TB | No hardware RAID | 1 Gbit/sec | 500 Mbit/sec | 100 Mbit/sec | 1 Gbit/sec |
+| Store-9-L | AMD EPYC™ 7313P | 128 GB | 6 x 1.92 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| Store-9-M | AMD EPYC™ 7272 | 128 GB | 4 x 4 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-9-S | AMD EPYC™ 7232P | 64 GB | 4 x 2 TB SSD NVMe | No hardware RAID | 10 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 10 Gbit/sec |
+| Store-9-XL | AMD EPYC™ 7313P | 256 GB | 6 x 3.84 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+
+## GPU range
+
+| Offer Name | CPU | RAM | Storage | Hardware RAID | NIC bandwidth | Included bandwidth | RPN speed | RPN Business speed |
+|:-------------|:--------------------------------|:-------|:---------------------|:-----------------|:----------------|:---------------------|:--------------|:---------------------|
+| GPU-10-H100 | AMD EPYC™ 9334 GPU NVIDIA H100 | 512 GB | 2 x 7.68 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
+| GPU-10-L40S | AMD EPYC™ 9334 GPU NVIDIA L40S | 256 GB | 2 x 3.84 TB SSD NVMe | No hardware RAID | 25 Gbit/s | 1 Gbit/sec | 1 Gbit/sec | 25 Gbit/sec |
diff --git a/pages/dedibox-hardware/troubleshooting/diagnose-defective-disk.mdx b/pages/dedibox-hardware/troubleshooting/diagnose-defective-disk.mdx
new file mode 100644
index 0000000000..29a9213759
--- /dev/null
+++ b/pages/dedibox-hardware/troubleshooting/diagnose-defective-disk.mdx
@@ -0,0 +1,196 @@
+---
+meta:
+ title: Diagnosis of a failing disk
+ description: This page explains how to diagnose a failing disk
+content:
+ h1: Diagnosis of a failing disk
+ paragraph: This page explains how to diagnose a failing disk
+tags: dedibox diagnosis failing-disk
+dates:
+ validation: 2024-09-10
+ posted: 2021-11-02
+categories:
+ - dedibox-servers
+---
+
+`Smartmontools` is a set of tools that controls and monitors a disk using the **SMART** standard (Self-Monitoring, Analysis, and Reporting Technology System).
+
+It consists of two parts:
+
+* `smartd`, a daemon that allows you to periodically check your hard drives
+* `smartctl`, a command line tool to view the status of the hard disk
+
+The tool supports the vast majority of modern hard drives.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/)
+
+## How to check a single-disk server
+
+1. Log into your server using SSH.
+2. Run the following command from the root account (or precede it with `sudo`):
+ ```
+ smartctl -a /dev/sda
+ ```
+
+ The identifier `sda` refers to your hard disk.
+
+
+## How to check a Dell multi-disk server
+
+### Dell PERC H200 controller
+
+On these servers, the physical disks are referred to as `sg*` devices.
+
+1. Log into your server using SSH.
+2. Run the following commands:
+ ```
+ smartctl -a -T permissive /dev/sg0
+ smartctl -a -T permissive /dev/sg1
+ smartctl -a -T permissive /dev/sg2
+ ```
+
+
+ As the devices can be positioned a little further away, do not hesitate to test up to `sg5` if you do not have conclusive results.
+
+
+### Dell PERC H310 controller
+
+Two possibilities exist for this type of controller:
+
+* `megaclisas-status` and
+* `megacli`
+
+The first one displays the status of the RAID volume, whilst the second one displays the SMART status of the disks.
+
+1. Log into your server using SSH.
+2. Update the APT package lists cache, and install the required packages:
+ ```
+ apt update
+ apt install megaclisas-status megacli
+ ```
+3. Run the following command to display the status of the RAID volume:
+ ```
+ megaclisas-status
+ ```
+4. Run the following little script to retrieve the SMART values of your disks:
+ ```
+ DEVICE=/dev/sda
+ for i in $(megacli -pdlist -a0 | grep Id | cut -d":" -f2); do
+ echo "============================== $i =============================="
+ smartctl -s on -a -d megaraid,${i} ${DEVICE} -T permissive
+ done
+ ```
+## How to check an HP multi-disk server
+
+1. Log into your server using SSH.
+2. Run the following command to display the status of the RAID:
+ ```
+ ssacli ctrl all show config
+ ```
+ An output similar to the following example displays:
+ ```
+ Smart Array P410 in Slot 1 (sn: PACCRID111003N3)
+
+ array A (SATA, Unused Space: 0 MB)
+
+ logicaldrive 1 (1.8 TB, RAID 1, OK)
+
+ physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SATA, 2 TB, OK)
+ physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SATA, 2 TB, OK)
+ ```
+3. Run the following command to display the SMART values of the disks:
+ ```
+ smartctl -a -d cciss,0 /dev/sg0
+ ```
+ then run:
+ ```
+ smartctl -a -d cciss,1 /dev/sg0
+ ```
+
+## How to use SMARTD to monitor your disks
+
+`smartd` allows you to monitor your disks and to be alerted (depending on the configuration) by email in case of failure.
+
+
+ There is no guarantee as to the result of SMARTD and the time remaining before the disk fails completely.
+ However, we strongly encourage you to back up and request a replacement rapidly.
+
+
+### How to configure SMARTD
+
+Below, you find an example of a single-disk server installed on a Debian-like machine.
+
+
+ The following commands are to be executed as `root` or via `sudo`.
+
+
+1. Log into your server using SSH.
+2. Enable basic SMART options:
+ ```
+ smartctl -s on -o on -S on /dev/sda
+ ```
+3. Check that the disk is healthy:
+ ```
+ smartctl -H /dev/sda
+ ```
+4. Edit the file `/etc/smartd.conf`, to set up automated tests:
+ * Start by commenting out the following line:
+ ```
+ DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner
+ ```
+ * Then add a line similar to the following example:
+
+ ```
+ /dev/sda -a -d sat -o on -S on -s (S/../.././01|L/../1/03) -m root -M exec /usr/share/smartmontools/smartd-runner
+ ```
+
+The example above allows you to test your hard disk as follows:
+
+
+ * A short test (S) every day at 1am (01)
+ * A long test (L), every Monday (1) at 3am (03)
+5. Activate the daemon by uncommenting the line `start_smartd=yes` in the file `/etc/default/smartmontools`.
+6. Start the daemon by running the following command:
+ ```
+ service smartmontools start
+ ```
+
+If a problem is detected, it will send a default mail to root (-m root).
+You can redirect the mails sent to the `root` user to your personal mailbox or send this mail directly to another address.
+
+### How to run tests manually
+
+
+To run SMART tests manually, use the following commands:
+
+* `smartctl -t short /dev/sda` to run a **short** test on your disk
+* `smartctl -t long /dev/sda` to run a **long** test on your disk
+
+Once the tests are completed, you can check the results with the following command:
+
+```
+smartctl -l selftest /dev/sda
+```
+
+## How to report disk failures
+
+If you notice any errors when running a SMART diagnosis on your disk, open a [support ticket](/account/how-to/open-a-support-ticket/) and ask for the disk to be replaced, indicating the serial number with the result of the `smartctl` command:
+
+```
+=== START OF INFORMATION SECTION ===
+Device Model: SAMSUNG HD103UJ
+Serial Number: S13PJ1KQ513170 <----------------------- Serial Number
+Firmware Version: 1AA01113
+User Capacity: 1 000 204 886 016 bytes
+Device is: In smartctl database [for details use: -P show]
+ATA Version is: 8
+ATA Standard is: ATA-8-ACS revision 3b
+Local Time is: Fri Oct 29 11:20:27 2010 CEST
+```
+
+
+ For more information on Smartmontools, refer to the [official documentation](https://www.smartmontools.org/wiki/TocDoc).
+
\ No newline at end of file
diff --git a/pages/dedibox-hardware/troubleshooting/index.mdx b/pages/dedibox-hardware/troubleshooting/index.mdx
new file mode 100644
index 0000000000..bf246738de
--- /dev/null
+++ b/pages/dedibox-hardware/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Hardware - Troubleshooting
+ description: Hardware Troubleshooting
+content:
+ h1: Hardware - Troubleshooting
+ paragraph: Hardware Troubleshooting
+---
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/concepts.mdx b/pages/dedibox-ip-failover/concepts.mdx
new file mode 100644
index 0000000000..2bf98a3270
--- /dev/null
+++ b/pages/dedibox-ip-failover/concepts.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: Scaleway Dedibox Failover IP - Concepts
+ description: This page explains all the concepts related to failover IP on Scaleway Dedibox
+content:
+ h1: Scaleway Dedibox Failover IP - Concepts
+ paragraph: This page explains all the concepts related to failover IP on Scaleway Dedibox
+tags: dedibox failover failover-ip plesk bridged nat virtualization
+dates:
+ validation: 2024-08-26
+categories:
+ - dedibox-network
+---
+
+## Bridged network
+
+A bridged network is a mode of networking for virtual machines, another being [NAT-ed networks](/dedibox-ip-failover/concepts/#nat-ed-network). In bridge mode, your server and your virtual machines are seen as different servers at the level of the network equipment. Setting up a bridged network requires a [Virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address).
+
+## Failover IPs
+
+Failover IPs are IP addresses that you can order and move from one server to another (even across data centers), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and have your services remain available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its own IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox.
+
+## IP configuration
+
+IP configuration refers to the assignment and management of IP addresses. Any server that needs to connect to the internet or to another computer, needs an IP address. There are many ways to configure IP addresses, including the use of Failover IPs, Virtual MAC addresses, and the Reverse DNS of IPs.
+
+## NAT-ed network
+
+A NAT-ed network is a mode of networking for virtual machines, another being [bridged networks](/dedibox-ip-failover/concepts/#bridged-network). In NAT mode, your server and its virtual machines are seen as one single server. As only the MAC address of your physical network card is broadcasted on the network, you do not require virtual MAC addresses for this network mode.
+
+## Reverse DNS
+
+Reverse DNS, or rDNS, is exactly the opposite of classic forward DNS as we know it. Forward DNS maps a hostname to an IP address. Reverse DNS means we are mapping the IP address to a hostname. This can be very useful, especially if you want to send emails from your server.
+
+## Virtual MAC address
+
+Virtual MAC addresses are associated with Failover IPs, and are virtual versions of MAC addresses that identify physical hardware. Virtual MAC addresses allow you to create a [bridged network](/dedibox-ip-failover/concepts/#bridged-network) of virtual machines from your server, where the physical server and its virtual machines are identified as different machines at the network level. The same virtual MAC can be associated with several Failover IPs.
+
+## Virtualization
+
+Virtualization refers to the creation of one or multiple virtual machines on a physical server. This can be achieved via virtualization solutions such as VMware vSphere Hypervisor (ESXi) or Proxmox. Virtualization allows you to create separate environments for your different services (for example, keeping mail and web services on different VMs) or to launch several virtual machines to make better use of the performance of the server. To communicate on the Internet, each of your virtual machines needs an IP Address. You can use [Failover IPs](/dedibox-ip-failover/concepts/#failover-ips) for this purpose. If you want to create a bridged network for your virtual machines, you will also need to configure [Virtual MAC addresses](/dedibox-ip-failover/concepts/#virtual-mac-address).
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_edit_reverse.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_edit_reverse.webp
new file mode 100644
index 0000000000..1ace78bacd
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_edit_reverse.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_failoverip_update.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_failoverip_update.webp
new file mode 100644
index 0000000000..443511f5f7
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_failoverip_update.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_update_reverse.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_update_reverse.webp
new file mode 100644
index 0000000000..67c8d65957
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_update_reverse.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo1.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo1.webp
new file mode 100644
index 0000000000..1ca13bf1b0
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo1.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo2.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo2.webp
new file mode 100644
index 0000000000..3f1db0f3a4
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo2.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo3.webp b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo3.webp
new file mode 100644
index 0000000000..d6cb61e3f8
Binary files /dev/null and b/pages/dedibox-ip-failover/how-to/assets/scaleway_windows_ipfo3.webp differ
diff --git a/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx b/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx
new file mode 100644
index 0000000000..8349b50962
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to assign a failover IP to a Dedibox server
+ description: This page explains how to assign a failover IP for Scaleway Dedibox servers.
+content:
+ h1: How to assign a failover IP to a Dedibox server
+ paragraph: This page explains how to assign a failover IP for Scaleway Dedibox servers.
+tags: dedibox failover failover-ip
+dates:
+ validation: 2024-07-22
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+Failover IP addresses allow you to have several IPs on the server and thus, for example, to have one IP for each website or for each virtual machine.
+
+Your failover IP can be routed at any time to your servers in just a few minutes by using the [Dedibox console](https://console.online.net) or through the [Dedibox API](https://console.online.net/en/api/). By switching your failover IP addresses from one server to another, the hosted services remain available without reconfiguring the IP address.
+
+For each server, you can add failover IP addresses according to the offer and your service level.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server
+
+
+
+1. Click **Server** in your Dedibox console to display a list of your dedicated servers. Then click on the server you want to configure.
+2. On the server's status page, click **Failover** in the menu on the left.
+3. The list of your existing failover IPs displays. Drag and drop your failover IP from the list on the left on the ID of the server you want to use as destination host.
+4. Click **Update** once you finish the failover IP destination configuration.
+
+ The failover IP will be routed to the new destination host within a few minutes.
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-centos.mdx b/pages/dedibox-ip-failover/how-to/configure-centos.mdx
new file mode 100644
index 0000000000..d88f68e57e
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-centos.mdx
@@ -0,0 +1,79 @@
+---
+meta:
+ title: How to configure a Dedibox failover IP on CentOS
+ description: This page explains how to configure a Scaleway Dedibnox failover IP on CentOS.
+content:
+ h1: How to configure a Dedibox failover IP on CentOS
+ paragraph: This page explains how to configure a Scaleway Dedibox failover IP on CentOS.
+tags: dedibox network failover ip failover-ip centos
+dates:
+ validation: 2024-08-05
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on CentOS.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server
+
+## Failover IP configuration using the Network Manager
+
+1. Connect to your server using SSH.
+2. Use the **Network Manager** tool to configure the interface by running the command:
+ ```sh
+ nmtui
+ ```
+
+
+ On older CentOS/RHEL versions, you might be used to configuring the interfaces by adding a new network-scripts file in `/etc/sysconfig/network-scripts/`. This way of configuration has been deprecated starting from CentOS 7 and you should use the Network Manager to avoid configuration issues.
+
+3. From the Network Manager interface, select **Edit a connection** and select the interface you want to add an alias to. Then Click **Edit...**.
+4. Browse through the **Add ...** section to add another IP address.
+5. Enter the details of your failover IP and save the settings to generate the configuration file.
+6. Check the configuration file, to verify that the failover IP address has been added:
+ ```
+ cat /etc/sysconfig/network-scripts/ifcfg-ens192
+ ...
+ # Alias on the interface
+ IPADDR1="62.120.123.123"
+ PREFIX1="32"
+ ```
+
+
+ Replace `ens192` with the name of your network interface.
+
+
+## Manual configuration of a failover IP
+
+
+ On recent versions of CentOS you should always prefer the configuration using the Network Manager tool. Manual configuration is not recommended for newer versions of CentOS (versions released after CentOS 6).
+
+
+1. Connect to your Dedibox using SSH.
+2. Copy the default network configuration of your primary interface to create an alias:
+ ```
+ cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scrits/ifcfg-eth0:0
+ ```
+
+
+ The file `ifcfg-eth0` might be named differently, depending on your network interfaces' name. Use `ifconfig` to determine the name of your network interface.
+
+3. Open the file `/etc/sysconfig/network-scrits/ifcfg-eth0:0` in a text editor, for example, `nano`, and edit it as follows:
+ ```
+ NM_CONTROLLED="no"
+ DEVICE="eth0:0"
+ BOOTPROTO="static"
+ IPADDR="my_failover_ip"
+ NETMASK="255.255.255.255"
+ ONBOOT="yes"
+ ```
+4. Bring up the interface using the following command:
+ ```
+ ifup eth0:0
+ ```
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx b/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx
new file mode 100644
index 0000000000..f528688b98
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx
@@ -0,0 +1,101 @@
+---
+meta:
+ title: How to configure a Dedibox failover IP on Debian and Ubuntu
+ description: This page explains how to configure a Dedibox failover IP on Debian or Ubuntu Linux.
+content:
+ h1: How to configure a Dedibox failover IP on Debian and Ubuntu
+ paragraph: This page explains how to configure a Dedibox failover IP on Debian or Ubuntu Linux.
+tags: failover-failover IP ip debian ubuntu dedibox linux
+dates:
+ validation: 2024-07-22
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on Debian or Ubuntu Linux.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server
+
+## Failover IP configuration on Debian
+
+
+ If you are using Ubuntu 18.04 or later, you should configure the interfaces using [Netplan](/dedibox-network/how-to/configure-network-netplan/).
+
+
+1. Connect to your server using SSH.
+2. Open the network configuration file `/etc/network/interfaces` in a text editor, for example `nano`:
+ ```
+ nano /etc/network/interfaces
+ ```
+3. Add the failover IP to the configuration as shown in the following example:
+ ```
+ # This file describes the network interfaces available on your system
+ # and how to activate them. For more information, see interfaces(5).
+ # The loopback network interface
+ auto lo
+ iface lo inet loopback
+ # The primary network interface
+ auto eth0
+ iface eth0 inet static
+ address 195.154.123.123
+ netmask 255.255.255.0
+ gateway 195.154.123.1
+ auto eth0:0
+ iface eth0:0 inet static
+ address ip_failover
+ netmask 255.255.255.255
+ ```
+
+
+ The interface name `eth0` may vary, depending on your OS version and system configuration. Use the `ifconfig` command to determine the name of your primary network interface.
+
+4. Save the file and exit the editor.
+5. Bring up the interface using the following command:
+ ```
+ ifup eth0:0
+ ```
+
+## Failover IP configuration on Ubuntu
+
+Since the release of version 18.04 (Bionic Beaver) Ubuntu has switched to [Netplan](https://netplan.io/) for the configuration of network interfaces.
+
+It is a YAML-based configuration system, which simplifies the configuration process.
+
+1. Connect to your Dedibox using SSH.
+2. Open the Netplan configuration file of the main interface in a text editor, for example `nano`:
+ ```
+ sudo nano /etc/netplan/01-netcfg.yaml
+ ```
+3. Edit the network configuration. The IP addresses have to be written with their [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). The netmask is `/24` for the principal IP of the server and `/32` for each failover IP. Your configuration should look as in the following example:
+ ```yaml
+ network:
+ renderer: networkd
+ ethernets:
+ ensXX:
+ addresses:
+ - /32
+ routes:
+ - to: 62.210.0.1
+ - to: default
+ via: 62.210.0.1
+ nameservers:
+ addresses:
+ - 51.159.47.28
+ - 51.159.47.26 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+ search: []
+ version: 2
+ ```
+
+ * Make sure to respect the YAML standards when you edit the file, as it might not work if there is a syntax error in your configuration.
+ * You can find an extended list of [netplan configuration examples](https://github.com/canonical/netplan/tree/main/examples) in the official Canonical Netplan repository.
+
+4. Activate the new configuration by running the following command:
+ ```
+ sudo netplan apply
+ ```
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-freebsd.mdx b/pages/dedibox-ip-failover/how-to/configure-freebsd.mdx
new file mode 100644
index 0000000000..ea7c0c6c42
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-freebsd.mdx
@@ -0,0 +1,53 @@
+---
+meta:
+ title: How to configure a failover IP on FreeBSD
+ description: This page explains how to configure a failover IP on Debian or FreeBSD.
+content:
+ h1: How to configure a failover IP on FreeBSD
+ paragraph: This page explains how to configure a failover IP on Debian or FreeBSD.
+tags: dedibox failover-failover IP freebsd
+dates:
+ validation: 2024-10-14
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on FreeBSD.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server
+
+## Failover IP configuration on FreeBSD
+
+1. Connect to your server using SSH.
+2. Open the network configuration file in a text editor, for example `nano`:
+ ```
+ nano /etc/rc.conf
+ ```
+3. Add the following line to the file, replace `FAILOVER_IP` with your failover IP address:
+ ```
+ ifconfig_em0_alias0="inet FAILOVER_IP netmask 255.255.255.255"
+ ```
+
+ Your modified configuration file should look like the following example:
+
+ ```
+ ifconfig_em0="inet IP_ADDRESS netmask 255.255.255.0"
+ defaultrouter="IP_ADDRESS"
+ sshd_enable="YES"
+ ntpd_enable="YES"
+ ntpd_sync_on_start="YES"
+ syslogd_flags="-ss"
+ fsck_y_enable="YES"
+ ifconfig_em0_alias0="inet FAILOVER_IP netmask 255.255.255.255"
+ ```
+4. Save the file and exit the text editor.
+5. Restart the network to activate the new IP address:
+ ```
+ /etc/rc.d/netif restart && /etc/rc.d/routing restart
+ ```
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx b/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx
new file mode 100644
index 0000000000..c5adc1bb5a
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx
@@ -0,0 +1,58 @@
+---
+meta:
+ title: How to configure multi-IP virtual MAC addresses
+ description: This page explains how to configure multi-IP virtual MAC addresses on Scaleway Dedibox.
+content:
+ h1: How to configure multi-IP virtual MAC addresses
+ paragraph: This page explains how to configure multi-IP virtual MAC addresses on Scaleway Dedibox.
+tags: dedibox multi-ip virtual mac
+dates:
+ validation: 2024-08-12
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+You can use the same virtual MAC at several failover IPs pointing on the same dedicated server.
+
+To do this, you need to have several [failover IPs](/dedibox-ip-failover/concepts/#failover-ips) at the same server and at least one [virtual MAC](/dedibox-ip-failover/concepts/#virtual-mac-address) associated with one of these failover IPs.
+
+As long as they share the same virtual MAC, your failover IPs must be moved in a group from one server to another.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server
+- At least 2 [failover IPs](/dedibox-ip-failover/concepts/#failover-ips)
+- Generated a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address)
+
+1. Click **Server** > **Server list** to display a list of your physical machines.
+2. Select the server you want to configure and click **Manage**. The servers' status page displays.
+3. Scroll down to the network configuration section and click **+ Info** next to the failover IP you want to configure. The advanced configuration displays.
+4. Click **Add virtual MAC**. The virtual MAC configuration displays. Click **Edit** to display the virtual MAC address page.
+5. Click the settings icon (cogwheel) next to the failover IP address that you want to add to a multi-IP MAC address group. A pop-up menu displays. Click **Use an existing MAC address**.
+6. Select the MAC address to clone in the pop-up and click **OK** to validate.
+
+ The failover IP now uses the same MAC address as the origin failover IP.
+
+
+ Failover IPs sharing the same MAC address have to point to the same dedicated server. In the failover IP configuration interface, they appear as a group and can not be moved individually.
+
+
+## How to delete a failover IP from a multi-IP virtual MAC group
+
+You can remove a failover IP from a multi-IP virtual MAC group if you do not require it any longer.
+
+
+ When you decide to delete a virtual MAC address associated with an IP address that shares the same virtual MAC with other IPs, only the connection between that particular IP address and the MAC is removed. The other IP addresses remain unaffected and are not modified.
+
+
+1. Click **Server** > **Server list** to display a list of your physical machines.
+2. Select the server you want to configure and click **Manage**. The servers' status page displays.
+3. Scroll down to the network configuration section and click **+ Info** next to the failover IP you want to configure. The advanced configuration displays.
+4. Click **Edit**. The virtual MAC configuration displays.
+5. Click the settings icon (cogwheel) next to the IP address you want to configure. Then click **Delete virtual MAC address**.
+
+ The failover IP will be removed from the group. All other IPs within the group remain configured.
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx b/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx
new file mode 100644
index 0000000000..a97bfc4f22
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx
@@ -0,0 +1,145 @@
+---
+meta:
+ title: How to configure the network of a virtual machine on a Dedibox host
+ description: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server.
+content:
+ h1: How to configure the network of a virtual machine on a Dedibox host
+ paragraph: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server.
+tags: dedibox network virtual-machine virtual machine ubuntu debian centOS windows-server
+dates:
+ validation: 2024-07-22
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+When you install your server with a virtualization solution like Proxmox, you can create multiple virtual machines on the physical server. This setup allows you to have separate environments for different services (e.g., mail and web services) or to optimize the server's performance by running several virtual machines.
+
+To communicate on the internet, each of your virtual machines needs an IP address. You can use failover IPs to have additional IP addresses available for your server.
+
+
+ You can configure a unique gateway for your virtual machines, allowing them to move between hypervisors without changing their network configuration.
+
+ * IP address of the unique gateway: `62.210.0.1`
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server and installed a hypervisor on it
+- Ordered a [failover IP](/dedibox-ip-failover/concepts/#failover-ips)
+- Generated a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address)
+
+Find below examples of network interface configurations on different distributions inside a virtual machine:
+
+## Ubuntu
+
+Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for configuring network interfaces. For older releases, refer to the Debian configuration.
+
+1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice, for example `nano`:
+ ```
+ sudo nano /etc/netplan/01-netcfg.yaml
+ ```
+2. Create a network configuration as follows. Replace `fail.over.ip.address` with your failover IP address:
+ ```yaml
+ network:
+ ethernets:
+ ens18:
+ addresses:
+ - [ "fail.over.ip.address/32" ]
+ nameservers:
+ addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+ routes:
+ - to: default
+ via: 62.210.0.1
+ - to: 62.210.0.1/32
+ via: fail.over.ip.address
+ scope: link
+ version: 2
+ ```
+3. Save the file and exit the text editor.
+4. Apply the new configuration:
+ ```
+ sudo netplan apply
+ ```
+
+## Debian
+
+1. Log into the virtual machine and edit the file `/etc/network/interfaces` with a text editor of your choice, for example, `nano`:
+ ```
+ sudo nano /etc/network/interfaces
+ ```
+2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address:
+ ```
+ auto eth0
+ iface eth0 inet static
+ address fail.over.ip.address
+ netmask 255.255.255.255
+ pointopoint 62.210.0.1
+ gateway 62.210.0.1
+ ```
+3. Save the file and exit the text editor.
+4. Set the DNS server information by editing the file `/etc/resolv.conf`:
+ ```
+ sudo nano /etc/resolv.conf
+ ```
+5. Set the DNS resolver by adding the following lines to the file. Then save it and exit the text editor:
+ ```
+ nameserver 51.159.47.28
+ nameserver 51.159.47.26
+ ```
+
+ Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers)
+
+6. Activate the network on your virtual machine by running:
+ ```
+ sudo ifup eth0
+ ```
+
+## CentOS
+
+1. Log into the virtual machine and edit the file `/etc/sysconfig/network-scripts/ifcfg-eth0` with a text editor of your choice, for example, `nano`:
+ ```
+ sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0
+ ```
+2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address and `virtual:mac:address` with the virtual MAC of the VM:
+ ```
+ DEVICE=eth0
+ BOOTPROTO=none
+ ONBOOT=yes
+ USERCTL=no
+ IPV6INIT=no
+ PEERDNS=yes
+ TYPE=Ethernet
+ NETMASK=255.255.255.255
+ IPADDR=fail.over.ip.address
+ GATEWAY=62.210.0.1
+ DNS1=51.159.47.28 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+ DNS2=51.159.47.26
+ ARP=yes
+ HWADDR=virtual:mac:address
+ ```
+3. Save the file and close the text editor.
+4. Edit the file `/etc/sysconfig/network-scripts/route-eth0` as follows, then save and exit the text editor:
+ ```
+ 62.210.0.1 dev eth0
+ default via 62.210.0.1 dev eth0
+ ```
+5. Run the following command to bring the network interface up:
+ ```
+ sudo ifup eth0
+ ```
+
+## Windows Server
+
+1. Connect to the desktop of your VM in the virtual console, then open the network settings of your server.
+2. Enter the following information in the network adapter configuration:
+ * Address: failover IP
+ * Subnetmask: `255.255.255.255`
+ * Gateway: `62.210.0.1`
+ * DNS 1: `51.159.47.28`
+ * DNS 2: `51.159.47.26`
+
+
+ Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers)
+
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx b/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx
new file mode 100644
index 0000000000..df15d2a2d2
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to configure the reverse DNS of a Dedibox failover IP
+ description: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle.
+content:
+ h1: How to configure the reverse DNS of a Dediboxfailover IP
+ paragraph: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle.
+tags: dedibox dns failover-ip failover
+dates:
+ validation: 2024-07-22
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+Failover IP addresses allow you to have several IP addresses with your server. This allows you to assign IP addresses to different websites or to virtual machines.
+
+Your failover IP can be routed at any time to your servers in just a few minutes by using our Account Management console or through our API. By switching your failover IP addresses from one server to another, the hosted services remain available without reconfiguring the IP address.
+
+You can add a failover IP address(es) for each server according to the offer and your service level.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+
+1. From your Scaleway console, click **Server** > **Network configuration**. The list of your failover IPs and IP blocks displays.
+
+2. Click **Edit reverses**. The list of your reverse DNS settings displays.
+3. Enter the new reverse DNS record and click **Update**.
+
+
+
+ Make sure to have a valid **[A record](/dedibox-dns/concepts/#dns-record)** for forwarding DNS configured and pointing to your IP address before changing the reverse DNS of it.
+
+
+
diff --git a/pages/dedibox-ip-failover/how-to/configure-windows.mdx b/pages/dedibox-ip-failover/how-to/configure-windows.mdx
new file mode 100644
index 0000000000..b454f3a644
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/configure-windows.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to configure a Dedibox failover IP on Windows Server 2019
+ description: Learn how to configure a Scaleway Dedibox failover IP on Windows Server 2019.
+content:
+ h1: How to configure a Dedibox failover IP on Windows Server 2019
+ paragraph: Learn how to configure a Scaleway Dedibox failover IP on Windows Server 2019.
+tags: dedibox failover-ip windows server windows-server-2019
+dates:
+ validation: 2024-07-22
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on Windows Server 2019.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+
+1. Log into your Dedibox using the **Remote Desktop** client.
+2. Open the start menu and type **Ethernet settings**. The Ethernet window displays.
+
+3. Click **Change adapter options**. The network connections window displays.
+4. Right-click on the internet connection. Then click **Properties** in the pop-up menu.
+5. Select **Internet Protocol version 4 (TCP/IPv4)** in the list of connection items and click **Properties**.
+6. Enter the static configuration of the principal IP address of the server. Then click **Advanced**. The advanced configuration window displays.
+
+7. Click **Add**. Then enter the configuration details for the failover IP. Finally, click **Add**.
+
+8. Click **OK** to close the advanced configuration window. Then click **OK** to validate the IP configuration and to close the Ethernet configuration windows.
+
+
diff --git a/pages/dedibox-ip-failover/how-to/create-virtual-mac.mdx b/pages/dedibox-ip-failover/how-to/create-virtual-mac.mdx
new file mode 100644
index 0000000000..5eda8824b0
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/create-virtual-mac.mdx
@@ -0,0 +1,79 @@
+---
+meta:
+ title: How to create a virtual MAC address for a Scaleway Dedibox failover IP
+ description: This page explains how to create a virtual MAC address for a Scaleway Dedibox failover IP.
+content:
+ h1: How to create a virtual MAC address for a Scaleway Dedibox failover IP
+ paragraph: This page explains how to create a virtual MAC address for a Scaleway Dedibox failover IP.
+tags: mac failover-ip briged nated network dedibox mac-address virtual mac
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+Virtualization requires, in most cases, that you configure additional IP addresses on your dedicated server to provide network connectivity to your virtual machines.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- Ordered a [failover IP](/dedibox-ip-failover/concepts/#failover-ips)
+
+
+
+In general, two connectivity modes are possible for the networking of virtual machines:
+
+* Bridge
+* NAT
+
+### Bridged network
+
+In bridge mode, the network equipment sees your server and your virtual machines as different servers.
+
+For security reasons, no other network equipment is allowed on our network, except for the MAC address of your physical network card.
+
+If you start a virtual machine in bridge mode, protection will be activated on the switch, and your network port will be closed.
+
+You can add virtual MAC addresses known and allowed on the network to solve this problem.
+
+### NATed network
+
+In this network setup, all of your virtual machines are assigned the same public IP address through a NAT configuration. This arrangement makes your physical server and its virtual machines appear as a unified entity. The only MAC address that is broadcasted on the network is that of your physical network card.
+As a result, there is no need for individual virtual MAC addresses in this configuration.
+
+## How to add a virtual MAC address
+
+1. Click **Server** > **Server list** to display a list of your physical machines.
+2. Select the server you want to configure and click **Manage**. The servers' status page displays.
+3. Scroll down to the network configuration section and click **+ Info** next to the failover IP you want to configure. The advanced configuration displays.
+4. Click **Add virtual MAC**. The virtual MAC configuration displays.
+5. Click the settings icon (cogwheel) next to the IP address you want to configure. Then select the type of MAC address and click **Add ... virtual MAC address**.
+
+ Each MAC address is associated with a manufacturer/organization. We provide virtual MAC addresses from the following Organizationally Unique Identifier (OUI):
+ * OUI VMWare: `00:50:56`
+ * OUI Xen: `00:16:3e`
+ * OUI KVM: `52:54:00`
+ You can choose the OUI of your preference. They are technically interchangeable.
+
+
+Once the virtual MAC is activated, use it to configure the network of your VM.
+
+## How to delete a virtual MAC address
+
+You can remove the virtual MAC address associated to a failover IP if you do not require it any longer.
+
+
+ If you delete a virtual MAC address that is shared by different IPs, this action will only affect the selected MAC address and IP. Any other IPs will remain as they are.
+
+
+1. Click **Server** > **Server list** to display a list of your physical machines.
+2. Select the server you want to configure and click **Manage**. The servers' status page displays.
+3. Scroll down to the network configuration section and click **+ Info** next to the failover IP you want to configure. The advanced configuration displays.
+4. Click **Edit**. The virtual MAC configuration displays.
+5. Click the settings icon (cogwheel) next to the IP address you want to configure. Then click **Delete virtual MAC address**.
+
+ The configuration of the failover IP will be updated, and the virtual MAC address will be deleted.
+
+
diff --git a/pages/dedibox-ip-failover/how-to/index.mdx b/pages/dedibox-ip-failover/how-to/index.mdx
new file mode 100644
index 0000000000..ec0de8a780
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Failover IP - How Tos
+ description: Failover IP How Tos
+content:
+ h1: Failover IP - How Tos
+ paragraph: Failover IP How Tos
+---
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/how-to/order-failover-ip.mdx b/pages/dedibox-ip-failover/how-to/order-failover-ip.mdx
new file mode 100644
index 0000000000..94c4ff9d4e
--- /dev/null
+++ b/pages/dedibox-ip-failover/how-to/order-failover-ip.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to order a Dedibox failover IP
+ description: Learn how to order a failover IP for Dedibox servers.
+content:
+ h1: How to order a Dedibox failover IP
+ paragraph: This guide explains how to order a failover IP for Dedibox servers.
+tags: dedibox, failover-ip, failover
+dates:
+ validation: 2024-08-05
+ posted: 2021-07-29
+categories:
+ - dedibox-network
+---
+
+Failover IP addresses allow you to have multiple IPs on a server, enabling you to assign a unique IP to each website or virtual machine.
+Each failover IP can be routed to your servers at any time in just a few minutes using our Account Management Console or API.
+By switching a failover IP addresses from one server to another, your hosted services remain available without the need to reconfigure the IP address.
+
+
+ - For each server, you can add failover IP addresses according to your service plan and service level.
+ - Dedibox failover IPs are compatible only with Dedibox servers and cannot be assigned to other products such as Elastic Metal servers or Instances.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+
+
+
+### How to order a failover IP for Dedibox servers
+
+1. In your [Dedibox console](https://console.online.net/), click **Server** to display a list of your dedicated servers. Then click on the server you want to configure.
+2. On the server's status page, click **Failover** in the menu on the left.
+3. The list of your existing failover IPs will display. Scroll to the bottom of the page and click **Order IP addresses**.
+4. Select either an IP block or an individual IP address and click **Command failover IP block** or **Command failover IP** for individual IPs.
+5. Confirm the order by clicking **Order**.
+
+ Failover IPs and failover IP blocks are paid options. They come with a **monthly** service charge and a **one-time** setup fee.
+
+
+The failover IP is now available in your account, and you can [assign it to your Dedibox server](/dedibox-ip-failover/how-to/assign-failover-ip/).
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/index.mdx b/pages/dedibox-ip-failover/index.mdx
new file mode 100644
index 0000000000..69e4f13b58
--- /dev/null
+++ b/pages/dedibox-ip-failover/index.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: Dedibox - Failover IP Documentation
+ description: Dive into Scaleway Dedibox - Failover IP with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/dedibox-ip-failover/quickstart.mdx b/pages/dedibox-ip-failover/quickstart.mdx
new file mode 100644
index 0000000000..eaf67f3c01
--- /dev/null
+++ b/pages/dedibox-ip-failover/quickstart.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: Failover IP - Quickstart
+ description: This page provides a quickstart guide for failover IP for Dedibox servers.
+content:
+ h1: Failover IP - Quickstart
+ paragraph: This page provides a quickstart guide for failover IP for Dedibox servers.
+tags: dedibox failover-failover IP ip
+categories:
+ - dedibox-network
+---
+
+Failover IPs are IP addresses you can order and move from one server to another (even across data centers), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and keep your services available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+
+
+
+## How to order a failover IP
+
+1. Click **Server** in your Dedibox console to display a list of your dedicated servers. Then click on the server you want to configure.
+2. On the server's status page, click **Failover** in the menu on the left.
+3. The list of your existing failover IPs displays. Scroll to the bottom of the page and click **Order IP addresses**.
+4. Select either an IP block or individual IP address and click **Command failover IP block** or **Command failover IP** for individual IPs.
+5. Confirm the order by clicking **Order**.
+
+## How to assign a failover IP
+
+1. Click **Server** in your Dedibox console to display a list of your dedicated servers. Then click on the server you want to configure.
+2. On the server's status page, click **Failover** in the menu on the left.
+3. The list of your existing failover IPs displays. Drag and drop your failover IP from the list on the left to the ID of the server you want to use as destination host.
+4. Click **Update** once you finish the failover IP destination configuration.
+
+ The failover IP will be routed to the new destination host within a few minutes.
+
+## How to configure a failover IP
+
+We provide a series of dedicated how-to's about the configuration of failover IPs on your Dedibox server:
+
+* [How to configure a failover IP on CentOS](/dedibox-ip-failover/how-to/configure-centos/)
+* [How to configure a failover IP on Debian/Ubuntu](/dedibox-ip-failover/how-to/configure-debian-ubuntu/)
+* [How to configure a failover IP on FreeBSD](/dedibox-ip-failover/how-to/configure-freebsd/)
+* [How to configure a failover IP on Windows Server](/dedibox-ip-failover/how-to/configure-windows/)
+* [How to configure the network of a virtual machine](/dedibox-ip-failover/how-to/configure-network-virtual-machine/).
\ No newline at end of file
diff --git a/pages/dedibox-ipv6/concepts.mdx b/pages/dedibox-ipv6/concepts.mdx
new file mode 100644
index 0000000000..2bca16045f
--- /dev/null
+++ b/pages/dedibox-ipv6/concepts.mdx
@@ -0,0 +1,53 @@
+---
+meta:
+ title: Scaleway Dedibox IPv6 - Concepts
+ description: This page explains all the concepts related to IPv6 on Scaleway Dedibox
+content:
+ h1: Scaleway Dedibox IPv6 - Concepts
+ paragraph: This page explains all the concepts related to IPv6 on
+tags: dedibox ipv6 duid dhcpv6 ipv4 slaac stateful stateless dhcp
+dates:
+ validation: 2024-09-02
+categories:
+ - dedibox-network
+---
+
+## DHCPv6
+
+**D**ynamic **H**ost **C**onfiguration **P**rotocol **V**ersion **6** (DHCPv6) is a network management protocol for dynamically assigning IPv6 addresses and other configuration parameters to clients on IPv6 networks. It represents a complete redesign of the functionalities of "classic" v4 DHCP, and comes in three different options: SLAAC, Stateless, and Stateful.
+
+## DUID
+
+Each DHCP client and server has a **D**HCP **U**nique **I**dentifier (DUID). DHCPv6 servers use the DUID to identify clients when assigning IPv6 addresses and other configuration parameters. DUIDs are made up of a 2-octet DUID type field, and a variable-length identifier field of up to 128 bytes. Four types of DUID are identified in [RFC 8415](https://tools.ietf.org/html/rfc8415):
+_ Link-layer address (MAC address) plus time (DUID-LLT)
+_ Vendor-assigned unique ID based on enterprise number (DUID-EN)
+_ Link-layer address (MAC address) (DUID-LL)
+_ UUID-based DUID (DUID-UUID)
+
+## IP Address
+
+An **I**nternet **P**rotocol address is a unique address that identifies a device on the internet or a local network. Generally, when we talk about IP addresses, we are referring to IPv4 addresses. However, due to the global shortage of IPv4 addresses, IPv6 addresses have also been in deployment since the mid-2000s.
+
+## IPv4
+
+**I**nternet **P**rotocol **V**ersion **4** is the standard protocol used for IP addresses and routes most internet traffic as of today. Each IPv4 address has 32 bits. Written in human-readable form, an IPv4 address is generally shown as four octets of numbers separated by periods, e.g. `72.16.254.1`
+
+## IPv6
+
+**I**nternet **P**rotocol **V**ersion **6** is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. Alternatively, `2001:DB8::3:0:1FF:0:2E`. Dedibox network is wholly IPv6 compatible. IPv6 can be used as the main IP of your server, and also as an [IP failover](/dedibox-ip-failover/concepts/#failover-ips) using the principle of [virtual MAC](/dedibox-ip-failover/concepts/#virtual-mac-address).
+
+## Neighbor Discovery Protocol
+
+The Neighbour Discovery Protocol (NDP) allows devices to discover neighbors, routers, prefixes, and other services on a Layer 3 network. When a client first comes online, it sends a Router Solicitation message, and if a router exists on the network it replies with a Router Advertisement message. From this message, the client learns the default gateway (the address of the router) and the global network prefix.
+
+## SLAAC
+
+**S**tateless **A**uto **A**ddress **C**onfiguration is the simplest way to assign IP addresses in an IPv6 network. Using the [Neighbor Discovery Protocol](/dedibox-ipv6/concepts/#neighbor-discovery-protocol), devices request the network prefix from the router, and then use this prefix and their own MAC address to create an IPv6 address.
+
+## Stateful DHCPv6
+
+With [stateful DHCPv6](/dedibox-ipv6/concepts/#stateful-dhcpv6), it is the DHCPv6 server that chooses and assigns IPv6 addresses to clients, unlike with [SLAAC](/dedibox-ipv6/concepts/#slaac) or [Stateless DHCPv6](/dedibox-ipv6/concepts/#stateless-dhcpv6) where the client creates their own IPv6 address. Stateful DHCPv6 is so-called because the DHCPv6 server keeps track of the state of IPv6 addresses on the network.
+
+## Stateless DHCPv6
+
+[Stateless DHCPv6](/dedibox-ipv6/concepts/#stateless-dhcpv6) involves the initial use of [SLAAC](/dedibox-ipv6/concepts/#slaac) by a client to create its own IPv6 address, followed by an extra DHCPv6 request to get extra details from the DHCPv6 server, such as DNS server or domain name information. Stateful DHCPv6 is so-called because no server or client is keeping track of the overall state of IPv6 addresses on the network.
\ No newline at end of file
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_config_win.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_config_win.webp
new file mode 100644
index 0000000000..87ba82ed4d
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_config_win.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_list.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_list.webp
new file mode 100644
index 0000000000..b621c3c803
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_list.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_ping6_win.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_ping6_win.webp
new file mode 100644
index 0000000000..e0b91bbe54
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_ping6_win.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit.webp
new file mode 100644
index 0000000000..15f93c3496
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit_edit.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit_edit.webp
new file mode 100644
index 0000000000..5c7f7ff6f2
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_regedit_edit.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_slaac.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_slaac.webp
new file mode 100644
index 0000000000..061fd29b67
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_ipv6_slaac.webp differ
diff --git a/pages/dedibox-ipv6/how-to/assets/scaleway_order_ipv6.webp b/pages/dedibox-ipv6/how-to/assets/scaleway_order_ipv6.webp
new file mode 100644
index 0000000000..32b73824d9
Binary files /dev/null and b/pages/dedibox-ipv6/how-to/assets/scaleway_order_ipv6.webp differ
diff --git a/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx b/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx
new file mode 100644
index 0000000000..391b92dd73
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx
@@ -0,0 +1,129 @@
+---
+meta:
+ title: How to configure IPv6 connectivity using systemd-networkd
+ description: This page explains how to configure IPv6 connectivity on a Scaleway Dedibox using systemd-networkd.
+content:
+ h1: How to configure IPv6 connectivity using systemd-networkd
+ paragraph: This page explains how to configure IPv6 connectivity on a Scaleway Dedibox using systemd-networkd.
+tags: dedibox ipv6 systemd-networkd
+dates:
+ validation: 2024-10-21
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix
+
+
+ Follow the IPv6 on Ubuntu configuration if you are on Ubuntu and use Netplan as your default network manager.
+ Follow the IPv6 on Linux configuration with systemd-networkd if you are on another Linux distribution or prefer to use directly systemd-networkd on Ubuntu.
+
+
+## How to configure IPv6 on Ubuntu
+
+Ubuntu uses [netplan](https://netplan.io) since the release of Ubuntu 18.04 LTS as network configuration tool.
+It replaces the classical network configuration with new configuration files, written in [YAML](https://yaml.org) format, and located in the `/etc/netplan` directory. For more information regarding netplan, refer to the official [documentation](https://netplan.readthedocs.io/en/stable/).
+
+1. Open the default configuration file `/etc/netplan/01-netcfg.yaml` in a text editor, and edit it as follows:
+ ```yaml
+ # This file describes the network interfaces available on your system
+ # For more information, see netplan(5).
+ network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ enp1s0:
+ dhcp4: no
+ dhcp6: no
+ addresses:
+ - "aaa.bbb.ccc.ddd/24" # The main IP address of your Dedibox server
+ - "2001:bc8:xxxx:xxx::x/64" # An IP address from your IPv6 block and its subnet mask /64, replace placeholder values
+ gateway4: aaa.bbb.ccc.1 # The gateway is the IPv4 address of your Dedibox, ending on .1
+ nameservers:
+ addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+ routes:
+ - to: 0.0.0.0
+ via: aaa.bbb.ccc.1
+ on-link: true
+ ```
+
+ Remember to replace `enp1s0` with the proper name of your internet interface.
+
+
+ The configuration example above is valid for the main IP address of your Dedibox server. If you want to use IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), remember to use the unique gateway for the failover IPv4.
+
+2. Check and validate your configuration file.
+ ```
+ sudo netplan –debug
+ ```
+3. Activate the new configuration:
+ ```
+ sudo netplan apply
+ ```
+
+## How to configure IPv6 on Linux with systemd-networkd
+
+`systemd-networkd` is the network manager of [systemd](https://systemd.io/). It is provided natively on most Linux distributions and can be used for the configuration of IPv6 with its DHCPv6 client feature.
+
+
+ When specifying the IP address of your Dedibox, you need to enter it in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing). The netmask for the main IPv4 of a Dedibox server is `/24`, the netmask for a failover IPv4 is `/32`. The netmask for the IPv6 is `/64`.
+
+
+1. Run the `ip link show` command to find the name of your public internet interface. Make sure to store it, as it will be required in the next steps.
+2. Run the following command to create a backup of the current network configuration and configure `systemd-networkd`:
+ ```
+ sudo mv /etc/systemd/network/eno1.network /etc/systemd/network/eno1.network.bkp
+ ```
+3. Run the following command to enable `systemd-networkd`.
+ ```
+ systemctl enable systemd-networkd.service
+ ```
+4. Create a new file called `.network` and open it in a text editor.
+ ```
+ sudo nano /etc/systemd/network/eno1.network
+ ```
+5. Open the file in a text editor and paste the following content. Make sure to replace the values in the example with your own and save them before exiting the text editor.
+ ```
+ [Match]
+ #The name must correspond to your interface name
+ Name=eno1
+
+ [Network]
+ DHCP=ipv6
+ IPv6AcceptRA=yes
+ # IPv4 of the Dedibox, change netmask to /32 if failover IPv4
+ Address=/24
+ # IPv6 of the Dedibox
+ Address=2001:bc8:xxxx:xxx::x/64
+
+ [Route]
+ # The IPv4 gateway is either your Dedibox IP ending on .1 (i.e. x.y.z.1) for the physical host or 62.210.0.1 for any VM running on a Dedibox
+ Gateway=
+ GatewayOnlink=yes
+
+ [DHCP]
+ ClientIdentifier=duid-only
+ DUIDType=link-layer
+ # Scaleway Dedibox DUID without the DUID-LL "00:03" at the beginning
+ DUIDRawData=
+
+ [DHCPv6]
+ UseAddress=no
+ WithoutRA=solicit
+
+ [IPv6AcceptRA]
+ DHCPv6Client=always
+ UseOnLinkPrefix=False
+ UseAutonomousPrefix=False
+ ```
+10. Run the following command to activate the new configuration.
+ ```
+ systemctl start systemd-networkd
+ ```
+
+
diff --git a/pages/dedibox-ipv6/how-to/configure-ipv6-windows.mdx b/pages/dedibox-ipv6/how-to/configure-ipv6-windows.mdx
new file mode 100644
index 0000000000..19c1b1608f
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/configure-ipv6-windows.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: How to configure an IPv6 subnet on a Dedibox running Windows Server
+ description: This page explains how to configure an IPv6 subnet on a Dedibox running Windows Server.
+content:
+ h1: How to configure an IPv6 subnet on a Dedibox running Windows Server
+ paragraph: This page explains how to configure an IPv6 subnet on a Dedibox running Windows Server.
+tags: dedibox ipv6 windows subnet
+dates:
+ validation: 2024-12-03
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix
+
+
+ * On servers supporting [IPv6 SLAAC](/dedibox-ipv6/how-to/enable-ipv6-slaac/), SLAAC has to be enabled in order to ensure that DHCPv6 works correctly.
+ * This documentation addresses the setup of a /48 IPv6 network on your Dedibox. If you intend to use only the SLAAC IP address, no additional configuration is necessary, and your machine can acquire its IP address automatically.
+
+
+## How to set the DUID in the Windows Registry
+
+
+ Modifying values in the Windows Registry may cause damage to your installation. Be careful when editing these settings.
+
+
+1. Launch the **Registry Editor** by typing `regedit.exe` in the start menu:
+
+2. Scroll down until you reach the following setting: `HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\TCPIP6\Parameters` and edit the value `Dhcpv6DUID` with the DUID of your block by double clicking on the default value:
+
+
+## How to configure IPv6 connectivity
+
+1. Go to your network settings, and double-click on your internet connection.
+2. Open the connection details and enter the IPv6 settings. Set the IP of the machine to an IPv6 address of your subnet and the netmask:
+
+3. Once you have saved the configuration, open a terminal and test the connection by running a `ping -6 google.com` or `tracert -6 google.com`:
+
+
+
diff --git a/pages/dedibox-ipv6/how-to/create-subnet.mdx b/pages/dedibox-ipv6/how-to/create-subnet.mdx
new file mode 100644
index 0000000000..a4e0e67092
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/create-subnet.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to create an IPv6 subnet
+ description: This page explains how to create an IPv6 subnet for Scaleway Dedibox servers.
+content:
+ h1: How to create an IPv6 subnet
+ paragraph: This page explains how to create an IPv6 subnet for Scaleway Dedibox servers.
+tags: dedibox ipv6 subnet
+dates:
+ validation: 2024-08-12
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+You can split your IPv6 prefix into several subnets and use them on your Dedibox servers both in Paris and Amsterdam. Each subnet has its own [DUID](/dedibox-ipv6/concepts/#duid) and can be configured individually.
+
+
+ * You can create as many /56 subnets as you have servers.
+ * You can create as many /64 subnets as you have failover IPs.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix
+
+1. Click **Server** > **Network configuration** in the Dedibox console. The network configuration pages displays. Scroll down to the IPv6 network configuration section.
+2. Click the settings icon (cogwheel) next to your `/48` prefix. Then click **Create subnet**.
+
+3. Select the subnet you want to create from the drop-down list. Then click **Create subnet**.
+
+ The subnet is created and visible in the list of your IPv6 subnets along with its DUID.
+
+
+ To create `/64` networks for virtual machines, repeat the steps above by clicking on the "cogweel" icon next to the `/56` subnet.
+
+
+
diff --git a/pages/dedibox-ipv6/how-to/debug-ipv6.mdx b/pages/dedibox-ipv6/how-to/debug-ipv6.mdx
new file mode 100644
index 0000000000..8a882cc51d
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/debug-ipv6.mdx
@@ -0,0 +1,105 @@
+---
+
+meta:
+ title: How to resolve IPv6 connection issues on Dedibox servers
+ description: Learn how to troubleshoot and resolve common IPv6 connection issues on your Dedibox server with our step-by-step guide.
+content:
+ h1: How to resolve IPv6 connection issues on Dedibox servers
+ paragraph: Learn how to troubleshoot and resolve common IPv6 connection issues on your Dedibox server with our step-by-step guide.
+tags: dedibox ipv6
+dates:
+ validation: 2024-07-30
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+- A [requested /48 IPv6 prefix](/dedibox-ipv6/how-to/request-prefix/)
+- Configured the `systemd-networkd` [DHCPv6 client](/dedibox-ipv6/how-to/configure-ipv6-linux/)
+
+
+## How to debug IPv6 connection issues from rescue mode
+
+If you experience IPv6 connection issues, you can test the network connectivity from [rescue mode](/dedicated-servers/how-to/use-rescue-mode/).
+
+To test IPv6 connectivity on your server in rescue mode, reboot the server into "Ubuntu rescue" mode. The `dhclient` is preinstalled in these images.
+
+1. Get the name of your internet interface using the following command:
+ ```bash
+ ip address show
+ ```
+2. Create a file to contain your DUID. The DUID is a unique "key" allowing access to your IPv6 prefix. You can find your DUID in your console.
+ ```bash
+ sudo nano /etc/dhcp/dhclient6.conf
+ ```
+3. Paste the following code into the file, editing the interface name (here `eno1`) and the DUID (here `DUID`) before saving the file and exiting the editor:
+ ```conf
+ interface "eno1" {
+ send dhcp6.client-id DUID;
+ }
+ ```
+4. Start the DHCPv6 client using the configuration file you created. Replace `eno1` with the name of your internet interface:
+ ```bash
+ dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
+ ```
+5. Add an IPv6 address to your network interface. Replace `eno1` with the name of your internet interface and `IPV6ADDRESS/PREFIXLENGTH` with an IPv6 address from your prefix and the length of your prefix:
+ ```bash
+ /sbin/ifconfig eno1 inet6 add IPV6ADDRESS/PREFIXLENGTH
+ ```
+6. Use `ping6` to validate the IPv6 connectivity of your server:
+ ```bash
+ ping6 ipv6.google.com
+ ```
+
+## How to debug IPv6 connection issues in normal mode
+
+If you experience IPv6 connection issues, start by verifying the internet interface name in your configuration. You can check the names of your interfaces using the following command:
+```bash
+ip address show
+```
+
+Additionally, your server needs to be configured to accept RA (Router Advertisement). By default, your server will not forward packets from one interface to another if it is automatically configured (through DHCPv6).
+
+If you need to forward IPv6 packets and use an automated configuration, set `net.ipv6.conf.all.accept_ra` to `2` in `/etc/sysctl.conf`. This is useful for hypervisor hosts such as Proxmox.
+
+## Additional methods to debug IPv6 connection issues
+
+### Check IPv6 route table
+Ensure that your server has the correct IPv6 routes. Use the following command to check the IPv6 route table:
+```bash
+ip -6 route show
+```
+Look for default routes and specific routes to your IPv6 network.
+
+### Check the Neighbor Discovery Protocol (NDP)
+Check the neighbor cache to ensure proper communication with the router:
+```bash
+ip -6 neigh show
+```
+
+### Use traceroute6 for path analysis
+Analyze the path to an external IPv6 address to identify where the connection might be failing:
+```bash
+traceroute6 ipv6.google.com
+```
+
+### Capture IPv6 traffic with tcpdump
+Capture and analyze IPv6 traffic to troubleshoot issues:
+```bash
+tcpdump -i eno1 -nnvvS ip6
+```
+Replace `eno1` with your network interface name.
+
+## How to avoid DHCPv6 floods
+
+In some cases, certain DHCPv6 clients may send several requests per second (especially `dhcp6c`). This can trigger blocking of your server's network port by our automatic protection, as it will be seen as a source of a UDP flood.
+
+To avoid this problem, limit the traffic sent from your `dhclient6` directly in your firewall configuration. Here is an example for IPTABLES:
+```bash
+ip6tables -A OUTPUT -p udp --dport 547 -m limit --limit 10/min --limit-burst 5 -j ACCEPT
+ip6tables -A OUTPUT -p udp --dport 547 -j DROP
+```
\ No newline at end of file
diff --git a/pages/dedibox-ipv6/how-to/enable-ipv6-slaac.mdx b/pages/dedibox-ipv6/how-to/enable-ipv6-slaac.mdx
new file mode 100644
index 0000000000..ef20df316f
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/enable-ipv6-slaac.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to enable IPv6 SLAAC on Dedibox servers
+ description: This page explains how to enable IPv6 SLAAC on Dedibox servers.
+content:
+ h1: How to enable IPv6 SLAAC on Dedibox servers
+ paragraph: This page explains how to enable IPv6 SLAAC on Dedibox servers.
+tags: dedibox slaac ipv6
+dates:
+ validation: 2024-12-03
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+Enabling IPv6 SLAAC assigns a single `/128` IPv6 prefix to your server, providing one usable IPv6 address. This IP is statically linked to your server and cannot be attributed to another server.
+
+
+ This feature is not yet available for all servers. Only compatible servers will show the related button.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+1. Click **Server** > **Server list** to display a list of all your servers.
+2. Click **Manage** next to the server you want to configure. The server's status page displays.
+3. Scroll down to the servers network section and click **Activate IPv6 SLAAC**:
+
+
+Your server's IPv6 SLAAC is now activated and displays in the network section.
+
+
+ If required, you can disable your server's IPv6 SLAAC by clicking on the button **Disable IPv6 SLAAC**.
+
+
+
diff --git a/pages/dedibox-ipv6/how-to/index.mdx b/pages/dedibox-ipv6/how-to/index.mdx
new file mode 100644
index 0000000000..ae06509e4c
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: IPv6 - How Tos
+ description: IPv6 How Tos
+content:
+ h1: IPv6 - How Tos
+ paragraph: IPv6 How Tos
+---
diff --git a/pages/dedibox-ipv6/how-to/request-prefix.mdx b/pages/dedibox-ipv6/how-to/request-prefix.mdx
new file mode 100644
index 0000000000..7319bb368a
--- /dev/null
+++ b/pages/dedibox-ipv6/how-to/request-prefix.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: How to request an IPv6 prefix
+ description: This page explains how to request a free /48 IPv6 prefix for Dedibox servers.
+content:
+ h1: How to request an IPv6 prefix
+ paragraph: This page explains how to request a free /48 IPv6 prefix for Dedibox servers.
+tags: dedibox ipv6 prefix
+dates:
+ validation: 2024-12-03
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+All Scaleway Dedibox dedicated servers support IPv6. You can request a free `/48` IPv6 prefix for your account, which can be divided into multiple `/56` or `/64` subnets. IPv6 support is available for all Dedibox servers.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+
+1. Click **Server** > **Network configuration** in the Dedibox console. The network configuration page displays.
+2. Scroll to the bottom of the page and click **Order a free /48 IPv6 block**:
+
+
+The IPv6 prefix is delivered within 30 minutes and is visible on the network configuration page.
+
+
+ You need to have at least one Dedibox dedicated server to order an IPv6 prefix.
+
+
+
+ The DUID (DHCP Unique Identifier) of your prefix and each of its subnets functions like a private key, granting you access to your prefix. It is crucial to keep this identifier confidential and not share it with anyone.
+
+
+
diff --git a/pages/dedibox-ipv6/index.mdx b/pages/dedibox-ipv6/index.mdx
new file mode 100644
index 0000000000..396d983308
--- /dev/null
+++ b/pages/dedibox-ipv6/index.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: Dedibox - IPv6 Documentation
+ description: Dive into Scaleway Dedibox - IPv6 with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
diff --git a/pages/dedibox-ipv6/quickstart.mdx b/pages/dedibox-ipv6/quickstart.mdx
new file mode 100644
index 0000000000..3eadf6f1cf
--- /dev/null
+++ b/pages/dedibox-ipv6/quickstart.mdx
@@ -0,0 +1,104 @@
+---
+meta:
+ title: Scaleway Dedibox IPv6 - Quickstart
+ description: This page shows you how to get started with IPv6 on Scaleway Dedibox.
+content:
+ h1: Scaleway Dedibox IPv6 - Quickstart
+ paragraph: This page shows you how to get started with IPv6 on Scaleway Dedibox.
+tags: dedibox ipv6 slaac dhcp
+dates:
+ validation: 2024-08-26
+ posted: 2021-08-03
+categories:
+ - dedibox-network
+---
+
+IPv6 stands as the latest iteration of the Internet Protocol (IP) used to allocate addresses across the web. Each IPv6 address is composed of 128 bits. When expressed in a human-friendly format, an IPv6 address takes the form of eight sets of four hexadecimal digits, with each set accounting for 16 bits. These sets are separated by colons, such as in `2001:0DB8:0000:0003:0000:01FF:0000:002E`. An alternate representation could be `2001:DB8::3:0:1FF:0:2E`. The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server's primary IP and also as a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) utilizing the concept of a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+
+
+ You need to have at least one Dedibox dedicated server to order an IPv6 prefix.
+
+
+## How to request an IPv6 prefix
+
+All Scaleway Dedibox dedicated servers support IPv6. You can request a free /48 IPv6 prefix for your account. This prefix can then be divided into multiple /56 or /64 subnets. IPv6 is available for Dedibox servers in Paris and Warsaw.
+
+1. Click **Server** > **Network configuration** in the Dedibox console. The network configuration page displays.
+2. Scroll to the bottom of the page and click **Order a free /48 IPv6 block**.
+
+ The IPv6 prefix will be delivered within 30 minutes and will be visible on the network configuration page.
+
+
+ The DUID of your prefix (and each of its subnets) is like a private key and grants you access to your prefix. Keep it secret and do not share it.
+
+
+## How to enable IPv6 SLAAC
+
+Activation of IPv6 SLAAC assigns **one** `/128` IPv6 subnet to your server (one usable IPv6 address). This IP will be statically linked to your server and can not be attributed to another server.
+
+
+ This feature is not yet available for all servers. Only the servers that are compatible will show the related button.
+
+
+1. Click **Server** > **Server list** to display a list of all your servers.
+2. Click **Manage** next to the server you want to configure. The server's status page displays.
+3. Scroll down to the server's network section and click **Activate IPv6 SLAAC**.
+
+ Your server's IPv6 SLAAC is activated now and displays in the network section.
+
+### How to configure the DHCPv6 client
+
+1. Log into your server using SSH.
+2. Open the file `/etc/dhcp/dhclient6.conf` in a text editor, for example: `nano`, and edit it as shown below:
+ ```
+ interface "eno1" {
+ send dhcp6.client-id DUID;
+ }
+ ```
+
+ Make sure to adapt the interface name (`eno1`) to the internet interface name of your system, and replace `DUID` with the DUID of your subnet.
+
+### How to autostart the DHCPv6 client during system boot
+
+
+ To enable automatic start of the DHCPv6 client during system boot, a SystemD service is required.
+
+
+1. Log into your server using SSH.
+2. Open the file `/etc/systemd/system/dhclient.service` in a text editor, for example: `nano`, and edit it as shown below:
+ ```
+ [Unit]
+ Description=dhclient for sending DUID IPv6
+ After=network-online.target
+ Wants=network-online.target
+
+ [Service]
+ Restart=always
+ RestartSec=10
+ Type=forking
+ ExecStart=/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
+ ExecStop=/sbin/dhclient -x -pf /var/run/dhclient6.pid
+
+ [Install]
+ WantedBy=network.target
+ ```
+
+
+ The path to the `dhclient` binary may vary depending on your OS. To see the exact path for your system, use the following command: `which dhclient`.
+
+3. Enable the service so it will start at each reboot of the machine:
+ ```
+ sudo systemctl enable dhclient.service
+ ```
+
+## How to configure IPv6 on your dedicated server
+
+You can find information regarding the configuration of IPv6 on your Dedibox dedicated server at the following links:
+
+* [How to configure IPv6 on Linux using `systemd-networkd`](/dedibox-ipv6/how-to/configure-ipv6-linux/)
+* [How to configure IPv6 on Windows Server](/dedibox-ipv6/how-to/configure-ipv6-windows/)
\ No newline at end of file
diff --git a/pages/dedibox-kvm-over-ip/assets/scaleway-idrac.webp b/pages/dedibox-kvm-over-ip/assets/scaleway-idrac.webp
new file mode 100644
index 0000000000..30a2c6c7f5
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/assets/scaleway-idrac.webp differ
diff --git a/pages/dedibox-kvm-over-ip/assets/scaleway-ilo.webp b/pages/dedibox-kvm-over-ip/assets/scaleway-ilo.webp
new file mode 100644
index 0000000000..1e254da8cc
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/assets/scaleway-ilo.webp differ
diff --git a/pages/dedibox-kvm-over-ip/concepts.mdx b/pages/dedibox-kvm-over-ip/concepts.mdx
new file mode 100644
index 0000000000..ca42d1bf73
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/concepts.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: KVM over IP - Concepts
+ description: This page explains all the concepts related to KVM over IP
+content:
+ h1: KVM over IP - Concepts
+ paragraph: This page explains all the concepts related to KVM over IP
+tags: kvm iso-file idrac ilo iso
+categories:
+ - dedibox-servers
+dates:
+ validation: 2024-09-02
+---
+
+## KVM Over IP
+
+KVM Over IP is a hardware-based solution that enables remote access to the **k**eyboard, **v**ideo (screen), and **m**ouse ports of a physical server. A unit plugs into these ports and transmits their signals to a connected user through a network. This allows access to the machine even if the installed OS is not working properly, and opens up possibilities for debugging and more.
+
+## iDRAC
+
+The **I**ntegrated **D**ell **R**emote **A**ccess **C**ontroller is the hardware allowing KVM Over IP and other management and monitoring features for Dell servers.
+
+## iLO card
+
+The **I**ntegrated **L**ights-**O**ut card is the hardware allowing KVM Over IP and other management and monitoring features for HP servers.
+
+## ISO file
+
+An ISO file, also called ISO image, is an archive file that contains an identical copy of data usually stored on a physical optical disk, such as a CD or DVD. The name ISO file comes from the file system type used by optical media (typically ISO 9660). The ISO file can be distributed to be burned on a physical disc or can be read directly by most operating systems or [KVM over IP](#kvm-over-ip) devices to install an operating system on a remote machine.
+
+
+ Scaleway provides a wide range of operating systems for installation on Dedibox servers equipped with a KVM over IP device. You can find a list of all available images at [http://virtualmedia.online.net/](http://virtualmedia.online.net). For more information on how to install an operating system using the KVM device, refer to our [dedicated documentation](/dedibox-kvm-over-ip/quickstart/).
+
\ No newline at end of file
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck.webp
new file mode 100644
index 0000000000..09af8d703b
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck2.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck2.webp
new file mode 100644
index 0000000000..16c2978ab8
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck2.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck3.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck3.webp
new file mode 100644
index 0000000000..fa9782af01
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway-bootstuck3.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_KVM.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_KVM.webp
new file mode 100644
index 0000000000..560d9ca574
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_KVM.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac.webp
new file mode 100644
index 0000000000..7e30ddbabd
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_boot_manager.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_boot_manager.webp
new file mode 100644
index 0000000000..f3159c43a0
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_boot_manager.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_cd.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_cd.webp
new file mode 100644
index 0000000000..6beb055d44
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_cd.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_console.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_console.webp
new file mode 100644
index 0000000000..978f06d902
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac6_virtual_console.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_bios_boot.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_bios_boot.webp
new file mode 100644
index 0000000000..f1973fb25b
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_bios_boot.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_console.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_console.webp
new file mode 100644
index 0000000000..1cf53fa640
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_console.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_dashboard.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_dashboard.webp
new file mode 100644
index 0000000000..c3fd769c41
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_dashboard.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_remote_share.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_remote_share.webp
new file mode 100644
index 0000000000..e93ded7113
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_remote_share.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_virtual_cd.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_virtual_cd.webp
new file mode 100644
index 0000000000..859b2bf541
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac7_virtual_cd.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_connect_vm.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_connect_vm.webp
new file mode 100644
index 0000000000..ddda86e890
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_connect_vm.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_dashboard.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_dashboard.webp
new file mode 100644
index 0000000000..20a91692b6
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_dashboard.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_iso.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_iso.webp
new file mode 100644
index 0000000000..2d1934497d
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_iso.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_map_cd.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_map_cd.webp
new file mode 100644
index 0000000000..762be4137f
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac8_map_cd.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_boot_manager.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_boot_manager.webp
new file mode 100644
index 0000000000..0280f2e7f8
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_boot_manager.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_connect_vm.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_connect_vm.webp
new file mode 100644
index 0000000000..43e9aa6992
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_connect_vm.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_console.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_console.webp
new file mode 100644
index 0000000000..ce4ff597ad
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_console.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_map_device.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_map_device.webp
new file mode 100644
index 0000000000..173b92c95a
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac9_map_device.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_console.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_console.webp
new file mode 100644
index 0000000000..dd72790ccb
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_console.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_launch_console.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_launch_console.webp
new file mode 100644
index 0000000000..59f1da084c
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_idrac_launch_console.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo.webp
new file mode 100644
index 0000000000..ac0dfa9296
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_menu.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_menu.webp
new file mode 100644
index 0000000000..960ee914ec
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_menu.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_options.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_options.webp
new file mode 100644
index 0000000000..bdd72859cc
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_ilo_boot_options.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_add_vm.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_add_vm.webp
new file mode 100644
index 0000000000..83c567aec9
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_add_vm.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_boot_device.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_boot_device.webp
new file mode 100644
index 0000000000..f086517dd5
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_boot_device.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_console_redir.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_console_redir.webp
new file mode 100644
index 0000000000..a407025ecf
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_console_redir.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_virtual_media.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_virtual_media.webp
new file mode 100644
index 0000000000..806ba309a7
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_qct_virtual_media.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_browse_file.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_browse_file.webp
new file mode 100644
index 0000000000..babb777de6
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_browse_file.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_f11.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_f11.webp
new file mode 100644
index 0000000000..aa87d5d943
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_f11.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_launch_kvm.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_launch_kvm.webp
new file mode 100644
index 0000000000..cb9617f300
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_launch_kvm.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_remote_control.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_remote_control.webp
new file mode 100644
index 0000000000..ecbd65e169
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_remote_control.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_start_media.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_start_media.webp
new file mode 100644
index 0000000000..c089935bb9
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_start_media.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_vcdrom.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_vcdrom.webp
new file mode 100644
index 0000000000..8da3f79fba
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_quantaplex_vcdrom.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_boot_mgr.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_boot_mgr.webp
new file mode 100644
index 0000000000..f4b5500f46
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_boot_mgr.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_drivers.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_drivers.webp
new file mode 100644
index 0000000000..5c684033f4
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_drivers.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_install.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_install.webp
new file mode 100644
index 0000000000..04c74b6952
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_install.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_nas.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_nas.webp
new file mode 100644
index 0000000000..ee84568fb8
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_nas.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_network.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_network.webp
new file mode 100644
index 0000000000..4d732c392c
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_network.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_ping.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_ping.webp
new file mode 100644
index 0000000000..428bdffbee
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_ping.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vcdrom.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vcdrom.webp
new file mode 100644
index 0000000000..f3bfb4d393
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vcdrom.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vdrive.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vdrive.webp
new file mode 100644
index 0000000000..e25abca0c1
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vdrive.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vm.webp b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vm.webp
new file mode 100644
index 0000000000..e948a34305
Binary files /dev/null and b/pages/dedibox-kvm-over-ip/how-to/assets/scaleway_supermicro_vm.webp differ
diff --git a/pages/dedibox-kvm-over-ip/how-to/dell-idrac6.mdx b/pages/dedibox-kvm-over-ip/how-to/dell-idrac6.mdx
new file mode 100644
index 0000000000..0cc00c277b
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/dell-idrac6.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: How to use the KVM Dell iDRAC 6
+ description: This page explains how to use the KVM DELL iDRAC 6 on a Scaleway Dedibox
+content:
+ h1: How to use the KVM Dell iDRAC 6
+ paragraph: This page explains how to use the KVM DELL iDRAC 6 on a Scaleway Dedibox
+tags: dedibox kvm idrac
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 6.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [Dell iDRAC 6](https://www.dell.com/support/kbdoc/en-us/000123577/set-up-and-manage-idrac-6-lifecycle-controller-for-dell-poweredge-11g-servers) KVM-over-IP device
+
+## Creating an iDRAC 6 session
+
+1. Click **Server** > **Server List** in your Dedibox console. The list of your dedicated servers displays.
+2. Click the name of the server you want to access. The server's status page displays.
+3. Click **iDRAC** in the menu on the right. A pop-up displays.
+
+4. Accept the terms for iDRAC access by clicking **I Accept**.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+The connection URL and your credentials display. Click on the link to access the iDRAC interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your iDRAC in your web browser, then log in using the credentials displayed during access creation.
+2. Click **Console/Media** the top menu.
+
+3. Click **Launch Virtual Console**.
+
+4. Download and execute the Java web start file. The virtual console window displays.
+
+
+
+ Your Java security settings should be set to **Low** to execute the Java applet.
+
+5. Click **Virtual Media** > **Launch virtual media** in the virtual console window. A pop-up window displays.
+6. Click **Add Image...** and select the ISO file containing your operating system. Keep the window open.
+7. Go back to the virtual console window and click **Power** > **Reboot** to restart the machine.
+8. During the boot process, press **F11** to access the BIOS boot manager.
+
+9. Select **Virtual CD** to boot the server using the ISO file mounted in the virtual CD drive.
+
+
+
+ The boot process may take a while, depending on your internet connection's available upstream bandwidth.
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/dell-idrac7.mdx b/pages/dedibox-kvm-over-ip/how-to/dell-idrac7.mdx
new file mode 100644
index 0000000000..ef9f1bce60
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/dell-idrac7.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: How to use the KVM Dell iDRAC 7
+ description: This page explains how to use the KVM DELL iDRAC 7 on Scaleway Dedibox.
+content:
+ h1: How to use the KVM Dell iDRAC 7
+ paragraph: This page explains how to use the KVM DELL iDRAC 7 on Scaleway Dedibox.
+tags: dedibox kvm idrac7 idrac
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 7.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [Dell iDRAC 7](https://www.dell.com/support/manuals/en-us/integrated-dell-remote-access-cntrllr-7-v1.50.50/idrac7ug1.50.50-v1/overview) KVM-over-IP device
+
+# Creating an iDRAC 7 Session
+
+1. Navigate to **Server** > **Server List** in your [Dedibox console](https://console.online.net). A list of your dedicated servers displays.
+2. Click the name of the server you wish to access. The server's status page displays.
+3. Click **iDRAC** on the right-hand menu. This will prompt a pop-up window to appear.
+
+4. Confirm your acceptance of the terms for iDRAC access by clicking **I Accept**.
+5. Provide the authorized IPv4 address for the iDRAC connection. The form will autofill with the IP address of your current internet connection. Proceed by clicking **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are supported.
+
+
+Upon completion, the connection URL and your credentials will be displayed. Click on the provided link to access the iDRAC interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your iDRAC in your web browser, then log in using the credentials provided during access creation.
+2. Navigate to **Attached Media** in the top menu. This action will display the virtual media page.
+
+3. Input the image file path in the form and click **Connect**.
+
+
+ You can locate the image file path for your OS on our [NAS](http://virtualmedia.online.net).
+ If your preferred OS is not available on the NAS, contact our support team for assistance.
+
+4. Click on **Properties** (A), then **Launch** (B) to initiate the virtual console.
+
+5. Reboot the server, then press **F11** during the boot process to access the boot manager.
+6. Select **BIOS Boot Menu**.
+
+7. Choose **iDRAC Virtual CD**.
+
+
+Your server boots from the ISO file on the NAS and you can complete the installation of your operating system.
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/dell-idrac8.mdx b/pages/dedibox-kvm-over-ip/how-to/dell-idrac8.mdx
new file mode 100644
index 0000000000..bedd171e54
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/dell-idrac8.mdx
@@ -0,0 +1,61 @@
+---
+meta:
+ title: How to use the KVM DELL iDRAC 8
+ description: This page explains how to use the KVM DELL iDRAC 8 on a Scaleway Dedibox
+content:
+ h1: How to use the KVM DELL iDRAC 8
+ paragraph: This page explains how to use the KVM DELL iDRAC 8 on a Scaleway Dedibox
+tags: dedibox kvm dell idrac idrac8
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 8.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [DELL iDRAC 8](https://www.dell.com/support/manuals/en-us/idrac8-with-lc-v2.05.05.05/idrac8_2.05.05.05_ug/overview) KVM-over-IP device
+
+## Creating an iDRAC 8 session
+
+1. Click **Server** > **Server List** in your Dedibox console. The list of your dedicated servers displays.
+2. Click the name of the server you want to access. The server's status page displays.
+3. Click **iDRAC** in the menu on the right. A pop-up displays.
+
+4. Accept the terms for iDRAC access by clicking **I Accept**.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+The connection URL and your credentials display. Click on the link to access the iDRAC interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your iDRAC in your web browser, then log in using the credentials displayed during access creation.
+2. Click **Launch** in the **Virtual Console Preview** section of the dashboard. A Java Web Start file is downloaded.
+
+3. Launch the Java web start file. The virtual console window displays.
+
+ Your Java security settings should be set to **Low** to execute the Java applet.
+
+4. Click **Virtual Media** > **Connect Virtual Media**.
+
+5. Click **Virtual Media** > **Map CD/DVD ...**. A pop-up displays.
+
+6. Select the installation ISO file on your computer by clicking **Browse**. Then click **Map Device** and reboot the server.
+
+7. Press **F12** during the boot process to enter the boot manager. Then select the virtual CD-ROM drive.
+
+ Your server boots from the ISO file, and you can complete the installation of your operating system.
+
+
+ The boot process may take a while, depending on your internet connection's available upstream bandwidth.
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/dell-idrac9.mdx b/pages/dedibox-kvm-over-ip/how-to/dell-idrac9.mdx
new file mode 100644
index 0000000000..dbe5deaf6c
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/dell-idrac9.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: How to use the KVM DELL iDRAC 9
+ description: This page explains how to use the KVM DELL iDRAC 9 on a Scaleway Dedibox
+content:
+ h1: How to use the KVM DELL iDRAC 9
+ paragraph: This page explains how to use the KVM DELL iDRAC 9 on a Scaleway Dedibox
+tags: dedibox kvm idrac
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 9.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [DELL iDRAC 9](https://www.dell.com/support/manuals/en-us/idrac8-with-lc-v2.05.05.05/idrac8_2.05.05.05_ug/overview) KVM-over-IP device
+
+## Creating an iDRAC 9 session
+
+1. Click **Server** > **Server List** in your Dedibox console. The list of your dedicated servers displays.
+2. Click the name of the server you want to access. The server's status page displays.
+3. Click **iDRAC** in the menu on the right. A pop-up displays.
+
+4. Accept the terms for iDRAC access by clicking **I Accept**.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+The connection URL and your credentials display. Click on the link to access the iDRAC interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your iDRAC in your web browser, then log in using the credentials displayed during access creation.
+2. Click **Configuration** in the top menu, then **Virtual Console**. The virtual console page displays. Click **Launch Virtual Console**.
+
+3. Click **Connect Virtual Media** in the virtual console window. The virtual media configuration displays.
+
+4. Click **Choose file** (A) in the **Map CD/DVD** section and select your ISO file. Then click **Map Device**. Once the device is mapped, click **Close**.
+
+5. Click **Console Controls**, choose the **Ctrl-Alt-Del** keyboard macro and click **Apply** to reboot the server.
+6. Press **F11** during the boot process to enter the boot manager.
+7. Click **One-shoot UEFI Boot Menu**:
+
+8. Click **Virtual Optical Drive**.
+
+ Your server boots from the ISO file, and you can complete the installation of your operating system.
+
+
+ The boot process may take a while, depending on your internet connection's available upstream bandwidth.
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx b/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx
new file mode 100644
index 0000000000..2ffc9b0642
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/disable-boot-errors-idrac.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: How to disable boot errors using iDRAC
+ description: This page explains how to disable boot errors using iDRAC on a Scaleway Dedibox
+content:
+ h1: How to disable boot errors using iDRAC
+ paragraph: This page explains how to disable boot errors using iDRAC on a Scaleway Dedibox
+tags: boot error idrac
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+This document shows you how to disable boot errors, where your server gets "stuck" showing the line `“trike the F1 key to continue, F2 to run the system setup program`.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server with a Dell iDRAC controller
+
+1. [Connect to your server's iDRAC](/dedicated-servers/how-to/use-ipmi-on-server/#how-to-use-ipmi-via-dell-idrac).
+2. Click **System**, on the side menu.
+3. Click the **Console/Media** tab, then **Launch virtual console**.
+
+ Your server will boot until it gets stuck as previously described:
+
+
+4. Click in the KVM window, then press **F2**. This allows you to enter the BIOS of your server and make configuration changes.
+
+5. Use the arrow keys to go to the line **F1/F2 Prompt on Error**.
+6. Press the spacebar to change the value of the line to **Disabled**.
+7. Press ESC. You are prompted to save your modifications to the BIOS.
+8. Press Enter to save your modifications.
+
+ The server reboots. You can watch the boot process in the KVM to make sure the server loads the OS correctly.
+
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/hp-ilo.mdx b/pages/dedibox-kvm-over-ip/how-to/hp-ilo.mdx
new file mode 100644
index 0000000000..157ea3dce0
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/hp-ilo.mdx
@@ -0,0 +1,56 @@
+---
+meta:
+ title: How to use the KVM HP iLO
+ description: This page explains how to use the KVM HP iLO on a Scalewaty Dedibox
+content:
+ h1: How to use the KVM HP iLO
+ paragraph: This page explains how to use the KVM HP iLO on a Scaleway Dedibox
+tags: kvm hp iLO access creation dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with HP iLO.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A Dedibox server with a KVM-over-IP device: [HP iLO (integrated lights-out)](https://www.hpe.com/us/en/servers/integrated-lights-out-ilo.html)
+
+## Creating an iLO session
+
+1. Click **Server** > **Server List** in your Dedibox console. The list of your dedicated servers displays.
+2. Click the name of the server you want to access. The server's status page displays.
+3. Click **iLO** in the menu on the right. A pop-up displays.
+
+4. Accept the terms for iLO access by clicking **I Accept**.
+5. Enter the authorized IPv4 address for the iLO connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+The connection URL and your credentials display. Click on the link to access the iLO interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your iLO in your web browser, then log in using the credentials displayed during access creation.
+2. Click **Integrated Remote Console**.
+
+ Depending on the model of your dedicated server, iLO may propose either an **HTML5-based** KVM-over-IP interface or a **Java-based** one. Make sure to have [Java installed](https://www.java.com/en/download/help/download_options.html) on your local computer if you want to use this version.
+
+3. Click the **Disc icon** > **CD/DVD** > **Local *.iso file** and select the local installation image of your operating system.
+
+ You can also use one of the ISO files available on our [NAS](https://virtualmedia.online.net/) by clicking **Scripted Media URL**.
+
+4. Click the menu icon > **Power** > **Reset** to reboot the machine.
+5. During reboot, press **F11** to launch the boot menu.
+
+6. Press **1** to boot from the virtual CD/DVD drive.
+
+
+The server boots into installation mode. Follow the wizard of your operating system to complete the installation.
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/index.mdx b/pages/dedibox-kvm-over-ip/how-to/index.mdx
new file mode 100644
index 0000000000..6cc0b9dd95
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/index.mdx
@@ -0,0 +1,9 @@
+---
+meta:
+ title: KVM over IP - How Tos
+ description: KVM over IP How Tos
+content:
+ h1: KVM over IP - How Tos
+ paragraph: KVM over IP How Tos
+---
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/quanta-computer.mdx b/pages/dedibox-kvm-over-ip/how-to/quanta-computer.mdx
new file mode 100644
index 0000000000..f675cd2153
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/quanta-computer.mdx
@@ -0,0 +1,53 @@
+---
+meta:
+ title: How to use the Quanta Computer KVM
+ description: This page explains how to use the KVM device of Quanta Computer servers on Scaleway dedicated servers
+content:
+ h1: How to use the Quanta Computer KVM
+ paragraph: This page explains how to use the KVM device of Quanta Computer servers on Scaleway dedicated servers
+tags: kvm quanta qct
+dates:
+ validation: 2024-12-23
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Quanta Computer KVM.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [Quanta Computer](https://www.qct.io) KVM-over-IP device
+
+## Creating a KVM session
+
+1. Click **Server** > **Server List** in your Dedibox console. The list of your dedicated servers displays.
+2. Click the name of the server you want to access. The server's status page displays.
+3. Click **KVM OVER IP** in the menu on the right. A pop-up displays.
+
+4. Accept the terms for KVM access by clicking **I Accept**.
+5. Enter the authorized IPv4 address for the KVM connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+The connection URL and your credentials display. Click on the link to access the KVM interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your KVM in your web browser, then log in using the credentials displayed during access creation.
+2. Click **Remote Control** > **Console Redirection** in the menu. Download and run the Java applet.
+
+3. Click **Media** > **Virtual Media** in the KVM window.
+
+4. Click **Browse** in the **CD/DVD Media I** section and select your operating system's ISO file. Then click **Connect CD/DVD**:
+
+5. Reboot the server and press **F11** to enter the boot menu once the Quanta Computer logo displays.
+6. Select the boot device **AMI Virtual CDROM0** to boot from the ISO file:
+
+
+The server boots into installation mode. Follow the wizard of your operating system to complete the installation.
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx b/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx
new file mode 100644
index 0000000000..5f4cff9cd2
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/quantaplex.mdx
@@ -0,0 +1,57 @@
+---
+meta:
+ title: How to use the QuantaPlex KVM
+ description: This page explains how to use the KVM device of QuantaPlex servers on Scaleway Dedibox.
+content:
+ h1: How to use the QuantaPlex KVM
+ paragraph: This page explains how to use the KVM device of QuantaPlex servers on Scaleway Dedibox.
+tags: kvm quantaplex
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a QuantaPlex Dedibox.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox server](/dedicated-servers/how-to/install-a-server/) with a [Quanta Computer QuantaPlex](https://www.qct.io) KVM-over-IP device
+
+## Creating a KVM session
+
+1. Navigate to **Server** > **Server List** in your [Dedibox console](https://console.online.net/) to view the list of your dedicated servers.
+2. Click the name of the server you wish to access. This will open the server's status page.
+3. Click **KVM OVER IP** on the right-hand menu. A pop-up window displays.
+
+4. Confirm your acceptance of the terms for KVM access by clicking **I Accept**.
+5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Proceed by clicking **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are supported.
+
+
+Upon completion, the connection URL and your credentials will be displayed. Click on the provided link to access the KVM interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your KVM in your web browser, then log in using the credentials provided during access creation.
+2. Navigate to **Remote Control** in the side menu of the BMC device.
+
+3. Click **Launch KVM** on the **Remote Control** page:
+
+4. In the KVM window, click **Browse File** and select your operating system's ISO file.
+
+5. Click **Start Media** to mount the virtual drive and reboot the machine:
+
+6. During the boot process, press **F11** to enter the boot menu:
+
+
+Select the boot device **AMI Virtual CDROM0** to boot from the ISO file:
+
+
+
+The server will boot into installation mode. Follow the operating system's installation wizard to complete the installation.
+
+
diff --git a/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx b/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx
new file mode 100644
index 0000000000..1a2c8cf183
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/how-to/supermicro.mdx
@@ -0,0 +1,84 @@
+---
+meta:
+ title: How to use the Supermicro KVM
+ description: This page explains how to use the KVM device of SuperMicro servers on Scaleway Dedibox.
+content:
+ h1: How to use the Supermicro KVM
+ paragraph: This page explains how to use the KVM device of SuperMicro servers on Scaleway Dedibox.
+tags: kvm supermicro
+dates:
+ validation: 2024-08-27
+ posted: 2021-07-16
+categories:
+ - dedibox-servers
+---
+
+This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Supermicro KVM.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
+- A Dedibox server with a [Supermicro](https://www.supermicro.com/en/solutions/management-software/bmc-resources) KVM-over-IP device
+
+## Creating a KVM session
+
+1. Access your [Dedibox console](https://console.online.net/) and navigate to **Server** > **Server List**. This will display a list of your dedicated servers.
+2. Select the server you wish to access by clicking its name. This will open the server's status page.
+3. Click **KVM OVER IP** on the right-hand menu. A pop-up window displays.
+
+4. Confirm your acceptance of the terms for KVM access by clicking **I Accept**.
+5. Provide the authorized IPv4 address for the KVM connection. The form will autofill with the IP address of your current internet connection. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+Once completed, the connection URL and your credentials will be displayed. Click on the provided link to access the KVM interface.
+
+## Accessing the KVM-over-IP device
+
+1. Open the connection URL of your KVM in your web browser and log in using the credentials provided during access creation.
+2. In the KVM menu, click on **Virtual Media** > **CD-ROM Image**:
+
+3. Enter the image file path of your OS image:
+
+
+
+ You can find the image file path for your OS on our [NAS](http://virtualmedia.online.net).
+ If your preferred OS is not available on the NAS, contact our support team for assistance.
+
+4. Launch the Java remote console by clicking on the preview screen on the homepage of the KVM device.
+
+ A Java security warning may appear. Validate it to launch the KVM applet.
+
+5. Reboot the server and press **F11** to enter the boot menu:
+
+6. Select the boot device **ATEN Virtual CDROM** to boot from the ISO file:
+
+
+Your server will boot into installation mode. Follow the operating system's installation wizard to complete the installation.
+
+
+
+## Installing Windows network drivers
+
+Microsoft Windows Server does not support the network adapter used in Supermicro servers by default. Follow these steps to manually install network drivers using the KVM-over-IP device:
+
+1. [Create](#creating-a-kvm-session) a Supermicro KVM session.
+2. Open the connection URL of the KVM in your web browser and log in using the provided credentials.
+3. [Download](https://www.supermicro.com/wdl/CDR_Images/CDR-A1-A2-UP/CDR-A1-A2-UP_1.02_for_Intel_A1_A2_UP_platform.iso.iso) the driver package from Supermicro to your local computer.
+
+ You can also download a local copy of the file directly onto your server using Scaleway's NAS: [https://virtualmedia.online.net/supermicro/CDR-A1-UP_1.00_for_Intel_A1_UP_platform.iso](https://virtualmedia.online.net/supermicro/CDR-A1-UP_1.00_for_Intel_A1_UP_platform.iso).
+
+4. Access the KVM-over-IP device by clicking **Remote Console Preview**.
+5. Click **Virtual Media** > **Virtual Storage**. A pop-up will appear:
+
+6. Select **ISO file** and choose the downloaded ISO image. Then click **Plug in** > **OK**.
+7. Double-click on the CD-ROM drive in your Windows installation and launch the setup tool. Accept the terms and conditions and click **Intel PRO Network Connections Drivers**:
+
+8. Complete the installation of the network drivers using the setup wizard:
+
+9. Test the network connection of your Dedibox using the `ping` command:
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/index.mdx b/pages/dedibox-kvm-over-ip/index.mdx
new file mode 100644
index 0000000000..0df7c3efc8
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/index.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Dedibox - KVM-over-IP Documentation
+ description: Dive into Scaleway Dedibox - KVM-over-IP with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
diff --git a/pages/dedibox-kvm-over-ip/quickstart.mdx b/pages/dedibox-kvm-over-ip/quickstart.mdx
new file mode 100644
index 0000000000..eb8185859b
--- /dev/null
+++ b/pages/dedibox-kvm-over-ip/quickstart.mdx
@@ -0,0 +1,82 @@
+---
+meta:
+ title: KVM over IP - Quickstart
+ description: KVM over IP Quickstart
+content:
+ h1: KVM over IP - Quickstart
+ paragraph: KVM over IP Quickstart
+tags: dedibox kvm over-ip
+dates:
+ validation: 2024-09-02
+categories:
+ - dedibox-servers
+---
+
+An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI allows you to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**ontroller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
+
+Some examples of features that can be remotely monitored via the IPMI include:
+
+ - Ventilation,
+ - Temperature,
+ - Voltage,
+ - Operating time.
+
+Actions that can be carried out via IPMI include:
+
+ - Rebooting via KVM,
+ - Switching the server off and/or on,
+ - Configuration of automatic notification in case of hardware problems (power supply failure, temperature anomalies, etc.),
+ - Viewing of logs from the BIOS,
+ - Accessing the serial port and BIOS over the network via serial console.
+
+In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox-kvm-over-ip/) documentation for information about other server models.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server with a dedicated KVM over IP device
+
+## How to use IPMI via Dell iDRAC
+
+IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **i**ntegrated **D**ell **R**emote **A**ccess **C**ontroller.
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the relevant server.
+3. Click the **IDRAC** button on the right. A disclaimer displays.
+4. Click **I Accept** to agree with the terms of the disclaimer.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+ The URL connection and your credentials display. Click the link to access the iDRAC interface.
+
+
+6. Use the interface to monitor and manage your server's hardware:
+ - The **System** tabs let you view various system information including system details, logs, and power status. You can also use the **Console/Media** > **Virtual Media** tab to install your server remotely with a custom OS by connecting virtual media. Click **Remote Access Controller** under **System Details** to launch the KVM.
+ - The **iDDRAC** tabs show you information about the iDRAC itself.
+ - Click the other relevant links on the left sidebar to see information about **Batteries**, **Temperatures**, **Voltages** etc., as required.
+
+## How to use IPMI via HPE iLO
+
+IPMI is a standard specification for a remote management subsystem. On an HPE server, IPMI is realized through the ILO: the **i**ntegrated **L**ights **O**ut processor.
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the relevant server.
+3. Click the **ILO** button on the right. A disclaimer displays.
+4. Click **I Accept** to agree with the terms of the disclaimer.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+ The URL connection and your credentials display. Click on the link to access the iLO interface.
+
+
+6. Use the interface to monitor and manage your server's hardware:
+ - The **Information** pages let you view various system information including system details, logs, and diagnostics.
+ - The **Remote Console** pages let you launch the KVM.
+ - The **Virtual Media** pages let you install your server remotely with a custom OS by connecting virtual media.
+ - Click the other relevant links on the left sidebar to see more information.
+
+
diff --git a/pages/dedibox-network/assets/scaleway-mtr1.webp b/pages/dedibox-network/assets/scaleway-mtr1.webp
new file mode 100644
index 0000000000..5abebb8f75
Binary files /dev/null and b/pages/dedibox-network/assets/scaleway-mtr1.webp differ
diff --git a/pages/dedibox-network/how-to/configure-network-netplan.mdx b/pages/dedibox-network/how-to/configure-network-netplan.mdx
new file mode 100644
index 0000000000..2f393f99c7
--- /dev/null
+++ b/pages/dedibox-network/how-to/configure-network-netplan.mdx
@@ -0,0 +1,108 @@
+---
+meta:
+ title: Network configuration with Netplan on Ubuntu on a Scaleway Dedibox
+ description: This page shows how to configure netplan on Ubuntu on a Scaleway Dedibox
+content:
+ h1: Network configuration with Netplan on Ubuntu on a Scaleway Dedibox
+ paragraph: This page shows how to configure netplan on Ubuntu on a Scaleway Dedibox
+tags: dedibox network netplan ubuntu
+dates:
+ validation: 2024-08-26
+ posted: 2021-08-20
+categories:
+ - dedibox-network
+---
+
+Since the release of its version 18.04, Bionic Beaver, [Ubuntu](http://www.ubuntu.org) has switched to [Netplan](http://netplan.io) for the network interface configuration. It is a [YAML](https://yaml.org/spec/1.2/spec.html) based configuration system, which simplifies the configuration process.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+## Configuration files
+
+This tool replaces the `/etc/network/interfaces` configuration file previously used to configure the network interfaces on Ubuntu.
+
+The configuration files are now YAML files located in `/etc/netplan/*.yaml`.
+
+
+
+ Make sure you respect the YAML standards when you edit the file, as syntax errors might cause errors in your configuration.
+
+
+
+The `01-netcfg.yaml` file is used to configure the first interface. Below, you can find the default configuration for an interface using DHCP:
+
+```
+# This file describes the network interfaces available on your system
+# For more information, see netplan(5).
+network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ enp1s0f0:
+ dhcp4: yes
+```
+
+
+Following, you can see a list of the most common configuration options and a description of how they are used.
+
+| Option | Example | Description |
+| :-------- | :-------- | :---------- |
+| addresses| 192.168.1.2/24, 62.210.123.123/32 | A list of IP addresses to be assigned to an interface. The format uses CIDR notation. |
+| gateway4 | 192.168.1.1 | The IP address of your local IPv4 gateway. |
+| dhcp4 | true | Set whether DHCP is enabled for IPv4 – true of false |
+| dhcp6 | true | Set whether DHCP is enabled for IPv6 – true or false |
+
+
+## Configuring a failover IP with Netplan
+
+To configure a failover IP, you must edit the file `/etc/netplan/01-netcfg.yaml` and configure static networking for your server. The IP addresses have to be written with their [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). The netmask is `/24` for the principal IP of the server and `/32` for each failover IP. Your configuration file should look like in the following example:
+
+```
+network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ enp1s0f0:
+ addresses: [163.172.123.123/24, 212.83.123.123/32]
+ gateway4: 163.172.123.1
+ nameservers:
+ addresses: [ "51.159.47.28", "51.159.47.26" ]
+```
+
+
+ Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency.
+
+
+Once you have edited and saved the file, you can reload the configuration with the following command:
+
+```
+sudo netplan apply
+```
+
+## Configuring a failover IP for virtual machines
+
+When configuring a failover IP in a virtual machine, you must specify which route will be used by the VM. Your configuration file should look like the following example:
+
+```
+ network:
+ ethernets:
+ ens18:
+ addresses:
+ - [ "fail.over.ip.address/32" ]
+ nameservers:
+ addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers/)
+ routes:
+ - to: default
+ via: 62.210.0.1
+ - to: 62.210.0.1/32
+ via: fail.over.ip.address
+ scope: link
+ version: 2
+```
+
+
+ Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency.
+
\ No newline at end of file
diff --git a/pages/dedibox-network/how-to/index.mdx b/pages/dedibox-network/how-to/index.mdx
new file mode 100644
index 0000000000..e85c096306
--- /dev/null
+++ b/pages/dedibox-network/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox Network - How Tos
+ description: Dedibox Network How Tos
+content:
+ h1: Dedibox Network - How Tos
+ paragraph: Dedibox Network How Tos
+---
diff --git a/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx b/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx
new file mode 100644
index 0000000000..002e243acb
--- /dev/null
+++ b/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to subscribe to JMRP
+ description: This page explains how to subscribe to JMRP.
+content:
+ h1: How to subscribe to JMRP
+ paragraph: This page explains how to subscribe to JMRP.
+tags: dedibox network jmrp
+dates:
+ validation: 2024-08-12
+ posted: 2021-08-20
+categories:
+ - dedibox-network
+---
+
+Subscribing to the Junk Mail Reporting Program (JMRP) allows you to register your IP addresses with Microsoft's mail delivery system. This registration helps you proactively manage your IP reputation by enabling you to take appropriate actions if your IP is flagged as a source of spam, thus reducing the risk of blacklisting.
+
+By default, the IP owner’s information (e.g., Scaleway/Online.net) is used to identify the association of an email address with a specific IP. However, if you have [properly configured the reverse DNS for your IP](/dedibox-ip-failover/how-to/configure-reverse-dns/), you can use an email address from your own domain for these notifications.
+
+Following these steps will help you maintain a clean email delivery system and protect your IP reputation.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+- [Configured the reverse DNS of your IP](/dedibox-ip-failover/how-to/configure-reverse-dns/)
+- [Created](https://signup.live.com/signup) a Microsoft account
+
+1. Open the [JMRP website](https://sendersupport.olc.protection.outlook.com/snds/JMRP.aspx) in your web browser.
+2. Log in using your Microsoft account credentials.
+3. Provide the necessary details about your IP addresses that you wish to register with the JMRP.
+4. Choose an email address that is associated with the domain configured in your reverse DNS settings. This address will receive notifications if your IP is flagged for sending spam.
+5. Follow the prompts to finalize your subscription to the JMRP.
diff --git a/pages/dedibox-network/index.mdx b/pages/dedibox-network/index.mdx
index f39d0c3fe9..003be32d0e 100644
--- a/pages/dedibox-network/index.mdx
+++ b/pages/dedibox-network/index.mdx
@@ -1,9 +1,32 @@
---
meta:
- title: Discover the Dedibox Network
- description: Discover the Dedibox Network
-content:
- h1: Discover the Dedibox Network
- paragraph: Discover the Dedibox Network
+ title: Dedibox - Network Documentation
+ description: Dive into Scaleway Dedibox - Network with our quickstart guides, how-tos, tutorials and more.
---
+
+
+## Getting Started
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/dedibox-network/reference-content/anti-ddos.mdx b/pages/dedibox-network/reference-content/anti-ddos.mdx
new file mode 100644
index 0000000000..abdcced5f2
--- /dev/null
+++ b/pages/dedibox-network/reference-content/anti-ddos.mdx
@@ -0,0 +1,26 @@
+---
+meta:
+ title: Scaleway Dedibox anti-DDoS solutions
+ description: This page explains the anti-DDoS technology used on Scaleway Dedibox.
+content:
+ h1: Scaleway Dedibox anti-DDoS solutions
+ paragraph: This page explains the anti-DDoS technology used on Scaleway Dedibox.
+tags: dedibox network anti-ddos ddos
+dates:
+ validation: 2024-08-26
+ posted: 2021-08-20
+categories:
+ - dedibox-network
+---
+
+Scaleway Dedibox provides comprehensive anti-DDoS protection for all its dedicated servers at no extra cost.
+This robust anti-DDoS system is built with state-of-the-art technology, leveraging advanced detection and mitigation algorithms powered by Arbor® Networks Peakflow and Sevi® M6-NG devices.
+
+Through swift identification of potential threats, Dedibox efficiently filters out malicious traffic, guaranteeing uninterrupted service delivery.
+Our strategically positioned equipment within the network core enables automatic detection of DDoS attacks, swiftly neutralizing any malicious activity and ensuring the seamless operation of your services.
+
+
+
+
+ If your activities require a higher level of management on the threat management system, two upgrade plans are available: Advanced and Curative. For more information, see the [anti-DDoS offers page](https://www.scaleway.com/en/dedibox/ddos-protection/).
+
\ No newline at end of file
diff --git a/pages/dedibox-network/reference-content/assets/scaleway-offre-ddos.webp b/pages/dedibox-network/reference-content/assets/scaleway-offre-ddos.webp
new file mode 100644
index 0000000000..0cb27ea8de
Binary files /dev/null and b/pages/dedibox-network/reference-content/assets/scaleway-offre-ddos.webp differ
diff --git a/pages/dedibox-network/reference-content/index.mdx b/pages/dedibox-network/reference-content/index.mdx
new file mode 100644
index 0000000000..a10e03ba18
--- /dev/null
+++ b/pages/dedibox-network/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox Network - Additional content
+ description: Dedibox Network additional content
+content:
+ h1: Dedibox Network - Additional content
+ paragraph: Dedibox Network additional content
+---
diff --git a/pages/dedibox-network/troubleshooting.mdx b/pages/dedibox-network/troubleshooting.mdx
new file mode 100644
index 0000000000..874c5c13c8
--- /dev/null
+++ b/pages/dedibox-network/troubleshooting.mdx
@@ -0,0 +1,154 @@
+---
+meta:
+ title: Dedibox Network - Troubleshooting
+ description: This page explains techniques for how to troubleshoot network related issues on your Scaleway Dedibox dedicated server.
+content:
+ h1: Dedibox Network - Troubleshooting
+ paragraph: This page explains techniques how to troubleshoot network-related issues on your Scaleway Dedibox dedicated server.
+tags: mtr-test dedibox network iperf mtr
+dates:
+ validation: 2024-08-26
+ posted: 2021-08-20
+categories:
+ - dedibox-network
+---
+
+## Running network tests
+
+To diagnose a network issue, you can perform different tests.
+
+## MTR test
+
+An MTR test combines the functions of traceroute and ping on all points between two machines.
+
+When running an MTR test, it is important to do it in both directions:
+
+- From the server to the IP of your connection
+- From your connection to the server
+
+### On Linux
+You have to check that the `mtr` packet is installed.
+
+```
+sudo apt-get install mtr
+```
+or
+```
+sudo yum install mtr
+```
+
+### On Windows
+
+
+ You have to install [WinMTR](https://sourceforge.net/projects/winmtr/) on your server.
+
+
+1. Download the application from its [project page](https://sourceforge.net/projects/winmtr/).
+2. Extract the archive and run the executable.
+3. Enter the target (IP) of your test in the Host text box, then click **Start**. Wait one or two minutes before you stop the test. You can then make a screenshot or export the result with the functions of the software.
+
+ Example of MTR between a Scaleway Dedibox server and `free.fr`:
+
+ ```
+ root@163-172-30-2:~# mtr --report free.fr
+ Start: Sun May 1 16:23:57 2016
+ HOST: 163-172-30-2 Loss% Snt Last Avg Best Wrst StDev
+ 1.|-- 163-172-30-1.rev.poneytel 0.0% 10 0.5 0.5 0.4 0.5 0.0
+ 2.|-- 195.154.1.248 0.0% 10 1.6 1.0 0.9 1.6 0.0
+ 3.|-- 195.154.1.254 0.0% 10 1.2 1.4 1.2 2.6 0.3
+ 4.|-- th2-crs16-1-be1503-t.intf 0.0% 10 1.3 1.3 1.1 1.4 0.0
+ 5.|-- p11-crs16-1-be1001.intf.r 0.0% 10 4.5 3.0 1.4 4.5 0.7
+ 6.|-- p11-9k-1-be1000.intf.rout 0.0% 10 1.5 2.1 1.4 3.5 0.6
+ 7.|-- bzn-9k-2-sys-be2001.intf. 0.0% 10 1.7 1.8 1.6 2.8 0.0
+ 8.|-- www.free.fr 0.0% 10 1.2 1.2 1.2 1.2 0.0
+ ```
+
+ The results show:
+
+ **Loss%**
+ : The percentage of lost packets
+
+ **Snt**
+ : The number of packets sent during the test (here 10)
+
+ **Last**
+ : The latency of the last packet sent between two points
+
+ **Avg**
+ : Average latency for all packets sent between two points
+
+ **Best**
+ : Latency of the best result
+
+ **Wrst**
+ : Latency of the worst result
+
+## iPerf test
+
+With an iPerf test, you can check the available bandwidth of your server.
+
+The iPerf server ping.online.net has several ports available (5200-5209). If the server is busy on the default port, you can specify another port using the `-p` flag, for example: `-p 5203 (5204, 5205, etc.)`.
+
+### On Linux
+
+If iPerf is not yet installed on your server, you can install it with the following command:
+
+```
+sudo apt-get install iperf3
+```
+or
+```
+yum apt-get install iperf3
+```
+
+Then launch the test:
+
+```
+root@163-172-30-2:~# iperf3 -c ping.online.net -R
+------------------------------------------------------------
+Client connecting to ping.online.net, TCP port 5001
+TCP window size: 85.0 KByte (default)
+------------------------------------------------------------
+[ 3] local 163.172.30.2 port 36490 connected with 62.210.18.40 port 5001
+[ ID] Interval Transfer Bandwidth
+[ 3] 0.0-10.0 sec 1.10 GBytes 943 Mbits/sec
+If your server is located at Amsterdam execute: root@163-172-30-2:~# iperf3 -c ping-ams1.online.net -R
+```
+
+### On Windows
+
+1. Download the tool [from its website](https://iperf.fr/iperf-download.php#windows).
+2. Choose the latest version and download the file.
+3. Extract the file.
+4. Open a terminal and run the following command:
+ ```
+ \iperf3.exe -c ping.online.net -p 5203
+ ```
+
+The results show:
+
+**Interval**
+: Sampling interval in seconds
+
+**Transfer**
+: Amount of data transferred during the test
+
+**Bandwidth**
+: Available bandwidth of your server
+
+## If your server's network port is off
+
+Sometimes when you change the mode of your dedicated server from normal to rescue mode during the reboot of a server, you may see the following error message in your console:
+
+
+ **Your server's network port is off.**
+ If you just asked for a server reboot, or to boot in rescue or test mode, this message will only be displayed for a few seconds. Otherwise, our network equipment may be on protective mode due to non-authorized traffic. In this case, ask the support team to unlock your server.
+
+
+If this message appears in cycles or for long periods, it means your server is distributing one of the following: unauthorized DHCP traffic, a MAC address unassigned to the server, ARP requests, or too many sending or receiving requests per second.
+
+If you continue to see this message, empty your browser cache, as the old page may be kept in it. Alternatively, you can reload the page several times until the message disappears.
+
+
+ When setting up the WAN interface on a PfSense firewall you should disable autoconfiguration, as it might cause an IPv6 packet flood, shutting down your server's network port. If your network ports do not become available after a few minutes, you need to contact the support.
+
\ No newline at end of file
diff --git a/pages/dedibox-rpn/concepts.mdx b/pages/dedibox-rpn/concepts.mdx
new file mode 100644
index 0000000000..ffb0b56b54
--- /dev/null
+++ b/pages/dedibox-rpn/concepts.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: Scaleway Dedibox RPN - Concepts
+ description: This page explains all the concepts related to RPN on Scaleway
+content:
+ h1: RPN - Concepts
+ paragraph: This page explains all the concepts related to RPN
+tags: dedibox rpn q-in-q rpn-san vlan
+dates:
+ validation: 2024-08-27
+categories:
+ - dedibox-network
+---
+
+## Q-in-Q mode
+
+Q-in-Q mode allows you to use more VLANs than you can use in Normal Mode.
+
+Q-in-Q takes the packets you send, along with your tags, and adds a special tag in the packet's header.
+This way, we keep your tags inside our tag, and use numerous possible VLANs on your side (up to 4096 per server).
+
+
+ Q-in-Q mode is not available on all offers. If you add a server that is not compatible with Q-in-Q mode, an error message displays. Do not hesitate to contact our [support team](https://console.online.net/en/assistance/ticket/list) if you have any questions regarding the Q-in-Q compatibility of a server.
+
+
+## RPN
+
+Real Private Network (RPN) is a second physical network that uses a dedicated Ethernet adapter to enable network coverage over all of Scaleway data centers. You can create "RPN Groups" with different servers that are able to communicate with each other. Servers of different accounts can be in the same RPN group, and each server can be in multiple groups. The RPN allows you to exchange internal data in a dedicated and secure network and without using the bandwidth of your internet connection. "Jumboframes" with an MTU of 9000 are supported in the RPN.
+
+## RPN SAN
+
+The RPN SAN is a network-attached storage providing additional storage for your Dedibox. The RPN-SAN Basic provides a cost-efficient way to extend your storage with HDD-based storage. The RPN-SAN HA provides high-available storage, replicated intra-DC, and is available in both HDD-based and SSD-based storage for best performance.
+
+## RPN v2
+
+RPN-v2 is a new version of Dedibox RPN Network (Real Private Network). It allows much more configuration, such as:
+
+- Custom address plan inside a private VLAN
+- Layer 2 Network
+- No MAC address restriction
+- Multicast
+
+## RPN VPN
+
+RPN VPN allows you to connect to your RPN group using a VPN. The VPN is based on OpenVPN to ensure easy configuration. You can add the VPN server to your RPN group as any other server.
+Notably, it allows you to securely connect from anywhere in your private network, as well as to connect servers that do not have an RPN interface to the RPN.
+
+## VLAN
+
+A virtual local area network (VLAN) is a logical group of workstations, servers, and network devices that appear to be on the same LAN despite their geographical distribution. The purpose of implementing a VLAN is to improve the performance of a network or apply appropriate security features.
+
+## VLAN ID
+
+VLANs are identified by a VLAN ID (a number between 0 – 4095), with the default VLAN on any network being VLAN 1. Each port on a switch or router can be assigned to be a member of a VLAN (enabling the receiving and sending traffic on that VLAN).
\ No newline at end of file
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-configure_iscsi.webp b/pages/dedibox-rpn/how-to/assets/scaleway-configure_iscsi.webp
new file mode 100644
index 0000000000..1839911302
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-configure_iscsi.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-datastore_device.webp b/pages/dedibox-rpn/how-to/assets/scaleway-datastore_device.webp
new file mode 100644
index 0000000000..38c40739d3
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-datastore_device.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-datastore_list.webp b/pages/dedibox-rpn/how-to/assets/scaleway-datastore_list.webp
new file mode 100644
index 0000000000..1b993a8f4c
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-datastore_list.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-enable_ssh.webp b/pages/dedibox-rpn/how-to/assets/scaleway-enable_ssh.webp
new file mode 100644
index 0000000000..5591ae31fb
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-enable_ssh.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-dashboard.webp b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-dashboard.webp
new file mode 100644
index 0000000000..5ddeadb071
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-dashboard.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-ssh.webp b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-ssh.webp
new file mode 100644
index 0000000000..4718772b4d
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-ssh.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-vmnic.webp b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-vmnic.webp
new file mode 100644
index 0000000000..f58349fb99
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-esxi7-vmnic.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-01.webp b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-01.webp
new file mode 100644
index 0000000000..a641ca91d8
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-01.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-02.webp b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-02.webp
new file mode 100644
index 0000000000..e5ed53a056
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-02.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-03.webp b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-03.webp
new file mode 100644
index 0000000000..787e2ef660
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-rpn-vpn-03.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch.webp b/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch.webp
new file mode 100644
index 0000000000..38dc6eb832
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch_connected.webp b/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch_connected.webp
new file mode 100644
index 0000000000..19651b343e
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-rpn_switch_connected.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway-vmkernel_nic.webp b/pages/dedibox-rpn/how-to/assets/scaleway-vmkernel_nic.webp
new file mode 100644
index 0000000000..6981cd0ecb
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway-vmkernel_nic.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-01.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-01.webp
new file mode 100644
index 0000000000..866efde393
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-01.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-02.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-02.webp
new file mode 100644
index 0000000000..1dcab9ff6f
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-02.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-03.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-03.webp
new file mode 100644
index 0000000000..8f201b06fd
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-03.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-04.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-04.webp
new file mode 100644
index 0000000000..c236e4b283
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-04.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-05.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-05.webp
new file mode 100644
index 0000000000..1c538eba18
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-05.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-06.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-06.webp
new file mode 100644
index 0000000000..6c56dd2071
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-06.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-07.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-07.webp
new file mode 100644
index 0000000000..3bf7905530
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-07.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-08.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-08.webp
new file mode 100644
index 0000000000..6e15960695
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-08.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-09.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-09.webp
new file mode 100644
index 0000000000..05c6fb6cea
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-09.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-10.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-10.webp
new file mode 100644
index 0000000000..423d24bfa2
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-10.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-11.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-11.webp
new file mode 100644
index 0000000000..1ab0a744b1
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-11.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-12.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-12.webp
new file mode 100644
index 0000000000..f8aa35256a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-12.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-13.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-13.webp
new file mode 100644
index 0000000000..273f4acb91
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-13.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-14.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-14.webp
new file mode 100644
index 0000000000..bc8e3d639a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-14.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-15.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-15.webp
new file mode 100644
index 0000000000..c3a88cea0a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-15.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-16.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-16.webp
new file mode 100644
index 0000000000..40f13f8833
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-16.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-17.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-17.webp
new file mode 100644
index 0000000000..94738b9a8a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-17.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-18.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-18.webp
new file mode 100644
index 0000000000..976f40af36
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi-san-en-18.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi_interfaces.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_interfaces.webp
new file mode 100644
index 0000000000..6950a05b8d
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_interfaces.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi_port_group.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_port_group.webp
new file mode 100644
index 0000000000..577e294824
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_port_group.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi_rpn.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_rpn.webp
new file mode 100644
index 0000000000..8e4517949d
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_rpn.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vlan.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vlan.webp
new file mode 100644
index 0000000000..bab32413d3
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vlan.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vswitch.webp b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vswitch.webp
new file mode 100644
index 0000000000..6edad12660
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_esxi_vswitch.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_proxmox_rpn.webp b/pages/dedibox-rpn/how-to/assets/scaleway_proxmox_rpn.webp
new file mode 100644
index 0000000000..5cfbb81e35
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_proxmox_rpn.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_add.webp b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_add.webp
new file mode 100644
index 0000000000..62b1d042e7
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_add.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_added.webp b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_added.webp
new file mode 100644
index 0000000000..aa1c21753a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_added.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_manage.webp b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_manage.webp
new file mode 100644
index 0000000000..356e95e5dd
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_rpn_san_manage.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_rpnv1_gateway.webp b/pages/dedibox-rpn/how-to/assets/scaleway_rpnv1_gateway.webp
new file mode 100644
index 0000000000..22bbe3acb1
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_rpnv1_gateway.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_01.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_01.webp
new file mode 100644
index 0000000000..84eed36c94
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_01.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_02.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_02.webp
new file mode 100644
index 0000000000..4a26051ce8
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_02.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_03.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_03.webp
new file mode 100644
index 0000000000..5d6c067be4
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_03.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_04.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_04.webp
new file mode 100644
index 0000000000..b6aa866c4a
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_04.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_05.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_05.webp
new file mode 100644
index 0000000000..75649ba163
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_05.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_06.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_06.webp
new file mode 100644
index 0000000000..51c823a8c4
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_06.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_07.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_07.webp
new file mode 100644
index 0000000000..689f3ed2c7
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_07.webp differ
diff --git a/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_08.webp b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_08.webp
new file mode 100644
index 0000000000..9910189be9
Binary files /dev/null and b/pages/dedibox-rpn/how-to/assets/scaleway_windows_server_san_08.webp differ
diff --git a/pages/dedibox-rpn/how-to/configure-jumboframes.mdx b/pages/dedibox-rpn/how-to/configure-jumboframes.mdx
new file mode 100644
index 0000000000..7d60df7681
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/configure-jumboframes.mdx
@@ -0,0 +1,100 @@
+---
+meta:
+ title: How to configure jumbo frames on Scaleway Dedibox RPN
+ description: This page explains how to configure jumbo frames on Scaleway Dedibox RPN
+content:
+ h1: How to configure jumbo frames on Scaleway Dedibox RPN
+ paragraph: This page explains how to configure jumbo frames on Scaleway Dedibox RPN
+tags: dedibox jumbo frames jumbo-frames rpn mtu NFS
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-network
+---
+
+The RPN network supports by default jumbo frames. This allows you to configure your network interfaces with an MTU 9000 (Maximum transfer unit).
+
+This technology allows you to significantly minimize the interruptions and processor latencies needed for data transfer. The performance gain can reach up to +20% on resource-intensive applications such as iSCSI, NFS, and DRDB.
+
+## How to check your current MTU settings
+
+1. To check your current MTU settings, type:
+ ```
+ ifconfig ethX | grep MTU
+ ```
+
+
+ Replace `ethX` with the name of your RPN interface.
+
+2. An output like the following example displays:
+ ```
+ root@my-dedibox-server:~# ifconfig ethX | grep MTU
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ ```
+
+ In the example above you can see the current MTU of the network interface is set to the Ethernet standard of 1500.
+
+
+## How to set the MTU 9000
+
+### On Linux
+
+#### CentOS
+
+1. Open the file `/etc/sysconfig/network-scripts/ifcfg-ethX`, where `X` is the number of your interface, in a text editor. Then add the following line to it:
+ ```
+ MTU="9000"
+ ```
+2. Restart the network service:
+ ```
+ service network restart
+ ```
+
+#### Debian
+
+1. Open the file `/etc/network/interfaces` in a text editor and insert `mtu 9000` below the line `iface ethX inet static`:
+ ```
+ auto ethX
+ iface ethX inet static
+ mtu 9000
+ [...]
+ ```
+2. Restart the network service:
+ ```
+ service network restart
+ ```
+
+#### Ubuntu
+
+1. Open the Netplan configuration file `/etc/netplan/01-netcfg.yaml` in a text editor and add the line `mtu: 9000` in the configuration of the RPN interface:
+ ```
+ ethernets:
+ enp3s0:
+ dhcp4: true
+ enp4s0:
+ addresses:
+ - 192.168.0.10/24
+ gateway4: 192.168.0.1
+ mtu: 9000
+ nameservers:
+ addresses:
+ - 1.1.1.1
+ - 2.2.2.2
+ ```
+2. Save the file, exit the text editor, and reload the network configuration:
+ ```
+ sudo netplan apply
+ ```
+
+### On Windows
+
+To change the MTU settings on Windows, you can use a tool like [TCP Optimizer](http://www.clubic.com/telecharger-fiche305576-tcp-optimizer.html) to modify the MTU settings.
+
+1. Download and start the tool.
+2. In the bottom right corner, click **Custom**.
+3. Go to **Network adapter selection** and select the RPN interface.
+4. Set the MTU value to `9000`.
+5. Click on **Apply change** to update the MTU settings.
+
+
diff --git a/pages/dedibox-rpn/how-to/configure-rpnv1-gateway.mdx b/pages/dedibox-rpn/how-to/configure-rpnv1-gateway.mdx
new file mode 100644
index 0000000000..3f1593c185
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/configure-rpnv1-gateway.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to configure the RPNv1 gateway on an RPNv2 Dedibox
+ description: This page explains how to configure the RPNv1 gateway on a Scaleway Dedibox
+content:
+ h1: How to configure the RPNv1 gateway on an RPNv2 Dedibox
+ paragraph: This page explains how to configure the RPNv1 gateway on a Scaleway Dedibox
+tags: dedibox rpnv1 rpnv2 rpn
+dates:
+ validation: 2024-08-26
+ posted: 2021-11-29
+categories:
+ - dedibox-network
+---
+
+If you have services that are available only on the RPNv1 (RPN SAN, server not compatible with RPNv2 etc), you can add a compatibility layer through your console.
+
+
+ This feature does currently not work with the RPN VPN and could cause problems across your whole RPN Group if you add it.
+
+
+In the RPNv2 management console, click on the corresponding button, and select an RPNv1 group that will be able to access it.
+
+Once you have done that, you can either restart your DHCLIENT on your RPNv1 servers for them to get the new routes or manually add a route to `10.88.0.0/13` through your existing RPN Gateway.
+
+You can do it with the following snippet:
+
+```
+ip route add 10.88.0.0/13 via $RPNGW
+```
+
+
+ Make sure to replace `$RPNGW` with your actual RPN Gateway.
+
+
+On the RPNv2 servers, you will be provided with an RPNv1 subnet usable on your VLAN ID. If, for example, you get the following block: `10.88.101.0/28`.
+
+* The IP `10.88.101.1` will be your gateway on the RPNv1 network for the RPNv2 server.
+* The IPs `10.88.101.2-14` can be used on your RPNv2 servers.
+
+1. Configure your interfaces as shown below in `/etc/network/interfaces` (on a Debian-based machine):
+ ```
+ iface eth1.3900:0 inet static
+ address 10.88.101.2
+ netmask 255.255.255.240
+ ```
+
+
+ The name of your network adapter may be different, depending on your OS version. You can use `ifconfig` to display information about your network adapters.
+
+2. Add the route for the whole network:
+ ```
+ ip route add 10.88.0.0/13 via 10.88.101.1
+ ```
+
+Find below a schema of how this works for all your RPN services (v1 and v2):
+
+
+
+
diff --git a/pages/dedibox-rpn/how-to/configure-rpnv1.mdx b/pages/dedibox-rpn/how-to/configure-rpnv1.mdx
new file mode 100644
index 0000000000..89eca7b729
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/configure-rpnv1.mdx
@@ -0,0 +1,56 @@
+---
+meta:
+ title: How to configure Scaleway Dedibox RPNv1 on a Dedibox
+ description: This page explains how to configure Scaleway Dedibox RPNv1 on a Dedibox
+content:
+ h1: How to configure Scaleway Dedibox RPNv1 on a Dedibox
+ paragraph: This page explains how to configure Scaleway Dedibox RPNv1 on a Dedibox
+tags: dedibox rpn rpnv1
+dates:
+ validation: 2024-08-26
+ posted: 2022-10-17
+categories:
+ - dedibox-network
+---
+
+The private RPNv1 network is connected to the second physical interface of your Dedibox. It is connected to a totally secure network, different from the one you use to connect to the internet.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) with RPNv1 connectivity
+
+## How to create a new RPNv1 group from the Scaleway console
+
+1. Click **RPN** > **RPN groups** in the navigation bar on top of your console to enter the [RPN groups configuration](http://console.online.net/en/server/rpn) page.
+2. Click **Create group** to create a new RPN group. The group creation interface displays.
+3. Enter a name for your RPN group, select the Dedibox servers you want to add to the group, and save.
+
+
+
+ It takes about five to ten minutes to activate a new RPNv1 group. Once the group is enabled, its status changes to **active**.
+
+
+
+## How to update or modify an RPNv1 group
+
+1. Click **RPN** > **RPN groups** in the navigation bar on top of your console to enter the [RPN groups configuration](http://console.online.net/en/server/rpn) page.
+2. Click **Edit group** below the server listing of the group you want to edit.
+
+ * Tick the boxes next to the servers you want to remove from the group. Then click **Remove selected servers from group**.
+ * Click **Add servers to the group** to add more servers to the RPN group. A pop-up displays. Tick the boxes next to the servers you want to add. Save by clicking **Add to group**.
+
+The servers are added/removed from the group and the RPN configuration is being updated.
+
+## How to share an RPN group with another Dedibox user
+
+1. Click **RPN** > **RPN groups** in the navigation bar on top of your console to enter the [RPN groups configuration](http://console.online.net/en/server/rpn) page.
+2. Click the **Shared groups** tab to display the list of the shared RPN groups.
+3. Click **Share existing local group**. The group sharing wizard displays.
+4. Select the group to share from the drop-down menu and enter the ID of the server you want to add. Then click **Share group** to save.
+
+
+ The owner of the server external to your account receives an email to confirm the sharing of the RPN group. You can not reach any external server until the RPN sharing has been confirmed by the server owner.
+
+
+
diff --git a/pages/dedibox-rpn/how-to/configure-rpnv2.mdx b/pages/dedibox-rpn/how-to/configure-rpnv2.mdx
new file mode 100644
index 0000000000..47767ad92b
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/configure-rpnv2.mdx
@@ -0,0 +1,188 @@
+---
+meta:
+ title: How to configure Scaleway Dedibox RPNv2
+ description: This page explains how to configure Scaleway Dedibox RPNv2 on a Dedibox dedicated server.
+content:
+ h1: How to configure Scaleway Dedibox RPNv2
+ paragraph: This page explains how to configure Scaleway Dedibox RPNv2 on a Dedibox dedicated server.
+tags: dedibox rpnv2 rpn
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-16
+categories:
+ - dedibox-network
+---
+
+[RPNv2](/dedibox-rpn/concepts/#rpn-v2) can be configured on any operating system supporting VLANs. The feature is available for selected Dedibox servers.
+
+## How to configure RPNv2 on Debian
+
+1. Install the vlan package by running the following command:
+ ```
+ sudo apt-get install vlan
+ ```
+2. Edit your `/etc/network/interfaces` file as follows (assuming your RPN NIC is `eth1` and your VLAN ID is `3900`):
+ ```
+ auto eth1.3900
+ iface eth1.3900 inet static
+ address my.pri.vate.address
+ netmask my.custom.net.mask
+ ```
+
+## How to configure RPNv2 on Ubuntu
+
+
+ The following configuration example uses [Netplan](https://netplan.io/). If you are using a classic network configuration, refer to the [Debian documentation](https://www.debian.org/doc/).
+
+
+```
+network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ mainif:
+ match:
+ macaddress: "de:ad:be:ef:ca:fe"
+ set-name: mainif
+ addresses: [ "10.3.0.5/23" ]
+ gateway4: 10.3.0.1
+ nameservers:
+ addresses: [ "8.8.8.8", "8.8.4.4" ]
+ search: [ example.com ]
+ vlans:
+ vlan15:
+ id: 15
+ link: mainif
+ addresses: [ "10.3.99.5/24" ]
+```
+
+## How to configure RPNv2 on CentOS
+
+In the following 'how to' we assume your RPN NIC is `eth1`.
+
+1. Create a configuration file for the parent interface, called `/etc/sysconfig/network-scripts/ifcfg-eth1`:
+ ```
+ DEVICE=eth1
+ TYPE=Ethernet
+ BOOTPROTO=none
+ ONBOOT=yes
+ ```
+2. Create another file for the vlan interface (assuming the VLAN ID is `3900`). The file is called `/etc/sysconfig/network-scripts/ifcfg-eth1.3900`:
+ ```
+ DEVICE=eth1.3900
+ BOOTPROTO=none
+ ONBOOT=yes
+ IPADDR=my.pri.vate.address
+ PREFIX=CIDR.Netmask
+ NETWORK=my.private.address.0
+ VLAN=YES
+ ```
+## How to configure RPNv2 on Rocky Linux 9
+
+For this how-to, we assume that your RPN NIC is `eth1`, the VLAN ID is `2001` and the new connection name is `VLAN2001`.
+
+To add a new VLAN connection using the nmcli command, follow the steps below:
+
+```
+[root@srv1 ~]# nmcli connection add type vlan ifname VLAN2001 dev eth1 id 2001
+Connection 'vlan-VLAN2001' (116121e0-4dca-4fb7-82ac-6e38b0f7d277) successfully added.d
+```
+
+Show the updated VLAN connection:
+
+```
+[root@srv1 ~]# nmcli connection show
+NAME UUID TYPE DEVICE
+vlan-VLAN2001 116121e0-4dca-4fb7-82ac-6e3888f7d277 vlan VLAN2001
+```
+
+Configure the second server to enable reachability from the group members.
+
+Assign an IP address to VLAN `2001` (your VLAN ID) on `serv1` and change `ipv4.method` to use the manual method
+
+```
+nmcli connection modify vlan-VLAN2001 ipv4.addresses 192.168.10.101/24 ipv4.method manual ipv4.addresses
+nmcli connection up vlan-VLAN2001
+```
+
+Assign an IP address to VLAN `2001` (your VLAN) on `serv2` and change `ipv4.method` to use the manual method
+
+```
+nmcli connection modify vlan-VLAN2001 ipv4.addresses 192.168.10.100/24 ipv4.method manual ipv4.addresses
+nmcli connection up vlan-VLAN2001
+```
+
+Test your configuration via `ping`:
+
+From 192.168.0.100 to 192.168.0.101
+
+```
+[root@srv1 ~]# ping 192.168.0.101
+PING 192.168.0.101 (192.168.0.101) 56(84) bytes of data.
+64 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=12.9 ms
+64 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=12.9 ms
+64 bytes from 192.168.0.101: icmp_seq=3 ttl=64 time=13.1 ms
+```
+
+From 192.168.0.100 to 192.168.0.100
+
+```
+[root@frontend-srv ~]# ping 192.168.0.100
+PING 192.168.0.100 (192.168.0.100) 56(84) bytes of data.
+64 bytes from 192.168.0.100: icmp_seq=1 ttl=64 time=13.2 ms
+64 bytes from 192.168.0.100: icmp_seq=2 ttl=64 time=13.1 ms
+64 bytes from 192.168.0.100: icmp_seq=3 ttl=64 time=13.1 ms
+```
+
+## How to configure RPNv2 on FreeBSD
+
+Edit your `/etc/rc.conf file`, assuming `ix0` is your RPN NIC, and `3900` your VLAN ID:
+
+```
+ifconfig_ix0="up"
+cloned_interfaces="vlan3900"
+ifconfig_vlan3900="inet my.pri.vate.IP/CIDR.NETMASK vlan 3900 vlandev ix0"
+```
+
+Do not forget to adapt the VLAN ID, Interface Name, and Network configuration to your needs.
+
+## How to configure RPNv2 on ESXi
+
+
+ Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Please note that the following content is provided as-is, without any guarantee of functionality.
+We suggest considering alternative hypervisors such as Proxmox. You can learn how to [deploy virtual machines with Proxmox on Scaleway Dedibox](/tutorials/configure-failover-proxmox/).
+
+
+On ESXi, you can create virtual switches that talk directly on the corresponding VLAN ID.
+
+1. Check your network interfaces, to discover which one corresponds to the RPN interface. In the following example, the RPN interface is `vmnic2`.
+
+2. Enter the **Virtual switch** section and add a new one by clicking **Add standard virtual switch**:
+
+3. Enter a name for the virtual switch, set the MTU to `9000`, and select the RPN interface as uplink:
+
+4. Click the **Port groups** tab and click **Add port group** to create a new one:
+
+5. Enter a name for the new port group and set the VLAN IP, then select the virtual switch and click **Add**.
+
+
+The virtual switch is configured now.
+
+Create a NIC directly linked to your new Group (**VM Network** in the example above) and configure it in your virtual machine using your address-plan.
+
+
+ No VLAN Configuration is required in your VM, everything is handled in your vSwitch directly.
+
+
+## How to configure RPNv2 on Proxmox
+
+1. Login to the Proxmox web interface and click **System** > **Network**.
+2. Click **Create** on the network page.
+3. Configure your bridge with a `bridge_port` which will be named after your RPN NIC, and your VLAN ID.
+
+
+
+ For instance, if your RPN NIC is eth2 and your VLAN ID 3900, name it `eth2.3900`.
+
+
+
diff --git a/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx b/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx
new file mode 100644
index 0000000000..257ae7390b
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: How to connect Windows Server to an RPN SAN
+ description: This page explains how to connect Windows Server to a Scalway Dedibox RPN SAN
+content:
+ h1: How to connect Windows Server to an RPN SAN
+ paragraph: This page explains how to connect Windows Server to a Scaleway Dedibox RPN SAN
+tags: dedibox windows-server windows server rpn san
+dates:
+ validation: 2024-08-12
+ posted: 2021-07-16
+categories:
+ - dedibox-network
+---
+
+The [RPN SAN](/dedibox-rpn/concepts/#rpn-san) is an iSCSI target, it is possible to mount it in Windows Server 2012 or later to use it as a normal disk in the system.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+1. Launch the **Server Manager** application of Windows and click **Tools** > **iSCSI Initiator**.
+
+2. Click the **Discovery** tab to add the SAN server:
+
+
+
+ The initiator is not activated by the default on the system start. If you start it for the first time, you are asked if you want to start it during the system start. Click **yes** to confirm.
+
+3. Click the **Targets** tab and select the target you want to connect to. Click **Connection** to confirm. The target will then be connected to the server as an unformatted disk.
+
+4. Launch the control panel and click **System and Security** > **Create and format hard disk partitions** in the **Administrative Tools** section.
+
+5. The disk can be configured from the **Storage** > **Disk Management** section of the **Computer Management** tool. By default, it displays as offline.
+
+6. Right-click on it and click **Online** to activate the disk. The system will propose the type of partition table to use for your disk.
+
+
+
+ For a 1 TB SAN, keep the default choice. If you have a larger SAN, select GPT, Windows can not handle partitions larger than 2 TB with anything except GPT.
+
+7. Format the disk with a file system (NTFS). Click **Next** > **Finish** to confirm formatting the disk.
+
+
+ Once finished formatting (in about 10 minutes using quick formatting), the hard disk drive should be accessible from the server manager as a regular disk:
+
+
+
+
diff --git a/pages/dedibox-rpn/how-to/connect-rpn-san.mdx b/pages/dedibox-rpn/how-to/connect-rpn-san.mdx
new file mode 100644
index 0000000000..b6abdfd2d1
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/connect-rpn-san.mdx
@@ -0,0 +1,58 @@
+---
+meta:
+ title: How to connect a Dedibox to RPN SAN
+ description: This page explains how to connect a Scaleway Dedibox to RPN SAN
+content:
+ h1: How to connect a Dedibox to RPN SAN
+ paragraph: This page explains how to connect a Scaleway Dedibox to RPN SAN
+tags: dedibox rpn san
+dates:
+ validation: 2024-08-12
+ posted: 2021-07-16
+categories:
+ - dedibox-network
+---
+
+[RPN SAN](https://www.scaleway.com/en/dedibox/storage/) is a performance-oriented SAN storage network solution (Storage Area Network) accessible in block mode and available in iSCSI through the RPN private network of your Dedibox.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+
+ - RPN SAN does not support RPNv2. To use RPNv2, you either need a server with an RPNv1 connection **or** to [enable the RPNv1 gateway](/dedibox-rpn/how-to/configure-rpnv1-gateway/).
+ - You must authorize the server(s) to connect to your RPN SAN.
+
+
+## How to authorize servers to connect to a SAN
+
+1. Enter the [RPN SAN configuration](https://console.online.net/en/server/rpn/san) by clicking **Storage** > **RPN SAN**. The list of your SANs displays.
+2. Click **Manage** next to the SAN you want to configure:
+
+3. Configure access to the SAN. You can allow connections either by using the server ID or by their RPN IP address. Then Click **Save** to validate the configuration.
+
+
+The allowed server(s) are listed on the SAN overview page.
+
+
+ Some SAN endpoints may not be reachable directly from the RPNv2, and it is required to configure an [RPNv1 gateway](/dedibox-rpn/how-to/configure-rpnv1-gateway/) to use them with RPNv2.
+
+
+## How to add a SAN to an RPN group
+
+
+ Recent SANs must be a member of an RPN group to be accessible. If your SAN is located on a SAN target >24 for SAN HA or >24 for SAN basic, you need to add the RPN SAN to your RPN group to access it.
+
+
+
+ **⚠ You must create or add your SAN RPN in an RPNv1 group with your servers.**
+
+
+1. Access the [RPN group](https://console.online.net/en/server/rpn) configuration by clicking **RPN** > **RPN groups** The list of your RPN groups displays.
+2. Click **Create group**. The group creation form displays. Enter a name for the new group and tick the checkboxes of your Dedibox and the RPN SAN you want to grant access to. Then click **Create group** to confirm. The RPN group is scheduled for creation.
+3. Once the status of your group changes to **Active** the group is ready to be used and your Dedibox is able to communicate with the SAN.
+
+
+
diff --git a/pages/dedibox-rpn/how-to/find-rpn-gateway.mdx b/pages/dedibox-rpn/how-to/find-rpn-gateway.mdx
new file mode 100644
index 0000000000..57491508ee
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/find-rpn-gateway.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: How to find your RPNv1 gateway
+ description: This page explains how to find your RPNv1 gateway on Scaleway Dedibox servers
+content:
+ h1: How to find your RPNv1 gateway
+ paragraph: This page explains how to find your RPNv1 gateway on Scaleway Dedibox servers
+tags: dedibox rpnv1 rpn
+dates:
+ validation: 2024-11-18
+ posted: 2021-11-10
+categories:
+ - dedibox-network
+---
+
+Your RPNv1 gateway may differ from one Dedibox to another for technical reasons.
+It is normally pushed by DHCP, and configured automatically. However, in some cases you may need to know the details of the gateway.
+
+You can find the RPNv1 gateway for your Dedibox in the Scaleway console, or by running the following commands.
+
+
+
+- A Dedibox account logged into the [Dedibox console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) with an RPN interface
+
+1. Connect to your Dedibox using SSH.
+2. Install the `iproute2` package, if not done yet. For Debian and Ubuntu, use the following command to install it:
+ ```
+ apt install iproute2
+ ```
+3. Run the `ip route show` command to display your RPNv1 gateway. An output as the following displays:
+ ```
+ # ip route show
+ 10.90.0.0/XX via X.X.X.X ...
+ ```
+ The output contains the following information:
+ * `10.90.0.0/XX`: Your RPNv1 IP subnet. The part after the `/` represents the [CIDR netmask](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) of your subnet.
+ * `X.X.X.X`: The IP address of the gateway. The gateway is always the first IP of the subnet.
+
+
+ The gateway does not ping, this is normal behavior.
+
+
+
+ If you know your RPN netmask, you can also find your gateway by using `ipcalc`.
+ - Run the following command to calculate the IP address of your RPNv1 gateway:
+ ```
+ # ipcalc -b [SET_HERE_YOUR_RPN_IP]/[CIDR_NETMASK] | grep HostMin
+ HostMin: X.X.X.X
+ ```
+ The gateway is located at the IP address in place of `X.X.X.X`.
+
+
+
diff --git a/pages/dedibox-rpn/how-to/index.mdx b/pages/dedibox-rpn/how-to/index.mdx
new file mode 100644
index 0000000000..f3e0ce7990
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: RPN - How Tos
+ description: RPN How Tos
+content:
+ h1: RPN - How Tos
+ paragraph: RPN How Tos
+---
diff --git a/pages/dedibox-rpn/how-to/mount-rpn-san-linux.mdx b/pages/dedibox-rpn/how-to/mount-rpn-san-linux.mdx
new file mode 100644
index 0000000000..ca49278b57
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/mount-rpn-san-linux.mdx
@@ -0,0 +1,109 @@
+---
+meta:
+ title: How to mount a Scaleway Dedibox RPN-SAN volume on Linux
+ description: This page explains how to mount a Scaleway Dedibox RPN-SAN volume on Linux
+content:
+ h1: How to mount a Scaleway Dedibox RPN-SAN volume on Linux
+ paragraph: This page explains how to mount a Scaleway Dedibox RPN-SAN volume on Linux
+tags: rpn san rpn-san volume linux dedibox open iscsi
+dates:
+ validation: 2024-08-26
+ posted: 2021-11-10
+categories:
+ - dedibox-network
+---
+
+You can mount RPN SAN volumes on Linux machines using Open-iSCSI.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+## How to install and configure Open-iSCSI
+
+1. Update the APT package cache and install Open-iSCSI:
+ ```
+ apt update && apt install -y open-iscsi
+ ```
+2. Open the file `/etc/iscsi/iscsid.conf` in a text editor:
+ ```
+ nano /etc/iscsi/iscsid.conf
+ ```
+3. Add the following configuration lines:
+ ```
+ node.conn[0].timeo.noop_out_interval = 0
+ node.conn[0].timeo.noop_out_timeout = 0
+ node.session.timeo.replacement_timeout = 86400
+ ```
+ The purpose of this modification is to prevent your file system from becoming read-only if the link is interrupted for more than two minutes (by default) between your server and the storage server.
+4. Adjust the setting for automatic reconnection of targets
+ ```
+ node.startup = automatic
+ ````
+5. Change the following settings to benefit from the data integrity check, if available:
+ ```
+ node.conn[0].iscsi.HeaderDigest = CRC32C,None
+ node.conn[0].iscsi.DataDigest = CRC32C,None
+ ```
+
+## How to discover and connect to targets
+
+1. Run the following command to obtain the list of available targets:
+ ```
+ iscsiadm -m discovery -t sendtargets -p SAN_SERVER
+ ```
+
+
+ The `SAN_SERVER` address is displayed in your Dedibox console.
+
+
+ The target name should look like the following example:
+ ```
+ X.X.X.X:3260,1 iqn.2013-01.net.online:XXXXXXXXXXX
+ ```
+2. Connect to the target by typing the following command:
+ ```
+ iscsiadm -m node -T iqn.2013-01.net.online:XXXXXXXXXXX --login
+ ```
+3. Type `dmesg` to see the kernel logs. You should see some lines like in the following example
+ ```
+ scsi25 : iSCSI Initiator over TCP/IP
+ scsi 25:0:0:0: Direct-Access IET VIRTUAL-DISK 0 PQ: 0 ANSI: 4
+ sd 25:0:0:0: Attached scsi generic sg4 type 0
+ sd 25:0:0:0: [sdd] 2147483648 512-byte logical blocks: (1.09 TB/1.00 TiB)
+ sd 25:0:0:0: [sdd] Write Protect is off
+ sd 25:0:0:0: [sdd] Mode Sense: 77 00 00 08
+ sd 25:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
+ sdd: sdd1
+ sd 25:0:0:0: [sdd] Attached SCSI disk
+ ```
+ In the example above, the disk detected is `sdd`, available at `/dev/sdd`.
+
+
+ The assigned device name may be different, depending on your configuration.
+
+
+ You can now use your SAN disk like you would any other disk.
+
+## Important recommendations for use
+
+As seen in the example above, the disk is available as `/dev/sdd.` It is not guaranteed that at the next reboot the same drive letter will be used, especially if you add other targets, or if your hardware configuration changes. It is therefore recommended not to use the names `/dev/sdX` in your configuration files.
+
+### How to address devices when using LVM
+LVM automatically uses UUIDs to recognize the partitions it uses. In this case, no problems should arise.
+
+### How to address devices when using direct disk formatting
+
+
+ This method is not recommended, because it aggregates several RPN SAN storage spaces, and does not allow you to make changes afterward.
+
+
+If you format the device or one of its partitions directly, use the link created by the system in `/dev/disk/by-uuid/` or the fstab notation `UUID=XXX-XXX...` for addressing purposes.
+
+### How to address devices directly by their UUID
+
+If (unlike LVM) your application does not support the auto-detection of the partitions associated with it via the UUID, it is recommended to use the link in `/dev/disk/by-id/`.
+
+
diff --git a/pages/dedibox-rpn/how-to/use-rpn-san-esxi-v7.mdx b/pages/dedibox-rpn/how-to/use-rpn-san-esxi-v7.mdx
new file mode 100644
index 0000000000..ef238e5271
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/use-rpn-san-esxi-v7.mdx
@@ -0,0 +1,145 @@
+---
+meta:
+ title: How to mount an RPN SAN volume in VMware ESXi 7 and later
+ description: This page explains how to mount a Scaleway RPN SAN volume in VMware ESXi 7 and later
+content:
+ h1: How to mount an RPN SAN volume in VMware ESXi 7 and later
+ paragraph: This page explains how to mount a Scaleway RPN SAN volume in VMware ESXi 7 and later
+tags: dedibox rpn san vmware esxi esxi7
+dates:
+ validation: 2024-08-12
+ posted: 2021-11-10
+categories:
+ - dedibox-network
+---
+
+
+ Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Please note that the following content is provided as-is, without any guarantee of functionality.
+We suggest considering alternative hypervisors such as Proxmox. You can learn how to [deploy virtual machines with Proxmox on Scaleway Dedibox](/tutorials/configure-failover-proxmox/).
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+
+ This documentation covers **VMware ESXi version 7** and later. Follow [this link](/dedibox-rpn/how-to/use-rpn-san-esxi/) to see the documentation for ESXi 5.0/5.1/5.5 and 6.0.
+
+
+## How to configure VMware ESXi to use RPN
+
+### Enable SSH on your ESXi
+
+1. Log into the ESXi web interface at `https://YOUR_ESXI_HOST_IP`.
+
+ Use the `root` user and the password set during installation of the machine to log in.
+
+
+ Once logged in, the ESXi dashboard displays.
+
+
+2. Click **Manage** in the menu on the left. Then click the **Services** tab to display a list of available services.
+3. Select **TSM-SSH**, then click **Start** to activate the SSH service.
+
+
+### Configure ESXi to access the RPN
+
+#### Configuration in the ESXi interface
+
+1. Connect to your Dedibox server by typing the server's IP address in a web browser. The ESXi login displays. Enter your credentials to log in.
+2. Click **Actions** > **Services** > **Enable Secure Shell (SSH)**:
+
+
+ The following warning displays once SSH is enabled: **SSH is enabled on this host. You should disable SSH unless it is necessary for administrative purposes**.
+3. Create a new **Virtual Switch** by clicking on **Networking** > **Virtual Switches** > **Add Standard Virtual Switch**. Configure it as shown in the following example:
+
+4. Create a new **VMkernel NIC** by clicking on **Networking** > **VMkernel NICs** > **Add VMkernel NIC** and configure it as follows.
+
+
+
+ Make sure to configure Jumboframes (MTU 9000) both for the switch and the NIC.
+
+5. Connect to your server using SSH. The SSH credentials are identical to those for the web interface.
+6. Locate the MAC address of the network card connected to the RPN (MTU 9000):
+ ```
+ esxcfg-nics -l
+ ```
+7. Export the current VMkernel NIC configuration:
+ ```
+ configstorecli config current get -c esx -g network -k vmknics > vmknics.json
+ ```
+8. Open the VMkernel NIC configuration file in a text editor:
+ ```
+ vi vmknics.json
+ ```
+9. Replace the MAC address of your RPN VMkernel NIC with your [virtual MAC](/dedibox-ip-failover/how-to/create-virtual-mac/).
+
+10. Import the new configuration:
+ ```
+ configstorecli config current set -c esx -g network -k vmknics -i vmknics.json --overwrite
+ ```
+11. Reboot the machine to activate the new configuration.
+### Setting RPN routes
+
+1. Enter the ESXi web interface, click **Networking** > **Virtual Switches** > **RPN Switch** and check the IP address of the VMkernel NIC. It now has the RPN IP auto-assigned to the interface via DHCP:
+
+2. Reactivte the SSH service and connect to the machine via SSH.
+3. Run the following command to add the RPN route:
+ ```
+ esxcfg-route -a 10.88.0.0/13 [YOUR_RPN_GATEWAY_IP]
+ ```
+
+
+ You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-rpn/how-to/find-rpn-gateway/).
+
+4. Ping the RPN-SAN to check if the RPN connection is working properly:
+ ```
+ ping san-1.rpn.online.net
+ ```
+5. Open the file `/etc/rc.local.d/local.sh` in a text editor and add the following lines to it to configure the RPN route automatically during boot:
+ ```
+ esxcfg-route -a 10.88.0.0/13 [YOUR_RPN_GATEWAY_IP]
+ exit 0
+ ```
+
+### Connecting the RPN-SAN
+
+To be able to communicate with the RPN-SAN, you need to allow your servers to access it.
+
+1. Connect to the Dedibox console and click **Storage** > **RPN-SAN**.
+2. Select the SAN you want to configure and click **Manage**.
+3. Add the server(s) you want to access your SAN services to the list. Optionally you can add RPN subnet IPs.
+
+ If you use RPNv2, an [additional configuration](/dedibox-rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN.
+
+
+
+ While it is technically possible, it is not recommended to allow more than one server at a time to communicate with the SAN. The iSCSI protocol does not handle concurrency: you may lose all your data if you allow more than one server to access this storage.
+
+4. Click **Save** to validate the new configuration of the SAN.
+5. Connect to the ESXi web interface of your server.
+6. Click **Storage** > **Adapters** > **Software iSCSI**. A configuration pop-up displays.
+7. **Enable** the service. Click **Add port binding** and add the RPN Network. Then click **Add dynamic target** and enter the address of your SAN. Then, click **Save configuration**:
+
+
+ESXi rescans for devices, and you can see the new iSCSI disk in the **Devices** tab of the storage section.
+
+## Adding a new Datastore
+
+To use the RPN-SAN with ESXi, you need to create a new datastore. To do so, follow these steps:
+
+1. Connect to the ESXi web interface, then click **Storage** > **Datastores** > **New Datastore**.
+2. Select **Create new VMFS datastore** and click **Next**.
+3. Enter a name for the new datastore and select the RPN-SAN iSCSI disk from the list of available devices. Then click **Next**:
+
+4. Configure the partitioning of the datastore. Then click **Next**. A summary displays.
+5. Validate all given information and click **Finish** to format the device.
+
+ Be careful, formatting the device deletes all data you may have stored on it.
+
+6. The newly created datastore displays in the datastore list and is ready for use:
+
+
+
diff --git a/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx b/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx
new file mode 100644
index 0000000000..e1dd7e5b02
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx
@@ -0,0 +1,137 @@
+---
+meta:
+ title: How to mount an RPN SAN volume in VMware ESXi
+ description: This page explains how to mount a Scaleway Dedibox RPN SAN volume in VMware ESXi
+content:
+ h1: How to mount an RPN SAN volume in VMware ESXi
+ paragraph: This page explains how to mount an RPN SAN volume in VMware ESXi
+tags: dedibox rpn san vmware esxi
+dates:
+ validation: 2024-08-12
+ posted: 2021-11-10
+categories:
+ - dedibox-network
+---
+
+
+ Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Please note that the following content is provided as-is, without any guarantee of functionality.
+We suggest considering alternative hypervisors such as Proxmox. You can learn how to [deploy virtual machines with Proxmox on Scaleway Dedibox](/tutorials/configure-failover-proxmox/).
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+
+ This documentation covers **VMware ESXi version ESXi 5.0/5.1/5.5 and 6.0** and later. Follow [this link](/dedibox-rpn/how-to/use-rpn-san-esxi-v7/) to see the Documentation for ESXi 7 and later.
+
+
+## How to configure VMware ESXi to use RPN
+
+### Enable SSH on your ESXi
+
+1. Start the vSphere client or log in using the web interface.
+2. Click the Configuration tab (1), then click **Security Profile** (2) in the software panel.
+
+3. Click **Properties** in the Services section.
+
+4. Select SSH (1) then click options (2). Select **Start and stop manually** (3) and launch the service manually (4).
+
+
+### Configure ESXi to access the RPN
+
+#### Configuration in the ESXi interface
+
+1. Go to **Configuration** > **Networking** (1). Then, click **Add Networking** (2).
+
+2. Create a new VMKernel named **RPN**, attached to the RPN network card.
+
+
+
+
+For the next step, validate the windows by choosing **Automatic recovery** for the IP addressing.
+
+
+ The network will go down because the virtual MAC is not the same as the physical one (for security reasons).
+
+
+#### Configuration of the MTU 9000
+
+1. Go to **Configuration** > **Networking** > **Properties...** (of vSwitch1).
+
+2. Select the vSwitch (1) and edit it (2).
+
+3. Set the MTU to **9000**, then confirm and quit.
+
+
+### ESXi configuration
+
+1. Edit the configuration file of ESXi.
+ ```
+ nano /etc/vmware/esx.conf
+ ```
+2. Locate the number of the child in the RPN portgroup (in this example: 0001).
+ ```
+ /net/vmkernelnic/child[0001]/portgroup = "RPN"
+ ```
+3. Locate the MAC of the network card connected to the RPN (in this example: `XX:YY:ZZ:AA:BB:CC`).
+ ```
+ /net/pnic/child[0001]/mac = "XX:YY:ZZ:AA:BB:CC”
+ ```
+4. Replace the MAC of the VMKernel RPN (see the number of the child) with the MAC of the network card connected to the RPN.
+ ```
+ /net/vmkernelnic/child[0001]/mac = "XX:YY:ZZ:AA:BB:CC”
+ ```
+5. Reboot the ESXi to take the changes into effect.4. Replace the MAC of the VMKernel RPN (see the number of the child) with the MAC of the network card connected to the RPN.
+ ```
+ /net/vmkernelnic/child[0001]/mac = "XX:YY:ZZ:AA:BB:CC”
+ ```
+5. Reboot the ESXi to take the changes into effect. ```
+
+ You need to add the route to `/etc/rc.`local` to keep it after a reboot.
+ For the version ESXi 5.1 the file is located at `/etc/rc.local.d/local.sh`.
+
+7. Ping the RPN SAN to check your configuration.
+ ```
+ # ping san-1.rpn.online.net
+ PING 10.90.254.2 (10.90.254.2): 56 data bytes
+ 64 bytes from 10.90.254.2: icmp_seq=0 ttl=61 time=0.241 ms
+ 64 bytes from 10.90.254.2: icmp_seq=1 ttl=61 time=0.241 ms
+ ```
+
+ The `ping` command must work. If not, check your configuration.
+
+
+#### Configuration from the ESXi interface
+
+1. Go back to **Configuration**, then click **Storage Adapter** (1) followed by **Add...** (2).
+
+2. Select **Add Software iSCSI Adapter**, then, click **OK**.
+
+
+ A new device created `vmhba32` should appear in the adapter list.
+3. Click the device (1), then, go to **Properties** (2).
+
+4. Go to the **Dynamic Discovery** tab (1), then click on **Add...** (2).
+
+5. Enter the RPN server address in the **iSCSI Server** box (the address is available in your Dedibox console).
+
+6. Click **OK** > **Close**. Then accept the rescan that is proposed.
+
+ * The IET disk is displayed in the device list in the bottom panel.
+7. Go to **Configuration** > **Storage** (1) > **Add storage...** (2).
+
+8. Select **Disk/LUN**.
+
+9. Select the Target, then click **Next**.
+
+
+Finish the configuration with the default settings.
+
+
+ If you have problems with VMFS5, choose to configure your target with VMFS3.
+
+
+
diff --git a/pages/dedibox-rpn/how-to/use-rpn-san-proxmox.mdx b/pages/dedibox-rpn/how-to/use-rpn-san-proxmox.mdx
new file mode 100644
index 0000000000..7bb52ae4cb
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/use-rpn-san-proxmox.mdx
@@ -0,0 +1,101 @@
+---
+meta:
+ title: How to mount a Scaleway Dedibox RPN-SAN volume on Proxmox
+ description: This page explains how to mount a Scaleway Dedibox RPN-SAN volume on Proxmox
+content:
+ h1: How to mount a Scaleway Dedibox RPN-SAN volume on Proxmox
+ paragraph: This page explains how to mount a Scaleway Dedibox RPN-SAN volume on Proxmox
+tags: dedibox rpn san proxmox
+dates:
+ validation: 2024-08-26
+ posted: 2021-11-10
+categories:
+ - dedibox-network
+---
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/)
+
+## Configuration of Proxmox to use the RPN
+
+1. Log in to your server as `root` using SSH:
+ ```
+ ssh root@sd-XXX.dedibox.fr
+ ```
+2. Edit the `/etc/network/interfaces` file, and replace the lines mentioning `eth1` with these:
+ ```
+ auto eth1
+ iface eth1 inet dhcp
+ ```
+
+
+ The interface may be named differently depending on your configuration. You can identify the RPN interface by running `ifconfig` which allows you to check the MAC address of the interface which is available in your Dedibox console.
+
+3. Reboot your Proxmox server to complete the RPN configuration.
+
+## Open-iSCSI installation and configuration
+
+Proxmox requires the Open-iSCSI software to support mounting of iSCSI volumes. It may not be installed by default in your system.
+
+1. Log in to your server as root using SSH.
+ ```
+ ssh root@sd-XXX.dedibox.fr
+ ```
+2. Install `open-iscsi` using the APT package manager.
+ ```
+ apt install open-iscsi
+ ```
+3. Open the file `/etc/iscsi/iscsid.conf` in a text editor, for example `nano`.
+ ```
+ vi /etc/iscsi/iscsid.conf
+ ```
+
+ * Adjust the following configuration directives:
+ ```
+ node.conn[0].timeo.noop_out_interval = 0
+ node.conn[0].timeo.noop_out_timeout = 0
+ node.session.timeo.replacement_timeout = 86400
+ ```
+ The purpose of this change is to prevent your file system from becoming read-only if the link is interrupted for more than two minutes (by default) between your server and the storage server, which can happen during maintenance periods.
+
+ * Configure the setting for automatic reconnection of targets:
+ ```
+ node.startup = automatic
+ ```
+
+ * Change the following settings to take advantage of the data integrity check, if available:
+ ```
+ node.conn[0].iscsi.HeaderDigest = CRC32C,None
+ node.conn[0].iscsi.DataDigest = CRC32C,None
+ ```
+ * Then save your configuration and quit the text editor.
+7. Reboot your server.
+ ```
+ reboot
+ ```
+
+## Discover and connect to targets in Proxmox
+
+1. In the **Server View**, click **Datacenter**, then **Storage**.
+2. Click **Add** and then **iSCSI Target**. Fill in the form:
+ * **ID**: any identifier used to name this RPN SAN volume.
+ * **Portal**: the server on which your space is available (ex: san-1.rpn.online.net).
+ * **Target**: click on the small arrow, and the list of available targets will be displayed (if it is not the case, no need to go further, as there is a problem).
+ * **Nodes**: the nodes that can access this target.
+ * **Enable**: check the box.
+ * **Use LUNs directly**: do not check if you want to create an LVM Group above (recommended, see next step). Check if you want to use the LUN directly.
+ * **Shared**: Leave the default option.
+ * Optionally, add the **LVM group**.
+ This step only applies if you want to create an LVM Group to store VM images.
+3. Click **Add** and then **LVM** or **LVM-Thin**. Fill in the form:
+ * **ID:** any identifier to name this LVM Group.
+ * **Base storage**: click on the small arrow, and select the previously mounted storage space.
+ * **Base volume**: click on the small arrow, and select the line that appears.
+ * **Volume group**: an identifier of your choice to name the volume group in the system.
+ * **Nodes**: the nodes that will be able to access this space.
+ * **Enable**: check the box.
+
+Your RPN SAN is available for use.
\ No newline at end of file
diff --git a/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx b/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx
new file mode 100644
index 0000000000..1b3f8a1134
--- /dev/null
+++ b/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx
@@ -0,0 +1,122 @@
+---
+meta:
+ title: How to use the RPN VPN with your Dedibox Servers
+ description: This page explains how to use the RPN VPN with your Scaleway Dedibox servers
+content:
+ h1: How to use the RPN VPN with your Dedibox Servers
+ paragraph: This page explains how to use the RPN VPN with your Scaleway Dedibox servers
+tags: dedibox rpn vpn dedibox-server
+dates:
+ validation: 2024-08-12
+ posted: 2021-10-07
+categories:
+ - dedibox-network
+---
+
+The RPN VPN service allows you to access machines inside your RPN from an external connection or from a Dedibox server that does not have an RPN interface.
+
+The feature is based on [OpenVPN](/tutorials/install-openvpn/) and you can add the RPN VPN to your RPNv1 group like any other server.
+
+The RPN VPN service allows you to:
+
+* Connect from anywhere in your totally secure and private network.
+* Connect servers which do not have an RPN interface to the RPN.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- An RPN-compatible [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- Installed an OpenVPN client on your local computer
+
+## How to download the RPN VPN configuration
+
+1. Click **Storage** > **RPN VPN** in the top menu of the Dedibox console. A summary of your RPN VPN services displays.
+
+2. Click **Configure** next to the RPN VPN service you want to configure. The RPN VPN information displays.
+
+
+
+ If you do not have any RPN VPN services yet, you can click **Order RPN VPN** directly on the page.
+
+3. Download the certificate files for your RPN VPN. Click **Show Password** to display the password associated with your RPN VPN.
+
+
+
+ To use your RPN VPN in your RPNv1 group, you must add it to your group as an RPN server. For more information, follow our [RPN documentation](/dedibox-rpn/quickstart/).
+
+
+## How to configure the RPN VPN client
+
+
+ To complete the following steps, you must have the following information available on the client:
+ * IP of the RPN VPN server
+ * CA Certificate
+ * Client Certificate
+ * `.key` Certificate
+ * RPN VPN Password
+
+
+### How to configure the Linux client
+
+1. Launch the installation of [OpenVPN](/tutorials/install-openvpn/) using the following command.
+ ```
+ root@:~# apt install openvpn
+ ```
+2. Edit the client configuration file `/etc/openvpn/client.conf` in a text editor. For example with `nano`:
+ ```
+ root@:~# nano /etc/openvpn/client.conf
+ ```
+ The configuration file looks like the following example:
+ ```
+ client
+ dev tun
+ ;proto tcp
+ proto udp
+ float
+ remote 1194
+ nobind
+ persist-key
+ persist-tun
+ ca
+ cert
+ key
+ askpass
+ ns-cert-type server
+ comp-lzo
+ verb 3
+ ```
+ Set the following values in the configuration file:
+ * ``: IP of the RPN VPN server
+ * ``: Path to ca.crt
+ * ``: Path to the client .crt
+ * ``: Path to the client .key
+ * ``: Path to the file containing your password
+
+ Then save the file and exit the text editor.
+3. To start the VPN automatically during the boot process of the server, edit the file `/etc/default/openvpn` and insert the following line:
+ ```
+ AUTOSTART="client"
+ ```
+
+ This line allows [OpenVPN](/tutorials/install-openvpn/) to start automatically with the configuration file located at `/etc/openvpn/client.conf`.
+
+ Once the connection to the RPN VPN server is established, you can use your RPN VPN IP to check whether a new interface displays:
+
+ ```
+ root@mydedibox:/etc/default# ifconfig tun0
+ tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
+ inet addr:10.90.250.25 P-t-P:10.90.250.26 Mask:255.255.255.255
+ ```
+
+ You can also check if the routes for the RPN network were set:
+
+ ```
+ root@mydedibox:/etc/default# route -n | grep 10.90
+ 10.90.0.0 10.90.250.26 255.255.0.0 UG 0 0 0 tun0
+ 10.90.250.1 10.90.250.26 255.255.255.255 UGH 0 0 0 tun0
+ 10.90.250.26 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
+ ```
+
+ Now you can [configure your server](/dedibox-rpn/quickstart/) in your RPN group.
+
+
diff --git a/pages/dedibox-rpn/index.mdx b/pages/dedibox-rpn/index.mdx
new file mode 100644
index 0000000000..e5dab6dccb
--- /dev/null
+++ b/pages/dedibox-rpn/index.mdx
@@ -0,0 +1,48 @@
+---
+meta:
+ title: Dedibox - RPN Documentation
+ description: Dive into Scaleway Dedibox - RPN with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
diff --git a/pages/dedibox-rpn/quickstart.mdx b/pages/dedibox-rpn/quickstart.mdx
new file mode 100644
index 0000000000..4263deb039
--- /dev/null
+++ b/pages/dedibox-rpn/quickstart.mdx
@@ -0,0 +1,154 @@
+---
+meta:
+ title: Scaleway Dedibox RPN - Quickstart
+ description: This page shows you how to get started with RPN (Real Private Network) on Scaleway Dedibox
+content:
+ h1: Scaleway Dedibox RPN - Quickstart
+ paragraph: This page shows you how to get started with RPN (Real Private Network) on Scaleway Dedibox
+tags: dedibox rpn real private network rpnv2 jumboframes
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - dedibox-network
+---
+
+RPN (Real Private Network) establishes a dedicated, secure connection through your server's secondary network interface. It allows you to seamlessly transfer data among your servers via a controlled, private network.
+
+With exceptional performance characterized by minimal latency and support for jumbo frames, this network ensures swift communication between your servers. Effortlessly organize your servers within your Private Network with just a few clicks, irrespective of their quantity or physical locations.
+
+RPNv2 offers unparalleled flexibility, enabling you to construct your architecture within a secure, isolated environment. You have complete control, allowing for the setup of custom VLANs, IP address ranges, subnets, routing tables, and network gateways.
+
+Furthermore, RPN v2 facilitates the configuration of robust security measures to manage your RPN. Segment your infrastructure by creating distinct public and private groups, ensuring that your web server applications are publicly accessible while keeping backend applications secluded from internet access.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) with RPNv2 connectivity
+
+## How to create an RPNv2 group
+
+1. Click on **RPN** > **RPN groups** in the menu on top of the console. Then click **Local RPNv2 groups** in the menu on the left. The RPNv2 groups page displays.
+2. Click **Add group**. The add RPNv2 groups form displays.
+3. Select the type of the group. It can either be **Standard** or **[Q-in-Q](/dedibox-rpn/concepts/#q-in-q-mode)**. Then enter the name of the group and select the servers to add to the group. Click **Submit** to confirm.
+
+ A VLAN ID is assigned automatically during the group creation. It is possible to modify the VLAN ID with values between 1 and 3967.
+
+
+## How to configure the RPN interface
+
+Below you find configuration instructions for the most common operating systems. For more information, refer to our how-to about [RPNv2 interface configuration](/dedibox-rpn/how-to/configure-rpnv2/).
+
+### How to configure RPNv2 on Debian
+
+1. Install the vlan package by running the following command:
+ ```
+ sudo apt-get install vlan
+ ```
+2. Edit your `/etc/network/interfaces` file as follows (assuming your RPN NIC is `eth1` and your VLAN ID is `3900`):
+ ```
+ auto eth1.3900
+ iface eth1.3900 inet static
+ address my.pri.vate.address
+ netmask my.custom.net.mask
+ ```
+
+### How to configure RPNv2 on Ubuntu
+
+
+ The following configuration example uses [Netplan](https://netplan.io/). If you are using a classic network configuration, refer to the [Debian documentation](https://www.debian.org/doc/).
+
+
+```
+network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ mainif:
+ match:
+ macaddress: "de:ad:be:ef:ca:fe"
+ set-name: mainif
+ addresses: [ "10.3.0.5/23" ]
+ gateway4: 10.3.0.1
+ nameservers:
+ addresses: [ "8.8.8.8", "8.8.4.4" ]
+ search: [ example.com ]
+ vlans:
+ vlan15:
+ id: 15
+ link: mainif
+ addresses: [ "10.3.99.5/24" ]
+```
+
+### How to configure RPNv2 on CentOS
+
+In the following 'how to' we assume your RPN NIC is `eth1`.
+
+1. Create a configuration file for the parent interface, called `/etc/sysconfig/network-scripts/ifcfg-eth1`:
+ ```
+ DEVICE=eth1
+ TYPE=Ethernet
+ BOOTPROTO=none
+ ONBOOT=yes
+ ```
+2. Create another file for the vlan interface (assuming the VLAN ID is `3900`). The file is called `/etc/sysconfig/network-scripts/ifcfg-eth1.3900`:
+ ```
+ DEVICE=eth1.3900
+ BOOTPROTO=none
+ ONBOOT=yes
+ IPADDR=my.pri.vate.address
+ PREFIX=CIDR.Netmask
+ NETWORK=my.private.address.0
+ VLAN=YES
+ ```
+
+## How to configure Jumboframes
+
+The RPN supports Jumboframes with a maximum payload of 9000 bytes. You need to configure your RPN interface to send pacekets with an MTU 9000. For more information, refer to our how-to: [Configuration of Jumboframes](/dedibox-rpn/how-to/configure-jumboframes/).
+
+#### CentOS
+
+1. Open the file `/etc/sysconfig/network-scripts/ifcfg-ethX`, where `X` is the number of your interface, in a text editor. Then add the following line to it:
+ ```
+ MTU="9000"
+ ```
+2. Restart the network service:
+ ```
+ service network restart
+ ```
+
+#### Debian
+
+1. Open the file `/etc/network/interfaces` in a text editor and insert `mtu 9000` below the line `iface ethX inet static`:
+ ```
+ auto ethX
+ iface ethX inet static
+ mtu 9000
+ [...]
+ ```
+2. Restart the network service:
+ ```
+ service network restart
+ ```
+
+#### Ubuntu
+
+1. Open the Netplan configuration file `/etc/netplan/01-netcfg.yaml` in a text editor and add the line `mtu: 9000` in the configuration of the RPN interface:
+ ```
+ ethernets:
+ enp3s0:
+ dhcp4: true
+ enp4s0:
+ addresses:
+ - 192.168.0.10/24
+ gateway4: 192.168.0.1
+ mtu: 9000
+ nameservers:
+ addresses:
+ - 1.1.1.1
+ - 2.2.2.2
+ ```
+2. Save the file, exit the text editor, and reload the network configuration:
+ ```
+ sudo netplan apply
+ ```
\ No newline at end of file
diff --git a/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-schema.webp b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-schema.webp
new file mode 100644
index 0000000000..37b698b155
Binary files /dev/null and b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-schema.webp differ
diff --git a/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table1.webp b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table1.webp
new file mode 100644
index 0000000000..245aec8898
Binary files /dev/null and b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table1.webp differ
diff --git a/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table2.webp b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table2.webp
new file mode 100644
index 0000000000..cd17f634ad
Binary files /dev/null and b/pages/dedibox-rpn/reference-content/assets/scaleway-private-networks-table2.webp differ
diff --git a/pages/dedibox-rpn/reference-content/index.mdx b/pages/dedibox-rpn/reference-content/index.mdx
new file mode 100644
index 0000000000..25459dcae4
--- /dev/null
+++ b/pages/dedibox-rpn/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: RPN - Additional content
+ description: RPN additional content
+content:
+ h1: RPN - Additional content
+ paragraph: RPN additional content
+---
diff --git a/pages/dedibox-rpn/reference-content/private-networks-overview.mdx b/pages/dedibox-rpn/reference-content/private-networks-overview.mdx
new file mode 100644
index 0000000000..01417fd59f
--- /dev/null
+++ b/pages/dedibox-rpn/reference-content/private-networks-overview.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: Private Networks between Dedibox and Scaleway cloud products
+ description: This page explains the different private network types and offers available at Scaleway and Dedibox, and compares their different capabilities and features.
+content:
+ h1: Private Networks between Dedibox and Scaleway cloud products
+ paragraph: This page explains the different private network types and offers available at Scaleway and Dedibox, and compares their different capabilities and features.
+tags: dedibox private-networks private network
+dates:
+ validation: 2024-08-26
+categories:
+ - dedibox-network
+---
+
+## Private Networks between Dedibox and Scaleway cloud products
+
+Network connectivity is crucial for deploying infrastructure on the Internet, impacting both performance and security. Achieving low latency and secure data transfer over public networks is essential for successful operations.
+
+The Internet was initially designed for academic data sharing, with minimal focus on security. As it evolved into the global network we rely on today, new challenges arose, including exposure to Distributed Denial-of-Service (DDoS) attacks and other threats. Despite advancements in security technologies, the Internet remains a public network where risks persist.
+
+Scaleway offers solutions to protect your infrastructure, including DDoS protection and the ability to create private networks compliant with [RFC 1918](https://docs.umbrella.com/umbrella-user-guide/docs/internal-networks-setup-guide). These isolated networks provide an added layer of security, fully separated from public networks.
+
+### Private Network Types on the Scaleway Platform
+
+Scaleway’s ecosystem supports a variety of public cloud services, enabling comprehensive infrastructure building within the cloud. Dedibox offers high-performance dedicated servers for demanding workloads. Both product categories provide distinct private network options:
+
+
+
+### RPN Feature on Scaleway Dedibox
+
+**Scaleway Dedibox** supports the Real Private Network (RPN) feature, a physical network within a data center that utilizes a secondary network interface on Dedibox servers, enabling direct server-to-server communication.
+
+Scaleway offers two RPN variants:
+
+- **RPNv1**: Basic service with a static private IP and up to 1 Gbps network speed.
+- **RPNv2**: Advanced service with VLAN support and up to 25 Gbps bandwidth, ideal for latency-sensitive applications.
+
+For instance, with six dedicated servers, you can create multiple RPN groups:
+
+```
+ RPN-group-1 = server 1 and 2 # Servers 1 and 2 can communicate
+ RPN-group-2 = server 1, 6, 3 # Servers 1, 6, and 3 can communicate
+ RPN-group-3 = server 1, 4, 5 # Servers 1, 4, and 5 can communicate
+```
+
+Servers from different Dedibox accounts can also join an RPN with permission. The **RPNv2** feature supports high bandwidth and real VLANs, making it suitable for tasks like large databases or load balancing.
+
+
+
+### Building Private Networks on Scaleway
+
+Scaleway offers the **Private Networks** feature for all Instances, enabling secure, isolated communication within an Availability Zone, independent of the Internet. These Private Networks function as layer 2 Ethernet networks.
+
+Instances connected to a Private Network automatically gain a virtual network interface, facilitating seamless internal communication without requiring a reboot. Multiple Private Networks can be assigned to each Instance, allowing for flexible and complex network configurations.
+
+Private Networks are also foundational for creating a Virtual Private Cloud (VPC).
+
+
+
+### Interconnecting services with Virtual Private Networks
+
+To link Scaleway Dedibox servers and Scaleway Instances, you can configure a **Virtual Private Network (VPN)**. A VPN creates an encrypted tunnel over the public Internet, masking IP addresses and securing data transfers. This enables the creation of hybrid infrastructures across Scaleway products, even across different availability zones.
+
+For example, a Dedibox server could serve as a load balancer, routing traffic via a VPN to virtual Instances. These Instances, in turn, can securely interact with a database on an Elastic Metal server. Techniques such as [WireGuard VPN](/tutorials/wireguard-mesh-vpn/) or a [GRE Tunnel](/tutorials/setting-up-tunnel/) can be employed for these setups.
+
+### Conclusion
+
+Scaleway provides a range of options for secure networking between Dedibox servers, Scaleway Instances, or both. Explore our [documentation](/instances/how-to/use-private-networks/) to learn more about Dedibox RPNs, Scaleway Private Networks, and VPN solutions.
diff --git a/pages/dedibox-scaleway/assets/scaleway-dedibox-login.webp b/pages/dedibox-scaleway/assets/scaleway-dedibox-login.webp
new file mode 100644
index 0000000000..c1b3a6c39b
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-dedibox-login.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-email-match.webp b/pages/dedibox-scaleway/assets/scaleway-email-match.webp
new file mode 100644
index 0000000000..fd67f98796
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-email-match.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-link-dedibox.webp b/pages/dedibox-scaleway/assets/scaleway-link-dedibox.webp
new file mode 100644
index 0000000000..5d2c50d1a3
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-link-dedibox.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-manage-dedibox.webp b/pages/dedibox-scaleway/assets/scaleway-manage-dedibox.webp
new file mode 100644
index 0000000000..6dbe8677dd
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-manage-dedibox.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-modify-options-ddx.webp b/pages/dedibox-scaleway/assets/scaleway-modify-options-ddx.webp
new file mode 100644
index 0000000000..26655575e7
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-modify-options-ddx.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-normal-boot.webp b/pages/dedibox-scaleway/assets/scaleway-normal-boot.webp
new file mode 100644
index 0000000000..1e3c95c366
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-normal-boot.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-rescue-credentials.webp b/pages/dedibox-scaleway/assets/scaleway-rescue-credentials.webp
new file mode 100644
index 0000000000..9639d6dcf2
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-rescue-credentials.webp differ
diff --git a/pages/dedibox-scaleway/assets/scaleway-select-orga.webp b/pages/dedibox-scaleway/assets/scaleway-select-orga.webp
new file mode 100644
index 0000000000..bb1e2cd24e
Binary files /dev/null and b/pages/dedibox-scaleway/assets/scaleway-select-orga.webp differ
diff --git a/pages/dedibox-scaleway/concepts.mdx b/pages/dedibox-scaleway/concepts.mdx
new file mode 100644
index 0000000000..be498c8683
--- /dev/null
+++ b/pages/dedibox-scaleway/concepts.mdx
@@ -0,0 +1,105 @@
+---
+meta:
+ title: Dedibox - Concepts
+ description: This page explains all the concepts related to Scaleway Dedibox servers
+content:
+ h1: Dedibox - Concepts
+ paragraph: This page explains all the concepts related to Scaleway Dedibox servers
+tags: dedibox concepts hostname
+dates:
+ validation: 2024-08-05
+categories:
+ - bare-metal
+---
+
+## Administrator password
+
+The administrator password represents the password of the `root` user on the system and is set during the installation of your Dedibox server. The administrator account has full rights to modify or delete any data on the server. Make sure to set a strong administrator password.
+
+## Access Control List (ACL)
+
+ACL allows you to restrict access to your backup space to the IP address of your Dedibox server. The connection attempts (successful or unsuccessful) are stored in your console in real-time.
+
+## Auto Login
+
+Auto Login allows you to log into your account without a password (automatic authentication based on your IP address and MAC address). This way, you can avoid transmitting your unencrypted login information over the network.
+
+
+ Once this feature has been activated in your account, use the `auto` user and an empty password to connect.
+
+
+## Backup
+
+A backup is a copy of your data, stored in another location. In case of any hardware or software failure, you can restore your data from the backup. It is recommended to make backups regularly. Each Dedibox server comes with 100 GB of free [Dedibackup](https://www.scaleway.com/en/dedibox/storage/) storage. You can upload your backups to this storage using the FTP protocol. A 750 GB Dedibackup is available as a further option.
+
+## cPanel
+
+[cPanel](https://cpanel.net/) is an industrial leading hosting automation platform. It allows you to automate server management tasks and to provision webhosting accounts for your users.
+
+## Dedibackup
+
+Dedibackup is a backup solution for your Dedibox server. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 data center. This allows you to store copies of your data for security purposes.
+
+## Dedicated server
+
+A dedicated server is a physical computer hosted in a data center and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it.
+
+## Hostname
+
+A hostname is a name associated with a machine. On the internet, hostnames are formed mostly of two parts: the local name of the computer (e.g., `myserver`) and the domain name (e.g., `mywebsite.org`). The complete hostname of that machine would be `myserver.mywebsite.org`.
+
+## IPMI
+
+Intelligent Platform Management Interface (IPMI) provides a way to access a computer using a network connection. It is independent of the main computer and allows you to access a remote computer that is not responding or powered off. Another use case is the installation of a custom operating system by mounting an ISO file on a virtual optical device. The installation of the remote computer can be done over the network without the need for physical access to the machine.
+
+## OS type
+
+Scaleway Dedibox provides a wide range of operating systems that can be automatically installed from the console. The available images are grouped into four use cases:
+
+- Server distributions: Linux and Windows distributions designed for server usage. They provide a basic installation and can be customized to your application's needs.
+- Virtualization distributions: Distributions designed to host virtual machines on the Dedibox server.
+- Panel distributions: Distributions with a preinstalled management panel to administrate the Dedibox server from a web-based control panel.
+- Desktop distributions: Distributions with a preinstalled graphical interface. Server administration can be done from a remote desktop tool.
+
+## Partitioning
+
+The partition layout of your Dedibox server can be customized during the installation of the server. You can customize the RAID settings and the disk layout to your application's needs.
+
+## Proxmox
+
+Proxmox is an open-source virtualization distribution based on Debian. It provides both KVM hypervisor and LXC container-based virtualization combined with an easy-to-use web interface to manage resources. Proxmox is available for automatic installation from the Dedibox console.
+
+## Remote reboot
+
+This feature allows you to reboot your Dedibox server from the Dedibox console if it is not responding via the network. You can also use this feature to reboot your server into rescue mode for maintenance actions.
+
+## Rescue mode
+
+Rescue mode is a small Linux distribution that is loaded during the system boot into the RAM of your Dedibox server. It allows you to gain access to your system and data if your server is not reachable on the internet in normal mode. You can perform maintenance tasks on your system and fix broken configurations before rebooting your server back into normal mode.
+
+## Secondary DNS
+
+When you run your own DNS server (for example BIND) on your Dedibox, you can use the Secondary DNS server to provide redundancy for your DNS infrastructure. You can allow the transfer of your domains' primary DNS zone to the secondary DNS server to automatically update it whenever the zone file on the primary server changes.
+
+## Server log files
+
+Your Dedibox server logs important events in log files located in the directory `/var/log` on Linux-based operating systems. Reading these files is a crucial element in the analysis of any issue with your server. Windows provides a [series of tools](https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/system-management-components-overview) to track the health state of your server.
+
+## Statistics
+
+The statistics page in the Dedibox console provides detailed bandwidth usage information of your server for the internet interface, as well as for the RPN interface (if available on the server). The measurement of your bandwidth consumption is done at the network switch of your server's rack.
+
+## User login
+
+During the installation of your server, a user account is created. The user account is a regular user account with `sudo` rights on Ubuntu Linux.
+
+## User password
+
+The password associated with the user login. You can set the user password during the installation of your Dedibox server. For security reasons, it is recommended to choose a temporary password for the installation and to change it once the server has been installed. The password must have at least 8 characters and contain only alphanumeric characters.
+
+## VMware vSphere Hypervisor (ESXi)
+
+A virtualization solution developed by VMware. It is a _type-1_ hypervisor, meaning that ESXi is not a software application that is installed on the server's operating system. It includes and integrates important OS components, such as a proprietary kernel.
+
+## Windows PE rescue mode
+The Windows PE or Windows Preinstallation Environment rescue mode is a minimal Windows operating system. It is used to prepare a computer for Windows installation, copy disk images from a network file server, launch a Windows installation, or have minimal access to fix an error on the server's operating system configuration.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/activate-ipv6-block.mdx b/pages/dedibox-scaleway/how-to/activate-ipv6-block.mdx
new file mode 100644
index 0000000000..760b501fd7
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/activate-ipv6-block.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to activate an IPv6 block for Scaleway Dedibox servers
+ description: This page explains avtivate an IPv6 block for Scaleway Dedibox servers
+content:
+ h1: How to activate an IPv6 block for Scaleway Dedibox servers
+ paragraph: This page explains activate an IPv6 block for Scaleway Dedibox servers
+tags: dedibox failover ip flexible-ip failover-ip
+dates:
+ validation: 2024-10-07
+ posted: 2022-03-24
+---
+
+
+
+
+
+- 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
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays.
+2. Click the **IPv6s** tab to enter the IPv6 section of the console.
+3. Click **+ Activate my IPv6 block**. A pop-up displays.
+4. Click **Activate my free IPv6 block** to obtain a /48 IPv6 block.
+
+ Your IPv6 block will be activated and displayed on the IPv6 page.
+
+
+ The DUID of your prefix (and each of its subnets) is like a private key and grants you access to your prefix. Keep it secret and do not share it.
+
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-dedibox-login.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-dedibox-login.webp
new file mode 100644
index 0000000000..dfcbad2461
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-dedibox-login.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-dragndrop-failover-ip.gif b/pages/dedibox-scaleway/how-to/assets/scaleway-dragndrop-failover-ip.gif
new file mode 100644
index 0000000000..e236d1ee2d
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-dragndrop-failover-ip.gif differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-edit-reverse.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-edit-reverse.webp
new file mode 100644
index 0000000000..d2eb6b22e1
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-edit-reverse.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-email-match.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-email-match.webp
new file mode 100644
index 0000000000..e16d11c238
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-email-match.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-link-dedibox.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-link-dedibox.webp
new file mode 100644
index 0000000000..5d2c50d1a3
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-link-dedibox.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-manage-dedibox.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-manage-dedibox.webp
new file mode 100644
index 0000000000..6dbe8677dd
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-manage-dedibox.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-modify-options.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-modify-options.webp
new file mode 100644
index 0000000000..26655575e7
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-modify-options.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-normal-mode.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-normal-mode.webp
new file mode 100644
index 0000000000..d03800ddab
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-normal-mode.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-rescue-credentials.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-rescue-credentials.webp
new file mode 100644
index 0000000000..0a083370a6
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-rescue-credentials.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-select-orga.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-select-orga.webp
new file mode 100644
index 0000000000..b371501add
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-select-orga.webp differ
diff --git a/pages/dedibox-scaleway/how-to/assets/scaleway-select-rescue.webp b/pages/dedibox-scaleway/how-to/assets/scaleway-select-rescue.webp
new file mode 100644
index 0000000000..d6cfa46370
Binary files /dev/null and b/pages/dedibox-scaleway/how-to/assets/scaleway-select-rescue.webp differ
diff --git a/pages/dedibox-scaleway/how-to/attach-detach-failover-ip.mdx b/pages/dedibox-scaleway/how-to/attach-detach-failover-ip.mdx
new file mode 100644
index 0000000000..42ee511ded
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/attach-detach-failover-ip.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: How to attach/detach a failover IP on Scaleway Dedibox
+ description: This page explains attach/detach a failover IP to a Scaleway Dedibox server
+content:
+ h1: How to attach/detach a failover IP on Scaleway Dedibox
+ paragraph: This page explains attach/detach a failover IP to a Scaleway Dedibox server
+tags: dedibox failover ip failover-ip failover-ip
+dates:
+ validation: 2024-10-14
+ posted: 2022-03-24
+---
+
+
+
+Each failover IP can be routed to any of your Dedibox servers at any time by using the Scaleway console or the API.
+
+
+
+
+
+- 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
+- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/)
+
+## How to attach a failover IP
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Click the **Failover IPs** tab to display a list of your failover IPs.
+3. Move your mouse over the failover IP you want to attach to your Dedibox server. Click the IP and drop it on the Dedibox you want to attach it to.
+
+
+The routing of your failover IP will be updated. Once the blue dot turns green, your IP is operational, and you can configure it on your machine.
+
+
+ Alternatively, you can attach a failover IP by clicking and **Assign IP**. Then, enter the ID of your Dedibox to attach the IP.
+
+
+## How to detach a failover IP
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Click the **Failover IPs** tab to display a list of your failover IPs.
+3. Move your mouse over the failover IP you want to detach from a Dedibox server. Click the IP and drop it in the failover IP list on the left of the screen.
+
+ The routing of your failover IP will be updated. Once the blue dot turns green your IP is no longer routed to the Dedibox and is ready to be attached to another machine.
+
+
+ * You can also drop the IP directly on another Dedibox to assign it to that machine without service interruption.
+ * Alternatively, you can detach a failover IP by clicking -> **Reassign IP**. Then click **Unassign** in the pop-up to detach the IP.
+
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx b/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx
new file mode 100644
index 0000000000..c7496300eb
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to configure a failover IP on a Scaleway Dedibox
+ description: This page explains configure a failover IP on a Scaleway Dedibox
+content:
+ h1: How to configure a failover IP on a Scaleway Dedibox
+ paragraph: This page explains configure a failover IP on a Scaleway Dedibox
+tags: dedibox failover ip failover-ip failover-ip
+dates:
+ validation: 2024-10-21
+ posted: 2022-04-13
+---
+
+
+
+
+
+
+
+- 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
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/)
+
+The following pages provide information on how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running various operating systems:
+
+* [CentOS](/dedibox-ip-failover/how-to/configure-centos/)
+* [Debian and Ubuntu Linux](/dedibox-ip-failover/how-to/configure-debian-ubuntu/)
+* [FreeBSD](/dedibox-ip-failover/how-to/configure-freebsd/)
+* [Windows Server](/dedibox-ip-failover/how-to/configure-windows/)
+
+Learn more about failover IPs with our [dedicated documentation](/dedibox-ip-failover/quickstart/).
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/configure-ipv6-dedibox.mdx b/pages/dedibox-scaleway/how-to/configure-ipv6-dedibox.mdx
new file mode 100644
index 0000000000..2ef16caa64
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/configure-ipv6-dedibox.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to configure IPv6 on a Dedibox
+ description: This page explains how to configure IPv6 on a Scaleway Dedibox
+content:
+ h1: How to configure IPv6 on a Dedibox
+ paragraph: This page explains how to configure IPv6 on a Scaleway Dedibox
+tags: dedibox failover ipv6
+dates:
+ validation: 2024-10-14
+ posted: 2022-04-13
+---
+
+
+
+
+
+- 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 and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Created](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation
+- [Activated](/dedibox-scaleway/how-to/activate-ipv6-block/) an IPv6 block
+
+The Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. The Dedibox network is wholly IPv6 compatible in all Availability Zones.
+
+IPv6 can be used as the main IP of a server, and also for failover IPs by using the principle of virtual MAC.
+
+Each Dedibox customer account comes with a /48 IPv6 block that can be divided into:
+* as many /56 as you have servers.
+* as many /64 as you have failover IPs.
+
+You can assign these blocks to your Dedibox servers by using DHCPv6 and the DUID assigned to each of these blocks. To find more information on IPv6 on Dedibox, refer to our [quickstart](/dedibox-ipv6/quickstart/).
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx b/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx
new file mode 100644
index 0000000000..e183574678
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to configure the reverse DNS of a failover IP on Dedibox
+ description: This page explains how to configure the reverse DNS of a failover IP on Scaleway Dedibox
+content:
+ h1: How to configure the reverse DNS of a failover IP on Dedibox
+ paragraph: This page explains how to configure the reverse DNS of a failover IP on Scaleway Dedibox
+tags: dedibox failover ip flexible-ip failover-ip
+dates:
+ validation: 2024-10-14
+ posted: 2022-04-13
+---
+
+
+
+You can edit the reverse DNS of a failover IP address to a custom value. This can be useful when you want to send emails from your Dedibox, as certain remote mail servers do not accept emails coming from generic reverse hostnames.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/)
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Click the **Failover IPs** tab to display a list of your failover IPs.
+3. Click next to the failover IP you want to edit. A drop-down menu displays.
+4. Click **Edit reverse**. A pop-up displays.
+
+
+ You can click next to the IP you want to configure in the listing of the failover IPs on the left.
+
+5. Enter a new IPv4 reverse DNS and click **Save changes**.
+
+ Make sure that a valid and corresponding A-Record is set for the reverse DNS you want to configure.
+
+
+The reverse DNS (PTR-Record) of the failover IP is being updated.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/connect-to-dedibox.mdx b/pages/dedibox-scaleway/how-to/connect-to-dedibox.mdx
new file mode 100644
index 0000000000..c62c9b9b6e
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/connect-to-dedibox.mdx
@@ -0,0 +1,91 @@
+---
+meta:
+ title: How to connect to a Dedibox server
+ description: This page explains how to connect to a Dedibox server
+content:
+ h1: How to connect to a Dedibox server
+ paragraph: This page explains how to connect to a Dedibox server
+tags: dedibox connect putty
+dates:
+ validation: 2024-08-19
+ posted: 2022-01-31
+---
+
+
+
+A common way of connecting to your Dedibox server is via the command line, using SSH. SSH is a secure communication protocol, which imposes an encryption key exchange at the beginning of the connection. This means that the exchange of data between the client and the server will be encrypted.
+
+However, you may also connect to your server via a graphical interface, such as Windows Remote Desktop.
+
+You can also use FTP, SFTP, or SCP to transfer data to and from your server.
+
+
+
+- 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 and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Created](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation
+
+## How to connect via SSH
+
+### From OSX (Mac) and Linux
+
+1. Open a terminal program on your local machine.
+2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_rsa`) and `your_server_ip` with the IP address of your server.
+ ```bash
+ ssh -i ~/.ssh/your_private_key root@your_server_ip
+ ```
+3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' cannot be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+ You are now connected to your server.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+### From Windows
+
+To connect to your server from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+1. Download and install PuTTY [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html)
+2. Launch PuTTY on your computer. The main screen of the application displays.
+3. Enter your Instance's IP address in the **Hostname** field.
+
+ To find the IP address of your Instance, log into the Scaleway console and
+ click **Dedibox** in the Bare Metal section of the side menu. A list of your
+ Dedibox servers and their associated IP addresses displays.
+
+4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**.
+5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/).
+6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host.
+7. Click **OK** to confirm. The terminal window displays.
+8. Enter your username and password to authenticate against the server with your SSH key.
+
+ You are now connected to your server.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+## How to connect via Remote Desktop
+
+The following steps show you how to connect to your Dedibox server on which you have installed Windows Server, from your local Windows machine.
+
+1. Open the **Remote Desktop Connection** tool on your local Windows machine.
+2. Click the drop-down arrow next to **Show connections**.
+3. Enter the following information:
+ - In **Computer**, enter the IP address of your Dedibox server (e.g. 163.172.20.01).
+ - In **Username**, for a Windows Server type **Administrateur**.
+4. Click **Connect**. You are prompted to enter a password.
+5. Enter the password that you set during installation of your Dedibox Windows Server machine, and click **OK**.
+6. You may be asked to confirm that you want to connect. Click **Yes**.
+
+ You are connected to the graphical interface of your Windows Server.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/index.mdx b/pages/dedibox-scaleway/how-to/index.mdx
new file mode 100644
index 0000000000..7c3c183a07
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox - How Tos
+ description: Dedibox How Tos
+content:
+ h1: Dedibox - How Tos
+ paragraph: Dedibox How Tos
+---
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/install-dedibox.mdx b/pages/dedibox-scaleway/how-to/install-dedibox.mdx
new file mode 100644
index 0000000000..a16d2fafe0
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/install-dedibox.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: How to install a Dedibox
+ description: This page explains how to install a Scaleway Dedibox
+content:
+ h1: How to install a Dedibox
+ paragraph: This page explains how to install a Scaleway Dedibox
+tags: dedibox install
+dates:
+ validation: 2024-10-21
+ posted: 2022-01-31
+---
+
+
+
+
+
+- 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
+- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+## How to install a Dedibox
+
+After the delivery of your server, you can start installing it.
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Choose the Dedibox server you want to install from the list.
+3. Click **Install** to launch the OS installation wizard.
+4. Select the type and version of the operating system you want to install.
+
+ For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type).
+
+5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters:
+ - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap)
+ - the mount point of the partition
+ - the partition size
+ - the software raid (RAID 0/1/5)
+
+
+ When you start a CentOS installation with custom partitioning, you need to keep about 5 GB of unallocated disk space to prevent the automatic installation system from crashing.
+
+6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key.
+
+ * To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/organizations-and-projects/how-to/create-ssh-key/) at this stage so that it can be transferred to your server during installation.
+ * Existing SSH keys from your current Dedibox console are not transferred to the Scaleway console. [Upload these keys](/organizations-and-projects/how-to/create-ssh-key#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) into your Scaleway console to use them with your Dedibox servers.
+
+7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Reinstall Dedibox server**.
+
+ The installation of your Dedibox server may take up to 20 minutes. Once completed, your server will reboot on its hard disk.
+
+
+ Depending on the OS, the installation can take several minutes to complete. Some operating systems may require additional reboots for completion. We recommend waiting 45 to 60 minutes before you connect to your server.
+
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/link-dedibox-account.mdx b/pages/dedibox-scaleway/how-to/link-dedibox-account.mdx
new file mode 100644
index 0000000000..32da16baf3
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/link-dedibox-account.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: How to link your existing Dedibox account to Scaleway
+ description: Learn how to link your existing Dedibox account to Scaleway with our comprehensive step-by-step guide. Follow our instructions to integrate and manage your Dedibox servers through the Scaleway console.
+content:
+ h1: How to link your existing Dedibox account to Scaleway
+ paragraph: Learn how to link your existing Dedibox account to Scaleway with our comprehensive step-by-step guide. Follow our instructions to integrate and manage your Dedibox servers through the Scaleway console.
+tags: dedibox link scaleway
+dates:
+ validation: 2024-12-19
+ posted: 2022-01-31
+---
+
+You can now manage your current and future Dedibox servers from the Scaleway console. This allows you to get the best console experience for your Dedibox servers.
+
+
+ Linking your account is not possible if you have
+ * a Web Hosting product
+ * a domain product
+ * a Dedirack product
+ * PayPal as a payment method
+ * outsourced services or if you are outsourcing your services
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+
+ You can come back to your current [Dedibox console](https://console.online.net/) at any time after you have received an invitation by email. Refer to our [FAQ](/faq/dedibox-in-scaleway-console/) for more information.
+
+
+Follow these steps to link your Dedibox account to your Scaleway account:
+
+1. Navigate to the [Link Dedibox](https://link-dedibox.scaleway.com/) website in your browser. On the **Link Dedibox** page, click **Get started**.
+2. Click **Connect to Dedibox** to start linking your Dedibox account.
+3. Enter your Dedibox login information and click **Sign in**.
+4. We run a check to locate your existing Scaleway account.
+ - If a Scaleway account with the same email as your Dedibox account is found, log in with your Scaleway password or request a magic link.
+ - If no related account is found, enter your account details.
+
+ To link your Dedibox account to a different Scaleway account, click **Choose another account** and enter the new account credentials.
+
+5. Choose the [Organization](/iam/concepts/#organization) in your Scaleway account to link your Dedibox servers, then click **Select Organization**.
+
+ If needed, click **Create a new Organization** to create a new Organization for your servers.
+
+6. Select the personal and billing information for your Scaleway account. You can use the details from your selected Scaleway Organization or your Dedibox account. Confirm the following by ticking the checkboxes:
+ - You have noted your login for the Scaleway console.
+ - Your Scaleway Dedibox and Scaleway Cloud account information will be updated with the information provided on this page.
+ - You understand that linked accounts cannot be unlinked.
+ - Payment information will be updated and unified based on these rules:
+ - If SEPA is your preferred payment method in either account, it becomes the default choice for both Scaleway Cloud and Dedibox invoices.
+ - If SEPA is not used, the preferred payment method of credit card remains the same for both accounts.
+ - If different credit cards are used for Dedibox and Scaleway Cloud, the card registered with Scaleway Cloud becomes the default for both accounts.
+
+ After linking accounts, you can modify your payment method in the [billing section](https://console.scaleway.com/billing/payment) of the Scaleway console. All default payment methods will be transferred to your linked account.
+
+
+ Click **Choose another account** if you want to link your Dedibox account with a Scaleway account using a different email address.
+
+7. Click **Link this account** to finish the linking process. Your console dashboard will display, allowing you to manage your Dedibox servers from the Scaleway console.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/modify-server-options.mdx b/pages/dedibox-scaleway/how-to/modify-server-options.mdx
new file mode 100644
index 0000000000..9b86f1097b
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/modify-server-options.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to modify your Dedibox server options
+ description: This page explains how to modify your Scaleway Dedibox server options
+content:
+ h1: How to modify your Dedibox server options
+ paragraph: This page explains how to modify your Scaleway Dedibox server options
+tags: dedibox link scaleway service-level
+dates:
+ validation: 2024-10-14
+ posted: 2022-04-12
+---
+
+
+
+
+
+- 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
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+1. Click **Dedibox** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Dedibox dashboard displays.
+2. Choose the server you want to configure from the list. Click its name to display that server's information page.
+3. Scroll down to the **Server options** section and click **Modify options**.
+
+ A list of modifiable options for your server displays.
+4. Modify the service level for your Dedibox as required. Based on the service level you can customize your server with additional options, such as storage or DDoS protection.
+
+5. A summary of your options and configuration modifications displays. Click **Save changes** to validate.
+
+ If you order a paid option, the price for the option or customization will be added to your next monthly invoice.
+
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/order-dedibox.mdx b/pages/dedibox-scaleway/how-to/order-dedibox.mdx
new file mode 100644
index 0000000000..0462019a2e
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/order-dedibox.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to order a Dedibox
+ description: This page explains how to order a Scaleway Dedibox dedicated server
+content:
+ h1: How to order a Dedibox
+ paragraph: This page explains how to order a Scaleway Dedibox dedicated server
+tags: dedibox order
+dates:
+ validation: 2024-10-14
+ posted: 2022-01-31
+---
+
+
+
+
+
+- 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
+- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays.
+2. Click **+ Order a Dedibox server** to launch the creation wizard.
+3. Choose a **Data center**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**.
+
+ You can group the offer list by clicking on the tab corresponding to each offer group.
+
+4. Select the service level for your server. Based on the service level you can customize your server with additional options, such as storage or DDoS protection. Then click **Summary >**.
+5. Read the order summary and tick the checkboxes. Click **Create a server** to confirm your order.
+
+ A confirmation of your order displays. In most cases, your Dedibox server is delivered within the hour.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/order-failover-ip.mdx b/pages/dedibox-scaleway/how-to/order-failover-ip.mdx
new file mode 100644
index 0000000000..d58b03fd3e
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/order-failover-ip.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to order a failover IP for Dedibox
+ description: This page explains order a failover IP for a Scaleway Dedibox dedicated server
+content:
+ h1: How to order a failover IP for Dedibox
+ paragraph: This page explains order a failover IP for a Scaleway Dedibox dedicated server
+tags: dedibox failover ip flexible-ip failover-ip
+dates:
+ validation: 2024-10-14
+ posted: 2022-03-24
+---
+
+
+
+
+
+Failover IP addresses allow you to have several IPs on the same server. You could then, for example, have one IP for each website or virtual machine hosted on the server.
+Each failover IP can be routed to any of your Dedibox servers at any time in just a few minutes by using the Scaleway console or the API. By switching your failover IP addresses from one server to another, the hosted services remain available without reconfiguring the IP address.
+
+Failover IPs can be bought as single IP addresses with a maximum number of IPs per Dedibox server, depending on your offer, or as /27 IP blocks for Dedibox servers with a Business service level.
+
+
+
+- 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
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Click the **Failover IPs** tab to display a list of your failover IPs.
+3. Click **+ Order a failover IP**. A pop-up displays.
+4. Choose the number of failover IPs you want to order. If you have servers with a Business service level, you can also order /27 IP blocks.
+
+ You can order up to 10 addresses at a time.
+
+5. Click **Order failover IP** to validate your order.
+
+ The failover IP is delivered to your account and displays in the list of failover IPs.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx
new file mode 100644
index 0000000000..51fd1f12c1
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to reinstall a Dedibox
+ description: This page explains how to reinstall a Scaleway Dedibox
+content:
+ h1: How to reinstall a Dedibox
+ paragraph: This page explains how to reinstall a Scaleway Dedibox
+tags: dedibox reinstall raid
+dates:
+ validation: 2024-10-14
+ posted: 2022-03-24
+---
+
+
+
+
+
+- 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
+- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+## How to reinstall a Dedibox dedicated server
+
+You can reinstall the operating system running on your Dedibox at any time. This can be useful if you want to have a fresh installation after modifying configurations for testing purposes, or if you want to switch to another distribution.
+
+
+ When reinstalling your Dedibox, all data stored on the servers' hard disk drives is deleted. Make sure to have a backup of your data before reinstalling.
+
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Choose the Dedibox server you want to reinstall by clicking on its name.
+3. On the server's dashboard, scroll down to **Reinstall Dedibox Server**. Then click **Reinstall Dedibox server** to launch the OS installation wizard.
+4. Select the type and version of the operating system you want to install.
+
+ For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type).
+
+5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters:
+ - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap)
+ - the mount point of the partition
+ - the partition size
+ - the software raid (RAID 0/1/5)
+
+
+ When you start a CentOS installation with custom partitioning, you need to keep about 5 GB of unallocated disk space to prevent the automatic installation system from crashing.
+
+6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key.
+
+ To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation.
+
+7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Reinstall Dedibox server**.
+
+ The installation of your Dedibox server may take up to 20 minutes. Once completed, your server will reboot on its hard disk.
+
+
+ Depending on the OS, the installation can take several minutes to complete. Certain operating systems may require additional reboots for completion. We recommend waiting 45 to 60 minutes before you connect to your server.
+
+
+
diff --git a/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx b/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx
new file mode 100644
index 0000000000..b0bbebbc0b
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to delete your Dedibox
+ description: This page explains how to delete your Scaleway Dedibox
+content:
+ h1: How to delete your Dedibox
+ paragraph: This page explains how to delete your Scaleway Dedibox
+tags: dedibox link scaleway termination
+dates:
+ validation: 2024-10-14
+ posted: 2022-02-01
+---
+
+
+
+
+
+- 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
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Choose the Dedibox server you want to delete by clicking on its name.
+3. On the server's dashboard, scroll down to **Terminate Dedibox subscription**. Then click **Terminate subscription** to end the subscription of your Dedibox. A pop-up displays.
+4. Type **Terminate** in the form to validate the termination of your server. Click **Terminate Dedibox subscription** to confirm.
+
+ This will permanently delete your server and all your data and associated services will be lost. Failover IPs will be unassigned from this server. This action is irreversible.
+
+
+You have successfully triggered the termination of your subscription and your Dedibox server will be deleted at the end of its billing cycle.
+
+
diff --git a/pages/dedibox-scaleway/how-to/use-rescue-mode.mdx b/pages/dedibox-scaleway/how-to/use-rescue-mode.mdx
new file mode 100644
index 0000000000..19a92ecade
--- /dev/null
+++ b/pages/dedibox-scaleway/how-to/use-rescue-mode.mdx
@@ -0,0 +1,64 @@
+---
+meta:
+ title: How to use rescue mode on Dedibox servers
+ description: This page explains how to use rescue mode on Scaleway Dedibox servers
+content:
+ h1: How to use rescue mode on Dedibox servers
+ paragraph: This page explains how to use rescue mode on Scaleway Dedibox servers
+dates:
+ validation: 2024-10-14
+ posted: 2022-04-12
+---
+
+
+
+
+ This documentation concerns rescue mode for [Dedibox servers](https://www.scaleway.com/en/dedibox/). To use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/) refer to the corresponding [documentation](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode).
+
+
+Rescue mode allows you to boot a [Scaleway Dedibox server](https://www.scaleway.com/en/dedibox/) from the network. It downloads a rescue operating system, that runs completely in the RAM of the server. This allows you to perform maintenance and data recovery operations, even if the machine is not reachable in normal mode.
+
+
+
+- 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
+- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server
+
+1. Click **Dedibox** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Dedibox dashboard displays.
+2. Choose the server you want to reboot into rescue mode from the list. Click its name to display that server's information page.
+3. Scroll down to the **Rescue Mode** section.
+4. Click **Boot in rescue mode.** A pop-up displays.
+5. Select the rescue operating system that fits your server's operating system and click **Boot in rescue mode**.
+
+
+ The server starts to reboot into rescue mode.
+
+
+ Depending on the hardware model of the machine, the reboot may take several minutes.
+
+6. Once rebooted, use a terminal application to log into the machine using SSH with the user account `root`:
+ ```bash
+ ssh rescue-user@
+ ```
+
+
+ Rescue mode uses the SSH keys registered for your Dedibox server as an authentication method. If you have lost your private key, you can access your server using the credentials displayed in the console:
+
+
+
+
+You are now logged into rescue mode and able to perform maintenance actions on the machine.
+
+
+ Rescue mode runs completely in the RAM of the server. To access files located on the hard disk, it needs to be mounted. The disk can be mounted automatically by running `mountall.sh`
+
+
+## How to reboot into normal mode
+
+Once the maintenance of the machine is completed, it can be rebooted back into the operating system installed on the hard disk of the server.
+
+To reboot the server into normal mode, click **Switch to normal node** on the server's overview page. The server reboots on the installed system and will be available in normal mode within a few minutes.
+
+
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/index.mdx b/pages/dedibox-scaleway/index.mdx
new file mode 100644
index 0000000000..71104de102
--- /dev/null
+++ b/pages/dedibox-scaleway/index.mdx
@@ -0,0 +1,88 @@
+---
+meta:
+ title: Dedibox Documentation
+ description: Dive into Scaleway Dedibox with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/dedibox-scaleway/quickstart.mdx b/pages/dedibox-scaleway/quickstart.mdx
new file mode 100644
index 0000000000..53d2b71781
--- /dev/null
+++ b/pages/dedibox-scaleway/quickstart.mdx
@@ -0,0 +1,133 @@
+---
+meta:
+ title: Dedibox - Quickstart
+ description: This page explains how to get started with Scaleway Dedibox dedicated servers
+content:
+ h1: Dedibox - Quickstart
+ paragraph: This page explains how to get started with Scaleway Dedibox dedicated servers
+tags: putty dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2022-01-17
+---
+
+
+
+
+
+- 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
+- A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox)
+- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts
+
+## How to order a Dedibox
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays.
+2. Click **+ Order a Dedibox server** to launch the creation wizard.
+3. Choose a **Data center**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**.
+
+ You can group the offer list by clicking on the tab corresponding to each offer group.
+
+4. Select the service level for your server. Based on the service level you can customize your server with additional options, such as storage or DDoS protection. Then click **Summary >**.
+5. Read the order summary and tick the checkboxes. Click **Create a server** to confirm your order.
+
+ A confirmation of your order displays, and your Dedibox will be delivered as soon as possible - in most cases within the following hour.
+
+## How to install a Dedibox
+
+After the delivery of your server, you can begin installing it.
+
+1. Click **Dedibox** in the **Bare Metal** section of the side menu.
+2. Choose the Dedibox server you want to install from the list.
+3. Click **Install** to launch the OS installation wizard.
+4. Select the type and version of the operating system you want to install.
+
+ For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type).
+
+5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters:
+ - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap)
+ - the mount point of the partition
+ - the partition size
+ - the software raid (RAID 0/1/5)
+
+
+ When you start a CentOS installation with custom partitioning, you need to keep about 5 GB of unallocated disk space to prevent the automatic installation system from crashing.
+
+6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key.
+
+ To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation.
+
+7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Install Dedibox server**.
+
+ The installation of your Dedibox server may take up to 20 minutes. Once complete, your server will reboot on its hard disk.
+
+
+ Depending on the OS, the installation may take several minutes to complete. Certain operating systems may require additional reboots for completion. We recommend waiting 45 to 60 minutes before you connect to your server.
+
+
+## How to connect to your Dedibox
+
+A common way of connecting to your Dedibox server is via the command line, using SSH. SSH is a secure communication protocol, which imposes an encryption key exchange at the beginning of the connection. This means that the exchange of data between the client and the server will be encrypted.
+
+However, you may also connect to your server via a graphical interface, such as Windows Remote Desktop.
+
+You can also use FTP, SFTP, or SCP to transfer data to and from your server.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Created and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key)
+- [Created](/dedibox-scaleway/how-to/order-dedibox) and [installed](/dedibox-scaleway/how-to/install-dedibox) a Dedibox and transferred your SSH key to the server during installation
+
+## How to connect via SSH
+
+### From OSX (Mac) and Linux
+
+1. Open a terminal program on your local machine.
+2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_rsa`) and `your_server_ip` with the IP address of your server.
+ ```bash
+ ssh -i ~/.ssh/your_private_key root@your_server_ip
+ ```
+3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' cannot be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+### From Windows
+
+To connect to your server from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+2. Launch PuTTY on your computer. The main screen of the application displays.
+3. Enter your Instance's IP address in the **Hostname** field.
+
+ To find the IP address of your Instance, log into the Scaleway console and
+ click **Dedibox** in the Bare Metal section of the side menu. A list of your
+ Dedibox servers and their associated IP addresses will display.
+
+4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**.
+5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/).
+6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host.
+7. Click **OK** to confirm. The terminal window displays.
+8. Enter your username and password to authenticate against the server with your SSH key.
+
+ You are now connected to your server.
+
+## How to connect via Remote Desktop
+
+The following steps show you how to connect to your Dedibox on which you have installed Windows Server, from your local Windows machine.
+
+1. Open the **Remote Desktop Connection** tool on your local Windows machine.
+2. Click the drop-down arrow next to **Show connections**.
+3. Enter the following information:
+ - In **Computer**, enter the IP address of your Dedibox server (e.g. 163.172.20.01).
+ - In **Username**, for a Windows Server type **Administrateur**.
+4. Click **Connect**. You are prompted to enter a password.
+5. Enter the password that you set during installation of your Dedibox Windows Server machine, and click **OK**.
+6. You may be asked to confirm that you want to connect. Click **Yes**.
+
+ You are connected to the graphical interface of your Windows Server.
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx b/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx
new file mode 100644
index 0000000000..05df93d2d9
--- /dev/null
+++ b/pages/dedibox-scaleway/reference-content/dedibox-datasheet.mdx
@@ -0,0 +1,254 @@
+---
+meta:
+ title: Dedibox datasheet
+ description: This page shows the technical characteristics of the different Dedibox offers.
+content:
+ h1: Dedibox datasheet
+ paragraph: This page shows the technical characteristics of the different Dedibox offers.
+tags: dedibox server
+dates:
+ validation: 2025-01-06
+ posted: 2023-12-18
+categories:
+ - compute
+---
+
+This datasheet provides a concise overview of the performance, technical features, components, materials, and associated documentation for different Dedibox offers.
+
+
+ This datasheet contains detailed information about the latest generations of Dedibox servers. You can find a complete listing of all Dedibox offers in the Dedibox console under [Server offers](https://console.online.net/en/order/server).
+
+
+## Generation 9 START servers
+
+### Server Dedibox START-9-S
+
+| Dedibox START-9-S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD Ryzen™ 5 PRO 3600 (6c/12t, 3.6 GHz) |
+| **RAM** | 16 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox START-9-M
+
+| Dedibox START-9-M | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD Ryzen™ 5 PRO 3600 (6c/12t, 3.6 GHz) |
+| **RAM** | 32 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+## Generation 9 PRO servers
+
+### Server Dedibox PRO-9-XS
+
+| Dedibox PRO-9-XS | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7281 (16c/32t, 2.1 GHz) |
+| **RAM** | 32 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps (10 Gbps optional) |
+| **Data center** | DC2, DC5 |
+
+### Server Dedibox PRO-9-S
+
+| Dedibox PRO-9-S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7281 (16c/32t, 2.1 GHz) |
+| **RAM** | 96 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps (10 Gbps optional) |
+| **Data center** | DC2, DC5 |
+
+### Server Dedibox PRO-9-M
+
+| Dedibox PRO-9-M | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 GHz) |
+| **RAM** | 128 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps (10 Gbps optional) |
+| **Data center** | DC2, DC5 |
+
+### Server Dedibox PRO-9-L
+
+| Dedibox PRO-9-L | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 GHz) |
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 2 x 2 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps (10 Gbps optional) |
+| **Data center** | DC2, DC5 |
+
+## Generation 9 CORE servers
+
+### Server Dedibox CORE-9-S
+
+| Dedibox CORE-9-S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7401P (24c/48t, 2.0 GHz)|
+| **RAM** | 128 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-9-M
+
+| Dedibox CORE-9-M | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7401P (24c/48t, 2.0 GHz)|
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-9-L
+
+| Dedibox CORE-9-L | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+## Generation 9 STORE servers
+
+### Server Dedibox STORE-9-S
+
+| Dedibox STORE-9-S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7232P (8c/16t, 3.1 GHz) |
+| **RAM** | 64 GB DDR4 ECC |
+| **Disk** | 4 x 2 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox STORE-9-M
+
+| Dedibox STORE-9-M | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7232P (8c/16t, 3.1 GHz) |
+| **RAM** | 128 GB DDR4 ECC |
+| **Disk** | 4 x 4 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox STORE-9-L
+
+| Dedibox STORE-9-L | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7232P (8c/16t, 3.1 GHz) |
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 4 x 8 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+## Generation 10 CORE servers
+
+### Server Dedibox CORE-10-XS
+
+| Dedibox CORE-10-XS | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 64 GB DDR4 ECC |
+| **Disk** | 2 x 960 GB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-10-S
+
+| Dedibox CORE-10-S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 128 GB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-10-M
+
+| Dedibox CORE-10-M | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 192 GB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-10-L
+
+| Dedibox CORE-10-L | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-10-XL
+
+| Dedibox CORE-10-XL | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 384 GB DDR4 ECC |
+| **Disk** | 2 x 3.84 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox CORE-10-XXL
+
+| Dedibox CORE-10-XXL | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 512 GB DDR4 ECC |
+| **Disk** | 2 x 3.84 TB NVMe SSD |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+## GPU servers
+
+### Server Dedibox GPU-10-L40S
+
+| Dedibox GPU-10-L40S | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 256 GB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe SSD |
+| **GPU** | NVIDIA® L40S |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
+
+### Server Dedibox GPU-10-H100
+
+| Dedibox GPU-10-H100 | |
+|------------------------|-----------------------------------|
+| **CPU** | AMD EPYC™ 7313P (16c/32t, 3.0 GHz)|
+| **RAM** | 512 GB DDR4 ECC |
+| **Disk** | 2 x 3.84 TB NVMe SSD |
+| **GPU** | NVIDIA® H100 |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Data center** | DC5 |
\ No newline at end of file
diff --git a/pages/dedibox-scaleway/reference-content/index.mdx b/pages/dedibox-scaleway/reference-content/index.mdx
new file mode 100644
index 0000000000..478e36fc42
--- /dev/null
+++ b/pages/dedibox-scaleway/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox - Additional content
+ description: Dedibox additional content
+content:
+ h1: Dedibox - Additional content
+ paragraph: Dedibox additional content
+---
\ No newline at end of file
diff --git a/pages/dedibox-vps/concepts.mdx b/pages/dedibox-vps/concepts.mdx
new file mode 100644
index 0000000000..45156270bc
--- /dev/null
+++ b/pages/dedibox-vps/concepts.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: Dedibox VPS - Concepts
+ description: This page explains all the concepts related to Dedibox Virtual Private Servers (VPS)
+content:
+ h1: Dedibox VPS - Concepts
+ paragraph: This page explains all the concepts related to Dedibox Virtual Private Servers (VPS)
+tags: vps dedibox
+dates:
+ validation: 2024-11-18
+categories:
+ - dedibox-vps
+---
+
+## Bandwidth
+
+Bandwidth refers to the maximum rate of data transfer across a network, typically measured in bits per second (bps). It determines the amount of data which can be transmitted between devices, servers, or over the internet.
+
+## Isolation
+
+Each VPS environment is isolated from the others, providing security and preventing one VPS from affecting others.
+
+## Operating system
+
+You can choose from various operating systems (e.g., Linux distributions) to run on your VPS.
+
+## Remote reboot
+
+This feature allows you to reboot your Dedibox VPS from the Dedibox console if it has stopped responding via the network. You can also use this feature to reboot your server into rescue mode for maintenance actions.
+
+## Resource allocation
+
+Each Dedibox VPS has resources (CPU, RAM, storage) allocated to it, ensuring consistent performance.
+
+## Root access
+
+You have root access or administrative control over your VPS, allowing customization and installation of software.
+
+## User login
+
+During the installation of your server, a user account is created. The user account is a regular user account with `sudo` rights on Ubuntu Linux.
+
+## User password
+
+The password associated with the user login. You can set the user password during the installation of your Dedibox server. For security reasons, it is recommended to choose a temporary password for the installation and to change it once the server has been installed.
+
+## Virtualization
+
+Dedibox VPS uses virtualization technology to create isolated virtual machines on a single physical server.
+
+
diff --git a/pages/dedibox-vps/how-to/connect-vps.mdx b/pages/dedibox-vps/how-to/connect-vps.mdx
new file mode 100644
index 0000000000..e18818b1e4
--- /dev/null
+++ b/pages/dedibox-vps/how-to/connect-vps.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: How to connect to a Dedibox VPS
+ description: This page explains how to connect to a Dedibox VPS
+content:
+ h1: How to connect to a Dedibox VPS
+ paragraph: This page explains how to connect to a Dedibox VPS
+tags: vps dedibox ssh connect
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+You can manage your Dedibox VPS by accessing it through SSH.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/)
+
+## Connecting from Linux and OSX (Mac)
+To connect to your Dedibox VPS from Linux or Mac OSX, follow these steps:
+
+1. Open a terminal program on your local machine.
+2. Type the following command. Make sure that you replace the placeholder with your own value.
+ ```
+ ssh root@
+ ```
+3. If prompted, allow connection to the host by typing `yes` and press Enter.
+4. Enter your password and press Enter to log in. You are now connected to your VPS.
+
+ * When you install your VPS using an SSH key, you do not need a password for authentication, as your key is used for identification.
+ * For beginners in the Linux shell, explore our tutorial designed to introduce you to [the first steps of the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+## Connecting from Windows
+To connect to your Dedibox VPS from Windows, follow these steps:
+
+1. Download and install [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+
+ You also have the option to use the [Windows SSH client](https://learn.microsoft.com/en-us/windows/terminal/tutorials/ssh), which is available on Windows 10 or 11 operating systems.
+
+2. Launch PuTTY and enter your Dedibox VPS' IP address in the **Hostname** field.
+3. Click **Open** to establish the connection. If prompted, confirm the connection.
+4. Enter the username root and the user's password. You are now connected to your VPS.
+
+ * When you install your VPS using an SSH key, you do not need a password for authentication, as your key is used for identification.
+ * For beginners in the Linux shell, explore our tutorial designed to introduce you to [the first steps of the Linux command line](/tutorials/first-steps-linux-command-line/).
+
diff --git a/pages/dedibox-vps/how-to/create-vps.mdx b/pages/dedibox-vps/how-to/create-vps.mdx
new file mode 100644
index 0000000000..2ab5cafba4
--- /dev/null
+++ b/pages/dedibox-vps/how-to/create-vps.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to create a Dedibox VPS
+ description: This page explains how to create a Dedibox VPS
+content:
+ h1: How to create a Dedibox VPS
+ paragraph: This page explains how to create a Dedibox VPS
+tags: vps dedibox order create
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+A Dedibox VPS (Virtual Private Server) is a private virtualized server that operates within a larger physical infrastructure.
+It provides directly accessible computing resources and greater control of your hosting environment than shared hosting solutions.
+
+VPS are suitable for various use cases, including hosting websites, web applications, databases, development environments, etc. They balance performance, control, and affordability for businesses and individuals with moderate to high-traffic websites or applications.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account
+
+1. Log in to your [Dedibox console](https://console.online.net) account and click **Order** in the navigation at the top of the page.
+2. From the drop-down menu, select **Dedibox VPS** to access the Dedibox VPS offers page.
+3. Choose the VPS offer you want to deploy, and proceed by clicking **Order**.
+4. Specify the geographical region where you want your VPS deployed.
+5. Select your preferred location for the virtual machine deployment, then click **Order** to proceed.
+6. Choose your virtual machine's desired Operating System (OS) and select the appropriate OS version.
+7. Enter a hostname for your VPS, ensuring it contains at least eight (8) alphanumeric characters.
+8. Optionally paste an [SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) that can be used for authentication when connecting to the Dedibox VPS using SSH, then click **Order**. An order summary displays.
+9. Review all the parameters for your virtual machine and check the message boxes to indicate you have read the terms of service and specific VPS conditions.
+10. Click **Confirm my order** to confirm your purchase and initiate the deployment of your VPS.
+
+ It may take a few minutes for your VPS to be delivered and visible in your account.
+
\ No newline at end of file
diff --git a/pages/dedibox-vps/how-to/delete-vps.mdx b/pages/dedibox-vps/how-to/delete-vps.mdx
new file mode 100644
index 0000000000..3d2d50a0fd
--- /dev/null
+++ b/pages/dedibox-vps/how-to/delete-vps.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: How to delete a Dedibox VPS
+ description: This page explains how to delete a Dedibox VPS
+content:
+ h1: How to delete a Dedibox VPS
+ paragraph: This page explains how to delete a Dedibox VPS
+tags: vps dedibox delete terminate
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+You can delete your VPS by requesting termination from the Dedibox console. To do so, follow these steps.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/)
+
+1. Log in to your [Dedibox console](https://console.online.net/) account and locate **Dedibox VPS** in the top navigation menu. Click it to access the list of your Dedibox VPS.
+2. Select the Dedibox VPS you want to delete and click **Manage**. This action will direct you to the VPS information dashboard.
+
+ You can also directly access the VPS information dashboard by clicking
+ the VPS Hostname or IP address.
+
+3. On the VPS dashboard, locate and click **Delete**. The service termination form displays.
+4. Select a reason for the service termination and click **Terminate this service and associated options**.
+ A notice informing you that your termination request has been validated displays. The service will be terminated at the end of its billing cycle.
diff --git a/pages/dedibox-vps/how-to/index.mdx b/pages/dedibox-vps/how-to/index.mdx
new file mode 100644
index 0000000000..0383d312c0
--- /dev/null
+++ b/pages/dedibox-vps/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedibox VPS - How Tos
+ description: Virtual Private Servers (VPS) How Tos
+content:
+ h1: Dedibox VPS - How Tos
+ paragraph: Virtual Private Servers (VPS) How Tos
+---
diff --git a/pages/dedibox-vps/how-to/manage-vps.mdx b/pages/dedibox-vps/how-to/manage-vps.mdx
new file mode 100644
index 0000000000..207473f343
--- /dev/null
+++ b/pages/dedibox-vps/how-to/manage-vps.mdx
@@ -0,0 +1,67 @@
+---
+meta:
+ title: How to manage a Dedibox VPS
+ description: This page explains how to manage a Dedibox VPS
+content:
+ h1: How to manage a Dedibox VPS
+ paragraph: This page explains how to manage a Dedibox VPS
+tags: vps dedibox manage
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+You can manage your Dedibox VPS directly from the Dedibox console.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/)
+
+## How to manage a Dedibox VPS from its information dashboard
+
+1. Log in to your Dedibox console account and click **Dedibox VPS** in the navigation at the top of the page. This will bring up a list of your Dedibox VPS.
+
+ You can filter your Dedibox VPS by offer type using the drop-down list.
+
+2. Choose the Dedibox VPS you wish to manage and click **Manage**. This action leads you to the VPS information dashboard.
+
+ Alternatively, you can directly access the VPS information dashboard by
+ clicking on the VPS Hostname or IP address.
+
+
+### How to view the root password of a Dedibox VPS
+
+1. Access the VPS information dashboard and click the **view icon** (eye symbol) next to **Password**.
+2. The password of your Dedibox VPS displays. You can copy and paste it into your SSH client during connection to your VPS.
+
+ Click the view icon again to hide the password.
+
+
+### How to update the root password of a Dedibox VPS
+
+1. Access the [VPS information dashboard](#how-to-manage-a-dedibox-vps-from-its-information-dashboard) and click **Edit Password**.
+2. Type your new password along with its confirmation, then click **Confirm** to finalize the update. You will receive a confirmation notification indicating your password was changed.
+3. Reboot your VPS to ensure the changes are taken into effect. After this, you can manage your VPS using the new password.
+
+### How to update the hostname of a Dedibox VPS
+
+1. Click the **Edit icon** on the [VPS information dashboard](#how-to-manage-a-dedibox-vps-from-its-information-dashboard) next to **Hostname**.
+2. Enter the new hostname for your VPS and confirm by clicking **Confirm**. A notification will confirm the update.
+
+### How to reboot a Dedibox VPS
+
+1. Click **Reboot** on the [VPS information dashboard](#how-to-manage-a-dedibox-vps-from-its-information-dashboard) to reboot your Dedibox VPS.
+2. Confirm the action by clicking **OK** in the pop-up prompt. Your VPS will proceed to reboot.
+
+### How to stop a Dedibox VPS
+
+1. Click **Stop** on the [VPS information dashboard](#how-to-manage-a-dedibox-vps-from-its-information-dashboard), if you wish to stop your Dedibox VPS.
+2. Confirm the action by clicking **OK** in the pop-up prompt. Your VPS will begin the stopping process.
+
+### How to start a Dedibox VPS
+
+1. Click **Start** on the [VPS information dashboard](#how-to-manage-a-dedibox-vps-from-its-information-dashboard) to start your Dedibox VPS.
+2. Confirm the action by clicking **OK** in the pop-up prompt. Your VPS will begin the starting process.
\ No newline at end of file
diff --git a/pages/dedibox-vps/how-to/reinstall-vps.mdx b/pages/dedibox-vps/how-to/reinstall-vps.mdx
new file mode 100644
index 0000000000..af7715207f
--- /dev/null
+++ b/pages/dedibox-vps/how-to/reinstall-vps.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to reinstall a Dedibox VPS
+ description: This page explains how to reinstall a Dedibox VPS
+content:
+ h1: How to reinstall a Dedibox VPS
+ paragraph: This page explains how to reinstall a Dedibox VPS
+tags: vps dedibox reinstall
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+You can reinstall your VPS at any time from your Dedibox console.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/)
+
+1. Log in to your [Dedibox console](https://console.online.net/) account and locate **Dedibox VPS** in the top navigation menu. Click it to access the list of your Dedibox VPS.
+2. Select the Dedibox VPS you want to reinstall and click **Manage** next to it. This action will direct you to the VPS information dashboard.
+
+ You can also directly access the VPS information dashboard by clicking
+ the VPS Hostname or IP address.
+
+3. In the dashboard, locate and click **Reinstall**. The reinstallation wizard displays.
+4. Choose your desired **Operating System (OS)** for the Dedibox VPS and select the OS version.
+5. Optionally paste an SSH key that can used for authentication when connecting to the Dedibox VPS using SSH.
+6. Confirm your selection by clicking **Reinstall** then click **OK** in the pop-up prompt to confirm the action. Your existing preferences will be saved, and the reinstallation process will begin.
+
+ Be careful, as reinstalling your VPS will erase all data. Make sure to have
+ backups of your data before initiating a reinstallation.
+
+
+ Reinstalling your Dedibox VPS will take a few minutes. During reinstallation, the VPS management page will be unavailable.
+
\ No newline at end of file
diff --git a/pages/dedibox-vps/index.mdx b/pages/dedibox-vps/index.mdx
new file mode 100644
index 0000000000..8e27175ccb
--- /dev/null
+++ b/pages/dedibox-vps/index.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: Dedibox VPS Documentation
+ description: Dive into Scaleway Dedibox VPS with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+
+
+## Getting Started
+
+
+
+
+
+
diff --git a/pages/dedibox-vps/quickstart.mdx b/pages/dedibox-vps/quickstart.mdx
new file mode 100644
index 0000000000..23f6c9a419
--- /dev/null
+++ b/pages/dedibox-vps/quickstart.mdx
@@ -0,0 +1,76 @@
+---
+meta:
+ title: Dedibox VPS - Quickstart
+ description: Learn how to get started with Dedibox VPS. Follow this step-by-step guide to set up, connect, and manage your virtual private server for hosting, development, and more.
+content:
+ h1: Dedibox VPS - Quickstart
+ paragraph: Learn how to get started with Dedibox VPS. Follow this step-by-step guide to set up, connect, and manage your virtual private server for hosting, development, and more.
+tags: dedibox vps virtual-machine
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - dedibox-vps
+---
+
+A Dedibox VPS (Virtual Private Server) operates within a larger physical infrastructure, providing directly accessible computing resources and greater control than shared hosting solutions.
+
+Dedibox VPSs are versatile, serving various purposes such as hosting websites, web applications, databases, and development environments.
+They offer a balance of performance, control, and affordability for businesses and individuals with moderate to high-traffic websites or applications.
+
+## Creating a Dedibox VPS
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account
+
+1. Navigate to your [Dedibox console](https://console.online.net) home page and select **Order** from the top navigation.
+2. Choose **Dedibox VPS** from the drop-down menu to access available offers.
+3. Select a VPS offer and proceed with the order.
+4. Specify the geographical region for deployment and confirm your choice.
+5. Choose the operating system (OS) and version for your virtual machine.
+6. Enter a hostname containing at least eight alphanumeric characters.
+7. Optionally, paste an [SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) for authentication.
+8. Review your order details and confirm by clicking **Confirm my order**.
+
+ It may take a few minutes for your VPS to be delivered and visible in your account.
+
+
+## Connecting to a Dedibox VPS
+
+You can manage your Dedibox VPS by accessing it through SSH.
+
+### Linux and Mac OSX (Mac) connection
+
+1. Open a terminal program on your local machine.
+2. Enter the command below, replacing `` with your the specific IP address of your VPS:
+ ```
+ ssh root@
+ ```
+3. If prompted, allow connection to the host by typing "yes" and pressing Enter.
+4. Enter your password to log in.
+
+ Authentication occurs without a password if your VPS is installed using an SSH key.
+
+
+### Windows connection
+
+1. Download and install [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+2. Launch PuTTY and enter your Dedibox VPS's IP address.
+3. Click "Open" to establish the connection.
+4. Enter the username `root` and your password to log in.
+
+ Authentication occurs without a password if your VPS is installed using an SSH key.
+
+
+## Deleting a Dedibox VPS
+
+You can delete your VPS by requesting termination from the Dedibox console. To do so, follow these steps.
+
+1. Access your list of virtual machines by clicking **Dedibox VPS** within the [Dedibox console](https://console.online.net/).
+2. Select the VPS you want to manage and click **Manage**.
+3. Navigate to **Delete** and select a reason for termination.
+4. Click **Terminate this service and associated options** to confirm.
+
+
diff --git a/pages/dedibox/concepts.mdx b/pages/dedibox/concepts.mdx
new file mode 100644
index 0000000000..df517efd77
--- /dev/null
+++ b/pages/dedibox/concepts.mdx
@@ -0,0 +1,106 @@
+---
+meta:
+ title: Dedibox dedicated servers - Concepts
+ description: This page explains all the concepts related to Scaleway Dedibox dedicated servers.
+content:
+ h1: Dedibox dedicated servers - Concepts
+ paragraph: This page explains all the concepts related to Scaleway Dedibox dedicated servers.
+tags: dedibox acl dedibackup os-type ipmi partitioning suchard vsphere esxi hostname
+dates:
+ validation: 2024-08-27
+categories:
+ - dedibox-servers
+---
+
+## Administrator password
+
+The administrator password represents the password of the `root` user on the system and is set during the installation of your Dedibox server. The administrator account has full rights to modify or delete any data on the server. Make sure to set a strong administrator password.
+
+## Access Control List (ACL)
+
+This feature allows you to restrict access to your backup space to the IP address of your Dedibox. The connection attempts (successful or unsuccessful) are stored in your console in real-time.
+
+## Auto login
+
+Auto Login allows you to log into your account without a password (automatic authentication based on your IP address and MAC address). This way, you can avoid transmitting your unencrypted login information over the network. Once this feature has been activated in your account, use the "auto" user and an empty password to connect.
+
+## Backup
+
+A backup is a copy of your data, stored in another location. In case of any hardware or software failure, you can restore your data from the backup. It is recommended to make backups regularly. Each Dedibox comes with 100 GB of free [Dedibackup](https://www.scaleway.com/en/dedibox/storage/) storage. You can upload your backups to this storage using the FTP protocol. A 750 GB Dedibackup is available as a further option.
+
+## cPanel
+
+[cPanel](https://cpanel.net/) is an industrial leading hosting automation platform. It allows you to automate server management tasks and allows you to provision webhosting accounts to your users.
+
+## Dedibackup
+
+A backup solution for your Dedibox. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 data center. This allows you to store copies of your data for security purposes.
+
+## Dedicated server
+
+A dedicated server is a physical computer hosted in a data center and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it.
+
+## Hostname
+
+A hostname is a name associated with a machine. On the internet, hostnames are formed mostly of two parts: the local name of the computer (e.g., `myserver`) and the domain name (e.g., `mywebsite.org`). The complete hostname of that machine would be `myserver.mywebsite.org`.
+
+## IPMI
+
+IPMI or Intelligent Platform Management Interface (IPMI) provides a way to access a computer using a network connection. It is independent of the main computer and allows you to access a remote computer that is not responding or powered off. Another use case is the installation of a custom operating system by mounting an ISO file on a virtual optical device. The installation of the remote computer can be done over the network without the need for physical access to the machine.
+
+## OS type
+
+Scaleway Dedibox provides a wide range of operating systems that can be automatically installed from the console. The available images are grouped into four use cases:
+
+- Server distributions: Linux and Windows distributions designed for server usage. They provide a basic installation and can be customized to your application's needs.
+- Virtualization distributions: Distributions designed to host virtual machines on the Dedibox server.
+- Panel distributions: Distributions with a preinstalled management panel to administrate the Dedibox server from a web-based control panel.
+- Desktop distributions: Distributions with a preinstalled graphical interface. Server administration can be done from a remote desktop tool.
+
+## Partitioning
+
+The partition layout of your Dedibox server can be customized during the installation of the server. You can customize the RAID settings and the disk layout to your application's needs.
+
+## Proxmox
+
+Proxmox is an open-source virtualization distribution based on Debian. It provides both KVM hypervisor and LXC container-based virtualization combined with an easy-to-use web interface to manage resources. Proxmox is available for automatic installation from the Dedibox console.
+
+## Remote reboot
+
+This feature allows you to reboot your Dedibox server from the Dedibox console in case it does not respond any longer via the network. You can also use this feature to reboot your server into rescue mode for maintenance actions.
+
+## Rescue mode
+
+Rescue mode is a small Linux distribution that is loaded during the system boot into the RAM of your Dedibox server. It allows you to access your system and data in case your server is not reachable on the internet in normal mode. You can perform maintenance tasks on your system and fix broken configurations before rebooting your server back into normal mode.
+
+## Secondary DNS
+
+When you run your own DNS server (for example BIND) on your Dedibox, you can use the Secondary DNS server to provide redundancy for your DNS infrastructure. You can allow the transfer of your domains' primary DNS zone to the secondary DNS server to automatically update it whenever the zonefile on the primary server changes.
+
+## Server log files
+
+Your Dedibox server logs important events in log files located in the directory `/var/log` on Linux-based operating systems. Reading these files is a crucial element in the analysis of any issue with your server. Windows provides a [series of tools](https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/system-management-components-overview) to track the health state of your server.
+
+## Statistics
+
+The statistics page in the Dedibox console provides detailed bandwidth usage information of your server for the internet interface, as well as for the RPN interface (if available on the server). The measurement of your bandwidth consumption is done at the network switch of your server's rack.
+
+## Suchard server
+
+The offers START-2-XS, START-2-S, and START-2-M use a mainboard developed in-house by Scaleway's R&D teams called *Suchard*. This mainboard is fully compatible with all Linux distributions. However, to be able to run Windows on this type of motherboard, it is required to deploy a XEN Hypervisor and run Windows inside a virtual machine. The hypervisor reserves 1 GB of RAM, so the amount of available RAM in Windows will display as the server's total RAM - 1 GB. These offers also exist in a configuration using the Motherboard Dell DSS5100 which can run Windows natively.
+
+## User login
+
+During the installation of your server, a user account is created. The user account is a regular user account with `sudo` rights on Ubuntu Linux.
+
+## User password
+
+The password associated with the user login. You can set the user password during the installation of your Dedibox server. For security reasons, it is recommended to choose a temporary password for the installation and to change it once the server has been installed.
+
+## VMware vSphere Hypervisor (ESXi)
+
+VMware vSphere Hypervisor (ESXi) is a _type-1_ hypervisor developed by VMware, now under Broadcom following its acquisition. ESXi is a bare-metal hypervisor, meaning it operates directly on server hardware without requiring an underlying operating system. It includes a proprietary kernel that integrates essential OS components, making it a robust and efficient solution for virtualization. Following the Broadcom acquisition, VMware has discontinued free licenses for ESXi, signaling a shift towards a more commercially-focused licensing model.
+
+## Windows PE rescue mode
+
+The Windows PE or Windows Preinstallation Environment rescue mode is a minimal Windows operating system. It is used to prepare a computer for Windows installation, copy disk images from a network file server, launch a Windows installation, or have minimal access to fix an error on the server's operating system configuration.
\ No newline at end of file
diff --git a/pages/dedibox/how-to/assets/scaleway-dedibox-logs.webp b/pages/dedibox/how-to/assets/scaleway-dedibox-logs.webp
new file mode 100644
index 0000000000..789d144176
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-dedibox-logs.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-dedibox-monitoring.webp b/pages/dedibox/how-to/assets/scaleway-dedibox-monitoring.webp
new file mode 100644
index 0000000000..f67f59a9e1
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-dedibox-monitoring.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-idrac.webp b/pages/dedibox/how-to/assets/scaleway-idrac.webp
new file mode 100644
index 0000000000..30a2c6c7f5
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-idrac.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-ilo.webp b/pages/dedibox/how-to/assets/scaleway-ilo.webp
new file mode 100644
index 0000000000..1e254da8cc
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-ilo.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-putty-logged.webp b/pages/dedibox/how-to/assets/scaleway-putty-logged.webp
new file mode 100644
index 0000000000..8ec0ac647d
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-putty-logged.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-putty-main.webp b/pages/dedibox/how-to/assets/scaleway-putty-main.webp
new file mode 100644
index 0000000000..46d9f9630f
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-putty-main.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-putty-security.webp b/pages/dedibox/how-to/assets/scaleway-putty-security.webp
new file mode 100644
index 0000000000..d1c3b0f6ac
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-putty-security.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-putty-ssh.webp b/pages/dedibox/how-to/assets/scaleway-putty-ssh.webp
new file mode 100644
index 0000000000..8b0ac2219a
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-putty-ssh.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-serial-console-2.webp b/pages/dedibox/how-to/assets/scaleway-serial-console-2.webp
new file mode 100644
index 0000000000..c6d06a4338
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-serial-console-2.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-serial-console-esxi.webp b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi.webp
new file mode 100644
index 0000000000..af5f8f962e
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-serial-console-esxi2.webp b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi2.webp
new file mode 100644
index 0000000000..423859cfbd
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi2.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-serial-console-esxi3.webp b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi3.webp
new file mode 100644
index 0000000000..60d1cafeef
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-serial-console-esxi3.webp differ
diff --git a/pages/dedibox/how-to/assets/scaleway-serial-console.webp b/pages/dedibox/how-to/assets/scaleway-serial-console.webp
new file mode 100644
index 0000000000..a3189a160e
Binary files /dev/null and b/pages/dedibox/how-to/assets/scaleway-serial-console.webp differ
diff --git a/pages/dedibox/how-to/assets/sftp.webp b/pages/dedibox/how-to/assets/sftp.webp
new file mode 100644
index 0000000000..784a32bde0
Binary files /dev/null and b/pages/dedibox/how-to/assets/sftp.webp differ
diff --git a/pages/dedibox/how-to/change-root-password.mdx b/pages/dedibox/how-to/change-root-password.mdx
new file mode 100644
index 0000000000..eb51ac2bf7
--- /dev/null
+++ b/pages/dedibox/how-to/change-root-password.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: How to change the root password
+ description: This page explains how to change the root password on a Scaleway Dedibox server
+content:
+ h1: How to change the root password
+ paragraph: This page explains how to change the root password on a Scaleway Dedibox server
+tags: root-password root password dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+This document shows you how to change your password using the [rescue system](/dedicated-servers/how-to/use-rescue-mode/). If you try to use the usual `passwd` command to change your password, it will only change the password of the rescue system. Your modifications are reset after a reboot. We will show you how to access your real files to change your password.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+1. From the console, [launch rescue mode](/dedicated-servers/how-to/use-rescue-mode/).
+2. Mount your partitions:
+ ```
+ sudo mountall.sh
+ ```
+
+
+ The mounted partitions are available in the directory `/mnt`. This means, you find the partition `/dev/sda1` mounted in `/mnt/sda1`.
+
+3. Chroot yourself into the root partition:
+ ```
+ sudo chroot /mnt/sda2
+ ```
+
+
+ - If you [installed your server](/dedicated-servers/how-to/install-a-server/) with the default partition layout, the root partition will be mounted on sda2.
+ - If you configured custom partitioning, your root partition may be mounted elsewhere.
+
+4. Use the following command to change the password:
+ ```
+ passwd
+ ```
+ You will be prompted two times to set the new password. While you are writing, nothing will appear on screen. This is a normal security measure.
+
+
+ If you want to reset the password of a user other than root, use the following command, replacing **USERNAME** with the relevant username.
+ `passwd USERNAME`
+
+5. Type `exit` when you have finished your modifications.
+6. Type the following command to finish:
+ ```
+ sudo umountall.sh && sudo reboot
+ ```
+7. From the console, click **Boot in normal mode** to reboot the server.
+
+ Your root password is now changed.
+
+
diff --git a/pages/dedibox/how-to/change-win-server-language.mdx b/pages/dedibox/how-to/change-win-server-language.mdx
new file mode 100644
index 0000000000..55b81ee940
--- /dev/null
+++ b/pages/dedibox/how-to/change-win-server-language.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: How to change the language of Windows Server 2019
+ description: Learn how to change the display language on your Windows Server 2019 installed on a Dedibox server with this step-by-step guide.
+content:
+ h1: How to change the language of Windows Server 2019
+ paragraph: Learn how to change the display language on your Windows Server 2019 installed on a Dedibox server with this step-by-step guide.
+tags: language windows-server-2019 windows-server dedibox
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+This guide provides step-by-step instructions to change the display language of a Windows Server 2019 installation on a Dedibox server.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox server](/dedicated-servers/how-to/order-a-server/) with Windows Server 2019 [installed](/dedicated-servers/how-to/install-a-server/)
+
+1. Log in to your Windows Server's graphical interface using Remote Desktop or a similar tool.
+2. Open the **Start** menu and click the settings icon to access the **Settings** interface.
+3. Select **Time & Language** (labeled **Heure et langue**, if in French).
+4. From the left-hand menu, click **Language** (**Langue**).
+5. On the Language screen, click **Add a language** (**Ajouter une langue**).
+6. In the **Choose a language to install** (**Choisir une langue à installer**) screen, select your desired language and click **Next** (**Suivant**).
+7. On the **Install language features** (**Installer des fonctionnalités linguistiques**) screen, check the desired features and click **Install** (**Installer**).
+
+ The system will download and install the language pack. After installation, the new language will appear under **Windows display language**. A server reboot may be required for the language change to take effect.
diff --git a/pages/dedibox/how-to/connect-to-server.mdx b/pages/dedibox/how-to/connect-to-server.mdx
new file mode 100644
index 0000000000..b5653e81bd
--- /dev/null
+++ b/pages/dedibox/how-to/connect-to-server.mdx
@@ -0,0 +1,110 @@
+---
+meta:
+ title: How to connect to a Dedibox server
+ description: This page explains how to connect to a Scaleway Dedibox server using SSH or RDP
+content:
+ h1: How to connect to a Dedibox server
+ paragraph: This page explains how to connect to a Scaleway Dedibox server using SSH or RDP
+tags: dedibox dedicated-server server
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+This guide provides instructions on connecting to your Scaleway Dedibox server using SSH (for Linux, macOS, and Windows) or Remote Desktop (for Windows Server).
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created and uploaded your SSH key](/dedibox-account/how-to/upload-an-ssh-key/)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation
+
+## Connecting via SSH
+
+### For macOS and Linux users
+
+1. Open the terminal on your local machine.
+2. Enter the command below, replacing `your_private_key` with the private key filename (typically `id_rsa`), `username` with the defined username, and `your_server_ip` with your server’s IP address:
+ ```bash
+ ssh -i ~/.ssh/your_private_key username@your_server_ip
+ ```
+3. If prompted, confirm the connection by typing `yes` and pressing **Enter**:
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' cannot be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+4. You are now connected to your server.
+
+
+ If you are new to the Linux shell, check out our [Linux command line tutorial](/tutorials/first-steps-linux-command-line/).
+
+
+### For Windows users
+
+To connect to your server from Windows, use the **PuTTY** SSH client.
+
+1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+2. Launch PuTTY on your computer.
+3. Enter your server's IP address in the **Hostname** field.
+
+ You can find your server's IP address in the [Dedibox management console](https://console.online.net/en/server/list).
+
+4. In the side menu, navigate to **Connection** > **SSH** > **Auth**.
+5. Click **Browse** and select your private key file.
+6. Click **Open** to start the connection. When prompted, confirm the connection to the host.
+7. Enter your username and password to authenticate using your SSH key.
+
+ You are now connected to your server.
+
+
+ New to the Linux shell? Explore our [Linux command line tutorial](/tutorials/first-steps-linux-command-line/).
+
+
+## Connecting via Remote Desktop
+
+If you have installed Windows Server on your Dedibox, follow these steps to connect using Remote Desktop:
+
+1. Open **Remote Desktop Connection** on your local Windows machine.
+2. Enter the IP address of your Dedibox server in the **Computer** field.
+3. In the **Username** field, enter `Administrateur` (for Windows Server).
+4. Click **Connect** and enter the password set during the server installation.
+5. Confirm the connection if prompted.
+
+You are now connected to the Windows Server graphical interface. For language settings, refer to the [Windows Server language change guide](/dedicated-servers/how-to/change-win-server-language/).
+
+## Transferring data to your server
+
+You can transfer files to and from your Dedibox server using SFTP or SCP.
+
+### Using SFTP with FileZilla
+
+1. [Download and install FileZilla](https://filezilla-project.org) on your local machine.
+2. Open FileZilla and navigate to **File** > **Site Manager**.
+3. Enter the following details:
+ - **Protocol**: SFTP
+ - **Host**: Your server's IP address
+ - **Port**: 22
+ - **User**: Your username
+ - **Key file**: Your private key file location
+4. Click **Connect** to start transferring files.
+
+### Using SCP in a terminal
+
+1. Open a terminal on your local machine.
+2. Use the following command:
+ ```s
+ scp file username@ipaddress:/DestinationDirectory
+ ```
+ Replace:
+ - **file**: Path of the file to transfer
+ - **username**: Your username
+ - **ipaddress**: Server IP address
+ - **/DestinationDirectory**: Destination path on the server
+
+ For example:
+ ```s
+ scp config.txt toto@62.210.***.***:/home/toto/prog/
+ ```
\ No newline at end of file
diff --git a/pages/dedibox/how-to/get-started-with-server.mdx b/pages/dedibox/how-to/get-started-with-server.mdx
new file mode 100644
index 0000000000..27994774d5
--- /dev/null
+++ b/pages/dedibox/how-to/get-started-with-server.mdx
@@ -0,0 +1,49 @@
+---
+meta:
+ title: Getting started with your Scaleway Dedibox server
+ description: Learn how to set up, use, and manage your Scaleway Dedibox server with this comprehensive guide, including tips on using the shell, installing software, and backing up your data.
+content:
+ h1: Getting started with your Scaleway Dedibox server
+ paragraph: Learn how to set up, use, and manage your Scaleway Dedibox server with this comprehensive guide, including tips on using the shell, installing software, and backing up your data.
+tags: dedibox dedicated server x2go
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+Once you have set up your Dedibox server, installed an operating system, and connected via SSH, you are ready to begin. This guide provides essential information and tips for efficiently using your Dedibox server.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+## Using the shell
+
+Dedibox servers do not come with a graphical interface by default. Instead, all commands are executed via a powerful shell/terminal. The shell allows you to:
+
+- Install, configure, and manage software
+- Create, edit, and delete files and directories
+- Configure server settings
+
+You can [connect to the shell via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). For essential commands, refer to our [basic Linux commands guide](/dedicated-servers/reference-content/basic-linux-commands/).
+
+## Using a graphical desktop
+
+If you prefer a graphical interface, you can install a desktop-oriented distribution and connect using the X2Go Client. For more information, refer to our [guide on connecting via Windows Remote Desktop](/dedicated-servers/how-to/connect-to-server/#connecting-via-remote-desktop).
+
+## Installing software on Linux OSes
+
+After setting up your Dedibox, only the operating system and an SSH server are installed. To add software, use a package manager specific to your distribution:
+
+- **Debian/Ubuntu**: Use the APT package manager. See our guide on [getting started with APT](/dedicated-servers/how-to/manage-packages/).
+- **CentOS/RHEL**: Use [DNF](https://dnf.readthedocs.io/en/latest/) (previously YUM for CentOS 7 and older).
+- **SuSE Linux**: Use [YAST](https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-yast-software.html).
+
+Package managers allow you to install, update, and remove software directly from the shell.
+
+## Backing up your Dedibox
+
+As the server owner, you are responsible for your data. Regular backups are strongly recommended. You can order a Dedibackup option with various disk sizes for secure FTP storage of your backups. Tools like [Backup Manager](https://manpages.ubuntu.com/manpages/oracular/en/man8/backup-manager.8.html) can help you automate the backup process.
\ No newline at end of file
diff --git a/pages/dedibox/how-to/index.mdx b/pages/dedibox/how-to/index.mdx
new file mode 100644
index 0000000000..0078a9f41d
--- /dev/null
+++ b/pages/dedibox/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedicated servers - How Tos
+ description: Dedicated Servers How Tos
+content:
+ h1: Dedicated servers - How Tos
+ paragraph: Dedicated Servers How Tos
+---
diff --git a/pages/dedibox/how-to/install-a-server.mdx b/pages/dedibox/how-to/install-a-server.mdx
new file mode 100644
index 0000000000..fff7bb7cd4
--- /dev/null
+++ b/pages/dedibox/how-to/install-a-server.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: How to install a Dedibox server
+ description: Learn how to install your Scaleway Dedibox dedicated server with step-by-step instructions for OS selection, partitioning, and configuration.
+content:
+ h1: How to install a server
+ paragraph: Learn how to install your Scaleway Dedibox dedicated server with step-by-step instructions for OS selection, partitioning, and configuration.
+tags: dedibox dedicated-server server
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+After your Scaleway Dedibox server has been delivered, you can proceed with the installation process by following these steps.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox server](/dedicated-servers/how-to/order-a-server/)
+
+1. In the [Dedibox console](https://console.online.net/), navigate to **Server** > **Server list** in the top menu. A list of your servers will be displayed.
+2. Click **Manage** next to the server you want to install. The server installation wizard will appear.
+3. Select the operating system type to be installed.
+
+ For detailed information about OS types, refer to the [dedicated servers concepts page](/dedicated-servers/concepts/#os-type).
+
+
+
+ If you prefer to complete the installation using [KVM Over IP](/dedibox-kvm-over-ip/), click **Install over KVM** on this page.
+
+4. Choose the specific operating system and version you wish to install, then click **Install**.
+5. Customize the [partitioning](/dedicated-servers/concepts/#partitioning) configuration:
+
+ - Select the **File system**, **RAID level**, and specify the **mount point** and **partition size** in MB.
+ - If the server has two disks, you can choose between **RAID 0**, **RAID 1**, or **No RAID**. For servers with more than two disks, **RAID 5** is also available. Configure the RAID and partitioning according to your needs. Ensure identical partitioning across all disks in a software RAID setup.
+
+ **Partitioning restrictions:**
+ - A maximum of 4 primary partitions per disk is allowed.
+ - Do not create a `/var` partition, as it may cause installation failure.
+ - The `/` partition must be at least 2048 MB.
+
+ After configuring the partitions, click **Validate** to confirm and proceed.
+
+6. Set a user and administrator password, and select SSH keys for server access. Once configured, click **Next Step**.
+7. Review the configuration summary. If everything is correct, confirm by clicking **Delete all my disks and install the system**. This will initiate the automatic server installation.
+
+
+ - **This will delete all existing data on the disks.** Ensure you have backups before proceeding to avoid data loss.
+ - If installing CentOS with custom partitioning, reserve approximately 5 GB of unallocated disk space to prevent installation errors.
+
+8. Configure the system parameters, such as server name, username, password, SSH key, monitoring alerts, and updates.
+
+ To connect via SSH, we recommend [creating and uploading your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage for transfer during installation.
+
+9. Verify all details on the installation summary tab. Once installation is complete, your server will automatically reboot from its hard disk.
+
+
+ - Installation time may vary depending on the OS; expect it to take several minutes.
+ - Some operating systems may require additional reboots to complete the setup.
+ - We recommend waiting 45 to 60 minutes before attempting to connect to your server.
+
\ No newline at end of file
diff --git a/pages/dedibox/how-to/manage-packages.mdx b/pages/dedibox/how-to/manage-packages.mdx
new file mode 100644
index 0000000000..abd44c2410
--- /dev/null
+++ b/pages/dedibox/how-to/manage-packages.mdx
@@ -0,0 +1,188 @@
+---
+meta:
+ title: How to manage software packages on Linux
+ description: Learn how to manage packages on a Dedibox server.
+content:
+ h1: How to manage software packages on Linux
+ paragraph: This guide explains how to manage packages on a Dedibox server.
+tags: dedibox, package, management
+dates:
+ validation: 2024-08-05
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+Packages are archives containing binaries, configuration files, and dependency information for software. A package manager automates software installation, upgrades, and configuration, keeping track of all installed packages and their versions.
+
+This guide covers package management on the following distributions:
+- Debian
+- Ubuntu
+- CentOS
+- AlmaLinux
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) Dedibox server
+
+## Debian and Ubuntu: Using APT
+
+On Debian and Ubuntu, use the **APT** (**A**dvanced **P**ackage **T**ool) package manager.
+
+### How to update repositories
+
+Update your package information with the following command:
+
+```bash
+sudo apt-get update
+```
+
+### How to update packages
+
+After updating your repositories, upgrade your packages:
+
+```bash
+sudo apt-get upgrade
+```
+
+
+ A reboot is recommended after kernel updates.
+
+
+### How to search for packages
+
+Search for specific software packages, such as MariaDB:
+
+```bash
+apt-cache search mariadb
+```
+
+### How to install a package
+
+Install a package, for example, MariaDB server:
+
+```bash
+sudo apt-get install mariadb-server
+```
+
+### How to keep your system tidy
+
+Remove unused dependencies:
+
+```bash
+sudo apt-get autoremove
+```
+
+### How to uninstall a package
+
+Remove a package, for example, MariaDB server:
+
+```bash
+sudo apt-get remove mariadb-server
+```
+
+To also remove all dependencies installed with the package:
+
+```bash
+sudo apt-get autoremove mariadb-server
+```
+
+## CentOS and AlmaLinux: Using YUM/DNF
+
+On CentOS and AlmaLinux, use the **YUM** (Yellowdog Updater, Modified) or **DNF** (Dandified YUM) package manager.
+
+### How to update repositories
+
+Update your package information with the following command:
+
+```bash
+sudo yum update
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf update
+```
+
+### How to update packages
+
+After updating your repositories, upgrade your packages:
+
+```bash
+sudo yum upgrade
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf upgrade
+```
+
+### How to search for packages
+
+Search for specific software packages, such as MariaDB:
+
+```bash
+sudo yum search mariadb
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf search mariadb
+```
+
+### How to install a package
+
+Install a package, for example, MariaDB server:
+
+```bash
+sudo yum install mariadb-server
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf install mariadb-server
+```
+
+### How to keep your system tidy
+
+Remove unused dependencies:
+
+```bash
+sudo yum autoremove
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf autoremove
+```
+
+### How to uninstall a package
+
+Remove a package, for example, MariaDB server:
+
+```bash
+sudo yum remove mariadb-server
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf remove mariadb-server
+```
+
+To also remove all dependencies installed with the package:
+
+```bash
+sudo yum autoremove mariadb-server
+```
+
+Or, if using DNF:
+
+```bash
+sudo dnf autoremove mariadb-server
+```
\ No newline at end of file
diff --git a/pages/dedibox/how-to/migrate-server.mdx b/pages/dedibox/how-to/migrate-server.mdx
new file mode 100644
index 0000000000..7d8cb2af60
--- /dev/null
+++ b/pages/dedibox/how-to/migrate-server.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: How to migrate your Dedibox server
+ description: Learn how to migrate your Dedibox server to a newer model.
+content:
+ h1: How to migrate your Dedibox server
+ paragraph: This guide explains how to migrate your Dedibox server to a newer model.
+tags: dedibox, migrate, migration, server
+dates:
+ validation: 2024-08-05
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+All physical servers eventually reach their End of Life (EOL), but this process is manageable and does not have to disrupt your operations.
+Hardware vendors provide a warranty and replacement parts for a limited time, usually a few years.
+If your Dedibox server approaches EOL, you will see a warning in the console.
+Rest assured, this guide will walk you through the steps to seamlessly migrate your services and data to a new server, ensuring continuity and minimal downtime.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) dedicated server
+
+## How to migrate your data
+
+Transferring data from one server to another is straightforward. Here are some methods you can use:
+
+- [Use FTP](/dedicated-servers/how-to/connect-to-server/#using-sftp-with-filezilla)
+- [Use SCP](/dedicated-servers/how-to/connect-to-server/#using-scp-in-a-terminal)
+- [Use Rsync](https://manpages.ubuntu.com/manpages/noble/en/man1/rsync.1.html)
+
+## How to migrate your services
+
+
+ Our support team is unable to provide software assistance. If necessary, contact one of our [verified partners](https://www.scaleway.com/en/dedibox/outsourcing/).
+
+
+### Migrating to the same OS version
+
+If you are migrating to the same OS version on your new server, you can copy the old server's configuration files to the new one. Most configuration files are located under `/etc/`, so it's a good idea to back up this entire directory.
+
+Some configuration files, such as those for IP addresses and MAC addresses, may need to be adapted for your new machine. For example, you might need to modify:
+
+- `/etc/network/interfaces`
+- `/etc/udev/rules.d/70-persistent-net.rules`
+
+### Migrating to a different OS version
+
+When migrating to a newer version of your OS, you will usually need to reconfigure your services. We do not recommend copying your old configuration files to your new server in this case.
+
+This version improves readability and ensures all necessary steps and information are clearly communicated.
\ No newline at end of file
diff --git a/pages/dedibox/how-to/monitor-server.mdx b/pages/dedibox/how-to/monitor-server.mdx
new file mode 100644
index 0000000000..62a69bdb37
--- /dev/null
+++ b/pages/dedibox/how-to/monitor-server.mdx
@@ -0,0 +1,77 @@
+---
+meta:
+ title: How to monitor your server
+ description: This page explains how to monitor your Dedibox server
+content:
+ h1: How to monitor your server
+ paragraph: This page explains how to monitor your Dedibox server
+tags: dedibox monitoring server
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+
+ The monitoring feature is deprecated and **no longer available** from the Dedibox console. For advanced monitoring of your server, refer to Scaleway’s [Observability Cockpit](https://www.scaleway.com/en/cockpit/).
+
+
+Your management console includes a monitoring system that can notify you by e-mail or SMS when a potential incident or anomaly occurs with your server. In addition, you can also view your server's logs from the console, which shows you a history of past actions carried out on your server.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+## How to use the monitoring page
+
+### Access the page
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the server you want to monitor.
+3. Click **Monitoring** on the left-side menu. The monitoring page displays.
+ - Under **Monitoring list**, you can see a list of your current monitoring services.
+ - Under **Add service monitoring**, you can add new monitoring services to your server.
+
+
+
+### Add a new monitoring service
+
+You can add an unlimited number of monitoring services and contacts.
+
+1. From the **Monitoring page**, scroll down to **Add service monitoring**.
+2. In the **Service** drop-down menu, choose the service you want to add. The following monitoring services are available:
+ - Ping ⇒ Verification that your server replies to “ping”
+ - DNS ⇒ Verification that your DNS server works correctly
+ - FTP ⇒ Verification that your FTP server works
+ - HTTP ⇒ Verification that your httpd answers
+ - IMAP ⇒ Verification of your IMAP server
+ - RDesktop ⇒ Verification of the availability of Remote Desktop
+ - POP ⇒ Verification of your POP server
+ - SMTP ⇒ Verification of your SMTP server
+ - SSH ⇒ Verification that your SSH server responds
+
+
+ You have to add the IP range `62.210.16.0/24` to permit the ICMP packets to receive monitoring updates.
+
+3. In the **Alert type** drop-down menu, select "E-mail" or "SMS".
+4. According to your chosen alert type, enter either your e-mail address or phone number in the final box.
+5. Click **Add service monitoring**.
+
+ Your new service is added to your monitoring list.
+
+### Delete a monitoring service
+
+From the **Monitoring page**, click the icon next to the service you want to delete.
+
+## How to view your server's logs
+
+Viewing your server's logs from the console shows you a list of actions carried out on it in the past. This can help you to diagnose hardware problems, such as reboot problems or network issues.
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the server you want to monitor.
+3. Click **Logs** on the left-side menu. The logs page displays.
+
+
+
diff --git a/pages/dedibox/how-to/order-a-server.mdx b/pages/dedibox/how-to/order-a-server.mdx
new file mode 100644
index 0000000000..36eabc649e
--- /dev/null
+++ b/pages/dedibox/how-to/order-a-server.mdx
@@ -0,0 +1,61 @@
+---
+meta:
+ title: How to order a server
+ description: This page explains how to order a Scaleway Dedibox dedicated server
+content:
+ h1: How to order a server
+ paragraph: This page explains how to order a Scaleway Dedibox dedicated server
+tags: dedibox dedicated server
+dates:
+ validation: 2024-08-30
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+[Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) are our high-quality dedicated servers. With over 15 years of experience, we provide dedicated servers which are recognized for their extreme reliability and best-in-class redundancy.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- Added [a payment method](/dedibox-account/how-to/add-payment-method/) to your account
+
+1. Click **Order** on your Dedibox console homepage.
+2. Click **Server**. The server offers page displays.
+
+ You can view all servers available in your preferred data center by clicking the **Datacenter selection** drop-down menu in the top right corner.
+
+3. Select a server model and click the **Order** button next to your choice. The server creation wizard displays.
+4. Complete the following steps in the wizard:
+ - Select your commitment period: rent without commitment, or choose a 12 or 36-month plan for lower monthly rates and free server setup.
+
+ This step only displays for Dedibox servers eligible for a commitment plan.
+
+ - Select the data center.
+
+ Some server models are available in more than one data center. If you have no preference, select **"No preference"**.
+
+ - Choose the service level. There are two plans available:
+ - **Basic service level**: Included with any Dedibox server. Offers:
+ - Assistance by ticket and phone
+ - H+4 GTI
+ - 99.9% SLA
+ - RPN with limited bandwidth
+ - **Business service level**: A paid plan with:
+ - Priority assistance by ticket and phone
+ - Sales assistance
+ - H+1 GTI
+ - 99.95% SLA
+ - RPN with high bandwidth
+ - Customization and security options (anti-DDoS)
+ - Quota of +15 failover IPs
+ - Dedicated project manager
+ - Select a backup option: 750 GB FTP, 100 GB FTP, or no FTP backup.
+ - Choose a plan for protection against DDoS.
+
+ To benefit from the **Preventive** or **Curative** anti-DDoS plans, you must activate the Business service level for the server.
+
+5. Click **Order**. A summary of your order displays.
+6. Select your payment method in the **Payment mode choice** drop-down menu in the top right corner.
+7. Check the boxes confirming that you have read and agreed to the terms of service.
+8. Click **Confirm my order**. A confirmation of your order displays.
\ No newline at end of file
diff --git a/pages/dedibox/how-to/rescue-your-data.mdx b/pages/dedibox/how-to/rescue-your-data.mdx
new file mode 100644
index 0000000000..4ca48b51f7
--- /dev/null
+++ b/pages/dedibox/how-to/rescue-your-data.mdx
@@ -0,0 +1,122 @@
+---
+meta:
+ title: How to rescue and recover your data using rescue mode
+ description: Learn how to recover and download backups of your data from a Scaleway Dedibox server using rescue mode with SFTP or Dedibackup.
+content:
+ h1: How to rescue and recover your data using rescue mode
+ paragraph: Learn how to recover and download backups of your data from a Scaleway Dedibox server using rescue mode with SFTP or Dedibackup.
+tags: recovery rescue data rescue-mode
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+If your server encounters issues but does not have a hardware failure, you can still recover your data using rescue mode, regardless of whether you are using Windows or Linux.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) dedicated server
+
+## Booting into rescue mode
+
+1. Follow [these instructions](/dedicated-servers/how-to/use-rescue-mode/) to start your server in rescue mode (emergency system) via the Dedibox console.
+2. Log into your server using one of the following methods:
+ - [PuTTY](http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe) on [Windows](/dedicated-servers/how-to/connect-to-server/#for-windows-users)
+ - `ssh` from a terminal on [Linux or macOS](/dedicated-servers/how-to/connect-to-server/#for-macos-and-linux-users).
+
+
+ The rescue mode credentials (username and password) are displayed in your Dedibox console.
+
+
+## Gaining root access
+
+By default, you are logged in as a regular user in rescue mode and may not have permission to execute all necessary commands.
+
+1. Switch to the `root` account by typing the following command and pressing Enter:
+ ```bash
+ sudo su
+ ```
+2. Enter the rescue user password displayed in the Dedibox console and press Enter.
+
+
+ For security reasons, the password will not be visible when typing.
+
+
+## Mounting partitions
+
+To access your data, you need to mount your server’s partitions in rescue mode. If this step succeeds, you can likely recover your files.
+
+1. As the `root` user, run the following command to mount all partitions:
+ ```bash
+ mountall.sh
+ ```
+ The partitions will be mounted in the `/mnt` directory.
+
+
+ You may encounter errors such as `swap cannot be mounted` or `many partitions do not exist`. These can be safely ignored.
+
+
+## Recovering your data
+
+You can recover your data by either transferring it to the [Dedibackup](https://www.scaleway.com/en/dedibox/storage/) storage space or downloading it directly to your local computer via SFTP.
+
+
+ Exercise caution when editing your data in rescue mode. The `root` user has full permissions, including the ability to irreversibly delete files.
+
+
+### Recovering data using Dedibackup
+
+To back up all disk contents (including partitions) to your Dedibackup storage:
+
+1. Install an FTP client and `screen` using the following command:
+ ```bash
+ apt -y install screen lftp
+ ```
+2. Start `screen`:
+ ```bash
+ screen
+ ```
+3. Transfer your data with this command:
+ ```bash
+ lftp -u YOUR_DEDIBACKUP_LOGIN,YOUR_DEDIBACKUP_PASSWORD dedibackup.online.net -e "mirror --reverse /mnt /; exit"
+ ```
+
+ Replace `YOUR_DEDIBACKUP_LOGIN` with your Dedibackup login (e.g., `sd-XXXX`) and `YOUR_DEDIBACKUP_PASSWORD` with your Dedibackup password.
+
+
+
+ If you have forgotten your password, reset it in the console to generate a new one.
+
+
+You can now access your files via any FTP client connected to Dedibackup.
+
+
+ Dedibackup is limited to 1000 files per volume. Consider using archives when backing up data.
+
+
+### Backing up data to your personal computer (via SFTP)
+
+You can use an SFTP client like [FileZilla](https://filezilla-project.org/) to download data from your server.
+
+1. Open FileZilla and fill in the following details:
+ - **Host**: Your server’s IP address
+ - **Username**: Rescue mode username (e.g., `sd-XXXX`)
+ - **Password**: Rescue mode password
+ - **Port**: 22
+
+
+ These details are available in your console once rescue mode is active.
+
+
+#### Example configuration
+
+
+
+Your data will be located in the `/mnt`, `/sda1`, or `/sda` directories. You can download it before reinstalling the server or transferring data to another server.
+
+
+ If you encounter difficulties, consider contacting a [certified outsourcer](https://www.scaleway.com/en/dedibox/outsourcing/) for professional data recovery.
+
\ No newline at end of file
diff --git a/pages/dedibox/how-to/restart-server.mdx b/pages/dedibox/how-to/restart-server.mdx
new file mode 100644
index 0000000000..c760a508e1
--- /dev/null
+++ b/pages/dedibox/how-to/restart-server.mdx
@@ -0,0 +1,35 @@
+---
+meta:
+ title: How to restart your server
+ description: This page explains how to restart your Scaleway Dedibox server
+content:
+ h1: How to restart your server
+ paragraph: This page explains how to restart your Scaleway Dedibox server
+tags: dedibox server restart
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+Your Dedibox server includes a remote reboot system, which we show you how to use in this document.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the server you want to restart.
+3. Click the **Reboot** button on the right. A pop-up asks if you are sure you want to reboot.
+4. Click **I accept** to confirm the reboot.
+
+ You are returned to your main server page, where you see the message **Reboot in progress**.
+
+
+ - You can also reboot your server via [KVM](/dedibox-kvm-over-ip/). In the iDRAC and iLO KVM interfaces, you can switch your server OFF and ON again. This allows you to check what happens during its boot sequence and intervene if necessary.
+ - If it stops responding, you can try [rebooting your server in Rescue Mode](/dedicated-servers/how-to/use-rescue-mode/). In the case the problem persists, [open a support ticket](https://console.online.net/en/assistance/ticket) to ask for a hardware check of your server.
+
+
+
diff --git a/pages/dedibox/how-to/terminate-dedibox-server.mdx b/pages/dedibox/how-to/terminate-dedibox-server.mdx
new file mode 100644
index 0000000000..141b32dd15
--- /dev/null
+++ b/pages/dedibox/how-to/terminate-dedibox-server.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: How to terminate a Dedibox server in the Online console
+ description: Learn how to terminate a Dedibox server in the Online console.
+content:
+ h1: How to terminate a Dedibox server
+ paragraph: This guide explains how to terminate a Online Dedibox server in the Online console.
+tags: dedibox terminate server online console delete cancel
+dates:
+ posted: 2024-12-12
+ validation: 2024-12-12
+categories:
+ - dedibox
+---
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- An active Dedibox server
+
+## How to terminate your Dedibox server
+1. Click your username, next to _logged in as_, in the top right corner of the [Online console](https://console.online.net/). From the drop-down menu, select **Services**. The service page displays.
+2. Click the **Detail** next to the Dedibox server you want to terminate. The **Server information** page displays.
+3. Click **Terminate**. A pop-up displays.
+4. Click **Confirm Termination**. The Server and all associated options display.
+5. Type a comment in the **Reason for termination** field, and enter a summary.
+6. Click **TERMINATE THIS SERVICE AND OPTION ASSOCIATED** to confirm the termination.
+
+
+Your Dedibox server will be terminated in accordance with the timing of your termination request:
+To terminate a server at the end of the current month, you must submit your termination request between the 1st and 20th of that month.
+If you submit your termination request after the 20th, the termination will be effective at the end of the following month.
+
diff --git a/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx b/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx
new file mode 100644
index 0000000000..c4c1bf144c
--- /dev/null
+++ b/pages/dedibox/how-to/use-dedibackup-ftp-backup.mdx
@@ -0,0 +1,161 @@
+---
+meta:
+ title: How to use the Dedibackup FTP backup space
+ description: This page explains how to use the Dedibackup FTP backup space for Dedibox servers
+content:
+ h1: How to use the Dedibackup FTP backup space
+ paragraph: This page explains how to use the Dedibackup FTP backup space for Dedibox servers
+tags: dedibackup ftp backup ftp-backup
+dates:
+ validation: 2024-08-05
+ posted: 2021-10-07
+categories:
+ - dedibox-servers
+---
+
+Dedibackup is a remote storage solution available for all Dedibox dedicated servers.
+
+Two options are available:
+
+* A storage capacity of **100 GB** (included in the offer, without additional costs),
+* A storage capacity of **750 GB** (as option).
+
+The storage system is backed by our [Object Storage](https://www.scaleway.com/en/object-storage/) solution in the PAR-1 region.
+
+
+ Each offer allows you to store up to 1000 (one thousand) files on your Dedibackup volume. We recommend using archives (tarballs/zip) for your backups.
+
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+## How to activate the Dedibackup service
+
+1. Access your [Dedibox console](https://console.online.net).
+2. Click **Server** in the menu on the top of the page, then click **Server list**. A list of your Dedibox servers displays.
+3. Click **Manage** next to the server you want to configure. The server overview displays.
+4. Click **Backup** in the side-menu. The backup management page displays.
+5. Click **Order a backup space**. The backup options display.
+6. Choose the offer of your Dedibackup and click **Order**. A summary of your order displays.
+7. Validate the terms and conditions and confirm your order by clicking **Confirm my order**.
+
+## How to access the backup space
+
+You can access your backup space after its activation using the FTP protocol.
+
+
+### FTP parameters
+
+| Name of the server | dedibackup-dcX.online.net |
+|--------------------|----------------------------------------|
+| Port | 21 |
+| Login | sd-serverid (ex. sd-1234) |
+| Password | the password you set during activation |
+
+
+Replace `dcX` in the Dedibackup hostname with the location of your Dedibackup account.
+
+You can find the hostname for your Dedibackup space in the **Backup** section of the server's console.
+
+Available locations are:
+- `dedibackup-dc2.online.net`
+- `dedibackup-dc3.online.net`
+
+
+You are not limited in number of simultaneous connections. The use of FTPFS is not allowed.
+
+
+ You cannot upload from an IP outside the Dedibox network.
+
+
+### Technical specifications
+
+The following FTP commands are allowed:
+
+```
+ABOR, ACCT, APPE, CDUP, CWD, DELE, FEAT, LIST, MDTM, MKD, MODE, NLIST, NOOP, PASS, PASV, PORT, PWD, QUIT, RETR (only with argument), REST, RNFR, RNTO, RMD, SITE, SIZE, SMNT, STAT, STOR, SYST, TYPE, USER, XCUP, XCWD, XMKD, XPWD, XRMD.
+```
+
+### Security
+
+* **Autologin**: If you activate this function, you can log into your account without a password (automatic authentication based on your IP address and MAC address). With this feature, you can avoid transmitting your login information unencrypted over the network. Once this feature has been activated in your account, use the username `auto` and an empty password to connect.
+
+#### How to enable autologin
+
+1. Access your [Dedibox console](https://console.online.net/).
+2. Click **Server** in the menu on the top of the page, then click **Server list**. A list of your Dedibox servers displays.
+3. Click **Manage** next to the server you want to configure. The server overview displays.
+4. Click **Backup** in the side menu. The backup management page displays.
+5. Click **Edit connection settings**
+6. Tick the box **Auto-login** and click **Update** to validate.
+
+
+ All connection attempts (successful or unsuccessful) are stored in your Dedibox console in real-time.
+
+
+### Error messages
+
+* **500 Not accepted**: Problem while establishing the DATA connection. Verify your firewall configuration and try to use passive mode.
+* **502 Command not implemented**: The used command is not implemented on our servers. This causes disconnection from the server.
+* **500 Service Dedibackup temporary unavailable, try again later**: The backup system is currently not available or locked for maintenance.
+* **500 Impossible to get the IP, try again later**: Contact the support. An internal verification routine of your account has blocked your account.
+* **500 Your account is currently in maintenance, try again later**: Your account is in maintenance. It is recommended to retry to connect after 15 minutes.
+* **500 Communication error, try again later**: Internal malfunction, contact technical assistance if the problem persists.
+* **500 Communication error at the identification, try again later**: Internal malfunction with the authentication server, contact technical assistance if the problem persists.
+* **421 Configuration problem, try again later**: The configuration of your account is incorrect. Verify the configuration of your account in the management panel, contact technical assistance if the problem persists.
+* **553 Upload forbidden from an IP address external of the Dedibox network**: Using the STOR command is not allowed outside the Dedibox network.
+* **Too many files: [....] won't be saved, make tarballs.**: The limit of 1000 files on your Dedibackup account was bypassed. It will not be possible to add new files before deleting old ones.
+
+In case of a failure during authentication (wrong identifier and/or password), connection failure of the access control list (ACL), or failure of the automatic login from an unauthorized IP, the connection will be systematically terminated with the message **421 Service not available**.
+
+
+### Usage on Linux
+
+To connect to the Dedibackup service, we recommend `lftp` for interactive use and `curl` for automated tasks:
+
+#### Recommended tools
+ * For interactive connections: Use `lftp`, which offers an interface and flexibility suitable for FTP sessions.
+ * For automated scripts: Use `curl` for automation, though some limitations exist with FTP servers that do not support all commands.
+
+#### Example of interactive connection with lftp
+
+For interactive sessions, use `lftp` with the following command:
+```sh
+apt install lftp # Requirement
+
+FTP_HOST="ftp://dedibackup-dc3.online.net"
+FTP_USER="sd-XXXXX" # Replace with your server ID or 'auto' for autologin
+FTP_PASS="your_password" # Leave blank if using autologin
+
+# - Connect to FTP server
+# - Upload a file, list files, remove a file
+# - Disconnect from FTP server
+lftp -u "$FTP_USER,$FTP_PASS" "$FTP_HOST" <
+ Passive mode in `lftp` is automatically managed, so manual configuration is usually unnecessary.
+
+
+#### Example of automated connection with curl
+When automating tasks, you can use `curl`, though command limitations may apply:
+
+```sh
+# Upload a file
+curl -T "path_to_your_file.7z" -u "sd-XXXXX:your_password" ftp://dedibackup-dc3.online.net/
+```
+
+ Replace `dedibackup-dc3` with the actual backup location (`-dc2`, `-dc3`, etc.), as specified in your Dedibox console.
+
+
diff --git a/pages/dedibox/how-to/use-ipmi-on-server.mdx b/pages/dedibox/how-to/use-ipmi-on-server.mdx
new file mode 100644
index 0000000000..43fae707f3
--- /dev/null
+++ b/pages/dedibox/how-to/use-ipmi-on-server.mdx
@@ -0,0 +1,83 @@
+---
+meta:
+ title: How to use IPMI on a Dedibox server
+ description: This page explains how to use IPMI on a Scaleway Dedibox server
+content:
+ h1: How to use IPMI on a Dedibox server
+ paragraph: This page explains how to use IPMI on a Scaleway Dedibox server
+tags: dedibox ipmi server
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+An **I**ntelligent **P**latform **M**anagement **I**nterface (IPMI) is an industry standard to describe the subsystem of a server providing remote management and monitoring capabilities. IPMI gives you a way to manage and monitor a server even if it is powered off or unresponsive, by using a network connection to the hardware. IPMI is made possible by the **B**aseboard **M**anagement **C**ontroller, an independent piece of hardware connected to your network card, composed of an I2C bus and a dedicated processor.
+
+Some examples of features that can be remotely monitored via the IPMI include:
+
+ - Ventilation,
+ - Temperature,
+ - Voltage,
+ - Operating time.
+
+Actions that can be carried out via IPMI include:
+
+ - Rebooting via KVM,
+ - Switching the server off and/or on,
+ - Configuration of automatic notification in case of hardware problems (power supply failure, temperature anomalies, etc.),
+ - Viewing of logs from the BIOS,
+ - Accessing the serial port and BIOS over the network via serial console.
+
+In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox-kvm-over-ip/) documentation for information about other server models.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a Dedibox server with a dedicated KVM over IP device
+
+## How to use IPMI via Dell iDRAC
+
+IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the iDRAC: the **i**ntegrated **D**ell **R**emote **A**ccess **C**ontroller.
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the relevant server.
+3. Click the **IDRAC** button on the right. A disclaimer displays.
+4. Click **I Accept** to agree with the terms of the disclaimer.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+ The connection URL and your credentials display. Click on the link to access the iDRAC interface.
+
+
+6. Use the interface to monitor and manage your server's hardware:
+ - The **System** tabs let you view various system information including system details, logs, and power status. You can also use the **Console/Media** > **Virtual Media** tab to install your server remotely with a custom OS by connecting virtual media. To launch the KVM, click **Remote Access Controller** under **System Details**.
+ - The **iDDRAC** tabs show you information about the iDRAC itself.
+ - Click the other relevant links on the left sidebar to see information about **Batteries**, **Temperatures**, **Voltages**, etc., as required.
+
+## How to use IPMI via HP iLO
+
+IPMI is a standard specification for a remote management subsystem. On a Dell server, IPMI is realized through the ILO: the **i**ntegrated **L**ights **O**ut processor.
+
+1. From the console, click **Server** > **Server list**. A list of your servers displays.
+2. Click **Manage** next to the relevant server.
+3. Click the **IDRAC** button on the right. A disclaimer displays.
+4. Click **I Accept** to agree with the terms of the disclaimer.
+5. Enter the authorized IPv4 address for the iDRAC connection. The IP address of your internet connection is already pre-filled in the form. Then click **Create** to generate your credentials.
+
+ Currently, only IPv4 addresses are accepted.
+
+
+ The connection URL and your credentials display. Click on the link to access the iLO interface.
+
+
+6. Use the interface to monitor and manage your server's hardware:
+ - The **Information** pages let you view various system information including system details, logs, and diagnostics.
+ - The **Remote Console** pages let you launch the KVM.
+ - The **Virtual Media** pages let you install your server remotely with a custom OS by connecting virtual media.
+ - Click the other relevant links on the left sidebar to see more information.
+
+
diff --git a/pages/dedibox/how-to/use-rescue-mode.mdx b/pages/dedibox/how-to/use-rescue-mode.mdx
new file mode 100644
index 0000000000..721a78384c
--- /dev/null
+++ b/pages/dedibox/how-to/use-rescue-mode.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: How to Use Rescue Mode on a Dedibox Server
+ description: Learn how to use rescue mode on a Scaleway Dedibox server to troubleshoot and recover your system.
+content:
+ h1: How to Use Rescue Mode on a Dedibox Server
+ paragraph: Learn how to use rescue mode on a Scaleway Dedibox server to troubleshoot and recover your system.
+tags: rescue mode rescue-mode dedicated-server dedicated server
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+Rescue mode is a minimal operating system that can be booted on demand over the network, allowing you to recover and troubleshoot your server when it fails to boot. Use rescue mode if your Dedibox server:
+
+- Fails to boot after a restart, possibly due to an **FSCK error**
+- Becomes unreachable due to a **firewall misconfiguration**
+- Does not boot after a **kernel upgrade**
+- Fails to start following a **bootloader configuration change** (e.g., Grub, LILO)
+- Does not boot after an **operating system update**
+- Becomes generally unavailable on the internet after booting
+
+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))
+- [FreeBSD](https://www.freebsd.org/)
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- A [Dedibox server](/dedicated-servers/how-to/order-a-server/)
+
+
+## Launching rescue mode
+
+1. Navigate to **Server** > **Server list** in the top menu of the Dedibox console.
+2. Find the relevant server and click **Manage**.
+3. Click **Rescue**.
+4. Select the appropriate rescue mode for your server’s operating system.
+5. Click **Launch rescue mode** to start the process.
+
+## Accessing rescue mode for Linux/FreeBSD
+
+To access your server in Linux/FreeBSD rescue mode:
+
+1. [Connect to your server via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh).
+2. Use the login credentials provided on the server’s status page in the console. Note that it may take approximately two minutes for rescue mode to fully initialize.
+
+ Once connected, you can operate rescue mode like a standard distribution, installing tools such as text editors or FTP clients as needed. Keep in mind that the size of the ramdisk is limited.
+
+## Accessing rescue mode for Windows
+
+To access your server in Windows PE rescue mode:
+
+1. Use the KVM/IP feature of your server, as it is the only way to connect in this mode.
+2. Refer to the [KVM/IP documentation](/dedibox-kvm-over-ip/quickstart/) for instructions specific to your server model.
diff --git a/pages/dedibox/how-to/use-serial-console.mdx b/pages/dedibox/how-to/use-serial-console.mdx
new file mode 100644
index 0000000000..32c13eac1a
--- /dev/null
+++ b/pages/dedibox/how-to/use-serial-console.mdx
@@ -0,0 +1,136 @@
+---
+meta:
+ title: How to use the serial console
+ description: This page explains how to use the serial console on a Scaleway Dedibox server
+content:
+ h1: How to use the serial console
+ paragraph: This page explains how to use the serial console on a Scaleway Dedibox server
+tags: dedibox serial console serial-console
+dates:
+ validation: 2024-08-19
+ posted: 2021-06-11
+categories:
+ - dedibox-servers
+---
+
+Some Dedibox server models do not have KVM over IP, but allow the visualization of a video output on a serial console. This allows you to interact with the server even if you have locked yourself out, for example by a malicious network configuration.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server
+
+## How to access the serial console
+
+1. From the console, click **Server** > **Server list** on the top menu. A list of your servers displays.
+2. Click **Manage** next to the relevant server.
+3. Click **Serial Console**. The connection information displays.
+
+4. Click **Access** to access the serial console of your server.
+
+
+## How to configure the serial console
+
+On certain installations, the serial console may not be activated by default. These steps show you how to activate it from the command line of your server.
+
+### On SystemD-based operating systems (Ubuntu 18.04 and later / Debian 8 and later / CentOS)
+
+To activate it on each reboot:
+
+```
+systemctl enable getty@ttyS1.service
+```
+
+To activate it on an already booted server:
+
+```
+systemctl start getty@ttyS1.service
+```
+
+### On Ubuntu 14.04
+
+Create the folder `/etc/init/ttyS1.conf`:
+
+```
+# ttyS1 - getty
+#
+# This service maintains a getty on ttyS1 from the point the system is
+# started until it is shut down again.
+
+start on stopped rc RUNLEVEL=[12345]
+stop on runlevel [!12345]
+
+respawn
+exec /sbin/getty -L 9600 ttyS1 vt102
+```
+
+After a reboot of the server, the serial console will be activated.
+
+
+### On Debian 7 (Wheezy)
+
+1. Edit the file `/etc/inittab`.
+2. Uncomment the following line:
+ ```
+ T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
+ ```
+
+ To put the changes into effect type:
+
+ ```
+ init q
+ ```
+
+### GRUB
+
+In certain cases, GRUB may not be configured to show the serial console.
+
+1. Edit `/etc/default/grub`, to add/change the following lines:
+ ```
+ GRUB_TERMINAL=serial
+ GRUB_SERIAL_COMMAND="serial --unit=1 --speed=9600 --word=8 --parity=no --stop=1"
+ ```
+2. Save the changes.
+3. Update your GRUB:
+ ```
+ update-grub or update-grub2.
+ ```
+
+### On ESXi
+
+Directly from the vSphere client:
+
+
+
+1. Enter the Configuration tab (1). In the **Software** section, click on **Advanced Settings** (2).
+
+ A new window will open.
+2. Go to VMKernel and open it by clicking on the small + icon on the left.
+3. Click on Boot (1).
+4. On the right side of the window, look for the VMKernel.Boot.com2_baud option
+5. Enter 9600 (2) as value:
+
+6. Look for the VMKernel.Boot.tty2Port value5. Enter 9600 (2) as value:
+
+6. Look for the VMKernel.Boot.tty2Port value.
+8. Reboot the ESXi host. You can now use the serial console of your server.
+
+### On FreeBSD
+
+1. Edit the `/boot/loader.conf` file:
+ ```
+ boot_multicons="YES"
+ boot_serial="YES"
+ comconsole_speed="9600"
+ console="comconsole"
+ comconsole_port="0x2F8"
+ ```
+
+ This will activate the console during the boot process of your server.
+2. Edit the `/etc/ttys` file to add the following information at the ttyu1 line:
+ ```
+ ttyu1 "/usr/libexec/getty std.9600" vt100 on secure
+ ```
+3. Reboot your server to access the serial console.
+
+
diff --git a/pages/dedibox/index.mdx b/pages/dedibox/index.mdx
index 37cf6f986d..d447baacea 100644
--- a/pages/dedibox/index.mdx
+++ b/pages/dedibox/index.mdx
@@ -1,9 +1,90 @@
---
meta:
- title: Discover Dedibox
- description: Discover Dedibox
-content:
- h1: Discover Dedibox
- paragraph: Discover Dedibox
+ title: Dedicated Servers Documentation
+ description: Dive into Scaleway Dedicated Servers with our quickstart guides, how-tos, tutorials and more.
---
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/dedibox/quickstart.mdx b/pages/dedibox/quickstart.mdx
new file mode 100644
index 0000000000..d18d74ed44
--- /dev/null
+++ b/pages/dedibox/quickstart.mdx
@@ -0,0 +1,169 @@
+---
+meta:
+ title: Dedicated servers - Quickstart
+ description: This page explains how to get started with Dedibox dedicated servers
+content:
+ h1: Dedicated servers - Quickstart
+ paragraph: This page explains how to get started with Dedibox dedicated servers
+tags: dedibox dedicated-server dedicated servers raid
+dates:
+ validation: 2024-08-19
+ posted: 2021-07-13
+categories:
+ - dedibox-servers
+---
+
+[Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) are our high-quality dedicated servers. With over 15 years of experience, we provide dedicated servers that are recognized for their extreme reliability and best-in-class redundancy.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account
+
+## How to order a server
+
+1. Click **Order** on your Dedibox console homepage.
+2. Click **Server**. The server offers page displays.
+
+ You can view all servers available in your preferred data center by clicking the **Datacenter selection** drop-down menu in the top right corner.
+
+3. Select a server model and click the **Order** button next to your choice. The server creation wizard displays.
+4. Complete the following steps in the wizard:
+ - Select your commitment period: rent without commitment, or choose a 12 or 36-month plan for lower monthly rates and free server setup.
+
+ This step only displays for Dedibox servers eligible for a commitment plan.
+
+ - Select the data center.
+
+ Some server models are available in more than one data center. If you have no preference, select **"No preference"**.
+
+ - Choose the service level. There are two plans available:
+ - **Basic service level**: Included with any Dedibox server. Offers:
+ - Assistance by ticket and phone
+ - H+4 GTI
+ - 99.9% SLA
+ - RPN with limited bandwidth
+ - **Business service level**: A paid plan with:
+ - Priority assistance by ticket and phone
+ - Sales assistance
+ - H+1 GTI
+ - 99.95% SLA
+ - RPN with high bandwidth
+ - Customization and security options (anti-DDoS)
+ - Quota of +15 failover IPs
+ - Dedicated project manager
+ - Select a backup option: 750 GB FTP, 100 GB FTP, or no FTP backup.
+ - Choose a plan for protection against DDoS.
+
+ To benefit from the **Preventive** or **Curative** anti-DDoS plans, you must activate the Business service level for the server.
+
+5. Click **Order**. A summary of your order displays.
+6. Select your payment method in the **Payment mode choice** drop-down menu in the top right corner.
+7. Check the boxes confirming that you have read and agreed to the terms of service.
+8. Click **Confirm my order**. A confirmation of your order displays.
+
+
+## How to install a server
+
+After the delivery of your server, you can begin installing it.
+
+1. From the console, click **Server** > **Server list** on the top menu. A list of your servers displays.
+2. Click **Manage** next to the server you want to install. The server installation wizard displays.
+3. Select the type of operating system you want to install.
+
+ For more information about OS types, refer to the [dedicated servers concepts page](/dedicated-servers/concepts/#os-type).
+
+
+
+ If you wish to complete your installation using KVM Over IP, click **Install over KVM** on this page.
+
+4. Choose the operating system and OS version. Then, click **Install**.
+5. Personalize the following [partitioning](/dedicated-servers/concepts/#partitioning) parameters:
+ - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap)
+ - the mount point of the partition
+ - the partition size
+ - the software raid (RAID 0/1/5)
+
+
+ When you start a CentOS installation with custom partitioning, you need to keep about 5 GB of unallocated disk space to prevent the automatic installation system from crashing.
+
+6. Click **Validate**.
+7. Configure the system parameters. You can edit parameters such as the name of the server, add a username, password, and SSH key, and configure monitoring alerts and updates.
+
+ To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation.
+
+8. Check that all information you entered is correct on the installation summary tab.
+
+ Once the installation completes, your server will reboot on its hard disk.
+
+
+ Depending on the OS, the installation may take several minutes to complete. Certain operating systems may require additional reboots for completion. We recommend waiting 45 to 60 minutes before you connect to your server.
+
+
+## How to connect to your server
+
+A common way of connecting to your Dedibox server is via the command line, using SSH. SSH is a secure communication protocol, which imposes an encryption key exchange at the beginning of the connection. This means that the exchange of data between the client and the server will be encrypted.
+
+However, you may also connect to your server via a graphical interface, such as Windows Remote Desktop.
+
+You can also use FTP, SFTP, or SCP to transfer data to and from your server.
+
+
+
+- A Dedibox account logged into the [console](https://console.online.net)
+- [Created and uploaded your SSH key](/dedibox-account/how-to/upload-an-ssh-key/)
+- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation
+
+## How to connect via SSH
+
+### From OSX (Mac) and Linux
+
+1. Open a terminal program on your local machine.
+2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_rsa`) and `your_server_ip` with the IP address of your server.
+ ```bash
+ ssh -i ~/.ssh/your_private_key root@your_server_ip
+ ```
+3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' cannot be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+### From Windows
+
+To connect to your server from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+1. Download and install [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+2. Launch PuTTY on your computer. The main screen of the application displays.
+3. Enter your Instance's IP address in the **Hostname** field.
+
+ To find the IP address of your Instance, log into the Scaleway console and
+ click **Instances** in the Compute section of the side menu. A list of your
+ Instances and their associated IP addresses will display.
+
+
+4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**.
+5. Click the **Browse** button and select the private key file you [generated previously](/dedibox-account/how-to/upload-an-ssh-key/).
+6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host.
+7. Click **OK** to confirm. The terminal window displays.
+8. Enter your username and password to authenticate against the server with your SSH key.
+
+ You are now connected to your server.
+
+## How to connect via Remote Desktop
+
+The following steps show you how to connect to your Dedibox on which you have installed Windows Server, from your local Windows machine.
+
+1. Open the **Remote Desktop Connection** tool on your local Windows machine.
+2. Click the drop-down arrow next to **Show connections**.
+3. Enter the following information:
+ - In **Computer**, enter the IP address of your Dedibox server (e.g. 163.172.20.01).
+ - In **Username**, for a Windows Server type **Administrateur**.
+4. Click **Connect**. You are prompted to enter a password.
+5. Enter the password that you set during installation of your Dedibox Windows Server machine, and click **OK**.
+6. You may be asked to confirm that you want to connect. Click **Yes**.
+
+ You are connected to the graphical interface of your Windows Server. If you need to change the language, refer to the [How to change the language of Windows Server](/dedicated-servers/how-to/change-win-server-language/) page.
\ No newline at end of file
diff --git a/pages/dedibox/reference-content/basic-linux-commands.mdx b/pages/dedibox/reference-content/basic-linux-commands.mdx
new file mode 100644
index 0000000000..e7726eb45f
--- /dev/null
+++ b/pages/dedibox/reference-content/basic-linux-commands.mdx
@@ -0,0 +1,95 @@
+---
+meta:
+ title: Basic Linux/Unix commands
+ description: Learn how to use some basic Linux/Unix commands
+content:
+ h1: Basic Linux/Unix commands
+ paragraph: Learn how to use some basic Linux/Unix commands
+tags: dedibox linux unix command
+dates:
+ validation: 2024-09-02
+categories:
+ - dedibox-servers
+---
+
+In this document, we go through some of the most basic Linux commands. These commands can be used in the shell (the command line terminal) to get full use of your remote server. Most of these commands will be compatible with all UNIX OSes. However, depending on the version, the arguments (the parameters after the basic command) used may change.
+
+## cd: Change directory
+
+The `cd` allows you to change the directory you are in on your shell.
+
+For example, you are in your personal directory (home) and want to navigate to the directory where your log files are (/var/log). Enter the following command:
+
+```
+cd /var/log/
+```
+
+You are now in the `/var/log` directory.
+
+## ls: List the content of a directory
+
+This command allows you to display all the contents of a directory.
+
+You are still in the `/var/log` directory, and want to see everything it contains. Enter the `ls` command. A list of the contents displays as output:
+
+```ls
+alternatives.log alternatives.log.7.gz apport.log.5.gz auth.log.4.gz dmesg.0 dpkg.log.3.gz fontconfig.log kern.log.3.gz pm-powersave.log.4.gz syslog.2.gz upstart
+alternatives.log.1 alternatives.log.8.gz apport.log.6.gz boot.log dmesg.1.gz dpkg.log.4.gz fsck kern.log.4.gz pm-suspend.log syslog.3.gz wtmp
+alternatives.log.10.gz alternatives.log.9.gz apport.log.7.gz bootstrap.log dmesg.2.gz dpkg.log.5.gz gpu-manager.log lastlog pm-suspend.log.1 syslog.4.gz wtmp.1
+```
+
+You can also perform a `ls` on another folder:
+
+```
+ls /etc
+```
+
+
+ To get a more detailed view of the files in a directory, type `ls -l`, or use the abbreviated command `ll`. This displays additional details such as file permissions, dates, and sizes.
+
+
+## rm: Remove (delete) folders and files
+
+To delete data, you need the command `rm`. Type `rm` followed by the name of the file you want to delete:
+
+```
+rm myFile
+```
+
+To delete folders as opposed to files, you need to add the `-r` argument:
+
+```
+rm -r myFolder
+```
+
+This command will recursively remove the folder and all its files and contents.
+
+
+ To force a deletion, use `rm -rf myFolder`. Pay attention when using this command. A mistake can delete critical data without asking you for confirmation.
+
+
+## man: User manual
+
+In Linux, everything is documented. If you want to know about the functioning or features of a certain program, `man` will give you the answer.
+
+The usage is pretty simple:
+
+```
+man COMMAND
+```
+
+For example, `man ls` will display all the details about the `ls` command we saw previously.
+
+## nano: File editor
+
+At some point, you will probably need to edit a text file using the command line. The easiest way to do this is via the `nano` editor. Type `nano` followed by the name of the file you want to edit (if you are in the same directory as the file) or the path to the file (if the file is in another directory):
+
+```
+nano /path/to/myFile.txt
+```
+
+The nano text editor displays, and you can make your edits. When you have finished, terminate nano by pressing the keys `CTRL + X`. If you made any changes, you will be prompted to save them.
+
+Once you have finished editing your file, terminate nano by pressing the keys `CTRL + X`.
+
+If you made any changes, you will be asked to save them.
diff --git a/pages/dedibox/reference-content/index.mdx b/pages/dedibox/reference-content/index.mdx
new file mode 100644
index 0000000000..c6f6205c84
--- /dev/null
+++ b/pages/dedibox/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Dedicated servers - Additional content
+ description: Dedicated Servers additional content
+content:
+ h1: Dedicated servers - Additional content
+ paragraph: Dedicated Servers additional content
+---
diff --git a/pages/domains-and-dns/assets/scaleway-dns-domain-validated.webp b/pages/domains-and-dns/assets/scaleway-dns-domain-validated.webp
new file mode 100644
index 0000000000..751d53aa10
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-dns-domain-validated.webp differ
diff --git a/pages/domains-and-dns/assets/scaleway-dns-nameserver.webp b/pages/domains-and-dns/assets/scaleway-dns-nameserver.webp
new file mode 100644
index 0000000000..77e11de982
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-dns-nameserver.webp differ
diff --git a/pages/domains-and-dns/assets/scaleway-dns-ongoing-validation.webp b/pages/domains-and-dns/assets/scaleway-dns-ongoing-validation.webp
new file mode 100644
index 0000000000..cc10a97136
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-dns-ongoing-validation.webp differ
diff --git a/pages/domains-and-dns/assets/scaleway-dns-validation-token.webp b/pages/domains-and-dns/assets/scaleway-dns-validation-token.webp
new file mode 100644
index 0000000000..56d6372e17
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-dns-validation-token.webp differ
diff --git a/pages/domains-and-dns/assets/scaleway-domain-namespace.webp b/pages/domains-and-dns/assets/scaleway-domain-namespace.webp
new file mode 100644
index 0000000000..2fbd4fe408
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-domain-namespace.webp differ
diff --git a/pages/domains-and-dns/assets/scaleway-fqdn.webp b/pages/domains-and-dns/assets/scaleway-fqdn.webp
new file mode 100644
index 0000000000..28b154e98c
Binary files /dev/null and b/pages/domains-and-dns/assets/scaleway-fqdn.webp differ
diff --git a/pages/domains-and-dns/concepts.mdx b/pages/domains-and-dns/concepts.mdx
new file mode 100644
index 0000000000..e3934db139
--- /dev/null
+++ b/pages/domains-and-dns/concepts.mdx
@@ -0,0 +1,126 @@
+---
+meta:
+ title: Domains and DNS - Concepts
+ description: Discover concepts related to Scaleway's Domains and DNS service. Learn about DNS namespaces, name servers, domain names, DNS resolution, records, zones, and more.
+content:
+ h1: Domains and DNS - Concepts
+ paragraph: Discover concepts related to Scaleway's Domains and DNS service. Learn about DNS namespaces, name servers, domain names, DNS resolution, records, zones, and more.
+tags: domains domain dns namespace dns-zone nameserver zone-file reverse-dns root-server
+dates:
+ validation: 2024-10-29
+categories:
+ - network
+---
+
+## DNS
+
+**D**omain **N**ame **S**ystem is a name management system for computing devices connected to a network, be it public (internet) or private. It translates text-based [domain names](#domain-name) to numerical IP addresses or other services such as emails.
+
+## DNS namespace
+
+DNS domains are all organized in a hierarchy called the DNS namespace. The hierarchy consists of:
+
+* **Top Level domains**: .com or .net (or any other)
+* **Second-level domains**: example.com
+* **Subdomains**: mysite.example.com or sub.domain.example.com.
+
+
+
+## DNS name server
+
+A DNS name server stores the [DNS Records](#dns-record) for given domains. Scaleway has its own name servers for its managed domains.
+
+
+
+## DNS record
+
+A [DNS](#dns) Record holds information translating a domain or subdomain to an IP address, mail server or other domain/subdomain. DNS records for each [DNS Zone](#dns-zone) are stored within files called [DNS zone files](#dns-zone-file). These are hosted on [DNS nameservers](#dns-name-server). DNS records act as instructions for the DNS servers, so they know which domain names and IP addresses are associated with each other. DNS records can be of multiple types, called [resource records](#resource-records). Check out our documentation on [how to manage DNS records](/domains-and-dns/how-to/manage-dns-records/).
+
+## DNS zone
+
+A DNS zone hosts the DNS records for a distinct part of the global domain namespace, and is managed by a specific organization or administrator. For example with Scaleway Domains and DNS, if you are managing the external domain `example.com` with us, this is your root zone. You can [create further zones and subdomains](/domains-and-dns/how-to/configure-dns-zones/), e.g. `mysubdomain.example.com`.
+
+## DNS zone file
+
+A DNS zone file describes a [DNS Zone](#dns-zone), containing DNS records which constitute mappings between domain names, IP addresses and other resources.
+
+## Domain name
+
+A **domain name** or **domain** is a unique alphanumeric name used to identify a computer (web or email server) on the internet. It translates the numeric address of the computer to a more legible human-readable and memorable name. A domain can consist of a single [DNS Zone](#dns-zone) or be divided into several zones.
+
+## Domain name resolution
+
+Domain name resolution refers to the process by which human-readable domain names, like `www.mydomain.com`, are translated into the numerical IP addresses that computers and servers use to communicate on the internet.
+
+## External domain
+
+An external domain is any domain created via an external registrar (i.e. not Scaleway). You can manage DNS zones for external domains from the Scaleway console.
+
+## Fully qualified domain name (FQDN)
+
+A fully qualified domain name, also known as **absolute domain**, is a complete domain name that allows computers and servers connected to the internet to have unique identities and a location within the internet framework.
+
+An FQDN consists of a [hostname](#hostname), a [subdomain](#subdomain), a domain name comprised of a [second-level-domain](#second-level-domain) and a [top-level domain (TLD)](#top-level-domain-tld), and a **trailing dot**. The trailing dot is used to differentiate fully qualified domain names from [partially qualified domain names](#partially-qualified-domain-name-pqdn) within DNS.
+
+
+
+## Hostname
+
+When looking at a [fully qualified domain name](#fully-qualified-domain-name-fqdn), the hostname usually comes before the domain name or the subdomain. A hostname is a label or name assigned to a computer, device, or server on a network. It helps identify and locate a specific computer or any device connected to a network among all the others.
+
+An example of a hostname can be `www` for the fully qualified domain name `www.mydomain.com.`.
+
+## Internal domain
+
+An internal domain is any domain name registered through Scaleway Domains and DNS. Register and (auto-)renew your domains with Domains and DNS and manage them from the Scaleway console.
+
+## Partially qualified domain name (PQDN)
+
+A partially qualified domain name or **relative domain name** is an incomplete domain name. It lacks the [top-level domain (TLD)](#top-level-domain-tld) and potentially even the subdomain part of the domain name.
+
+## Resource records
+
+Information in [DNS zones](#dns-zone) is categorized and organized through a list of [DNS record](#dns-record) types, called Resource Records (RRs). Each of these records has a type, an expiration time (Time to Live - TTL), a name, and type-specific data for certain types of records.
+
+The most common records are:
+
+* **A record**: Address record, mostly used to map domain names to the IPv4 address of a specific server.
+* **AAAA record**: IPv6 Address record, returns an IPv6 address and is mostly used to map domain names to the IPv6 address of a specific server.
+* **CNAME record**: Canonical name record, an alias of one name to another. The DNS lookup will continue by looking up the new name.
+* **MX record**: Mail exchange record, maps a domain name to a list of one or several mail servers for that domain.
+* **TXT record**: Text record, often used to carry machine-readable data such as information for automated domain validation.
+
+## Reverse DNS
+
+Reverse DNS (rDNS) allows you to resolve from an IP address to a Fully Qualified Domain Name (FQDN). An FQDN consists of a complete address for a website, computer, server or similar entity that exists on the internet. Reverse DNS is the exact opposite of the classic use of DNS, which associates domain names to IP addresses. Here, it operates by creating a reverse DNS zone in which DNS PTR records (for Pointer Record) will be configured.
+
+Reverse DNS can be helpful when sending emails from your server. Indeed, many mail servers on the internet are configured to reject incoming mail from any IP address that does not have reverse DNS. For those who manage their own mail server, reverse DNS must exist for the IP address from which the outgoing email is sent.
+
+## Root server
+
+Root Servers are a type of DNS name servers pertaining to [top-level domains](#top-level-domain-tld). They are the first step in the resolution of any domain name, since they contain information about the authoritative DNS servers for each top-level domain.
+
+## Scaleway Domains and DNS
+
+Scaleway Domains and DNS is a managed [DNS](#dns) service that allows you to easily configure the [DNS zones](#dns-zone) of your [domains](#domain-name). It provides support for queries via both IPv4 and IPv6, and supports all common types of [DNS records](#dns-record).
+
+## Second-level domain
+
+A second-level domain is the part of a domain name that is located directly to the left of the [top-level domain](#top-level-domain-tld). For example, in the domain name `mydomain.com`, **mydomain** is the second-level domain.
+
+## SSL/TLS certificates
+
+SSL/TLS certificates are cryptographic protocols that provide secure communication over the internet. They ensure that the data transmitted between a user's browser and a website's server is encrypted and protected from unauthorized access, interception, or tampering.
+
+## Subdomain
+
+A subdomain is an additional piece of information added to your domain name to create separate sections or categories within your website. Subdomains help organize content and services, making it easier for users to access specific information. For example, in the domain name `blog.mydomain.com`, **blog** is the subdomain. Your users accessing `blog.mydomain.com` will thus, be directed to the blog part of your website.
+
+## Top-level domain (TLD)
+
+In the [DNS](#dns) hierarchy, a top-level domain is the last part of text in a domain name. For instance, in the domain name `mydomain.com`, **.com** is the top-level domain.
+
+## Trade
+
+A trade is the process of transferring ownership rights of a domain name from one entity (current owner) to another (new owner).
+However, Scaleway's Domains and DNS trade feature only allows you to **edit the registrant contact information of an internal domain (to correct typing errors, for example), or information such as a company name, or a SIRET number**.
\ No newline at end of file
diff --git a/pages/domains-and-dns/how-to/add-external-domain.mdx b/pages/domains-and-dns/how-to/add-external-domain.mdx
new file mode 100644
index 0000000000..0944d3aee4
--- /dev/null
+++ b/pages/domains-and-dns/how-to/add-external-domain.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: How to add an external domain to Domains and DNS
+ description: Discover how to add an external domain to Scaleway's Domains and DNS service. Follow step-by-step instructions to manage DNS zones, validate domain ownership with TXT records, and integrate external domains efficiently.
+content:
+ h1: How to add an external domain to Domains and DNS
+ paragraph: Discover how to add an external domain to Scaleway's Domains and DNS service. Follow step-by-step instructions to manage DNS zones, validate domain ownership with TXT records, and integrate external domains efficiently.
+tags: external-domain domain dns
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Domains and DNS allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones.
+
+
+
+- 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
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+2. Click the **External domains** tab, then click **+ Manage new domain**.
+3. Enter the external domain name in the box and click the search icon to check whether the domain exists. If it does, the estimated cost to add it displays.
+
+4. Click **Manage as external**. The instructions to set up your external domain display. Add a `TXT`record to the root zone of the domain at your current registrar to validate the domain ownership.
+
+ `TXT` means text record. It is used to carry machine-readable data such as information for automated domain validation.
+
+ Copy the token displayed and create a `TXT` record with the name `_scaleway-challenge` within your current DNS zone as instructed:
+
+
+ The token's presence will be checked regularly. If it has not been set within 48 hours, the external domain will be deleted from the service.
+
+5. Click **Back to my external domains** once you have set up the record in your current DNS zone. The list of your external domains displays.
+
+Once the TXT record is validated, the dot next to your domain turns green, and you will receive an email with instructions on how to update your domain's DNS name servers.
+
+Update the name server information at your current registrar once your domain is validated to link your existing domain name with your Scaleway DNS zone.
+
+
+ Scaleway's name servers are:
+ * ns0.dom.scw.cloud
+ * ns1.dom.scw.cloud
+
+
+You can verify that the association of your domain has been completed by checking the **Name servers** section on the **Domain information** page.
+
+
+ You have a maximum of 14 days to complete the entire process before the external domain gets deleted. You will receive emails reminding you to complete the process on days 7 and 13.
+
+
+
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-add-records.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-add-records.webp
new file mode 100644
index 0000000000..4a7f4b7683
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-add-records.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-add-zone.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-add-zone.webp
new file mode 100644
index 0000000000..fd89267694
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-add-zone.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-confirm-delete.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-confirm-delete.webp
new file mode 100644
index 0000000000..3f9bfdf599
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-confirm-delete.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-delete-zone.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-delete-zone.webp
new file mode 100644
index 0000000000..08044c53cb
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-delete-zone.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-information.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-information.webp
new file mode 100644
index 0000000000..c8801d8ce5
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-information.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-validated.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-validated.webp
new file mode 100644
index 0000000000..48520f42a9
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-domain-validated.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-records.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-records.webp
new file mode 100644
index 0000000000..56793b9c18
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-records.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-zone-name.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-zone-name.webp
new file mode 100644
index 0000000000..4c899b1148
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-edit-zone-name.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-geo-ip.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-geo-ip.webp
new file mode 100644
index 0000000000..c2f61925fb
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-geo-ip.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-healthcheck.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-healthcheck.webp
new file mode 100644
index 0000000000..faaf813456
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-healthcheck.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-interface.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-interface.webp
new file mode 100644
index 0000000000..ce7cd9c02c
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-interface.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-more-info.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-more-info.webp
new file mode 100644
index 0000000000..f048a0d988
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-more-info.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-ongoing-validation.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-ongoing-validation.webp
new file mode 100644
index 0000000000..cc10a97136
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-ongoing-validation.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-validation-token.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-validation-token.webp
new file mode 100644
index 0000000000..56d6372e17
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-validation-token.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-view.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-view.webp
new file mode 100644
index 0000000000..933d89e61c
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-view.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-weighted.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-weighted.webp
new file mode 100644
index 0000000000..4142cf8e95
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-weighted.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-dns-zone-list-edit.webp b/pages/domains-and-dns/how-to/assets/scaleway-dns-zone-list-edit.webp
new file mode 100644
index 0000000000..e5352014a7
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-dns-zone-list-edit.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-domain-autorenew.webp b/pages/domains-and-dns/how-to/assets/scaleway-domain-autorenew.webp
new file mode 100644
index 0000000000..cfd8113ade
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-domain-autorenew.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-domain-copy-auth.webp b/pages/domains-and-dns/how-to/assets/scaleway-domain-copy-auth.webp
new file mode 100644
index 0000000000..7c9be13579
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-domain-copy-auth.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-domain-dnssec.webp b/pages/domains-and-dns/how-to/assets/scaleway-domain-dnssec.webp
new file mode 100644
index 0000000000..c7bd55ebcc
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-domain-dnssec.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-domain-unlock.webp b/pages/domains-and-dns/how-to/assets/scaleway-domain-unlock.webp
new file mode 100644
index 0000000000..724678774b
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-domain-unlock.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-domains-and-dns-renew-domain.webp b/pages/domains-and-dns/how-to/assets/scaleway-domains-and-dns-renew-domain.webp
new file mode 100644
index 0000000000..a69406240f
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-domains-and-dns-renew-domain.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-register_new_domain.webp b/pages/domains-and-dns/how-to/assets/scaleway-register_new_domain.webp
new file mode 100644
index 0000000000..e8904d7e72
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-register_new_domain.webp differ
diff --git a/pages/domains-and-dns/how-to/assets/scaleway-registration-period.webp b/pages/domains-and-dns/how-to/assets/scaleway-registration-period.webp
new file mode 100644
index 0000000000..50454dda1b
Binary files /dev/null and b/pages/domains-and-dns/how-to/assets/scaleway-registration-period.webp differ
diff --git a/pages/domains-and-dns/how-to/configure-autorenew.mdx b/pages/domains-and-dns/how-to/configure-autorenew.mdx
new file mode 100644
index 0000000000..cbc69c1773
--- /dev/null
+++ b/pages/domains-and-dns/how-to/configure-autorenew.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to configure autorenew for an internal domain
+ description: Learn how to set up and manage the autorenew feature for your internal domains. Follow straightforward steps to activate or deactivate autorenewal, ensuring seamless renewal of domain validity.
+content:
+ h1: How to configure autorenew for an internal domain
+ paragraph: Learn how to set up and manage the autorenew feature for your internal domains. Follow straightforward steps to activate or deactivate autorenewal, ensuring seamless renewal of domain validity.
+tags: domain dns internal-domain automatic-renewal autorenew
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Autorenew is a feature that allows you, on a yearly basis, to automatically renew the validity period of an internal domain registered with Scaleway Domains and DNS.
+
+
+
+- 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
+- An internal domain registered with [Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/)
+
+## How to activate autorenew
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. Your internal domains display.
+2. Click the domain you want to configure. The domain's **Overview** tab displays.
+3. Click **Activate** under **Autorenew** in the domain information section. A pop-up displays prompting you to confirm.
+4. Click **Activate autorenew** to confirm.
+
+You have activated autorenew for your internal domain.
+
+## How to deactivate autorenew
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. Your internal domains display.
+2. Click the domain you want to configure. The domain's **Overview** tab displays.
+3. Click **Deactivate** under **Autorenew** in the domain information section. A pop-up displays prompting you to confirm.
+4. Click **Deactivate autorenew** to confirm.
+
+You have deactivated autorenew for your domain name.
+
+
diff --git a/pages/domains-and-dns/how-to/configure-dns-zones.mdx b/pages/domains-and-dns/how-to/configure-dns-zones.mdx
new file mode 100644
index 0000000000..4dbe58c770
--- /dev/null
+++ b/pages/domains-and-dns/how-to/configure-dns-zones.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: How to configure DNS zones
+ description: Discover how to effectively configure DNS zones using Scaleway's Domains and DNS service. Learn to add, edit, and delete DNS zones to manage your domain's configurations with ease and precision.
+content:
+ h1: How to configure DNS zones
+ paragraph: Discover how to effectively configure DNS zones using Scaleway's Domains and DNS service. Learn to add, edit, and delete DNS zones to manage your domain's configurations with ease and precision.
+tags: domain dns zone dns-zone
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+A [DNS zone](/domains-and-dns/concepts/#dns-zone) is a distinct part of the [domain namespace](/domains-and-dns/concepts/#dns-namespace) that allows granular control of DNS components.
+
+It contains configuration stored in multiple [DNS records](/domains-and-dns/concepts/#dns-record). Each record consists at minimum of a type, a time to live (TTL), and a value. For example, type A records contain information to resolve a domain name to its associated IP address.
+
+Each **Zone Name** created translates into a [**Domain Name**](/domains-and-dns/concepts/#domain-name). For example, the zone `myzone` in the domain `example.com` becomes `myzone.example.com`. This works also on multiple levels, meaning that the zone `myzone.subdomain` becomes the domain name `myzone.subdomain.example.com`.
+
+
+
+- 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
+- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway DNS
+
+## How to add a new DNS zone
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain for which you want to add a DNS zone. The domain's **Overview** tab displays.
+3. Click the **DNS Zones** tab. A list of DNS zones you have configured within the selected domain displays.
+
+ The **Root zone** is always available, by default. This zone is directly associated with the domain name and cannot be deleted. It will only be removed from the DNS when its associated domain name is deleted.
+
+4. Click **+ Add zone** to create a new DNS zone. A pop-up appears prompting you to enter a zone name.
+5. Enter a name for the new zone, check the estimated cost, and click **Add zone**.
+
+
+## How to manage DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain for which you want to manage DNS records. The domain's **Overview** tab displays.
+3. Click the **DNS Zones** tab. A list of DNS zones you have configured within the selected domain displays.
+4. Click next to the DNS zone of your choice, then **Records** to manage the zone's [DNS records](/domains-and-dns/reference-content/understanding-dns-records/).
+5. Click **+ Add records** to add records.
+6. Select the desired [record type](/domains-and-dns/reference-content/understanding-dns-records/) in the drop-down, and fill out the required information.
+7. Click **Add records** to confirm.
+
+## How to edit an existing DNS zone name
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain for which you want to edit a DNS zone. The domain's **Overview** tab displays.
+3. Click the **DNS Zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click , then **Edit name** to edit a zone's name.
+
+5. Enter a new name in the pop-up, then click **Edit Name** to confirm.
+
+
+## How to delete an existing DNS zone
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain for which you want to delete a DNS zone. The domain's **Overview** tab displays.
+3. Click the **DNS Zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click , then click **Delete**.
+5. Type **DELETE** in the pop-up, and click **Delete zone** to confirm the action.
+
+
diff --git a/pages/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx b/pages/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx
new file mode 100644
index 0000000000..ef79108b91
--- /dev/null
+++ b/pages/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx
@@ -0,0 +1,45 @@
+---
+meta:
+ title: How to configure DNSSEC for an internal domain name
+ description: Learn how to configure DNSSEC for your internal domains using Scaleway's Domains and DNS service. Enable, edit, or deactivate DNSSEC to enhance security and authentication for your domains.
+content:
+ h1: How to configure DNSSEC for an internal domain name
+ paragraph: Learn how to configure DNSSEC for your internal domains using Scaleway's Domains and DNS service. Enable, edit, or deactivate DNSSEC to enhance security and authentication for your domains.
+tags: domain dns dnssec internal-domain
+dates:
+ validation: 2025-01-20
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+DNSSEC uses digital signatures based on public key cryptography to strengthen DNS authentication. You can enable or disable DNSSEC for each of your internal domain names.
+
+This page shows you how to enable DNSSEC for your Domains and DNS internal domains only. You can also [enable DNSSEC using the API](https://www.scaleway.com/en/developers/api/domains-and-dns/registrar-api/#path-domains-update-domain-dnssec).
+
+
+
+- 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
+- An internal domain name managed with [Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/)
+
+## How to activate DNSSEC
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays with a list of your domains.
+2. Click the **Internal domains** tab. The list of your internal domains displays.
+3. Click the domain name you want to configure.
+4. Click **Activate** under **DNSSEC** in the domain information section.
+
+
+DNSSEC will be active in a matter of minutes.
+
+## How to edit or deactivate DNSSEC
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays with a list of your domains.
+2. Click the **Internal domains** tab. The list of your internal domains displays.
+3. Click the domain name you want to configure.
+4. Click **Deactivate** under **DNSSEC** in the domain information section.
+
+DNSSEC will be deactivated in a matter of minutes.
+
+
diff --git a/pages/domains-and-dns/how-to/delete-external-domain.mdx b/pages/domains-and-dns/how-to/delete-external-domain.mdx
new file mode 100644
index 0000000000..4c4428a71b
--- /dev/null
+++ b/pages/domains-and-dns/how-to/delete-external-domain.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to delete an external domain from Scaleway Domains and DNS
+ description: Discover how to securely delete an external domain from Scaleway's Domains and DNS service. Follow these steps to terminate domain management, ensuring irreversible deletion and removing associated DNS zones.
+content:
+ h1: How to delete an external domain from Scaleway Domains and DNS
+ paragraph: Discover how to securely delete an external domain from Scaleway's Domains and DNS service. Follow these steps to terminate domain management, ensuring irreversible deletion and removing associated DNS zones.
+tags: domain dns external-domain
+dates:
+ validation: 2024-11-27
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+
+
+- 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
+- [Added your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays.
+2. Click the **External domains** tab, and click the domain you want to delete.
+3. Click **Terminate management** in the **Terminate domain management** section. A pop-up displays.
+4. Type **DELETE** to confirm the deletion of the domain, then click **Terminate domain management**.
+
+ This will permanently delete your external domain and its related zones from Scaleway Domains and DNS. This action is irreversible and your domain name may become unresolvable.
+
+
+
+ You can also delete your domain from the list of domains by clicking , then **Delete**.
+
+
+
diff --git a/pages/domains-and-dns/how-to/index.mdx b/pages/domains-and-dns/how-to/index.mdx
new file mode 100644
index 0000000000..b1db063366
--- /dev/null
+++ b/pages/domains-and-dns/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Domains and DNS - How Tos
+ description: Domains and DNS How Tos
+content:
+ h1: Domains and DNS - How Tos
+ paragraph: Domains and DNS How Tos
+---
diff --git a/pages/domains-and-dns/how-to/manage-dns-records.mdx b/pages/domains-and-dns/how-to/manage-dns-records.mdx
new file mode 100644
index 0000000000..e8ef7575e2
--- /dev/null
+++ b/pages/domains-and-dns/how-to/manage-dns-records.mdx
@@ -0,0 +1,130 @@
+---
+meta:
+ title: How to manage DNS records
+ description: Learn how to manage DNS records effectively with Scaleway Domains and DNS. Discover how to add, edit, and delete DNS records, along with advanced configurations like dynamic records for traffic management and Geo IP for optimizing user experience based on location.
+content:
+ h1: How to manage DNS records
+ paragraph: Learn how to manage DNS records effectively with Scaleway Domains and DNS. Discover how to add, edit, and delete DNS records, along with advanced configurations like dynamic records for traffic management and Geo IP for optimizing user experience based on location.
+tags: txt-record mx-record dns-record dns domain records
+dates:
+ validation: 2024-10-29
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+
+
+- 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
+- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS
+
+## How to add DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+2. Click the domain you want to manage. The domain's **Overview** page displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click the DNS zone you want to add a record in.
+5. Click **+ Add records**. A pop-up displays.
+6. Fill in the required information for the record.
+7. Click **Add records** to confirm.
+
+## How to edit DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+2. Click the domain you want to manage. The domain's **Overview** page displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click the DNS zone you want to edit.
+5. Click the icon next to the record you want to edit. A pop-up displays.
+6. Fill in the required information.
+7. Click **Edit record**.
+
+## How to delete DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+2. Click the domain you want to manage. The domain's **Overview** page displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click the DNS zone containing the record you want to delete.
+5. Click the icon next to the record you want to delete.
+6. Type **DELETE** to confirm when prompted, then click **Delete record**.
+
+## How to configure dynamic records
+
+Scaleway Domains and DNS provides advanced features for traffic management using your DNS zone. It allows you to redirect users based on their geolocation, the load on your different servers, and more.
+
+### Weight Records
+
+You provide a list of IPs with their corresponding “weights”. These weights are used to proportionally direct requests to each IP. Depending on the weight of a record, more or fewer requests are answered with its related IP compared to the others in the list.
+
+**Example**
+: Your website runs on a large server and has a smaller companion to provide more resources. You can configure the list so that DNS will answer with the IP address of the main server 90% of the time, and with the IP address of the secondary server 10% of the time. With a list of coupled IP/weights, depending on the "weight", IPs with heavier weights will answer more requests than those with lighter weights.
+
+**Limitations**
+: This record type is only available for A and AAAA records.
+
+### Geo IP Records
+
+The Geo IP feature provides DNS resolution, based on the user's geographical location. You can define a default IP which resolves if no Geo IP rule matches, and specify IPs for each geographical zone.
+
+**Example**
+: Your website has two servers: one in Europe and one in Asia, and its visitor base spans both continents. DNS replies to requests from visitors in Asia with the IP address of the server located in Asia, and to requests from visitors in Europe with the IP address of the server located in Europe. This reduces network latency and makes your website faster.
+
+**Limitations**
+: This record type is only available for A, AAAA, CNAME and ALIAS records.
+
+
+### Health check records
+
+The DNS service performs health checks as follows:
+
+ - You define a list of IPs (a pool) reachable via a single URL.
+ - The servers in the IP pool are contacted by their IP, and an HTTP GET request is sent to each, with the URL as a parameter.
+ - Each IP passes the health check if it sends a response which includes a predefined string.
+
+Having established the 'healthy' IPs, the DNS service responds to requests using one of the following strategies:
+
+ - Random: It sends a random healthy IP.
+ - Hashed: It uses the caller's IP address to send a specific random healthy IP, which will always be returned for this caller IP.
+ - All: It sends all healthy IPs in a random order.
+
+If none of the addresses in the IP list has passed the health check, it sends a fallback IP.
+
+
+ The following table shows more explicitly how the results of the IP health check determine the single IP address that the DNS service will send:
+
+ | IP list health check | Fallback IP check | Response |
+ |:-------------------:|:------------------:|:-----------------------------------------:|
+ | All or some IPs OK | n/a | A healthy IP from the list |
+ | No IPs OK | OK | The fallback IP |
+ | No IPs OK | not OK | An IP from the IP list OR the fallback IP |
+
+
+
+The following values should be provided to use the DNS health check service:
+
+ - Fallback IP: The fallback IP address to return if all health checks fail.
+ - URL: A (common) URL to use in GET (e.g. `http://example.com/healthcheck`).
+ - Data: The string to look for in the GET result (e.g. IamHealthy).
+ - Response strategy: The strategy to use. It can either be random or hashed.
+ - Random: A random IP from the pool of healthy IPs is returned upon each request.
+ - Hashed: The same (random) IP, from the pool of healthy IPs is always returned to the same caller IP.
+ - All: All IPs from the pool of healthy IPs are returned in a random order.
+ - IPs: A list of IPs to test during the check (e.g. 1.2.3.4, 2.3.4.5).
+
+**Example**
+: A website relies on different servers and maintenance is planned on one of them. To plan the maintenance, an endpoint is configured to fail over one hour before and during the planned period, so requests will not be forwarded to the impacted server.
+
+**Limitations**
+: This record type is only available for A and AAAA records.
+
+### Views records
+
+The answer to a DNS request is based on the client's (resolver's) subnet.
+
+**Example**
+: A website has a public version with a public IP. A specific version for employees exists on an intranet. To use the same domain name for both versions, the Intranet IP will be answered if the DNS resolution is requested from the Intranet subnet, while for any other requests the DNS request will resolve to the public IP address.
+
+**Limitations**
+: This record type is only available for A, AAAA, CNAME and ALIAS records.
+
+
diff --git a/pages/domains-and-dns/how-to/manage-external-domain.mdx b/pages/domains-and-dns/how-to/manage-external-domain.mdx
new file mode 100644
index 0000000000..072141aad8
--- /dev/null
+++ b/pages/domains-and-dns/how-to/manage-external-domain.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to manage external domains
+ description: Discover how to efficiently manage your external domains from the Scaleway console. Learn how to access domain information, verify domain status, manage name servers, and delete domains when necessary, all through the Domains and DNS dashboard.
+content:
+ h1: How to manage external domains
+ paragraph: Discover how to efficiently manage your external domains from the Scaleway console. Learn how to access domain information, verify domain status, manage name servers, and delete domains when necessary, all through the Domains and DNS dashboard.
+tags: external-domain dns domain
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Once your external domains have been created and validated, you can manage them from the Scaleway console.
+
+
+
+- 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
+- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+2. Click the **External domains** tab.
+3. Click next to the domain you want to manage.
+
+
+ A **green** dot displays next to your domain name once it is validated.
+
+
+The domain's **Overview** tab displays. This gives you an overview of the status of your domain, as well as a list of all name servers associated with it. At the bottom of the page, you can also delete your domain from Scaleway Domains and DNS.
+
+
+
+
diff --git a/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx b/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx
new file mode 100644
index 0000000000..bda4cf16d3
--- /dev/null
+++ b/pages/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to manage name servers for an internal domain
+ description: Learn how to effectively manage name servers for your internal domains. This guide covers editing name server information, adding and removing name servers, and validating configurations through the intuitive Domains and DNS dashboard.
+content:
+ h1: How to manage name servers for an internal domain
+ paragraph: Learn how to effectively manage name servers for your internal domains. This guide covers editing name server information, adding and removing name servers, and validating configurations through the intuitive Domains and DNS dashboard.
+tags: nameserver internal-domain domain dns
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Scaleway Domains and DNS provides a managed DNS solution by providing default name servers for each domain name. If you want to use your own DNS servers, you can edit the name servers associated with your domain name.
+
+
+
+- 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
+- A domain name registered with Scaleway Domains and DNS
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain name you want to configure. The **Overview** tab for your domain displays.
+3. Click **Edit** in the **Name servers** section.
+4. Edit the name server information. For each name server, you can provide:
+ * A name server
+ * An IPv6 address
+ * An IPv4 address
+
+ IP addresses are only required if you want to create **glue records**. A glue record provides the IP address of a name server so that DNS can resolve the domain name if the domain uses name servers hosted under that same domain name.
+
+5. Optionally, click **Add name server** to add more name servers and enter your server's information.
+
+ We recommend you configure a minimum of two and a maximum of seven DNS servers for each domain name.
+
+6. Click the icon to delete a name server.
+7. Click the icon to validate your configuration.
+8. Click the icon to cancel all the changes you have made.
+
+
diff --git a/pages/domains-and-dns/how-to/register-internal-domain.mdx b/pages/domains-and-dns/how-to/register-internal-domain.mdx
new file mode 100644
index 0000000000..566b3a0656
--- /dev/null
+++ b/pages/domains-and-dns/how-to/register-internal-domain.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: How to register an internal domain name
+ description: Efficiently register an internal domain using Scaleway Domains and DNS. This guide walks you through the process of checking domain availability, configuring contacts, selecting registration periods, and completing your order securely via the Scaleway console.
+content:
+ h1: How to register an internal domain name
+ paragraph: Efficiently register an internal domain using Scaleway Domains and DNS. This guide walks you through the process of checking domain availability, configuring contacts, selecting registration periods, and completing your order securely via the Scaleway console.
+tags: internal-domain domain dns
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Domains and DNS allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. Domains and DNS provide support for queries via both IPv4 and IPv6.
+
+
+
+- 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
+- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click **+ Search domain name**.
+3. Enter the domain name you wish to register in the search bar.
+4. Click the search icon to check the domain availability. A selection of available domain names appears.
+5. Tick the box next to the domain name you want to register, then click **Select and configure contacts**.
+6. Enter the required information, then click **Add new contact**.
+7. Select your domain contact information from the drop-down list and click **Validate and continue**. Your order summary displays.
+8. Choose the registration period.
+9. Tick the box to confirm you understand that you will be debited the price that displays.
+10. Click **Register domain** to confirm your order and to register the domain name.
+
+
+ * Make sure to check your domain name for any spelling mistakes before you place the order.
+ * You cannot change the domain name once the registration is complete and the fees will still apply. You can of course register another domain with the correctly spelled name.
+ * Internal domains are billed immediately upon registration.
+
+
+
diff --git a/pages/domains-and-dns/how-to/renew-domain.mdx b/pages/domains-and-dns/how-to/renew-domain.mdx
new file mode 100644
index 0000000000..d947ac7bc0
--- /dev/null
+++ b/pages/domains-and-dns/how-to/renew-domain.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to renew a domain name
+ description: Learn how to effortlessly renew your domain. This guide provides step-by-step instructions for accessing your domain details, selecting your preferred renewal period, and confirming your renewal securely through the Scaleway console.
+content:
+ h1: How to renew a domain name
+ paragraph: Learn how to effortlessly renew your domain. This guide provides step-by-step instructions for accessing your domain details, selecting your preferred renewal period, and confirming your renewal securely through the Scaleway console.
+tags: renew domain dns
+dates:
+ validation: 2024-09-30
+ posted: 2023-09-19
+categories:
+ - network
+---
+
+This page shows you how to renew your domain using Scaleway Domains and DNS.
+
+
+
+- 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
+- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account
+- Registered one or more domain names with Scaleway Domains and DNS
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The list of your domains displays.
+2. Click the domain you want to renew. Your domain's overview page displays.
+3. Click **Renew** under **Expiration date**. A pop-up displays.
+4. Choose your registration period in the drop-down list.
+
+
+ You can renew your domain for up to 9 years with a maximum domain name registration period of 10 years.
+
+5. Tick the box to confirm you understand your domain will be renewed and that you will be debited the displayed price.
+
+
+6. Click **Renew this domain**. Your domain displays in the **Operations** tab until the renewal is complete.
+
+
+ You can [configure the autorenew feature](/domains-and-dns/how-to/configure-autorenew/) if you want to avoid renewing your domain manually.
+
+
+
diff --git a/pages/domains-and-dns/how-to/test-dns-zones-with-dig.mdx b/pages/domains-and-dns/how-to/test-dns-zones-with-dig.mdx
new file mode 100644
index 0000000000..64956df527
--- /dev/null
+++ b/pages/domains-and-dns/how-to/test-dns-zones-with-dig.mdx
@@ -0,0 +1,80 @@
+---
+meta:
+ title: How to test your DNS zones using dig
+ description: Learn to test DNS zones using dig with our straightforward guide. Whether troubleshooting DNS issues or verifying configurations, this tutorial covers everything you need to know to leverage dig effectively.
+content:
+ h1: How to test your DNS zones using dig
+ paragraph: Learn to test DNS zones using dig with our straightforward guide. Whether troubleshooting DNS issues or verifying configurations, this tutorial covers everything you need to know to leverage dig effectively.
+tags: dns-zone dig records configuration
+dates:
+ validation: 2024-11-18
+ posted: 2024-05-15
+categories:
+ - network
+---
+
+`Dig` or `domain information groper` is a command line tool used to query domain information on [DNS](/domains-and-dns/concepts/#dns) servers. You can use it to troubleshoot DNS issues.
+
+`Dig` is installed by default on most Unix operating systems. You will however need to [install it if you are using Windows](https://www.isc.org/download/).
+
+This page shows you how to use the `dig` command to perform some common DNS tests. You do not need to have registered domains with Scaleway Domains and DNS to use this documentation page, but if you are using Scaleway Domains and DNS, refer to the **Before you start** section.
+
+
+
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - [Added](/domains-and-dns/how-to/add-external-domain/) **external domains** with Scaleway Domains and DNS or not
+ - [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission)
+ - Installed `dig`
+
+
+## How to perform a basic DNS query
+
+
+Open a terminal and paste the following command to get a general overview of your domain's DNS configuration.
+
+```
+dig
+```
+
+This command could be useful if you want to verify the DNS configuration of a website before migrating it to a new server, for example. By running `dig` without any additional arguments, you can see if the domain's DNS records are resolving correctly and if you need to make any changes before the migration.
+
+
+---
+
+## How to query a specific record type
+
+
+The following command allows you to retrieve your domain's [DNAME](/domains-and-dns/reference-content/understanding-dns-records/#dname-record) record. This command allows you to focus on particular aspects of your domain's DNS configuration.
+
+```
+dig DNAME
+```
+
+This command could also be useful if you are troubleshooting email delivery issues for a domain, for example. By querying the domain's MX record with `dig`, you can verify that the mail server listed is correct and accessible. If there is an issue with email delivery, checking your domain's MX record can help pinpoint potential misconfigurations.
+
+
+---
+
+## How to perform a reverse DNS lookup
+
+The following command allows you to verify the authenticity of an IP address, identify its associated domain name, and check for misconfigurations or suspicious activity.
+
+```
+dig -x
+```
+
+This command could be useful if you notice unusual traffic originating from an IP address in your server logs, for example. Performing a reverse DNS lookup with dig can reveal the domain name associated with that IP address. This information can help you determine if the traffic is legitimate or if further investigation is needed to address potential security threats.
+
+
+---
+
+## How to query a specific DNS server
+
+The following command allows you to query a specific DNS server. Querying a specific DNS server is useful for troubleshooting DNS issues, checking DNS propagation, and verifying the accuracy of DNS configurations. It allows you to test how different DNS servers resolve domain names, ensuring your DNS records are properly propagated and resolving as intended.
+
+```
+dig @
+```
+
+You do not need to have a domain with the provider of the DNS server you are querying for your dig command to work. You can query any DNS server for any domain name to check how that specific DNS server resolves the domain. This is useful for verifying DNS resolution and propagation from different DNS servers regardless of where the domain is registered.
+Make sure that you replace `<` with the IP of the desired DNS server, and `` with your actual domain.
\ No newline at end of file
diff --git a/pages/domains-and-dns/how-to/trade-domain.mdx b/pages/domains-and-dns/how-to/trade-domain.mdx
new file mode 100644
index 0000000000..7ecda4b52f
--- /dev/null
+++ b/pages/domains-and-dns/how-to/trade-domain.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: How to use the Domains and DNS trade feature
+ description: Discover how to edit registrant contact details for your internal domain using Scaleway's Domains and DNS trade feature.
+content:
+ h1: How to use the Domains and DNS trade feature
+ paragraph: Discover how to edit registrant contact details for your internal domain using Scaleway's Domains and DNS trade feature.
+tags: domain trade edit-registrant contact-information
+dates:
+ validation: 2024-09-17
+ posted: 2024-09-17
+categories:
+ - network
+---
+
+Scaleway's Domains and DNS [trade](/domains-and-dns/concepts/#trade) feature allows you to edit your contact information for an internal domain, and update your data from the Scaleway console.
+
+
+
+
+
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - Entered your credit card information on your account
+ - [Registered](/domains-and-dns/how-to/register-internal-domain/) at least one **internal domain** with Scaleway Domains and DNS
+ - [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission)
+
+
+ The Domains and DNS trade feature allows you to **only edit the registrant contact information of an internal domain (to correct typing errors, for example), or information such as a company name, or a SIRET number**.
+
+
+## How to use the trade feature
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard with the list of your domains displays.
+2. Click the internal domain you want to edit. The domain's **Overview** tab displays.
+3. Click the **Contacts** tab. Your domain's registrant, technical, and administrative contacts display.
+4. Click **Trade domain**.
+5. Edit your information as you wish.
+6. Tick the box to confirm that you understand you will be debited the price displayed for the trade.
+7. Click **Initiate trade**.
+8. You will receive an email with instructions to validate or refuse the edits you have made.
+
diff --git a/pages/domains-and-dns/how-to/transfer-external-domain.mdx b/pages/domains-and-dns/how-to/transfer-external-domain.mdx
new file mode 100644
index 0000000000..22e723f587
--- /dev/null
+++ b/pages/domains-and-dns/how-to/transfer-external-domain.mdx
@@ -0,0 +1,67 @@
+---
+meta:
+ title: How to transfer an external domain
+ description: Learn how to transfer an external domain to Scaleway with our comprehensive guide. Discover step-by-step instructions, from verifying domain availability to initiating the transfer, and managing authorizations.
+content:
+ h1: How to transfer an external domain
+ paragraph: Learn how to transfer an external domain to Scaleway with our comprehensive guide. Discover step-by-step instructions, from verifying domain availability to initiating the transfer, and managing authorizations.
+tags: external-domain domain dns
+dates:
+ validation: 2024-09-30
+ posted: 2022-03-01
+categories:
+ - network
+---
+
+
+
+- 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
+- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account
+- External domains to transfer
+- Requested the authorization code to transfer your domain from your registrar
+
+## How to transfer .fr and .be domains
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click ** + Register new domain**.
+
+3. Enter the domain name you wish to transfer in the box and click the search icon to verify that the domain is available. A selection of available domains displays.
+4. Click **Transfer** next to the domain you wish to transfer. A screen displays to help you prepare your transfer.
+
+ - You must have administrative rights to manage and unlock your domain for transfers.
+ - You must have the authorization code to initiate the transfer.
+ - Your domain must have been registered at least 60 days ago or renewed for more than 45 days.
+ - Your domain expires in at least 2 weeks.
+
+5. Click **Initiate transfer** once you are ready to proceed.
+6. Enter your authorization code and click **Validate**. Your order summary displays.
+
+ You can find your authorization code under your domain information or by asking for it directly to your current registrar.
+
+7. Tick the box confirming you accept to be debited.
+8. Click **Transfer domain**. Once your domain transfer is approved, your domain will display in your **Internal domains** tab.
+
+## How to transfer domains with other extensions
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click ** + Register new domain**:
+
+3. Enter the domain you wish to transfer in the box and click the search icon to verify that the domain is available. A selection of available domains displays.
+4. Click **Transfer** next to the domain name you wish to transfer. A screen displays to help you prepare your transfer.
+
+ - You must have administrative rights to manage and unlock your domain for transfers.
+ - You must have the authorization code to initiate the transfer.
+ - Your domain must have been registered at least 60 days ago or renewed for more than 45 days.
+ - Your domain must not expire for a minimum of 2 weeks.
+
+5. Click **Initiate transfer** once you are ready to proceed.
+6. Enter your authorization code and click **Configure registrant contact**.
+
+ You can find your authorization code under your domain information or by asking your current registrar for it directly.
+
+7. Select an existing registrant contact or create a new one and click **Validate**. Your order summary displays.
+8. Tick the box confirming you accept to be debited.
+9. Click **Transfer domain**. Once your domain transfer is approved, your domain will display in your **Internal domains** tab.
+
+
diff --git a/pages/domains-and-dns/how-to/unlock-internal-domain.mdx b/pages/domains-and-dns/how-to/unlock-internal-domain.mdx
new file mode 100644
index 0000000000..95ae3dab9d
--- /dev/null
+++ b/pages/domains-and-dns/how-to/unlock-internal-domain.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: How to unlock an internal domain name
+ description: Discover how to unlock internal domain names effortlessly. Follow our detailed steps to manage domain security and facilitate transfers.
+content:
+ h1: How to unlock an internal domain name
+ paragraph: Discover how to unlock internal domain names effortlessly. Follow our detailed steps to manage domain security and facilitate transfers.
+tags: internal-domain-name domain-name domain dns
+dates:
+ validation: 2024-08-19
+ posted: 2022-10-31
+categories:
+ - network
+---
+
+Domain names are locked by default to avoid any unsolicited outgoing transfer. If you want to transfer your domain name to another registrar, you can unlock it from your Scaleway console.
+
+
+ You cannot unlock internal domain names for a period of 60 days after creating them.
+
+
+
+
+- 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
+- A domain name registered with Scaleway Domains and DNS
+
+## How to unlock a domain name
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain name you want to unlock. The domain's **Overview** tab displays.
+3. Click **Unlock** under **Transfer** in the **Domain Information** section. A pop-up displays.
+
+4. Click **Unlock** to confirm.
+
+The operation might take a few minutes to complete.
+
+
+## How to lock a domain name
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays.
+2. Click the domain name you want to lock. The domain's **Overview** tab displays.
+3. Click **Lock** under **Transfer** in the **Domain Information** section. A pop-up displays.
+4. Click **Lock** to confirm.
+
+The operation might take a few minutes to complete.
diff --git a/pages/domains-and-dns/index.mdx b/pages/domains-and-dns/index.mdx
new file mode 100644
index 0000000000..f36ce9a2a9
--- /dev/null
+++ b/pages/domains-and-dns/index.mdx
@@ -0,0 +1,61 @@
+---
+meta:
+ title: Domains and DNS Documentation
+ description: Explore Scaleway Domains and DNS with quickstart guides, how-tos, tutorials, and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/domains-and-dns/quickstart.mdx b/pages/domains-and-dns/quickstart.mdx
new file mode 100644
index 0000000000..7ebc977fff
--- /dev/null
+++ b/pages/domains-and-dns/quickstart.mdx
@@ -0,0 +1,109 @@
+---
+meta:
+ title: Domains and DNS - Quickstart
+ description: Discover how to effectively manage your domains and DNS zones using Scaleway's intuitive platform. From registering both internal and external domains to configuring DNS zones and adding DNS records, streamline your network management tasks.
+content:
+ h1: Domains and DNS - Quickstart
+ paragraph: Discover how to effectively manage your domains and DNS zones using Scaleway's intuitive platform. From registering both internal and external domains to configuring DNS zones and adding DNS records, streamline your network management tasks.
+tags: domains dns internal-domain external-domain
+dates:
+ validation: 2024-11-27
+ posted: 2021-05-26
+categories:
+ - network
+---
+
+[Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/) allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones.
+
+
+
+- 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
+
+## How to register an internal domain
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays.
+2. Click **+ Search domain name**.
+3. Enter the domain name you wish to register in the search bar and hit `Enter` to verify that the domain is available. A list of domain names displays with their availability status.
+4. Tick the box next to the domain you want to register. Then click **Select and configure contacts**.
+5. Fill in the **Contact information**, **Address**, and **Additional information** sections, then click **Add new contact**.
+6. Select the registrant, administrative, and technical contact for your domain from the drop-down. Then click **Validate and continue**. Your order summary displays.
+7. Choose a registration period for your domain.
+8. Check the box to confirm you understand that you will be billed the price that displays.
+9. Click **Register domain** to confirm your order.
+
+
+ * Make sure to check your domain name for any spelling mistakes before you place the order.
+ * You cannot change the domain name once the registration is complete and the fees will still apply. You can of course register another domain with the correctly spelled name.
+ * Internal domains are billed immediately upon registration.
+
+
+## How to register an external domain
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays.
+2. Click the **External domains** tab, then click **+ Manage new domain**.
+3. Enter the external domain name in the search bar and hit `Enter` to check if the domain exists.
+4. Enter the number of million queries you need. The estimated cost for the domain name displays.
+5. Click **Manage as external**. The instructions to set up your external domain display.
+6. Copy the token displayed and [create](/domains-and-dns/how-to/manage-dns-records/#how-to-add-dns-records) a `TXT` record with the name `_scaleway-challenge` within your current DNS zone as instructed.
+
+ The token's presence will be checked regularly. If it has not been set within 48 hours, the external domain will be deleted from the service.
+
+7. Click **Back to my external domains** once you have set up the record in your current DNS zone. The list of your external domains displays.
+
+The status of any ongoing DNS operations is visible through a blue dot on the left side of the domain.
+Once the record has been validated, the dot turns green, and you will receive an email with further instructions on how to update your domain's DNS servers.
+
+Update the name server information at your current registrar once your domain name is validated, in order to link your existing domain name with your Scaleway Domains DNS zone.
+
+ Scaleway's DNS servers are:
+ * ns0.dom.scw.cloud
+ * ns1.dom.scw.cloud
+
+
+You can verify whether the association of your domain has been completed by checking the **Name servers** section, in the **Domain information** page.
+
+
+ If the entire process is not completed after 14 days, the domains are deleted from the DNS and you will have to start over. Emails reminding you to complete the process are sent on days 7 and 13.
+
+
+
+## How to add a new DNS zone
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays.
+2. Click the domain for which you want to add a DNS zone. The domain's **Overview** tab displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+
+ The **Root zone** is always available, by default. This zone is directly associated with the domain name and cannot be deleted. It will only be removed from the DNS when its associated domain name is deleted.
+
+4. Click **+ Add zone** to create a new DNS zone. A pop-up displays prompting you to enter a name for the new DNS zone.
+5. Enter a name, check the estimated cost, and click **Add zone**.
+
+## How to delete an existing DNS zone
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays.
+2. Click the domain for which you want to delete a DNS zone. The domain's **Overview** tab displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click next to the DNS zone you want to delete, then click **Delete**.
+5. Type **DELETE** and click **Delete zone** to confirm the action.
+
+
+## How to add DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS zone screen displays.
+2. Click the domain you want to manage. The domain's **Overview** tab displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click the DNS zone you want to add a record in.
+5. Click **+ Add records**. A pop-up displays.
+6. Fill in the required information for the record.
+7. Click **Add records** to confirm.
+
+## How to delete DNS records
+
+1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS zone screen displays.
+2. Click the domain you want to manage. The domain's **Overview** tab displays.
+3. Click the **DNS zones** tab. A list of the DNS zones you have configured within the selected domain displays.
+4. Click the DNS zone containing the record you want to delete.
+5. Click next to the record. A pop-up displays.
+6. Type **DELETE** to confirm.
+7. Click **Delete record** to delete the record from the zone.
\ No newline at end of file
diff --git a/pages/domains-and-dns/reference-content/index.mdx b/pages/domains-and-dns/reference-content/index.mdx
new file mode 100644
index 0000000000..e1f7a874e8
--- /dev/null
+++ b/pages/domains-and-dns/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Domains and DNS - Additional content
+ description: Domains and DNS additional content
+content:
+ h1: Domains and DNS - Additional content
+ paragraph: Domains and DNS additional content
+---
\ No newline at end of file
diff --git a/pages/domains-and-dns/reference-content/understanding-dns-records.mdx b/pages/domains-and-dns/reference-content/understanding-dns-records.mdx
new file mode 100644
index 0000000000..e0145c914a
--- /dev/null
+++ b/pages/domains-and-dns/reference-content/understanding-dns-records.mdx
@@ -0,0 +1,180 @@
+---
+meta:
+ title: Understanding DNS records
+ description: Learn about various record types and their applications, ensuring effective management and configuration of your domain's DNS settings.
+content:
+ h1: Understanding DNS records
+ paragraph: Learn about various record types and their applications, ensuring effective management and configuration of your domain's DNS settings.
+tags: domains dns record
+dates:
+ validation: 2024-09-04
+ posted: 2023-08-18
+categories:
+ - network
+---
+
+This page provides information about the different DNS record types available with Domains and DNS and how to use them.
+
+Information in DNS zones is categorized and organized through a list of [DNS record](/domains-and-dns/concepts/#dns-record) types, called [resource records](/domains-and-dns/concepts/#resource-records) (RRs).
+
+Each of these records has a type, an expiration time (Time to Live - TTL) and a name. Certain types of records also have type-specific data.
+
+
+### A record
+
+**A record** stands for **Address record**. It is mostly used to map domain names to the IPv4 address of a specific server. In other words, it allows to connect a domain name to the numerical IP address of a server where the website or online service is hosted.
+
+An A record ensures that when you type a website's name into your browser, your computer knows where to find that website on the internet.
+
+### AAAA record
+
+Just like an A record connects a domain to an IPv4 address, an **AAAA record** does the same thing for the newer IPv6 addresses. It allows devices to locate and communicate with websites and services using the IPv6 protocol.
+
+### ALIAS record
+
+An ALIAS record works exactly like a [CNAME record](#cname-record)
+
+An ALIAS record could be useful if you want your domain name (not its subdomains) to point to a hostname.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### CAA record
+
+**CAA record** stands for **Certification Authority Authorization record**. It allows domain owners to specify which certificate authorities (CAs) are authorized to issue [SSL/TLS certificates](/domains-and-dns/concepts/#ssltls-certificates) for their domain.
+
+This adds an extra layer of security, as it reduces the risk of unauthorized or fraudulent SSL/TLS certificates being issued by untrustworthy certificate authorities.
+
+The CAA record provided with Domains and DNS includes the following components:
+
+- **Tags**: Tags indicate the type of property being defined.
+
+ * **issue**: This tag specifies the certificate authorities that are allowed to issue certificates for the domain.
+
+ * **issuewild**: This tag specifies which certificate authorities are allowed to issue wildcard certificates for the domain.
+
+ * **iodef**: This tag specifies the email address to which CAA-related issue reports should be sent.
+
+- **Target Auth**: This value specifies the domain names of the allowed certificate authorities.
+
+- **Flags**: Flags are a single-byte value that indicates the CAA record's properties.
+
+ * **0 or None**: This flag means that any unrecognized tags in your record will be ignored, and other requests will be processed.
+
+ * **128 or Issuer critical**: This flag means that any unrecognized tags will halt the certificate issuance, assuming the issuer is compliant to standards.
+
+### CNAME record
+
+**CNAME record** stands for **Canonical name record**. It is used to point subdomains to a hostname. A CNAME record does not directly [resolve](/domains-and-dns/concepts/#domain-name-resolution) to an IP address. Instead, it refers to whether the domain is an [absolute](/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) or [relative](/domains-and-dns/concepts/#partially-qualified-domain-name-pqdn) domain.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### DNAME record
+
+**DNAME record** stands for **Delegation name record**. It is used for domain name redirection and renaming. Unlike other DNS record types that map domain names to IP addresses, a DNAME record allows you to redirect an entire domain and all of its subdomains to a different domain name.
+
+You should configure a DNAME record if you want to rename or restructure a domain while ensuring that all of its subdomains are automatically redirected to the new domain.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### MX record
+
+**MX record** stands for **Mail exchange record**. It is used to specify the mail servers responsible for receiving and handling emails for a specific domain. For example, when sending an email to an address within your domain `my@domain.com`, your email server needs to determine where to deliver the emails. Your MX record provides this information by pointing to the receiver domain's mail servers that are designated to accept incoming emails.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### NAPTR record
+
+**NAPTR record** stands for **Naming Authority Pointer record**. It provides instructions for translating a specific type of data into a different format. NAPTR records help devices and services such as Voice over Internet Protocol systems, find the appropriate servers or services to connect to. They essentially act as a guide, pointing out how to transform certain data to match what is needed for communication or service interaction.
+
+NAPTR records allow you to specify a series of transformations or replacements that need to be applied to a specific domain name before it can be used for a particular service.
+
+NAPTR records are more complex and specialized than standard DNS records. They are typically used in advanced networking scenarios, especially in the context of SIP-based VoIP services and ENUM to map telephone numbers to domain names for IP-based communication.
+
+The NAPTR record provided with Domains and DNS includes the following components:
+
+- **Order**: An integer value (0 to 65535) that determines the order in which NAPTR records should be processed. Lower values indicate higher priority.
+
+- **Preference**: An integer value (0-65535) used to prioritize NAPTR records with the same order value. Records with lower preference values are prioritized.
+
+- **Flags**: Flags provide instructions on how to interpret the subsequent fields in the record. Flags can indicate things like case-insensitivity, whether the rule should be applied to both the original and transformed names, etc.
+
+ * **The S flag**: This flag indicates that after processing this NAPTR record the visitor's system should look for an SRV record for the domain entered in the **Domain replacement** field.
+
+ * **The A flag**: This flag indicates that after processing this NAPTR record the visitor's system should look for an A record or an AAAA record for the domain entered in the **Domain replacement** field.
+
+ * **The U flag**: This flag indicates that after processing this NAPTR record the visitor's system should not look for another DNS record but instead, needs to look at the output in the **Regular expression** field.
+
+ * **The P flag**: This flag indicates that the visitor's system needs to continue according to the rules of the protocol that is entered in the **Services** field.
+
+- **Services**: String that specifies the service or protocol for which the NAPTR record is intended. Common values include `SIP+D2U` for SIP URI information and `E2U+sip` for ENUM services.
+
+- **Regular expression**: A regular expression that defines the transformation to be applied to the domain name.
+
+- **Replacement domain**: A replacement string that is used to replace the matched portion of the domain name based on the regular expression.
+
+### NS record
+
+**NS record** stands for **Name server record**. It is used to designate the authoritative name servers for a specific domain.
+
+When a DNS query is made for a domain's information (like its IP address), DNS resolvers will follow the NS records to determine which authoritative name servers to contact for that domain.
+The authoritative name servers then provide the necessary DNS information to complete the query.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### SRV record
+
+**SRV record** stands for **Service record**. It provides information about specific network services offered by a domain.
+
+It includes details like the service's protocol, port number, priority, weight, and the domain name of the server offering the service. SRV records help devices locate and connect to the right servers for specific services on the internet such as chat or phone services.
+
+
+ You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.
+
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).
+
+ For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
+
+
+### TLSA record
+
+**TLSA record** stands for **Transport Layer Security Authentication record**. It is used to associate a TLS certificate or public key with the specified domain name.
+
+TLSA records allow you to improve the security of encrypted connections by specifying how clients should verify the authenticity of the server's certificate when establishing a TLS connection.
+
+When a client connects to a server using TLS and encounters a TLSA record, it can use the information in the record to verify that the presented certificate matches the expected one. This adds an extra layer of security by making sure that encrypted connections are established with legitimate servers.
+
+### TXT record
+
+**TXT record** stand for **Text record**. It consists of plain text data, and its content can be human-readable or machine-interpretable, depending on its intended purpose.
+
+TXT records can be used for various purposes such as adding information, verification, authentication, and configuration settings to a domain.
\ No newline at end of file
diff --git a/pages/domains-and-dns/reference-content/understanding-domains-and-dns.mdx b/pages/domains-and-dns/reference-content/understanding-domains-and-dns.mdx
new file mode 100644
index 0000000000..58277e1418
--- /dev/null
+++ b/pages/domains-and-dns/reference-content/understanding-domains-and-dns.mdx
@@ -0,0 +1,72 @@
+---
+meta:
+ title: Understanding Domains and DNS
+ description: Learn about domain management, DNS zones, and the advantages of utilizing subdomains.
+content:
+ h1: Understanding Domains and DNS
+ paragraph: Learn about domain management, DNS zones, and the advantages of utilizing subdomains.
+tags: domains dns subdomain zone
+dates:
+ validation: 2024-10-29
+ posted: 2023-04-12
+categories:
+ - network
+---
+
+This page provides information about Scaleway's Domains and DNS service.
+
+## Domain and zone
+
+A domain name is an identification string that defines a realm of administrative autonomy, authority, or control within the internet. Domain names are formed by the rules and procedures of the Domain Name System (DNS). Any name registered in the DNS is a domain name.
+
+Domains are further divided into subdomains, that become DNS zones with their own set of administrators and DNS servers.
+
+The term domain is used in the business functions of the entity assigned to it and the term zone is usually used for the configuration of DNS services.
+
+## Example
+
+`domain_example.com` is the `domain` and has only one owner who can manage it.
+
+By default, the domain only has a root zone and no subdomains.
+
+The `zone` for `example.com` allows you to configure records such as:
+
+```bash
+example.com
+├── (root)
+ ├── www # www.example.com
+ ├── mail # mail.example.com
+ └── www.dev # www.dev.example.com
+```
+
+If we add a DNS zone to the subdomain `dev.example.com`, we get:
+
+```bash
+example.com
+├── (root)
+│ ├── www # www.example.com
+│ └── mail # mail.example.com
+│
+├── dev
+ └── www # www.dev.example.com
+```
+
+## Advantages of subdomains and multiple zones
+
+Multiple zones (i.e. subdomains) allow:
+
+- access delegation to zone(s) (preventing access to the root zone)
+- access (future) to features based on `templates`
+- performance tuning. For example, if you have 10,000 records, we recommend that you divide them into zones or subdomains.
+
+
+ - To be RFC compliant, each zone will automatically have name server records added.
+
+
+## Internationalized domain name
+
+An internationalized domain name (IDN) is an internet domain name that contains at least one label that is displayed in software applications. The label is in whole or in part in a language-specific script or alphabet, such as Arabic, Chinese, Cyrillic, Tamil, Hebrew, or the Latin alphabet-based characters with diacritics or ligatures, such as French. These writing systems are encoded by computers in multibyte Unicode. Internationalized domain names are stored in the Domain Name System as ASCII strings using Punycode transcription.
+
+Example: `allélua.com` converted in IDN is `xn--alllua-dva.com`.
+
+To simplify its use, the [Domains and DNS API](https://www.scaleway.com/en/developers/api/domains-and-dns/) uses `unicode` (`UTF-8`) for name and data fields.
\ No newline at end of file
diff --git a/pages/edge-services/assets/scaleway-cname-success.webp b/pages/edge-services/assets/scaleway-cname-success.webp
new file mode 100644
index 0000000000..ba6f5f4ff7
Binary files /dev/null and b/pages/edge-services/assets/scaleway-cname-success.webp differ
diff --git a/pages/edge-services/assets/scaleway-create-es-pipeline-lb.webp b/pages/edge-services/assets/scaleway-create-es-pipeline-lb.webp
new file mode 100644
index 0000000000..75d89eb2b6
Binary files /dev/null and b/pages/edge-services/assets/scaleway-create-es-pipeline-lb.webp differ
diff --git a/pages/edge-services/assets/scaleway-create-pipeline-lb.webp b/pages/edge-services/assets/scaleway-create-pipeline-lb.webp
new file mode 100644
index 0000000000..b2840e1f6b
Binary files /dev/null and b/pages/edge-services/assets/scaleway-create-pipeline-lb.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-create-pipeline-os.webp b/pages/edge-services/assets/scaleway-edge-create-pipeline-os.webp
new file mode 100644
index 0000000000..bdeb85751f
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-create-pipeline-os.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-pipelines.webp b/pages/edge-services/assets/scaleway-edge-pipelines.webp
new file mode 100644
index 0000000000..49f8cb4408
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-pipelines.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-cache.webp b/pages/edge-services/assets/scaleway-edge-services-cache.webp
new file mode 100644
index 0000000000..670b8c1bf6
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-cache.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-configure-domain.webp b/pages/edge-services/assets/scaleway-edge-services-configure-domain.webp
new file mode 100644
index 0000000000..520f1f44fb
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-configure-domain.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-customised.webp b/pages/edge-services/assets/scaleway-edge-services-customised.webp
new file mode 100644
index 0000000000..127c869f22
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-customised.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-dashboard.webp b/pages/edge-services/assets/scaleway-edge-services-dashboard.webp
new file mode 100644
index 0000000000..c2a1fb4897
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-dashboard.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-lb-dashboard.webp b/pages/edge-services/assets/scaleway-edge-services-lb-dashboard.webp
new file mode 100644
index 0000000000..659b74e395
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-lb-dashboard.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-pipeline.webp b/pages/edge-services/assets/scaleway-edge-services-pipeline.webp
new file mode 100644
index 0000000000..49ffb573d9
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-pipeline.webp differ
diff --git a/pages/edge-services/assets/scaleway-edge-services-splash.webp b/pages/edge-services/assets/scaleway-edge-services-splash.webp
new file mode 100644
index 0000000000..16412c63db
Binary files /dev/null and b/pages/edge-services/assets/scaleway-edge-services-splash.webp differ
diff --git a/pages/edge-services/assets/scaleway-lb-edge-services.webp b/pages/edge-services/assets/scaleway-lb-edge-services.webp
new file mode 100644
index 0000000000..59d99a1efe
Binary files /dev/null and b/pages/edge-services/assets/scaleway-lb-edge-services.webp differ
diff --git a/pages/edge-services/concepts.mdx b/pages/edge-services/concepts.mdx
new file mode 100644
index 0000000000..5b828b9497
--- /dev/null
+++ b/pages/edge-services/concepts.mdx
@@ -0,0 +1,67 @@
+---
+meta:
+ title: Edge Services - Concepts
+ description: Understand Scaleway Edge Services terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and best practices.
+content:
+ h1: Edge Services - Concepts
+ paragraph: Understand Scaleway Edge Services terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and best practices.
+tags: edge-services edge services pipeline custom-domain cache
+dates:
+ creation: 2024-07-24
+ validation: 2024-10-14
+categories:
+ - networks
+---
+
+## Cache
+
+The storage location where Edge Services stores copies of content that it has retrieved from a given origin. When users request content from the Edge Services endpoint, it serves content directly from the cache wherever possible, in accordance with the caching rules defined by the user. This reduces load on the origin bucket or Load Balancer/backend servers.
+
+Note that if an object has a caching directive, the caching directive always takes precedence over any lifetime setting defined in Edge Services.
+
+## Certificate
+
+The SSL/TLS certificate for your subdomain to enable Edge Services to serve content over HTTPS, if you have customized your [Edge Services endpoint](#endpoint). You can choose between uploading your own certificate held in Scaleway Secret Manager, or letting Edge Services generate a fully-managed Let's Encrypt certificate.
+
+## CNAME record
+
+The CNAME record pointing your subdomain to the Edge Services endpoint, if you have customized your [Edge Services endpoint](#endpoint). This is necessary to ensure that traffic for your customized subdomain is correctly directed towards the Edge Services endpoint by DNS servers.
+
+## Edge Services
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice.
+
+## Endpoint
+
+The endpoint from which a given Edge Services pipeline can be accessed, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. When a client requests content from the Edge Services endpoint, it is served by Edge Services and its cache, rather than from the origin (Object Storage bucket or Load Balancer backend servers) directly. Edge Services automatically manages redirection from HTTP to HTTPS.
+
+The endpoint can be customized with a user-defined subdomain, allowing you to replace the standardized endpoint with the subdomain of a domain you already own, e.g. `http://my-own-domain.com`. An associated [certificate](#certificate), and [CNAME record](#cname-record) will be required, in this case.
+
+## Origin
+
+The primary source from which a Scaleway Edge Services pipeline retrieves and caches data. An origin can consist of either:
+
+- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/), or
+- A [Load Balancer](#origin-load-balancer) and frontend port that Edge Services connects to to request content, and (optionally) a specified [host](#origin-host) associated with the Load Balancer, used in the HTTP request Host Header.
+
+## Origin host
+
+In the case of a Load Balancer origin, the specific host for which Edge Services requests and caches data. This is an optional setting: when specified, this host (e.g. `mydomain.com`) is used in the HTTP Host Header when Edge Services requests data from the Load Balancer. If no origin host is specified, the Load Balancer's IP address is used in the Host Header.
+
+The origin host must be associated with the origin Load Balancer / its backend servers, and only one host may be set per pipeline. If your Load Balancer is in front of multiple hosts, you can create a separate Edge Services pipeline for each. Each host will therefore get its own Edge Services endpoint and cache.
+
+## Origin Load Balancer
+
+The Load Balancer defined by the user as origin for a given Edge Services pipeline. The pipeline connects to this Load Balancer, on the specified frontend port to request content.
+
+## Pipeline
+
+
+
+An Edge Services pipeline consists of an [origin](#origin) for which Edge Services requests and [caches](#cache) content, and an [endpoint](#endpoint) from which this content is served via Edge Services. The pipeline's endpoint can be customized with a user-defined [subdomain](/domains-and-dns/concepts/#subdomain) and associated [certificate](#certificate) so that Edge Services can serve content over HTTPS.
+
+You can create an Edge Services pipeline for each of your Object Storage buckets or Load Balancer origins. Note that the cache can be enabled and disabled at will, so it is an optional part of the pipeline, as is the customization of the endpoint.
+
+## Protocol
+
+The protocol (HTTP or HTTPS) that the Edge Services pipeline should use when sending requests to an origin Load Balancer. HTTPS is recommended, but you should choose the protocol that corresponds with your Load Balancer setup.
\ No newline at end of file
diff --git a/pages/edge-services/how-to/assets/scaleway-cname-success.webp b/pages/edge-services/how-to/assets/scaleway-cname-success.webp
new file mode 100644
index 0000000000..ba6f5f4ff7
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-cname-success.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-create-es-pipeline-lb.webp b/pages/edge-services/how-to/assets/scaleway-create-es-pipeline-lb.webp
new file mode 100644
index 0000000000..75d89eb2b6
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-create-es-pipeline-lb.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp b/pages/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp
new file mode 100644
index 0000000000..b2840e1f6b
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-create-pipeline-lb.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-configure-domain.webp b/pages/edge-services/how-to/assets/scaleway-edge-configure-domain.webp
new file mode 100644
index 0000000000..31d4775176
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-configure-domain.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp b/pages/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp
new file mode 100644
index 0000000000..bdeb85751f
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-create-pipeline-os.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-pipelines.webp b/pages/edge-services/how-to/assets/scaleway-edge-pipelines.webp
new file mode 100644
index 0000000000..49f8cb4408
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-pipelines.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-cache.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-cache.webp
new file mode 100644
index 0000000000..670b8c1bf6
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-cache.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-certificate-complete.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-certificate-complete.webp
new file mode 100644
index 0000000000..201006af81
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-certificate-complete.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-configure-domain.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-configure-domain.webp
new file mode 100644
index 0000000000..520f1f44fb
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-configure-domain.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-customised.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-customised.webp
new file mode 100644
index 0000000000..127c869f22
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-customised.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-lb-dashboard.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-lb-dashboard.webp
new file mode 100644
index 0000000000..659b74e395
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-lb-dashboard.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-metrics.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-metrics.webp
new file mode 100644
index 0000000000..5096d2fd73
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-metrics.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp
new file mode 100644
index 0000000000..49ffb573d9
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-pipeline.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-purge-cache.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-purge-cache.webp
new file mode 100644
index 0000000000..105dbf2f60
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-purge-cache.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edge-services-purge-object.webp b/pages/edge-services/how-to/assets/scaleway-edge-services-purge-object.webp
new file mode 100644
index 0000000000..546797deef
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edge-services-purge-object.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-edit-edge-lb-pipeline.webp b/pages/edge-services/how-to/assets/scaleway-edit-edge-lb-pipeline.webp
new file mode 100644
index 0000000000..9fb5769c9e
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-edit-edge-lb-pipeline.webp differ
diff --git a/pages/edge-services/how-to/assets/scaleway-lb-edge-services.webp b/pages/edge-services/how-to/assets/scaleway-lb-edge-services.webp
new file mode 100644
index 0000000000..59d99a1efe
Binary files /dev/null and b/pages/edge-services/how-to/assets/scaleway-lb-edge-services.webp differ
diff --git a/pages/edge-services/how-to/configure-cache.mdx b/pages/edge-services/how-to/configure-cache.mdx
new file mode 100644
index 0000000000..653ce172f7
--- /dev/null
+++ b/pages/edge-services/how-to/configure-cache.mdx
@@ -0,0 +1,113 @@
+---
+meta:
+ title: How to configure an Edge Services cache
+ description: Learn how to configure a cache for Edge Services. Enhance performance and finely control your cached objects via purging (cache invalidation).
+content:
+ h1: How to configure an Edge Services cache
+ paragraph: Learn how to configure a cache for Edge Services. Enhance performance and finely control your cached objects via purging (cache invalidation).
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: object-storage edge-services cdn network cache purge
+categories:
+ - network
+---
+
+The cache feature allows you to cache your origin's content with Edge Services. This means that content can be served directly to users from Edge Services' servers, instead of from your Object Storage bucket or Load Balancer origin, enhancing performance.
+
+You can disable and enable caching at will, as well as control the lifetime of an object in the cache. You can also purge your entire cache, or specific objects within it. A log is displayed to help you track your purge events.
+
+## How to enable the cache
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline on which you want to enable caching:
+
+
+
+2. In the **Cache** panel, use the icon to enable the cache.
+
+ The **Lifetime** configuration box displays. This enables you to define, in seconds, how long an object can be stored in the cache before it must be retrieved freshly from the origin (Object Storage bucket or Load Balancer).
+
+
+
+
+ As an example, a value of 0 means that objects will not be cached, unless they have a separately-defined caching directive. Note that in any case, if an object has a caching directive, the caching directive always takes precedence over any lifetime setting defined here in Edge Services.
+
+
+3. Leave the default value of 1 hour in place, or enter another value.
+
+The cache is now enabled.
+
+## How to purge all objects from your cache
+
+Purging objects clears all objects from your cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache.
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
+
+
+
+2. In the **Purge cache** panel, click **Purge all**.
+
+
+
+ A screen displays, warning you that your cache will be emptied, and Edge Services will have to retrieve objects from your origin before re-caching them.
+
+3. Click **Purge cache** to confirm.
+
+## How to purge specific objects from your cache
+
+This allows you to specify the precise objects that you want to clear from the cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache.
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
+
+
+
+2. In the **Purge cache** panel, click **Purge by object**.
+
+
+
+ A screen displays prompting you to enter the path of each object you want to purge from the cache.
+
+
+
+3. Enter the path of each object you want to purge. You can purge a maximum of 5 objects at a time.
+
+
+
+ The path for each object should be defined from the root and must start with a slash, e.g. `/videos/my-video.mp4`.
+
+ You **cannot** purge entire directories by simply specifying the path to the directory, e.g. `/videos`. Purging objects must be done strictly object-by-object, so `/videos/my-video1.mp4`, `/videos/my-video2.mp4`, `/videos/my-video3.mp4` etc. Watch this space for updates to this feature in the future.
+
+ For example, if we imagine an Object Storage bucket containing one file at the root level called `object1.jpg`, and a subfolder at root level called `videos` containing an item called `my-video.mp4`, we would enter the object paths as follows:
+
+ - `/object1.jpg`
+ - `/videos/my-video.mp4`
+
+
+
+4. Click **Purge objects from cache**.
+
+ The specified objects are purged from your cache and you are returned to the Edge Services dashboard.
+
+## How to use Cache-Control
+
+To avoid repeated purging, you can also set the `Cache-Control` HTTP header directly on your files/objects. This allows you to define how long items should remain in the cache before being freshly retrieved from the origin. Edge Services will respect this header when determining where to fetch content.
+
+For Object Storage bucket origins, the following example call to the S3 API updates the `Cache-Control` header for **all** objects in the bucket, setting a maximum age of 60 seconds before they must be freshly retrieved.
+
+```
+./s3cmd --recursive modify --add-header="Cache-Control:max-age=60" s3://yourbucket/
+```
+
+## How to disable your cache
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to disable:
+
+
+
+2. In the **Cache** panel, use the icon to disable the cache.
+
+ A pop-up displays, asking you to confirm the action.
+
+3. Click **Disable cache**.
+
+ Your cache is purged and disabled. Edge Services will now serve content by fetching it from your origin (Object Storage bucket or Load Balancer) directly. If you reenable your cache at a later point, you will begin with an empty cache.
\ No newline at end of file
diff --git a/pages/edge-services/how-to/configure-custom-domain.mdx b/pages/edge-services/how-to/configure-custom-domain.mdx
new file mode 100644
index 0000000000..f700c23a6c
--- /dev/null
+++ b/pages/edge-services/how-to/configure-custom-domain.mdx
@@ -0,0 +1,123 @@
+---
+meta:
+ title: How to configure a custom domain for Edge Services
+ description: Learn how to configure an Edge Services endpoint with a custom subdomain. Access your Object Storage bucket or Load Balancer origin via your own domain name instead of the standardized endpoint.
+content:
+ h1: How to configure a custom domain for Edge Services
+ paragraph: Learn how to configure an Edge Services endpoint with a custom subdomain. Access your Object Storage bucket or Load Balancer origin via your own domain name instead of the standardized endpoint.
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: object-storage edge-services cdn network domain ssl tls https
+categories:
+ - network
+---
+
+If you already own a domain, you can customize an Edge Services pipeline endpoint with a subdomain of your choice. This means you can access your Object Storage bucket or Load Balancer origin through Edge Services via your own subdomain rather than the standardized Edge Services endpoint.
+
+For example, if you own `beautiful-domain.com`, you can customize the endpoint to be `whatever-i-want.beautiful-domain.com`. You must also add an SSL/TLS certificate so that Edge Services can securely serve your content via HTTPS.
+
+You cannot customize your endpoint with a primary domain directly (e.g. `beautiful-domain.com`), only with a subdomain of it.
+
+## How to configure a custom domain
+
+The procedure for adding a customized endpoint is as follows:
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline whose domain you want to customize:
+
+
+
+2. In the **Endpoint** panel, click **Configure domain**. The following screen displays:
+
+
+
+3. Set a subdomain from which your Object Storage bucket or Load Balancer origin will be accessible via its Edge Services pipeline. You must already own the primary domain. For example, if you own `beautiful-domain.com`, choose any subdomain you like and enter `my-chosen-subdomain.beautiful-domain.com` into the box.
+
+
+ It is **not** possible to use only a root domain (aka primary domain or apex domain), you must use a subdomain. This is because CNAME records, essential to point your domain to your Edge Services endpoint, cannot by definition be created for root domains, only for subdomains.
+ ✅ blog.example.com
+ ❌ example.com
+
+
+4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below.
+
+
+
+
+ The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:
+ - You [registered the domain](/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or
+ - You [transferred an externally-registered domain](/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS
+
+ If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6.
+
+ You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console.
+
+
+
+ Scaleway cannot itself create the appropriate CNAME record to point your subdomain to Edge Services if your domain is managed by an external provider. You must create the CNAME record yourself.
+
+ Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/edge-services/reference-content/cname-record/).
+
+ Back in the Scaleway console, click the `Verify CNAME` button to check whether your CNAME record has been correctly configured. Edge Services will carry out a check, and if it is successful the following message displays:
+
+
+
+ If the check fails, an error message will display. See the documentation linked above for help troubleshooting such errors. Note that it may take a short time for the DNS record to be propagated and the check to pass.
+
+
+
+5. Provide an SSL/TLS certificate for your subdomain so that Edge Services can serve traffic for it over HTTPS. You have three options for this:
+ - Generate a free Let's Encrypt certificate, managed by Scaleway, including automatic renewals.
+ - Select an existing certificate that you have stored in [Scaleway Secret Manager](/secret-manager/quickstart/).
+ - Manually import a certificate into Scaleway Secret Manager:
+ - Enter a name for your certificate (alphanumeric characters only)
+ - Optionally, add tags by typing each tag and then pressing enter
+ - Copy and paste the full PEM-formatted certificate chain into the box.
+ Your certificate will be automatically stored in Secret Manager and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/).
+
+
+ For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/edge-services/reference-content/ssl-tls-certificate/).
+
+
+6. Click **Customize domain** to finish.
+
+Your customized domain is set up, and you are returned to the Edge Services dashboard. The customized domain displays in the Endpoint panel. When you access your Object Storage or Load Balancer origin through this domain, its content will be served via Edge Services.
+
+
+If you chose to generate a managed Let's Encrypt certificate, allow a few minutes for the certificate to finish creating. When the process is complete and the certificate is ready, you will see a green status light for **SSL/TLS certificate** on your endpoint dashboard.
+
+
+
+
+
+## How to edit your customized domain or its certificate
+
+After customizing your domain, you can edit it (or its certificate) at any time as follows:
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to customize:
+
+
+
+2. In the **Endpoint** panel, click **Edit**. The **Edit Domain** screen displays.
+
+3. Edit the subdomain as desired - do not forget to also set up a new CNAME record, if necessary.
+
+4. Edit your certificate options as required - choose to generate a managed Let's Encrypt certificate, managed by Scaleway including automatic renewals, or select a different certificate from Secret Manager, or manually import a new certificate for your custom domain.
+
+5. Click **Edit domain** to finish.
+
+## How to reset your customized domain
+
+Even though the original Edge Services endpoint (e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`) will continue to work after you add a customized domain, you can choose to remove your customized domain completely and go back to the original Edge Services endpoint only. This is done via the reset function:
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to reset:
+
+
+
+2. In the **Endpoint** panel, click **Reset**.
+
+ A screen displays, warning you that this will reset the pipeline's domain back to the default Edge Services endpoint. Edge Services will consider your customized subdomain as unknown. You should also remember to:
+ - Delete your CNAME record from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you.
+ - Delete any SSL/TLS certificates you imported into Secret Manager (if no longer required elsewhere, so that you are no longer billed for it). If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you.
+
+3. Click **Reset domain** to finish.
diff --git a/pages/edge-services/how-to/create-pipeline-bucket.mdx b/pages/edge-services/how-to/create-pipeline-bucket.mdx
new file mode 100644
index 0000000000..b7ebb6fe21
--- /dev/null
+++ b/pages/edge-services/how-to/create-pipeline-bucket.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: How to create an Edge Services pipeline for an Object Storage bucket
+ description: This page explains how to configure an Edge Services pipeline for a Scaleway Object Storage bucket. Set up your own custom domain to point to your bucket, and enable a caching service for faster and more efficient delivery.
+content:
+ h1: How to create an Edge Services pipeline for an Object Storage bucket
+ paragraph: This page explains how to configure an Edge Services pipeline for a Scaleway Object Storage bucket. Set up your own custom domain to point to your bucket, and enable a caching service for faster and more efficient delivery.
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: object-storage edge-services cdn network cache domain https
+categories:
+ - network
+---
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. Creating an Edge Services pipeline towards your Object Storage bucket brings you a number of possible benefits:
+
+
+
+Read on to learn how to create an Edge Services pipeline for your Object Storage bucket.
+
+
+
+- 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
+- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/)
+- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/)
+
+## How to create an Edge Services pipeline
+
+
+You can create an Edge Services pipeline [from the Object Storage section of the console](/object-storage/how-to/get-started-edge-services/), by navigating to your bucket's dashboard and clicking the **Edge Services** tab. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console.
+
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.
+
+2. Click **Create pipeline**. The pipeline creation wizard displays.
+
+
+
+3. Select **Object Storage** as the origin type.
+
+4. Choose the bucket you want this pipeline to serve content for, under **Origin bucket**.
+
+5. Enter a name for the pipeline, or leave the randomly generated name in place.
+
+6. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**.
+
+ You are returned to the **Pipelines** tab, where the newly created pipeline now displays.
+
+ Click on the pipeline to go to its **Overview** page and start configuration.
+
+
+
+ Your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private.
+
+
+
+## How to access your bucket via Edge Services
+
+Once you have created an Edge Services pipeline for your bucket, you can access your bucket and its content via the following endpoints. Make sure that you replace `bucket-name` with the name of your bucket.
+
+| Endpoint | Where to find this endpoint in the console | Notes |
+|-----------------------------------------|--------------------------|-----------------------------------------------------------------------------------|
+| `https://bucket-name.s3.nl-ams.scw.cloud` | The **Bucket settings** tab | Edge Services is bypassed when the bucket is accessed via this endpoint |
+| `https://bucket-name.svc.edge.scw.cloud` | The **Edge Services** tab | Edge Services serves bucket content when this endpoint is used |
+
+The two endpoints shown above are available as standard. However, with Edge Services, you can also choose to configure a **custom domain** from which your bucket can be accessed. Read more about this in the [next section](/edge-services/how-to/configure-custom-domain/).
\ No newline at end of file
diff --git a/pages/edge-services/how-to/create-pipeline-lb.mdx b/pages/edge-services/how-to/create-pipeline-lb.mdx
new file mode 100644
index 0000000000..850f0a1a20
--- /dev/null
+++ b/pages/edge-services/how-to/create-pipeline-lb.mdx
@@ -0,0 +1,123 @@
+---
+meta:
+ title: How to create an Edge Services pipeline for a Load Balancer
+ description: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery.
+content:
+ h1: How to create an Edge Services pipeline for a Load Balancer
+ paragraph: This page explains how to configure an Edge Services pipeline on your Load Balancer, enabling a caching service for faster and more efficient delivery.
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: load-balancer edge-services cdn network cache domain https
+categories:
+ - network
+---
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets.
+
+
+
+
+
+- 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
+- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/)
+- A [Load Balancer](/load-balancer/how-to/create-load-balancer/)
+
+## How to create an Edge Services pipeline for Load Balancer
+
+
+You can create an Edge Services pipeline from the Load Balancer section of the console, via the **Edge Services** tab there. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console.
+
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.
+
+2. Click **Create pipeline**. The pipeline creation wizard displays.
+
+
+
+3. Configure the [origin](/edge-services/concepts/#origin) for this pipeline:
+ - Select **Load Balancer** as the origin type.
+ - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content.
+ - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend.
+
+
+ For Kubernetes Load Balancers, see our [dedicated documentation](#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend.
+
+
+
+4. Define the protocol and origin host for this pipeline:
+ - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup.
+ - Optionally, enter an [origin host](/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer.
+
+5. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place.
+
+ The summary cost for the creation of this pipeline is displayed, notably whether it falls within the limits of your current [subscription plan](/edge-services/reference-content/understanding-pricing/)
+
+6. Click **Create Edge Services pipeline** to finish.
+
+ You are returned to the **Pipelines** tab, where the newly created pipeline now displays.
+
+ Click on the pipeline to go to its **Overview** page and start configuration. From the **Overview**, you can see the endpoint from which you can access your Load Balancer origin via Edge Services, e.g. `https://pipeline-id.edge.scw.cloud`.
+
+## Troubleshooting pipeline creation
+
+If you see the message `Edge Services was unable to contact the host via the Load Balancer Please check your origin configuration settings and try again`, check the following elements of your configuration:
+
+- **Protocol**: Ensure you did not select the wrong protocol, e.g. HTTP selected while the frontend chosen is configured to receive HTTPS, or the opposite.
+- **Origin host**: Ensure that you entered the correct origin host, with no typos, for a host that exists behind the selected Load Balancer.
+- **Load Balancer ACLs**: Ensure that there are no [ACLs](/load-balancer/how-to/create-manage-acls/) configured on your Load Balancer which are blocking traffic from Edge Services.
+
+## Help for Kubernetes Load Balancers
+
+If you are setting up an Edge Services pipeline for a [Kubernetes Kapsule](/kubernetes) Load Balancer, follow these steps to determine which Load Balancer and frontend to configure for your pipeline:
+
+1. Run `kubectl describe svc`.
+
+ An output displays.
+
+2. Locate the section of the output that relates to your LoadBalancer service. It should look something like this:
+
+ ```
+ Name: myloadbalancer
+ Namespace: default
+ Labels: app=mydeployment
+ Annotations: service.beta.kubernetes.io/scw-loadbalancer-id: fr-par-1/a92de52e-262f-99f9-be66-5220003a2e42
+ Selector: app=mydeployment
+ Type: LoadBalancer
+ IP Family Policy: SingleStack
+ IP Families: IPv4
+ IP: 10.32.220.60
+ IPs: 10.32.220.60
+ LoadBalancer Ingress: 51.159.25.111
+ Port: http 8000/TCP
+ TargetPort: 8000/TCP
+ NodePort: http 32041/TCP
+ Endpoints:
+ Session Affinity: None
+ External Traffic Policy: Cluster
+ ```
+3. Find the `service.beta.kubernetes.io/scw-loadbalancer-id` annotation, and note your Load Balancer ID (e.g. `a92de52e-262f-99f9-be66-5220003a2e42`). Check your Load Balancer list in the [console](https://console.scaleway.com/load-balancer/lbs) to find the Load Balancer name that corresponds to this ID. This is the Load Balancer you should select for the Edge Services pipeline.
+
+4. Find the **NodePort** line and note the port mentioned (in the case above, `32041`). In the [console](https://console.scaleway.com/load-balancer/lbs), find the frontend of the Load Balancer from step 3 that corresponds with this port. This is the frontend and port you should select for the Edge Services pipeline.
+
+## How to edit an Edge Services pipeline origin
+
+You can edit the protocol, origin host, and name of an Edge Services pipeline as follows.
+
+1. Click **Load Balancers** in the **Network** section of the Scaleway console side menu. The list of your Load Balancers displays.
+
+2. Click the **Edge Services** tab.
+
+3. Click the Edge Services pipeline you want to edit. The **Overview** page for the pipeline displays.
+
+4. In the top right corner, click **Edit**. A pop-up displays.
+
+
+
+5. Make the edits required. You can:
+ - Change the **protocol**
+ - Change the **origin host**
+ - Change the pipeline **name**
+
+6. Click **Save**.
\ No newline at end of file
diff --git a/pages/edge-services/how-to/delete-pipeline.mdx b/pages/edge-services/how-to/delete-pipeline.mdx
new file mode 100644
index 0000000000..240cfc68f7
--- /dev/null
+++ b/pages/edge-services/how-to/delete-pipeline.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to delete an Edge Services pipeline
+ description: Learn how to delete a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively.
+content:
+ h1: How to delete an Edge Services pipeline
+ paragraph: Learn how to delete a Scaleway Edge Services pipeline with this step-by-step guide. Follow our instructions to ensure a smooth process and manage your domains and SSL/TLS certificates effectively.
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: load-balancer edge-services cdn network pipeline
+categories:
+ - network
+---
+
+You can delete an Edge Services pipeline at any time by following the steps below.
+
+
+
+- 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
+- An Edge Services pipeline
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays.
+
+2. Click the pipeline that you want to delete. You are taken to the pipeline's **Overview** page
+
+4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**.
+
+ A pop-up displays, asking you to confirm that you want to delete the pipeline.
+ - The Load Balancer/Object Storage bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint.
+ - Any files stored in the Edge Services cache will be removed.
+
+
+ Remember to:
+ - Delete any CNAME records created for this pipeline from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you.
+ - Delete any SSL/TLS certificates you imported into Secret Manager for this pipeline (if no longer required elsewhere), so that you are no longer billed for them. If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you.
+
+
+5. Click **Confirm**.
+
+ The Edge Services pipeline is deleted. You can create a new pipeline for this origin at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty.
\ No newline at end of file
diff --git a/pages/edge-services/how-to/index.mdx b/pages/edge-services/how-to/index.mdx
new file mode 100644
index 0000000000..7cf1c10784
--- /dev/null
+++ b/pages/edge-services/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Edge Services - How Tos
+ description: Learn how to set up and optimize Scaleway Edge Services. These how to guides cover pipeline creation, customization of your domain, cache configuration, and advanced features for improved performance of your Object Storage bucket and Load Balancer origins.
+content:
+ h1: Edge Services - How Tos
+ paragraph: Learn how to set up and optimize Scaleway Edge Services. These how to guides cover pipeline creation, customization of your domain, cache configuration, and advanced features for improved performance of your Object Storage bucket and Load Balancer origins.
+---
diff --git a/pages/edge-services/how-to/monitor-cockpit.mdx b/pages/edge-services/how-to/monitor-cockpit.mdx
new file mode 100644
index 0000000000..2f25fe6899
--- /dev/null
+++ b/pages/edge-services/how-to/monitor-cockpit.mdx
@@ -0,0 +1,48 @@
+---
+meta:
+ title: How to monitor Edge Services with Scaleway Cockpit
+ description: Get easy access to your Edge Services metrics via Scaleway Cockpit. Monitor ingress, egress, request rate and cache hit ratio in a convenient managed Grafana dashboard.
+content:
+ h1: How to monitor Edge Services with Scaleway Cockpit
+ paragraph: Get easy access to your Edge Services metrics via Scaleway Cockpit. Monitor ingress, egress, request rate and cache hit ratio in a convenient managed Grafana dashboard.
+dates:
+ validation: 2024-10-15
+ posted: 2024-07-24
+tags: load-balancer edge-services cdn cache-hit-ratio grafana observability
+categories:
+ - network
+---
+
+You can view your Edge Services metrics via [Scaleway Cockpit](/cockpit/quickstart/). This allows you to monitor your ingress, egress, request rate, and cache hit ratio as well as other metrics, in a convenient managed Grafana dashboard.
+
+Access your Edge Services dashboard in the Scaleway console via either
+
+- Clicking **Track your Edge Services metrics with Cockpit** shortcut in the **Edge Services** dashboard of the pipeline in question.
+- The **Metrics** tab in the **Edge Services** section of the console.
+
+Note that you will first need to [create a Grafana user and credentials](/cockpit/how-to/retrieve-grafana-credentials/).
+
+### Understanding the dashboard
+
+The Grafana dashboard presents a number of different metrics. Use the drop-down in the top left to select which pipeline and origin to view Edge Services metrics for, and the time range drop-down in the top right to modify the time period to apply to the metrics.
+
+
+
+- **Request rate**: The number of requests made to Edge Services per second, for the specified origin, averaged over the specified time period.
+- **Cache hit ratio**: The percentage of requests served from Edge Services' cache, compared to the total number of requests in total to Edge Services for this origin, over the specified time period.
+- **Cache HIT/MISS**: A visual representation of the ratio of cache hits to misses, for the specified origin, over the specified time period.
+ - **Cache hit line**: The number of requests per second made to Edge Services for this origin, which were served directly from its cache.
+ - **Cache miss line**: The number of requests per second made to Edge Services for this origin, where the content was fetched from the origin rather than the cache.
+ - **Total line**: The number of requests per second made to Edge Services for this origin.
+
+- **Egress (to client)**: The total volume of data served to clients from Edge Services, for the specified origin, over the specified time period.
+- **Ingress (from origin)**: The total volume of data from the origin server to Edge Services over the specified time period. This represents the traffic that occurs when Edge Services retrieves content from the origin server in order to fulfill requests.
+- **Edge Services throughput**: A visual representation of the rate of data transfer for the specified origin with Edge Services over the specified time period.
+ - **Output bitrate line**: The rate at which data is being delivered from Edge Services to end users.
+ - **Input bitrate line**: The rate at which Edge Services is fetching data from the origin server. Peaks in this line may represent times when Edge Services had to fetch content from the origin server, rather than being able to serve it directly from its own cache.
+
+- **Requests served**: The total number of requests that Edge Services has successfully served, for the specified origin, over the specified time period.
+- **Edge Services response statuses**: A visual representation of the distribution of HTTP response statuses for requests served by Edge Services over the specified time period. Consult [the full list of HTTP status codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) for more information if necessary.
+
+- **Request origin country**: The proportion of requests (to Edge Services for the specified origin over the specified time period) originating from different countries.
+- **End users location**: A visual representation of where Edge Services end users have been making requests from geographically.
diff --git a/pages/edge-services/how-to/subscribe-edge-services.mdx b/pages/edge-services/how-to/subscribe-edge-services.mdx
new file mode 100644
index 0000000000..df1485aad4
--- /dev/null
+++ b/pages/edge-services/how-to/subscribe-edge-services.mdx
@@ -0,0 +1,69 @@
+---
+meta:
+ title: How to subscribe to Edge Services
+ description: Find out how to take your first steps with Scaleway Edge Services by subscribing to a pricing plan. Learn how to choose the best plan for your needs and change your plan at the click of a button.
+content:
+ h1: How to subscribe to Edge Services
+ paragraph: Find out how to take your first steps with Scaleway Edge Services by subscribing to a pricing plan. Learn how to choose the best plan for your needs and change your plan at the click of a button.
+dates:
+ validation: 2024-10-15
+ posted: 2024-10-15
+tags: object-storage edge-services subscription-plan subscribe billing pricing
+categories:
+ - network
+---
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It lets you benefit from a powerful caching service to reduce the load on your origin servers and streamline delivery. On top of this, you get a customizable Edge Services endpoint and can set it to a subdomain of your choice, securing it with an SSL/TLS certificate.
+
+To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes:
+
+- A fixed number of Edge Services [pipelines](/edge-services/concepts/#pipeline). You can create pipelines for either Load Balancers, Object Storage buckets, or a mixture of both, with your subscription plan.
+- A certain amount of egress [cache](/edge-services/concepts/#cache) data (the quantity of data transferred from Edge Services' caches, not including the transfer from the origin bucket or Load Balancer).
+- A custom domain and SSL certificate (managed or custom) for each pipeline.
+
+If you create more pipelines than are included in your plan, or your pipelines' caches egress more data than is included, you will be charged additionally for this. The rates per pipeline/GB of data are indicated on the [pricing](https://www.scaleway.com/en/pricing/network/#edge-services) page.
+
+Subscriptions are pro-rata, meaning you can cancel your subscription or change your plan at any time, and you will be charged proportionally.
+
+Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page.
+
+## How to subscribe to Edge Services
+
+
+
+- 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
+
+
+You can subscribe to Edge Services from the Object Storage or Load Balancer dashboards of the Scaleway console. However, the instructions below detail how to describe from the dedicated Edge Services section of the console. Whichever path you use, the same pricing plans and subscription mechanisms apply. Subscribing from the Object Storage or Load Balancer dashboards does **not** limit you to only creating pipelines for that product with your subscription. Subscription plans are scoped to a single Scaleway [Project](/organizations-and-projects/concepts/#project).
+
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.
+
+2. Click **Subscribe to Edge Services**.
+
+ Information about available [pricing plans](https://www.scaleway.com/en/pricing/network/#edge-services) is displayed. All pricing plans have a fixed monthly price, and include a certain number of pipelines and a certain amount of cache data (data egressed from all your Edge Services pipelines' caches). Any extra pipelines or cache egress data are charged at the additional rates shown.
+
+3. Select a plan, and click **Subscribe to Edge Services**.
+
+ Your subscription is created, and you are returned to the Edge Services dashboard, on the **Pipelines** tab. All your Edge Services pipelines will display here.
+
+## How to change your subscription plan
+
+You can change your Edge Services subscription plan at any time. Subscriptions are pro-rata: the monthly price will be applied based on the proportion of the month you are subscribed to the plan.
+
+If you upgrade your plan, any additional charges (for extra pipelines or cache data) that you had already accumulated before the time of upgrade will still stand.
+
+Find out more about how Edge Service subscription plans and billing works, including scenarios for changing your plan mid-month, on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page.
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays.
+
+2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription.
+
+3. Scroll down to the **Manage your plan subscription** section, and click **Select plan** on the plan you want to switch to.
+
+ A pop-up displays, asking you to confirm that you want to change plans.
+
+4. Click **change plan** to confirm.
+
+Your subscription plan is updated, and you are returned to the **Plans** tab of your Edge Services dashboard.
\ No newline at end of file
diff --git a/pages/edge-services/how-to/terminate-edge-services.mdx b/pages/edge-services/how-to/terminate-edge-services.mdx
new file mode 100644
index 0000000000..da90c90ada
--- /dev/null
+++ b/pages/edge-services/how-to/terminate-edge-services.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to terminate an Edge Services subscription
+ description: Find out how to terminate your Scaleway Edge Services subscription whenever you want, at the click of a button.
+content:
+ h1: How to terminate an Edge Services subscription
+ paragraph: Find out how to terminate your Scaleway Edge Services subscription whenever you want, at the click of a button.ow to choose the best plan for your needs and change your plan at the click of a button.
+dates:
+ validation: 2024-10-15
+ posted: 2024-10-15
+tags: object-storage edge-services subscription-plan subscribe billing pricing terminate cancel
+categories:
+ - network
+---
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It lets you benefit from a powerful caching service to reduce the load on your origin servers and streamline delivery. On top of this, you get a customizable Edge Services endpoint and can set it to a subdomain of your choice, securing it with an SSL/TLS certificate. To use Edge Services, you must subscribe to a monthly plan.
+
+## How to terminate your Edge Services subscription
+
+
+
+- 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
+- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/)
+- [Deleted all your Edge Services pipelines](/edge-services/how-to/delete-pipeline/)
+
+You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro-rata for the month you cancel, based on how much of that month your subscription was active.
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays.
+
+2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription.
+
+3. Scroll down to the **Terminate subscription** section, and click **Terminate subscription**.
+
+ A pop-up displays, asking you to confirm that you want to terminate your subscription.
+
+4. Type **DELETE** in the box, and click **Terminate** to confirm.
+
+ Your Edge Services subscription is terminated. You can subscribe again at any time.
\ No newline at end of file
diff --git a/pages/edge-services/index.mdx b/pages/edge-services/index.mdx
new file mode 100644
index 0000000000..d9b7221d92
--- /dev/null
+++ b/pages/edge-services/index.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: Edge Services Documentation
+ description: Dive into Scaleway Edge Services with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+ Edge Services for Object Storage and Load Balancers is now in General Availability, and a subscription-based pricing plan applies. Find out more in our [dedicated documentation](/edge-services/reference-content/understanding-ga/).
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/edge-services/quickstart.mdx b/pages/edge-services/quickstart.mdx
new file mode 100644
index 0000000000..5b4dec08a9
--- /dev/null
+++ b/pages/edge-services/quickstart.mdx
@@ -0,0 +1,225 @@
+---
+meta:
+ title: Edge Services - Quickstart
+ description: Quickly set up Scaleway Edge Services for Object Storage buckets or Load Balancer origins with our guide. Learn to configure pipelines, customize endpoints, and manage caching for optimal performance.
+content:
+ h1: Edge Services - Quickstart
+ paragraph: Quickly set up Scaleway Edge Services for Object Storage buckets or Load Balancer origins with our guide. Learn to configure pipelines, customize endpoints, and manage caching for optimal performance.
+tags: edge-services edge services pipeline custom-domain cache
+dates:
+ validation: 2024-10-15
+ creation: 2024-07-24
+categories:
+ - networks
+---
+
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/edge-services/concepts/#origin), and a customizable and secure [endpoint](/edge-services/concepts/#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice.
+
+To use Edge Services, you must take out a subscription plan, which then enables you to create a certain number of Edge Services pipelines towards your Load Balancer origins or Object Storage buckets.
+
+
+
+
+
+- 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 either a [Load Balancer](/load-balancer/how-to/create-load-balancer/) or an [Object Storage bucket](/object-storage/how-to/create-a-bucket/)
+
+## How to subscribe to Edge Services
+
+To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate.
+
+Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page, or follow the steps below to subscribe.
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.
+
+2. Click **Subscribe to Edge Services**. Information about available [pricing plans](https://www.scaleway.com/en/pricing/network/#edge-services) is displayed.
+
+3. Select a plan, and click **Subscribe to Edge Services**.
+
+ Your subscription is created, and you are returned to the Edge Services dashboard, on the **Pipelines** tab. All your Edge Services pipelines will display here.
+
+## How to create an Edge Services pipeline
+
+You can create [pipelines](/edge-services/concepts/#pipeline) for either Object Storage buckets or Load Balancer origins.
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.
+
+2. Click **Create pipeline**. The pipeline creation wizard displays.
+
+3. Choose an **origin type**, the type of resource which Edge Services will connect to to fetch content to serve. This can either be **Load Balancer** or **Object Storage**.
+
+ Follow the steps below depending on whether you are creating a Load Balancer or Object Storage pipeline
+
+
+
+
+
+
+ 4. Configure the [origin](/edge-services/concepts/#origin) for this pipeline:
+ - Select **Load Balancer** as the origin type.
+ - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content.
+ - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend.
+
+
+ For Kubernetes Load Balancers, see our [dedicated documentation](/edge-services/how-to/create-pipeline-lb/#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend.
+
+
+
+ 5. Define the protocol and origin host for this pipeline:
+ - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup.
+ - Optionally, enter an [origin host](/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer.
+
+ 6. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place.
+
+ 7. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**.
+
+
+
+
+
+
+ 4. Select **Object Storage** as the origin type.
+
+ 5. Choose the bucket you want this pipeline to serve content for, under **Origin bucket**.
+
+ 6. Enter a name for the pipeline, or leave the randomly generated name in place.
+
+ 7. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**.
+
+
+ Your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private.
+
+
+
+
+
+ You are returned to the **Pipelines** tab, where the newly created pipeline now displays. Click on the pipeline to go to its **Overview** page and start configuration.
+
+## How to configure a custom domain
+
+If you already own a domain, you can customize an Edge Services pipeline endpoint with a subdomain of your choice, e.g. `subdomain.mydomain.com`. This means you can access your Object Storage bucket or Load Balancer origin through Edge Services via your own subdomain rather than the standardized Edge Services endpoint.
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to customize:
+
+
+
+2. In the **Endpoint** panel, click **Configure domain**. The following screen displays:
+
+
+
+3. Set a subdomain from which your Object Storage bucket or Load Balancer origin will be accessible via its Edge Services pipeline. You must already own the primary domain. For example, if you own `beautiful-domain.com`, choose any subdomain you like and enter `my-chosen-subdomain.beautiful-domain.com` into the box.
+
+
+ It is **not** possible to use only a root domain (aka primary domain or apex domain), you must use a subdomain. This is because CNAME records, essential to point your domain to your Edge Services endpoint, cannot by definition be created for root domains, only for subdomains.
+ ✅ blog.example.com
+ ❌ example.com
+
+
+4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below.
+
+
+
+
+ The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:
+ - You [registered the domain](/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or
+ - You [transferred an externally-registered domain](/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS
+
+ If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6.
+
+ You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console.
+
+
+
+ Scaleway cannot itself create the appropriate CNAME record to point your subdomain to Edge Services if your domain is managed by an external provider. You must create the CNAME record yourself.
+
+ Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/edge-services/reference-content/cname-record/).
+
+ Back in the Scaleway console, click the `Verify CNAME` button to check whether your CNAME record has been correctly configured. Edge Services will carry out a check, and if it is successful the following message displays:
+
+
+
+ If the check fails, an error message will display. See the documentation linked above for help troubleshooting such errors. Note that it may take a short time for the DNS record to be propagated and the check to pass.
+
+
+
+5. Provide an SSL/TLS certificate for your subdomain so that Edge Services can serve traffic for it over HTTPS. You have three options for this:
+ - Generate a free Let's Encrypt certificate, managed by Scaleway, including automatic renewals.
+ - Select an existing certificate that you have stored in [Scaleway Secret Manager](/secret-manager/quickstart/).
+ - Manually import a certificate into Scaleway Secret Manager:
+ - Enter a name for your certificate (alphanumeric characters only)
+ - Optionally, add tags by typing each tag and then pressing enter
+ - Copy and paste the full PEM-formatted certificate chain into the box.
+ Your certificate will be automatically stored in Secret Manager and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/).
+
+
+ For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/edge-services/reference-content/ssl-tls-certificate/).
+
+
+6. Click **Customize domain** to finish.
+
+Your customized domain is set up, and you are returned to the Edge Services dashboard. The customized domain displays in the Endpoint panel. When you access your Object Storage or Load Balancer origin through this domain, its content will be served via Edge Services.
+
+## How to configure your cache
+
+The cache feature allows you to cache your origin's content with Edge Services. This means that content can be served directly to users from Edge Services' servers, instead of from your Object Storage bucket or Load Balancer origin, enhancing performance.
+
+You can disable and enable caching at will, as well as control the lifetime of an object in the cache. You can also purge your entire cache, or specific objects within it. A log is displayed to help you track your purge events.
+
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline for which you want to enable caching:
+
+
+
+2. In the **Cache** panel, use the icon to enable the cache.
+
+ The **Lifetime** configuration box displays. This enables you to define, in seconds, how long an object can be stored in the cache before it must be retrieved freshly from the origin (Object Storage bucket or Load Balancer).
+
+
+
+
+ As an example, a value of 0 means that objects will not be cached, unless they have a separately-defined caching directive. Note that in any case, if an object has a caching directive, the caching directive always takes precedence over any lifetime setting defined here in Edge Services.
+
+
+3. Leave the default value of 1 hour in place, or enter another value.
+
+The cache is now enabled.
+
+For information on purging your cache, see our [dedicated documentation](/edge-services/how-to/configure-cache/).
+
+## How to delete an Edge Services pipeline
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays.
+
+2. Click the pipeline that you want to delete. You are taken to the pipeline's **Overview** page
+
+4. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**.
+
+ A pop-up displays, asking you to confirm that you want to delete the pipeline.
+ - The Load Balancer/Object Storage bucket will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint.
+ - Any files stored in the Edge Services cache will be removed.
+
+
+ Remember to:
+ - Delete any CNAME records created for this pipeline from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you.
+ - Delete any SSL/TLS certificates you imported into Secret Manager for this pipeline (if no longer required elsewhere), so that you are no longer billed for them. If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you.
+
+
+5. Click **Confirm**.
+
+ The Edge Services pipeline is deleted. You can create a new pipeline for this origin at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty.
+
+## How to terminate an Edge Services subscription
+
+You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro-rata for the month you cancel, based on how many days in that month your subscription was active.
+
+1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays.
+
+2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription.
+
+3. Scroll down to the **Terminate subscription** section, and click **Terminate subscription**.
+
+ A pop-up displays, asking you to confirm that you want to terminate your subscription.
+
+4. Type **DELETE** in the box, and click **Terminate** to confirm.
+
+ Your Edge Services subscription is terminated. You can subscribe again at any time.
\ No newline at end of file
diff --git a/pages/edge-services/reference-content/assets/scaleway-cert-expired.webp b/pages/edge-services/reference-content/assets/scaleway-cert-expired.webp
new file mode 100644
index 0000000000..d7fa525696
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-cert-expired.webp differ
diff --git a/pages/edge-services/reference-content/assets/scaleway-current-conso.webp b/pages/edge-services/reference-content/assets/scaleway-current-conso.webp
new file mode 100644
index 0000000000..4ef75bb663
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-current-conso.webp differ
diff --git a/pages/edge-services/reference-content/assets/scaleway-edge-services-cname-error.webp b/pages/edge-services/reference-content/assets/scaleway-edge-services-cname-error.webp
new file mode 100644
index 0000000000..a0f926abaa
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-edge-services-cname-error.webp differ
diff --git a/pages/edge-services/reference-content/assets/scaleway-edge-services-configure-domain.webp b/pages/edge-services/reference-content/assets/scaleway-edge-services-configure-domain.webp
new file mode 100644
index 0000000000..520f1f44fb
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-edge-services-configure-domain.webp differ
diff --git a/pages/edge-services/reference-content/assets/scaleway-edge-services-dashboard-error.webp b/pages/edge-services/reference-content/assets/scaleway-edge-services-dashboard-error.webp
new file mode 100644
index 0000000000..59296526db
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-edge-services-dashboard-error.webp differ
diff --git a/pages/edge-services/reference-content/assets/scaleway-pipelines-limit.webp b/pages/edge-services/reference-content/assets/scaleway-pipelines-limit.webp
new file mode 100644
index 0000000000..67f0561d69
Binary files /dev/null and b/pages/edge-services/reference-content/assets/scaleway-pipelines-limit.webp differ
diff --git a/pages/edge-services/reference-content/cname-record.mdx b/pages/edge-services/reference-content/cname-record.mdx
new file mode 100644
index 0000000000..15a7a184b3
--- /dev/null
+++ b/pages/edge-services/reference-content/cname-record.mdx
@@ -0,0 +1,93 @@
+---
+meta:
+ title: CNAME records and DNS for Edge Services
+ description: Learn how to set up and manage CNAME records for Scaleway Edge Services pipelines. Follow our detailed guide to configure your custom domain and enhance your cloud accessibility.
+content:
+ h1: CNAME records and DNS for Edge Services
+ paragraph: Learn how to set up and manage CNAME records for Scaleway Edge Services pipelines. Follow our detailed guide to configure your custom domain and enhance your cloud accessibility.
+tags: edge-services pipeline cname dns
+dates:
+ validation: 2024-07-25
+categories:
+ - network
+---
+
+This document contains information to help you successfully create a CNAME record for your customized [Edge Services](/edge-services/) domain, and troubleshoot any potential DNS problems.
+
+## What is a CNAME record?
+
+A **C**anonical **Name** (CNAME) record is a type of [DNS record](/domains-and-dns/concepts/#dns-record). Generally, DNS records hold information for translating a domain or subdomain to an IP address, mail server or other domain/subdomain. They are crucial in directing internet traffic to the correct servers. More specifically, CNAME records map one domain name (an alias) to another (the canonical name).
+
+A CNAME record may look like the following:
+
+| Hostname / Alias | Destination / Canonical Name |
+|----------------------------|-------------------------------|
+| `videos.example.com` | `otherdomain.com` |
+
+In this case, when a DNS server sees this record for `videos.example.com` it will know not to direct traffic to `videos.example.com`'s own IP address, but to that of `otherdomain.com`. It will find `othercomain.com`'s IP address via its [A record](/domains-and-dns/reference-content/understanding-dns-records/#a-record).
+
+When the client actually connects to `otherdomain.com`'s IP address, the web server can see that the requested URL was `videos.example.com`, and deliver the relevant content.
+
+## When and why do I need to create a CNAME record for Edge Services?
+
+When you create an Edge Services pipeline to an [origin](/edge-services/concepts/#origin) (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. `pipeline-id-or-bucket-name.svc.edge.scw.cloud`. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records.
+
+However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), a CNAME record must be created to point your subdomain to the Edge Services endpoint.
+
+ - If your domain is managed with [Scaleway Domains and DNS](/domains-and-dns/quickstart/), we take care of auto-generating the appropriate CNAME record for you, as well as deleting it if and when you deactivate Edge Services. There is no action for you to take. You should not attempt to modify or delete the CNAME record (which will be visible among your Domains and DNS records in the console).
+ - If your domain is managed by an external provider, Scaleway is unable to create the appropriate CNAME record for you. You will be prompted, as part of the process for customizing your Edge Services domain, to create this record yourself with your domain provider.
+
+
+
+## How to create a CNAME record
+
+Log into your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services endpoint for your bucket or Load Balancer origin. This endpoint can be retrieved from the Scaleway console.
+
+The interface used by different domain providers varies, but creating your CNAME record may look like one of the following examples:
+
+| Record | Destination |
+|--------------------------------------------|------------------------------------------|
+| `my-chosen-subdomain.beautiful-domain.com` | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.` |
+
+| Subdomain | Target host |
+|--------------------------------------------|------------------------------------------------|
+| `my-chosen-subdomain` | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.` |
+
+| Host record | Points to |
+|--------------------------------------------|------------------------------------------------|
+| `my-chosen-subdomain` | `pipeline-id-or-bucket-name.svc.edge.scw.cloud.` |
+
+| `my-chosen-subdomain` | Record Type | Value |
+|--------------------------------------------|-----------------|------------------------------------------------|
+| `@` | `CNAME` | is an alias of `pipeline-id-or-bucket-name.svc.edge.scw.cloud.`|
+
+
+The trailing dot at the end of the target endpoint (`pipeline-id-or-bucket-name.svc.edge.scw.cloud.`) is implicitly added by some domain and DNS providers, and must be explicitly added for others. Check with yours whether the dot is necessary.
+
+
+You may also see a `TTL` field, which stands for **T**ime **T**o **L**ive. This tells the DNS resolver how long it can cache this record, before it must re-check the origin source in case something has changed. TTL is measured in seconds, and the default value is usually 12 hours (43200 seconds) or 24 hours (86400 seconds).
+
+ ## Troubleshooting DNS and subdomain errors
+
+When setting up your customized subdomain with Edge Services, you have the option to carry out a verification check on the CNAME record (if your domain is managed with an external provider). Edge Services will query the subdomain and check that it resolves correctly to the Edge Services endpoint. If there is a problem, you will see an error message:
+
+
+
+An error message may also display at a later point from your Edge Services dashboard if a problem is detected at any point with your CNAME record or subdomain:
+
+
+
+See the table below for help with troubleshooting these errors:
+
+| Error message | Solution |
+|-------------------------------------------|---------------------------------------------------------------------|
+| No CNAME record found | Make sure you have created a valid DNS record of type **CNAME** (not **A**, **AAAA** or another type), where your subdomain points to the Edge Services endpoint. |
+| Incorrect CNAME | Make sure your CNAME record points to the Edge Services endpoint in the format `bucket-name.svc.edge.scw.cloud.`, and that you have replaced `pipeline-id-or-bucket-name` with the name of your bucket in the case of an Object Storage origin, or the pipeline ID in the case of a Load Balancer origin. |
+| Domain does not exist | You must own the domain name you are attempting to configure. If you do not already own the domain name, you cannot create a subdomain or CNAME record for it. Register the domain name, for example using our [Domains and DNS](/domains-and-dns/how-to/register-internal-domain/) product, then create a CNAME record for the subdomain. Otherwise, ensure you did not make a typo when entering the domain name into the Scaleway console. |
+| scw.cloud is forbidden | You cannot use subdomains of the `scw.cloud` domain, as the domain is owned and managed by Scaleway and you cannot create DNS records for it. Use your own domain and subdomain. |
+| Invalid Top Level Domain | Make sure the Top-Level Domain (e.g. `.com`, `.fr`) you entered is correct. |
+| Root domain not allowed | You cannot use a root domain alone to customize Edge Services (e.g. `example.com`. Make sure you use a subdomain (e.g. `blog.example.com`)) | |
+| Subdomain must be a correctly-formatted, fully-qualified subdomain name | Make sure the subdomain name you entered is [correctly formatted](https://en.wikipedia.org/wiki/Domain_name#Domain_name_syntax), e.g. `foo.example.fr`. |
+| Record already exists for this FQDN in your DNS zone | Choose a different subdomain, or delete the existing DNS record. |
+
+Note that if your domain is managed by Scaleway Domains and DNS and you therefore have an auto-created CNAME record, you should **not** attempt to delete it or modify it in any way. Scaleway will take care of deleting the CNAME record if and when you deactivate Edge Services.
diff --git a/pages/edge-services/reference-content/index.mdx b/pages/edge-services/reference-content/index.mdx
new file mode 100644
index 0000000000..1fed4496b5
--- /dev/null
+++ b/pages/edge-services/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Edge Services - Additional Content
+ description: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Edge Services. Optimize creation of your SSL/TLS certificates and CNAME records with our comprehensive reference guide.
+content:
+ h1: Edge Services - Additional Content
+ paragraph: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Edge Services. Optimize creation of your SSL/TLS certificates and CNAME records with our comprehensive reference guide.
+---
diff --git a/pages/edge-services/reference-content/ssl-tls-certificate.mdx b/pages/edge-services/reference-content/ssl-tls-certificate.mdx
new file mode 100644
index 0000000000..d9f6431f37
--- /dev/null
+++ b/pages/edge-services/reference-content/ssl-tls-certificate.mdx
@@ -0,0 +1,231 @@
+---
+meta:
+ title: SSL/TLS Certificates for Edge Services
+ description: Discover how to configure SSL/TLS certificates for Scaleway Edge Services pipelines. Follow our comprehensive guide to secure your custom domains and ensure data protection.
+content:
+ h1: SSL/TLS Certificates for Edge Services
+ paragraph: Discover how to configure SSL/TLS certificates for Scaleway Edge Services pipelines. Follow our comprehensive guide to secure your custom domains and ensure data protection.
+tags: edge-services pipeline ssl-tls certificate ssl tls pem certificate-authority root-certificate pem chain ca
+dates:
+ validation: 2024-07-25
+categories:
+ - network
+---
+
+This document contains information to help you with SSL/TLS certificates that enable your origin bucket or Load Balancer content to be served over HTTPS, through your customized [Edge Services](/edge-services/) domain.
+
+## Introduction
+
+### What is an SSL/TLS certificate?
+
+An SSL/TLS certificate is a digital certificate that enables an encrypted connection between a client and a web server over HTTPS.
+
+You may hear certificates referred to as “SSL certificates”, “TLS certificates” or “SSL/TLS certificates”. These are all the same thing. SSL (Secured Socket Layer) was the protocol initially used for encryption, though it has now been replaced with TLS (Transport Layer Security).
+
+SSL/TLS certificates contain a **public key**, which corresponds to a separate **private key**. These work as a pair. When a client wants to establish an encrypted connection to a host, it requests the host's certificate. The host shares the certificate, which includes the public key (the private key is never shared and is kept by the host). The client checks the certificate, and uses the host's public key to encrypt the data that it transfers to the host. The host uses its private key to decrypt the data that has been encrypted by the public key.
+
+The private key is also used by the host for generating digital signatures, while the public key is used by clients for verifying those signatures.
+
+### When and why do I need an SSL/TLS certificate for Edge Services?
+
+When you create an Edge Services pipeline, initially your [origin's](/edge-services/concepts/#origin) content is served through the standard Edge Services endpoint, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. Scaleway's own SSL/TLS certificate, which covers this subdomain, is used to establish the encrypted connection between client and host. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about creating SSL/TLS certificates.
+
+However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), Scaleway's own SSL/TLS certificate can no longer be used to establish encrypted connections to your subdomain. Client connections are now initially going to a different domain which needs to be "guaranteed" by its own certificate (despite the CNAME record for the subdomain pointing to the Scaleway endpoint).
+
+Therefore, when you customize your Edge Services endpoint with a subdomain, you are prompted to generate or upload an SSL/TLS certificate for that subdomain.
+
+
+Even if you have an Edge Services pipeline for a Load Balancer origin, and you have already configured your Load Balancer with a certificate for HTTPS (using Let's Encrypt or a custom certificate), you will still need to follow the steps of this document to provide a certificate for your Edge Services pipeline's customized domain.
+
+
+## How can I provide an SSL/TLS certificate for my Edge Services customized domain?
+
+You will be prompted to choose one of the following options when [customizing your domain](/edge-services/how-to/configure-custom-domain/):
+
+- **Generate a Let's Encrypt certificate**: Scaleway generates a free, managed Let's Encrypt certificate for your domain and automatically renews it as necessary.
+
+- **Select an existing certificate from Secret Manager**: You select a certificate that you have already uploaded in [Scaleway Secret Manager](/secret-manager/quickstart/).
+
+- **Manually import a certificate into Secret Manager**: You can manually create your own certificate and import it. It will be stored in Scaleway Secret Manager (check the [dedicated pricing page](https://www.scaleway.com/en/pricing/?tags=securityandidentity)).
+
+## Generating a managed Let's Encrypt certificate
+
+This is the hassle-free option if you do not want to create or manage your own SSL/TLS certificate. Scaleway takes care of generating a certificate for your customized domain in the correct format. The certificate is automatically renewed before it expires. This option is available for free: it costs you nothing for Scaleway to generate and manage a Let's Encrypt certificate for your domain.
+
+You must ensure that you have correctly set the [CNAME record](/edge-services/reference-content/cname-record/) for your domain. Without having done this, the Let's Encrypt certificate option in the console will not be available. It is also important to check the CNAME is correctly set up so that the certificate is properly generated and reviewed.
+
+Note that you will not have access to the generated certificate itself in Secret Manager or elsewhere. It is entirely generated and managed "behind the scenes", and is not configurable by the user. If you reset your domain, or delete your Edge Services, Scaleway automatically deletes the generated Let's Encrypt certificate.
+
+### Troubleshooting Let's Encrypt certificate errors
+
+#### Errors
+
+If there is a problem generating your managed Let's Encrypt certificate, an error will be displayed. See the table below for help resolving these errors.
+
+| Error | Solution |
+| ------------------------------------------------------------------------|---------------------------------------------------------------------|
+| Too many certificates already issued for this domain | Wait, before retrying. This error occurs when you hit the limit of generating 50 Let's Encrypt certificates in a rolling 7 day period for the same domain. |
+| Internal managed certificate error | There has been an unspecified error in generating a managed Let's Encrypt certificate for your subdomain. Try [resetting your domain to the default endpoint](/edge-services/how-to/configure-custom-domain/#how-to-reset-your-customized-domain), and then recustomizing it again, to trigger generation of a new Let's Encrypt certificate. If that fails, [open a support ticket](https://console.scaleway.com/support/tickets/create). |
+| Certificate cannot be renewed - Your CNAME record is no longer accurate | Your CNAME record has either been deleted or modified. Without a correct CNAME record, we cannot renew your managed Let's Encrypt certificate. [Rectify your CNAME record](/edge-services/reference-content/cname-record/#how-to-create-a-cname-record), and when Edge Services detects the correct record exists, your certificate will be automatically renewed. |
+
+## Using your own certificate
+
+If you wish to use your own certificate, rather than the option of generating a managed Let's Encrypt certificate, take into account the following points.
+
+### Accepted certificate types
+
+Types of validation:
+
+- ❌ **Self-signed certificates**. Certificates for Edge Services must be signed by a trusted Certificate Authority (CA)
+- ✅ **Domain Validated Certificate**. The CA simply checks that the applicant owns the domain.
+- ✅ **Extended/Organization Validation Certificate**. The applicant must pass more in-depth validation procedures and checks by the CA.
+
+Types of domain coverage:
+
+- ✅ **Single domain certificate**. Secures a single domain or subdomain. Note that the certificate must be for `your-sub.domain.com`, where the subdomain corresponds to the [subdomain for Edge Services](/edge-services/how-to/configure-custom-domain/). A single domain certificate simply for `yourdomain.com` would not be acceptable, as it would not cover the subdomain for Edge Services.
+- ✅ **Wildcard certificate**. Secures multiple subdomains for a domain, using a wildcard `*` symbol. The **Common Name** of the certificate should look like `*.yourdomain.com`.
+- ✅ **Multi-domain (MD) / Subject Alternative Name (SAN) / Unified Communications Certificate (UCC) certificate**. Secures multiple explicitly-defined fully qualified domain names (`www.yourfirstdomain.com`, `sub.yourfirstdomain.com`, `yourfirstdomain.com`, `yourseconddomain.com`, `sub.yourseconddomain.com` etc.)
+
+### PEM format certificate chain
+
+Edge Services requires that you import your certificate as a PEM-formatted certificate chain, which includes the private key. PEM format is Base64 encoded ASCII, and by definition includes lines stating `-----BEGIN x-----` and `-----END x-----`.
+
+Your PEM formatted certificate chain should look like this:
+
+```
+-----BEGIN PRIVATE KEY-----
+(private key here)
+-----END PRIVATE KEY-----
+-----BEGIN CERTIFICATE-----
+(primary certificate (aka server certificate) here)
+-----END CERTIFICATE-----
+-----BEGIN CERTIFICATE-----
+(intermediate certificate here)
+-----END CERTIFICATE-----
+-----BEGIN CERTIFICATE-----
+(root certificate here)
+-----END CERTIFICATE-----
+```
+
+| Section | Contains | Subject (issued for) | Issued and signed by |
+|--------------------------|------------------------------------------------------------------|------------------------|----------------------|
+| Private key | The private key file for the certificate | | |
+| Primary/server certificate | The certificate issued by the CA for your domain name | Your name and public key | CA |
+| Intermediate certificate | The intermediate certificate chaining your primary certificate to the root certificate | CA's name and public key. | Root CA |
+| Root certificate | The root certificate by the CA, for the trusted CA itself | The Root CA's name and public key | Root CA (self signed) |
+
+Note that in certain cases an intermediate certificate may not be necessary, if the root certificate chains directly to the primary/server certificate. The crucial thing is that the subject and issuers of each certificate form a coherent chain of validation. If a certificate is issued by an authority that is not present in the chain, an error will occur.
+
+
+
+You can use the [OpenSSL](https://www.openssl.org/) utility to convert certificates and keys from other formats to PEM, from the command line. Once installed, use a command like the following:
+
+```sh
+openssl x509 -in cert.crt -out cert.pem
+```
+
+```sh
+openssl x509 -in cert.der -out cert.pem
+```
+
+```sh
+openssl x509 -in cert.cer -out cert.pem
+```
+
+When you have your key, your server certificate and your root certificate all in separate files, you can use the `cat` command to chain them together into one file, ready to be copied and pasted:
+
+```sh
+cat private_key.pem cert.pem root_cert.pem > cert_chain.pem
+```
+
+
+
+### Tips for creating a certificate
+
+In general, SSL/TLS certificates can either be **self-signed** (signed by the subject of the certificate, e.g. the owner of the domain) or **CA-signed** (signed by a third party **C**ertificate **A**uthority which is publicly trusted).
+
+**Self-signed certificates cannot be used with Edge Services, all certificates must be signed by a CA that is known and trusted by Edge Services.**
+
+To get an SSL/TLS certificate for your domain or subdomain, you need to generate a Certificate Signing Request (CSR) and submit it to a Certificate Authority (CA) for them to validate your domain, who then send you a signed certificate. You may be able to carry out this procedure via your hosting provider, or from the command line.
+
+CAs of private companies whose primary business is not SSL or domains may not be trusted by Edge Services. If you encounter a self-signed certificate error with Edge Services, but you believe your certificate is legitimately signed by an official CA, [open a support ticket](https://console.scaleway.com/support/tickets) to tell us.
+
+
+
+To get a working Let's Encrypt certificate using certbot on the command line, follow the steps below:
+
+1. Install [certbot](https://certbot.eff.org/) on your machine.
+2. Open a terminal and run the following command, inserting your subdomain where shown:
+ ```bash
+ sudo certbot certonly --manual --preferred-challenges dns -d
+ ```
+ The command returns a token and asks you to create a TXT record in your DNS.
+3. Go to your domain/DNS provider and create a TXT record. The record name should be `_acme-challenge.your-subdomain.your-domain.ext` and the record must contain the token provided by certbot. Make sure the record has a short TTL in case you have to modify it for debugging purposes.
+4. Return to the terminal and press `Enter` once your record is ready.
+ Certbot starts the verification process. If it succeeds, the certificate is downloaded to your machine in two files: the private key and the certificate.
+5. Concatenate the two files into one, using the following command:
+ ```bash
+ cat privkey.pem fullchain.pem > certificate.pem
+ ```
+6. Delete the TXT record from your DNS.
+
+
+
+### Uploading your certificate
+
+When you [configure your customized domain](/edge-services/how-to/configure-custom-domain/) with Edge Services for the first time, you are prompted to upload your certificate. You can do so in two ways:
+
+ - Select an existing certificate that you have stored in a secret in [Scaleway Secret Manager](/secret-manager/quickstart/). The secret must be of the **certificate** type in order to be visible to Edge Services. The type can be defined when creating a secret via the [API](https://www.scaleway.com/en/developers/api/secret-manager/#path-secrets-create-a-secret), but not via the console. For that reason, if you prefer to use the console to create your certificates, we suggest using the next option:
+ - Manually import a certificate into Scaleway Secret Manager, directly from the Edge Services **Configure domain** wizard (copy and paste the PEM formatted chain). Your certificate will be automatically stored in Secret Manager, held in a secret that automatically inherits the type "certificate".
+
+### Keeping your certificate up to date
+
+SSL/TLS certificates all expire at some point. If your certificate expires before you upload a new one, you will see an error like this on your Edge Services dashboard:
+
+
+
+You must renew your certificate or create a new one. A number of tools are available to ensure that certificates are automatically renewed before expiry, for example [Certbot for LetsEncrypt](https://eff-certbot.readthedocs.io/en/stable/using.html#renewing-certificates). However, since Certbot or other tools for automatically renewing certificates are not currently integrated into Edge Services, you will need to manually update the certificate via the Scaleway console.
+
+When you have your up to date certificate, go to [Secret Manager](https://console.scaleway.com/secret-manager/secrets) in the console, and access the secret that contains your certificate. [Create a new version](/secret-manager/how-to/create-version/) of the secret, to hold the up to date certificate. Edge Services will automatically detect and use the most recent enabled version of the secret. You can nonetheless choose to disable or delete the old version(s) as you prefer, which will also save your billing costs (since you are billed per version).
+
+
+
+If you change your customized subdomain to something new, you will need to generate and import a new certificate for that subdomain. In this case, it is recommended to create a new [secret](/secret-manager/concepts/#secret) to hold the new certificate, rather than creating a new version of an existing secret.
+
+
+
+### Troubleshooting certificate errors
+
+#### Errors
+
+If Edge Services detects a problem with your certificate, an error will be displayed. See the table below for help resolving these errors.
+
+| Error | Solution |
+|-------------------------------------------------------------------------|---------------------------------------------------------------------|
+| Certificate format | Make sure your certificate is in [PEM format](#pem-format-certificate-chain). |
+| Certificate private key format | Make sure your private key is in [PEM format](#pem-format-certificate-chain).|
+| Missing server certificate | Make sure the server certificate (which validates your own subdomain) is included in the [PEM-formatted chain](#pem-format-certificate-chain).|
+| Missing private key | Make sure your private key is included in the [PEM-formatted chain](#pem-format-certificate-chain).|
+| Missing root certificate | Make sure a valid root certificate is included in the [PEM-formatted chain](#pem-format-certificate-chain). |
+| Wrong order | Make sure the server certificate (which validates your own subdomain) is listed before the intermediate and root certificates in the [PEM-formatted chain](#pem-format-certificate-chain) |
+| Too many private keys | Make sure the [PEM-formatted chain](#pem-format-certificate-chain) includes only one corresponding private key |
+| Self-signed certificates not allowed | Create and upload a certificate issued by a recognized [certificate authority](#tips-for-creating-a-certificate). If you receive this error but believe your certificate is legitimately signed by an official CA, [open a support ticket](https://console.scaleway.com/support/tickets) to tell us. |
+| Invalid intermediate or root certificate authority | Make sure each **Issuer** field matches the **Subject** of the next certificate in the [PEM-formatted chain](#pem-format-certificate-chain).|
+| Incorrect root certificate | Make sure your server certificate chains up to the provided root(s) certificate(s) in the [PEM-formatted chain](#pem-format-certificate-chain). |
+| Private key and certificate mismatch | Make sure the private key in the [PEM-formatted chain](#pem-format-certificate-chain) matches the server certificate. |
+| Subdomain and server certificate mismatch | Make sure the subdomain you configured for Edge Services matches that of the server certificate. |
+| Certificate expired | [Create a new certificate](#keeping-your-certificate-up-to-date) and import it. |
+
+If any of these errors are detected while you are initially configuring your subdomain, you will be blocked from continuing until the error is fixed.
+
+However, these errors may also be detected and displayed on your Edge Services dashboard even after you have initially successfully configured your subdomain and certificate. This could be the case, for example, if your certificate has since expired, you have modified your subdomain without modifying the certificate, or you have modified the certificate in Secret Manager. In this case, your initial certificate will remain in use by Edge Services until the error is fixed, but clients may see an error in their browser as they try to access your customized domain.
+
+To fix the problem, you must generate a valid certificate, and then do one of the following:
+
+- [Use Edge Services to import a new certificate directly](/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate)
+- [Create a new secret](/secret-manager/how-to/create-secret/) to hold the certificate in Secret Manager, and [edit your customized endpoint with Edge services](/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate) to tell it to use this secret
+- [Create a new version](/secret-manager/how-to/create-version/) of the existing secret holding your expired certificate, where the new version contains a valid certificate. If Edge Services is already using this secret, it will automatically detect and use the new version - it always uses the most recent enabled version of a secret.
+
+#### Secret not visible for selection in Edge Services
+
+You may find that a certificate you have stored in Secret Manager is not available for selection from Edge Services. This is probably because the secret does not have the "certificate" type, which is necessary for it to be visible to Edge Services. The "type" of a secret can be defined when creating a secret via the [API](https://www.scaleway.com/en/developers/api/secret-manager/#path-secrets-create-a-secret), but not via the console. For that reason, if you prefer to use the console to create your certificates, we suggest manually importing the certificate via Edge Services rather than via Secret Manager. This way, it will automatically inherit the "certificate" type.
\ No newline at end of file
diff --git a/pages/edge-services/reference-content/understanding-ga.mdx b/pages/edge-services/reference-content/understanding-ga.mdx
new file mode 100644
index 0000000000..8eadb53a03
--- /dev/null
+++ b/pages/edge-services/reference-content/understanding-ga.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: Understanding Edge Services General Availability
+ description: Scaleway Edge Services has left Public Beta and gone into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take.
+content:
+ h1: Understanding Edge Services General Availability
+ paragraph: Scaleway Edge Services has left Public Beta and gone into General Availability. This page answers all your questions about the timeline, pricing and any action you need to take.
+tags: edge-services public-beta general-availability pricing billing ga
+dates:
+ validation: 2024-10-16
+ creation: 2024-09-27
+categories:
+ - network
+---
+
+Scaleway Edge Services has left Public Beta and gone into General Availability. Read on to find out more about this transition.
+
+## Edge Services Public Beta
+
+Edge Services for Object Storage and Load Balancer was in Public Beta until November 1 2024. This meant that the product was ready to be tested by customers, but some features may have been missing, and usage was intended for test environments rather than production. Edge Services was free to use during Public Beta, and was not billed.
+
+## Edge Services General Availability
+
+From **November 1st 2024** Edge Services went into General Availability, for both Object Storage and Load Balancer usage. This means that:
+- We considered that the product was ready for production environments.
+- The product was no longer be free to use, and is now billed.
+
+## Edge Services pricing
+
+
+Check out the [Edge Services pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for full pricing details.
+
+
+Edge Services is billed via **subscription**. Three different subscription plans are available, each including different amounts of monthly usage for **cache size** and **number of pipelines**. If your consumption of Edge Services in a given month exceeds the cache size and number of pipelines included in your subscription, you are billed for this extra usage on top of your plan.
+
+
+An Edge Services pipeline consists of an origin for which Edge Services requests and caches content, and an endpoint from which this content is served via Edge Services. In the case of Object Storage during Public Beta, a pipeline corresponded to a bucket Edge Services was enabled on. If Edge Services was enabled on three different buckets, this equaled three pipelines. In the case of Load Balancer, pipelines were already an explicit concept in the console.
+
+
+At the start of October 2024, current Edge Services users received an email with full details of the three subscription plans.
+
+Pricing plan details can also be viewed on the [Scaleway pricing page](https://www.scaleway.com/en/pricing/network/).
+
+## Transitioning from free to paid use
+
+At the end of October 2024, we automatically selected the most cost-effective subscription plan for each existing Edge Services user, based on their usage. When billing started on the 1st of November 2024, users therefore saw in the [Scaleway console](https://console.scaleway.com/) that they were subscribed to the plan we had selected for them.
+
+Billing for Edge Services is pro-rata, and you can cancel or change your subscription plan at any time.
+
+
+If you did not wish to be billed for Edge Services, you were warned that you must disable it on all your buckets, and delete any Load Balancer pipelines you had created **before November 1st 2024**.
+
+
+### Estimating your billing and understanding pricing
+
+Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page.
+
+## Further support
+
+If you have any questions about the transition to Edge Services General Availability, please feel free to get in touch on the `#edge-services-beta` channel on the [Scaleway Community Slack](https://slack.scaleway.com/).
\ No newline at end of file
diff --git a/pages/edge-services/reference-content/understanding-pricing.mdx b/pages/edge-services/reference-content/understanding-pricing.mdx
new file mode 100644
index 0000000000..7b923a02ce
--- /dev/null
+++ b/pages/edge-services/reference-content/understanding-pricing.mdx
@@ -0,0 +1,164 @@
+---
+meta:
+ title: Understanding Edge Services pricing
+ description: Find answers to all your questions about how pricing for Edge Services works, how to calculate your billing, and the different subscription plans available. Different scenarios are presented, with explanations of how you would be billed in each one.
+content:
+ h1: Understanding Edge Services pricing
+ paragraph: Find answers to all your questions about how pricing for Edge Services works, how to calculate your billing, and the different subscription plans available. Different scenarios are presented, with explanations of how you would be billed in each one
+tags: edge-services general-availability pricing billing subscription-plan pro-rata
+dates:
+ validation: 2024-10-16
+ creation: 2024-10-16
+categories:
+ - network
+---
+
+Find out everything you need to know about how Edge Services is billed in this document.
+
+## Edge Services billing basics
+
+Edge Services billing is based on [monthly subscription plans](https://www.scaleway.com/en/pricing/network/#edge-services). Three plans are available, with different prices and consumption limits:
+
+- **Starter**
+- **Professional**
+- **Advanced**
+
+When you subscribe to a plan, you are billed its flat monthly fee, which allows you to:
+
+- Run a fixed maximum number of Edge Services [pipelines](/edge-services/concepts/#pipeline) for the month. They can be for Object Storage or Load Balancer origins, or a mixture of both.
+- Egress a fixed maximum amount of data from all your pipelines' [caches](/edge-services/concepts/#cache).
+
+If you subscribe to a plan, and exceed its monthly limits for pipelines or cache data, you will incur additional charges that month.
+
+Essentially, your Edge Services monthly bill is made up of your **monthly subscription plan price** + **any additional pipeline charges incurred** + **any additional cache charges incurred**.
+
+For full details of the price and limits of each plan, refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services). Subscription plans are scoped to a single Scaleway [Project](/organizations-and-projects/concepts/#project).
+
+## Keeping track of your Edge Services consumption
+
+You can check the number of pipelines you have at any one time in the **Pipelines** tab of the Edge Services dashboard in the Scaleway console. [Scaleway Cockpit](/edge-services/how-to/monitor-cockpit/) can be used to monitor the data egressing from your Edge Services caches.
+
+## Included usage vs additional charges
+
+Additional charges apply when you either:
+
+- Have more pipelines in existence (at any given time) than the limit of your monthly plan
+- Egress more data from all your pipelines' caches combined, than the limit of your monthly plan
+
+Read on to understand more about how additional charges are applied.
+
+### Additional pipeline charges
+
+Additional pipeline charges are based on a monthly fee per additional pipeline. This monthly fee is applied pro-rata based on how long you had additional pipelines in existence during the calendar month.
+
+For example:
+
+
+The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information.
+
+
+- For the entire month of November, you are subscribed to the **Starter** plan, which has a limit of 1 pipeline.
+- You start the month with 1 pipeline (A) in existence, which runs until the end of the month.
+- On November 5 you create a second pipeline (B), which you later delete on November 10.
+- On November 15 you create another pipeline (C), which runs until the end of the month.
+
+There are 30 days in the month of November.
+- Pipeline A falls within the limit of your Starter plan, so is not billed.
+- Pipeline B was an additional pipeline which existed for 5 days
+- Pipeline C is an additional pipeline which existed for 15 days
+
+Your November Edge Services billing, in terms of additional pipeline charges, is therefore calculated as follows:
+
+`({Monthly flat fee for an additional pipeline} / 30 days) * 5 days` + `({Monthly flat fee for an additional pipeline} / 30 days) * 15 days`
+e.g. `(4 / 30) * 5 = €0.67` + `(4 / 30) * 15 = €2` = `€2.67`
+
+### Additional cache charges
+
+Cache consumption is based on the volume of data egressed from all your Edge Services pipelines' caches combined, in a given month. The transfer of data from the origin bucket or Load Balancer into the cache, or directly from the origin to a user, does not count towards the limit of your plan, and does not incur any additional charges.
+
+For every extra GB of data that is egressed from your Edge Services caches in a month, **beyond** the limit of your monthly plan, an additional charge applies.
+
+For example:
+
+
+The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information.
+
+
+- For the entire month of November, you are subscribed to the **Starter** plan, which has a limit of 100 GB of cache data.
+- Over the course of the month, a total of 300 GB of data is egressed from your Edge Services caches.
+
+You consumed 200 GB of cache data that was not included within your monthly plan. Your November Edge Services billing, in terms of additional cache charges, is therefore calculated as follows:
+
+`{Fee per GB of additional cache} * 200 GB`
+e.g. `0.0135 * 200 = €2.70`
+
+## Changing your subscription plan
+
+You can upgrade or downgrade your subscription plan at any time. Read on to understand how changing plan mid-month affects your billing.
+
+### Monthly plan price
+
+You will be billed pro-rata for the old and new monthly plan prices, based on how long you were subscribed to each plan during the billing month.
+
+For example:
+
+
+The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information.
+
+
+- From November 1-10 you are subscribed to the **Starter** plan.
+- On November 11, you switch to the **Professional** plan.
+- You remain subscribed to the **Professional** plan for the rest of the month (ending November 30)
+
+There are 30 days in the month of November, and you spent 10 of them subscribed to the Starter plan, and 20 of them subscribed to the Professional plan. Your November Edge Services billing, in terms of the monthly plan price, is therefore calculated as follows:
+
+`({Monthly price for Starter plan} / 30 days) * 10 days` + `({Monthly price for Professional plan} / 30 days) * 20 days`
+e.g. `(0.99 / 30) * 10 = 0.33` + `(12.99 / 30) * 20 = 8.66 ` = `€8.99`
+
+### Pipeline charges
+
+Any additional pipeline charges accumulated when you had more pipelines in existence than the previous plan's limit will remain on your monthly bill. From the moment you change your plan, you can consume pipelines up to the new plan's monthly limit without being charged.
+
+Additional pipeline charges are based on a monthly fee per additional pipeline. This monthly fee is applied pro-rata based on how long you had additional pipelines in existence during the calendar month.
+
+For example:
+
+
+The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information.
+
+
+- From November 1-10 you are subscribed to the **Starter** plan, which has a limit of 1 pipeline.
+- You have 2 pipelines in existence during these 10 days.
+- On November 11, you upgrade to the **Professional** plan, which has a limit of 10 pipelines.
+- You create 8 more pipelines, which you keep for the rest of the month: you finish the month with 10 pipelines.
+
+There are 30 days in the month of November. For 10 of these days, you had an extra pipeline beyond the limits of your **Starter** plan. After upgrading, and even after creating more pipelines, you were within the pipeline limits of your new plan. Your November Edge Services billing, in terms of the additional pipeline charges, is therefore calculated as follows:
+
+`({Monthly flat fee for an additional pipeline} / 30 days) * 10 days`
+e.g. `(4 / 30) * 10 = €1.33`
+
+### Cache charges
+
+Any additional cache charges accumulated when you exceeded your previous plan's cache limit will remain on your monthly bill. From the moment you change your plan, your cache consumption resets to 0. During the rest of the month, you can consume cache up to the new plan's limit without being charged.
+
+
+- If you **downgrade** your plan, all the data egressed from the cache within the hour of changing plans will count towards the cache consumption of the new plan.
+- If you **upgrade** your plan, all the data egressed from the cache within the hour of changing plans will count towards the cache consumption of the old plan.
+
+
+For example:
+
+
+The example prices and limits used below are subject to change. You should always refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services) for the most up to date information.
+
+
+- From November 1-10 you are subscribed to the **Starter** plan, which has a cache limit of 100 GB.
+- From November 1-10 you consume 300 GB of cache data.
+- On November 11, you upgrade to the **Professional** plan, which has a limit of 1 TB of cache data. Your cache usage resets to 0.
+- Between November 11 and the end of the month, you consume 1 TB of cache data.
+
+You consumed 200 GB of cache data that was not included within your monthly Starter plan, between November 1-10. For the rest of the month, you were within the limits of your new Professional plan. Your November Edge Services billing, in terms of the additional cache charges, is therefore calculated as follows:
+
+`{Fee per GB of additional cache} * 200 GB`
+e.g. `0.0135 * 200 = €2.70`
+
diff --git a/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx b/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx
new file mode 100644
index 0000000000..7fc794bfd2
--- /dev/null
+++ b/pages/elastic-metal/api-cli/elastic-metal-with-api.mdx
@@ -0,0 +1,157 @@
+---
+meta:
+ title: Deploying an Elastic Metal server with one API call
+ description: Learn how to deploy a Scaleway Elastic Metal server on your favorite OS with a single API command.
+content:
+ h1: Deploying an Elastic Metal server with one API call
+ paragraph: Learn how to deploy a Scaleway Elastic Metal server on your favorite OS with a single API command.
+tags: baremetal elastic metal cloud server dedicated elastic-metal api-call
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - bare-metal
+ - elastic-metal
+---
+
+Scaleway's [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) provide 100% dedicated resources while offering the flexibility and scalability of the cloud, including hourly billing and full customization. The hardware is entirely dedicated to you — free from virtualization, overallocation, or neighboring tenants.
+
+Elastic Metal servers also feature a robust [REST API](https://www.scaleway.com/en/developers/api/elastic-metal/) that enables seamless automation of tasks and deployments. Integration with tools like [Terraform](https://www.terraform.io/) further streamlines infrastructure management.
+
+The **one-command deployment feature** accelerates server provisioning by combining delivery and setup into a single API call. This simplifies server provisioning, ensuring your machine is fully operational in less than 15 minutes.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+
+## Deploying Elastic Metal servers using the API
+
+Besides creating your Elastic Metal servers from the graphical [Scaleway console](/elastic-metal/how-to/create-server/), you can also create and manage them directly from the command line using the [CLI-tool](https://github.com/scaleway/scaleway-cli) or the [API](https://www.scaleway.com/en/developers/api/elastic-metal/).
+
+
+ You need to [generate API keys](/iam/how-to/create-api-keys/) to access the Scaleway API.
+
+
+1. Open a terminal on your computer and set your secret API key, your SSH key ID, and your Project ID as variables.
+ ```
+ export SCW_SECRET_KEY=""
+ export SCW_SSH_KEY=""
+ export SCW_PROJECT_ID=""
+ ```
+2. Retrieve a list of all operating systems available in the desired Availability Zone.
+ ```
+ curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/offers -H "X-Auth-Token: $SCW_SECRET_KEY" | jq . | grep "EM-"
+ ```
+
+ A list of all available offers displays. Take note of the ID of the offer you want to deploy, as you need it in a later step.
+
+ ```
+ "name": "EM-A210R-SATA",
+ "name": "EM-L101X-SATA",
+ "name": "EM-A410X-SSD",
+ "name": "EM-B111X-SATA",
+ "name": "EM-B112X-SSD",
+ "name": "EM-B211X-SATA",
+ "name": "EM-B212X-SSD",
+ "name": "EM-L110X-SATA",
+ "name": "EM-B311X-SATA",
+ "name": "EM-B312X-SSD",
+ "name": "EM-T210E-NVME",
+ "name": "EM-T510X-NVME",
+ ```
+3. Retrieve a list of all available operating systems available in the desired Availability Zone (in our case, `fr-par-2`).
+ ```
+ curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/os -H "X-Auth-Token: $SCW_SECRET_KEY" | jq .
+ ```
+
+ You will receive a JSON-formatted list of all operating systems available, and their associated ID. Take note of the ID of the image you want to install:
+
+ ```
+ {
+ "total_count": 8,
+ "os": [
+ {
+ "id": "03b7f4ba-a6a1-4305-984e-b54fafbf1681",
+ "name": "Ubuntu",
+ "version": "20.04"
+ },
+ {
+ "id": "60f5d1e3-fa69-45af-9fc0-c9e3c114dd09",
+ "name": "Ubuntu",
+ "version": "19.10"
+ },
+ [...]
+ ]
+ }
+ ```
+4. Create the Elastic Metal server from the API using cURL and the `POST` command on the endpoint `/baremetal/v1/zones/fr-par-2/servers`:
+
+ The syntax to [create the server](https://www.scaleway.com/en/developers/api/elastic-metal/#path-servers-create-an-elastic-metal-server) is as follows:
+ ```
+ {
+ "offer_id": "",
+ "project_id": "$SCW_SECRET_KEY",
+ "name": "",
+ "description": "",
+ "tags": [
+ ""
+ ],
+ "install": {
+ "os_id": "",
+ "hostname": "",
+ "ssh_key_ids": [
+ ""
+ ]
+ }
+ }
+ ```
+
+ In the following example, we create a **GP-BM1-S** server running on Ubuntu 20.04 LTS:
+
+ ```
+ curl -X POST -H "X-Auth-Token: $SCW_KEY" -H "Content-Type: application/json" -d "{ \"offer_id\": \"7fde3890-9787-488c-ac89-c4e00a4e5f83\", \"project_id\": \"$SCW_PROJECT\", \"name\": \"my-bmaas\", \"description\": \"my server running on ubuntu\", \"tags\": [
+ \"bmaas, tutorial\" ], \"install\": { \"os_id\": \"03b7f4ba-a6a1-4305-984e-b54fafbf1681\", \"hostname\": \"my-bmaas-api\", \"ssh_key_ids\": [ \"$SSH_KEY_ID\" ] }}" https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers | jq .
+ ```
+
+ Again, the API returns a JSON output informing you about the server creation:
+
+ ```
+ {
+ "id": "",
+ "organization_id": "",
+ "name": "my-bmaas",
+ "description": "my server running on ubuntu",
+ "updated_at": "2020-10-05T13:37:02.136789208Z",
+ "created_at": "2020-10-05T13:37:02.136789208Z",
+ "status": "delivering",
+ "offer_id": "7fde3890-9787-488c-ac89-c4e00a4e5f83",
+ "install": {
+ "os_id": "03b7f4ba-a6a1-4305-984e-b54fafbf1681",
+ "hostname": "my-bmaas-api",
+ "ssh_key_ids": [
+ ""
+ ],
+ "status": "to_install"
+ },
+ "tags": [
+ "bmaas, tutorial"
+ ],
+ "ips": [],
+ "domain": "",
+ "boot_type": "normal",
+ "ping_status": "ping_status_unknown",
+ "project_id": "",
+ "zone": "fr-par-2"
+ }
+ ```
+5. The server is being delivered to your account and is automatically being installed on the operating system chosen. You can retrieve the status of the installation using the following API call:
+ ```
+ curl https://api.scaleway.com/baremetal/v1/zones/fr-par-2/servers/{server_id} -H "X-Auth-Token: $SCW_SECRET_KEY" | jq .
+ ```
+
+ Your new Elastic Metal server will be installed and ready to be used in usually less than **15 minutes**, all API features are listed in the [API documentation](https://www.scaleway.com/en/developers/api/elastic-metal/).
+
+For more information about Elastic Metal servers, refer to our [dedicated product documentation](/elastic-metal/) and the [FAQ](/faq/elastic-metal/).
\ No newline at end of file
diff --git a/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx b/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx
new file mode 100644
index 0000000000..0dd62e5dd4
--- /dev/null
+++ b/pages/elastic-metal/api-cli/elastic-metal-with-cli.mdx
@@ -0,0 +1,366 @@
+---
+meta:
+ title: Create and manage Elastic Metal servers with the Scaleway CLI
+ description: Learn to create and manage Elastic Metal servers using the Scaleway CLI in this comprehensive guide.
+content:
+ h1: Create and manage Elastic Metal servers with the Scaleway CLI
+ paragraph: Learn to create and manage Elastic Metal servers using the Scaleway CLI in this comprehensive guide.
+tags: elastic-metal command-line-interface cli scw
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Scaleway's [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) provide you with dedicated servers on-demand, with all the benefits of the cloud, including flexibility and hourly billing. These servers are great for large workloads, big data, and applications that require increased security and dedicated resources. You can create and manage your Elastic Metal servers from the [Scaleway console](https://console.scaleway.com/), via the [API](https://www.scaleway.com/en/developers/api/elastic-metal/) or the [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2).
+
+In this tutorial, you will learn how to use the CLI to create an Elastic Metal server, install an OS, and manage the server lifecycle.
+
+## Scaleway Command Line Interface overview
+
+The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway-cli) allows you to pilot your Scaleway infrastructure directly from your terminal, providing a faster way to administer and monitor your resources. Scaleway CLI is easy to set up and use, and an essential tool for operating efficiently in your cloud environment. The CLI provides many functionalities, including the ability to create and administer Elastic Metal servers.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+- [Installed and configured the Scaleway CLI](/scaleway-cli/quickstart/)
+
+## Creating an Elastic Metal server
+
+
+ - The help info for the `zone` argument informs you that the default zone is `fr-par-2` because Elastic Metal servers are only available in the `fr-par-2` zone at the moment. However, `fr-par-2` is not necessarily the default zone in your configuration. To create a server, you need to either change the default zone in your configuration file (check the location of this file in the output of scw init and change the value for `default zone` to `fr-par-2`), or explicitly target the `fr-par-2` zone in the commands to create and manage your server.
+ - The available server types are the following: `GP-BM1-L` `GP-BM1-M` `GP-BM1-S` `HC-BM1-L` `HC-BM1-S` `HM-BM1-XL` `HM-BM1-M`.
+
+
+
+1. Type the following command in your terminal to create your Elastic Metal server:
+ ```
+ scw baremetal server create name=name-of-your-server type=GP-BM1-L zone=fr-par-2
+ ```
+
+ An output similar to the following displays:
+
+ ```
+ ID 12345678-1234-1234-1234-123456789123
+ OrganizationID 12345678-1234-1234-1234-123456789123
+ ProjectID 12345678-1234-1234-1234-123456789123
+ Name name-of-your-server
+ Description -
+ UpdatedAt 36 seconds ago
+ CreatedAt 36 seconds ago
+ Status delivering
+ OfferID 12345678-1234-1234-1234-123456789123
+ Domain -
+ BootType normal
+ Zone fr-par-2
+ PingStatus unknown
+
+ ```
+
+
+ - For more information on creating an Elastic Metal server, type `scw baremetal server create --help` in your terminal.
+ - You can add additional arguments to your command, such as `description` to add a description of your Elastic Metal server, or `tags.0` to add tags.
+
+2. Write down the ID of your server, as you will need it in the next steps.
+
+ * Type `scw baremetal server list zone=fr-par-2` for a summary of information for your Elastic Metal server, and details for other servers you have previously created.
+ * Use the command `scw baremetal server get ID-of-your-server zone=fr-par-2` for information about a specific server.
+
+
+## Installing an OS
+
+
+ You will need the SSH key ID associated with your account to install your chosen OS on your server.
+
+
+
+1. Type the following command in your terminal to see a list of available OSes:
+
+ `scw baremetal os list zone=fr-par-2`
+
+ An output with available OSes and their associated IDs displays:
+
+ ```
+ ID NAME
+ 82ed3c56-935c-4012-b01f-69070fce1b1d Ubuntu
+ 0aa99516-52bb-4a7d-b9fe-1adc8478c2e0 Debian
+ 58bf948f-8b9b-45c2-9ad6-582c26133f9e Rocky Linux
+ e8fc12e5-cfcd-434a-a8b0-d5f5141baf91 Ubuntu
+ 03b7f4ba-a6a1-4305-984e-b54fafbf1681 Ubuntu
+ 86fd5e3a-b023-4fa8-a3ae-1a194d8cd68c CentOS
+ f2aeab5d-6015-4b7c-b4ed-d76e89093621 Debian
+ 01d6eef6-6b96-47fd-b9f9-3857321abe4f Ubuntu
+ ```
+2. Write down the ID of the OS you want to install.
+3. Type the following command to display the list of your SSH key's ID:
+ ```
+ scw iam ssh-key list
+ ```
+
+ You will see an output similar to the following:
+
+ ```
+ ID NAME CREATED AT UPDATED AT
+ your-ssh-key-ID name-of-your-ssh-key 1 week ago 1 week ago
+ ```
+4. Write down your SSH key ID, as you will need it in the next steps.
+5. Type the following command to install an OS on your Elastic Metal server:
+ ```
+ scw baremetal server install ID-of-your-elastic-metal-server os-id=ID-of-OS-you-want-to-install hostname=hostname-for-your-server ssh-key-ids.0=your-ssh-key-ID zone=fr-par-2
+ ```
+
+
+ If you have multiple SSH keys, you can use the argument `all-ssh-keys=true` to install all your SSH keys on the server.
+
+
+ An output similar to the following displays:
+ ```
+ ID ID-of-your-Elastic-Metal-Server
+ OrganizationID ID-of-your-organization
+ ProjectID ID-of-your-project
+ Name name-of-your-server
+ Description -
+ UpdatedAt 8 minutes ago
+ CreatedAt 11 minutes ago
+ Status ready
+ OfferID ID-of-the-offer
+ IPs.0.ID 12345678-1234-1234-1234-123456789123
+ IPs.0.Address 12.345.67.89
+ IPs.0.Reverse -
+ IPs.0.Version IPv4
+ IPs.0.ReverseStatus unknown
+ IPs.0.ReverseStatusMessage -
+ IPs.1.ID 12345678-1234-1234-1234-123456789123
+ IPs.1.Address 1234:123:4567:8:9123:4567:8912:345
+ IPs.1.Reverse 12345678-1234-1234-1234-123456789123.fr-par-2.baremetal.scw.cloud
+ IPs.1.Version IPv6
+ IPs.1.ReverseStatus active
+ IPs.1.ReverseStatusMessage -
+ Domain 12345678-1234-1234-1234-123456789123.fr-par-2.baremetal.scw.cloud
+ BootType normal
+ Zone fr-par-2
+ Install.OsID ID-of-your-OS
+ Install.Hostname hostname-for-your-server
+ Install.SSHKeyIDs.0 your-ssh-key-ID
+ Install.Status to_install
+ PingStatus up
+ ```
+
+
+ You can check the status of your server with the command `scw baremetal server list zone=fr-par-2`.
+
+
+## Using other CLI commands
+
+There are many other functionalities you can access for your Elastic Metal server via the Scaleway CLI. In the following examples, replace `your-elastic-metal-server-ID` with your server's ID.
+
+
+ * Before powering off your server, we recommend you [log into your server as root](/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS.
+ * Type `scw baremetal server get name-of-server-ID zone=fr-par-2` in your terminal if you are not sure what the IP address of your Elastic Metal server is. It will display in the `IPs.0.Address` field.
+
+
+### Powering on your server
+
+Type the following command in your terminal:
+
+```
+scw baremetal server start your-elastic-metal-server-ID zone=fr-par-2
+```
+The following output displays, and you will see "starting" next to the `Status` field:
+
+```
+ID 12345678-1234-1234-1234-123456789123
+OrganizationID 12345678-1234-1234-1234-123456789123
+ProjectID 12345678-1234-1234-1234-123456789123
+Name name-of-your-server
+Description -
+UpdatedAt 3 seconds from now
+CreatedAt 3 hours ago
+Status starting
+OfferID 12345678-1234-1234-1234-123456789123
+IPs.0.ID 12345678-1234-1234-1234-123456789123
+IPs.0.Address 12.345.67.89
+IPs.0.Reverse -
+IPs.0.Version IPv4
+IPs.0.ReverseStatus unknown
+IPs.0.ReverseStatusMessage -
+IPs.1.ID 12345678-1234-1234-1234-123456789123
+IPs.1.Address IPs.1.Address
+IPs.1.Reverse IPs.1.Reverse
+IPs.1.Version IPv6
+IPs.1.ReverseStatus pending
+IPs.1.ReverseStatusMessage -
+IPs.2.ID IPs.2.ID
+IPs.2.Address 51.159.17.32
+IPs.2.Reverse IPs.2.Reverse
+IPs.2.Version IPv4
+IPs.2.ReverseStatus active
+IPs.2.ReverseStatusMessage -
+Domain your-domain-name
+BootType normal
+Zone fr-par-2
+Install.OsID 12345678-1234-1234-1234-123456789123
+Install.Hostname hostname-for-your-server
+Install.SSHKeyIDs.0 12345678-1234-1234-1234-123456789123
+Install.Status completed
+PingStatus up
+```
+
+### Powering off your server
+
+
+ Before powering off your Elastic Metal server, we recommend you [log into your server as root](/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS.
+
+
+
+Type the following command in your terminal:
+
+```
+scw baremetal server stop your-elastic-metal-server-ID zone=fr-par-2
+```
+
+The following output displays, and you will see "stopping" next to the `Status` field:
+
+```
+ID 12345678-1234-1234-1234-123456789123
+OrganizationID 12345678-1234-1234-1234-123456789123
+ProjectID 12345678-1234-1234-1234-123456789123
+Name name-of-your-server
+Description -
+UpdatedAt 3 seconds from now
+CreatedAt 3 hours ago
+Status stopping
+OfferID 12345678-1234-1234-1234-123456789123
+IPs.0.ID 12345678-1234-1234-1234-123456789123
+IPs.0.Address 12.345.67.89
+IPs.0.Reverse -
+IPs.0.Version IPv4
+IPs.0.ReverseStatus unknown
+IPs.0.ReverseStatusMessage -
+IPs.1.ID 12345678-1234-1234-1234-123456789123
+IPs.1.Address IPs.1.Address
+IPs.1.Reverse IPs.1.Reverse
+IPs.1.Version IPv6
+IPs.1.ReverseStatus pending
+IPs.1.ReverseStatusMessage -
+IPs.2.ID IPs.2.ID
+IPs.2.Address 51.159.17.32
+IPs.2.Reverse IPs.2.Reverse
+IPs.2.Version IPv4
+IPs.2.ReverseStatus active
+IPs.2.ReverseStatusMessage -
+Domain your-domain-name
+BootType normal
+Zone fr-par-2
+Install.OsID 12345678-1234-1234-1234-123456789123
+Install.Hostname hostname-for-your-server
+Install.SSHKeyIDs.0 12345678-1234-1234-1234-123456789123
+Install.Status completed
+PingStatus up
+```
+
+### Rebooting your Server
+
+Type the following command:
+
+```
+scw baremetal server reboot your-elastic-metal-server-ID zone=fr-par-2
+```
+
+The following output displays, and you will see "down" next to the `PingStatus` field:
+
+```
+ID 12345678-1234-1234-1234-123456789123
+OrganizationID 12345678-1234-1234-1234-123456789123
+ProjectID 12345678-1234-1234-1234-123456789123
+Name name-of-your-server
+Description -
+UpdatedAt 3 seconds from now
+CreatedAt 3 hours ago
+Status stopping
+OfferID 12345678-1234-1234-1234-123456789123
+IPs.0.ID 12345678-1234-1234-1234-123456789123
+IPs.0.Address 12.345.67.89
+IPs.0.Reverse -
+IPs.0.Version IPv4
+IPs.0.ReverseStatus unknown
+IPs.0.ReverseStatusMessage -
+IPs.1.ID 12345678-1234-1234-1234-123456789123
+IPs.1.Address IPs.1.Address
+IPs.1.Reverse IPs.1.Reverse
+IPs.1.Version IPv6
+IPs.1.ReverseStatus pending
+IPs.1.ReverseStatusMessage -
+IPs.2.ID IPs.2.ID
+IPs.2.Address 51.159.17.32
+IPs.2.Reverse IPs.2.Reverse
+IPs.2.Version IPv4
+IPs.2.ReverseStatus active
+IPs.2.ReverseStatusMessage -
+Domain your-domain-name
+BootType normal
+Zone fr-par-2
+Install.OsID 12345678-1234-1234-1234-123456789123
+Install.Hostname hostname-for-your-server
+Install.SSHKeyIDs.0 12345678-1234-1234-1234-123456789123
+Install.Status completed
+PingStatus down
+```
+
+## Deleting your server
+
+
+ This action is irreversible and will permanently delete your Elastic Metal server and your data.
+
+
+Type the following command in your terminal:
+
+```
+scw baremetal server delete your-elastic-metal-server-ID zone=fr-par-2
+```
+
+An output like the following displays, and you will see "deleting" next to the `Status` field:
+
+```
+ID your-elastic-metal-server-ID
+OrganizationID your-organization-ID
+ProjectID your-project-ID
+Name name-of-your-server
+Description -
+UpdatedAt now
+CreatedAt 4 hours ago
+Status deleting
+OfferID your-offer-ID
+Tags.0 -
+IPs.1.ID 12345678-1234-1234-1234-123456789123
+IPs.1.Address 1234:123:4567:8:9123:4567:8912:345
+IPs.1.Reverse 12345678-1234-1234-1234-123456789123.fr-par-2.baremetal.scw.cloud
+IPs.1.Version IPv6
+IPs.1.ReverseStatus active
+IPs.1.ReverseStatusMessage -
+Domain 12345678-1234-1234-1234-123456789123.fr-par-2.baremetal.scw.cloud
+BootType normal
+Zone fr-par-2
+Install.OsID ID-of-your-OS
+Install.Hostname hostname-for-your-server
+Install.SSHKeyIDs.0 your-ssh-key-ID
+Install.Status completed
+PingStatus down
+
+```
+
+Enter the following command to make sure that your server has been deleted:
+
+```
+scw baremetal server list zone=fr-par-2
+```
+
+An output similar to the following displays:
+
+```
+12345678-1234-1234-1234-123456789123 name-of-your-server GP-BM1-L stopped
+```
\ No newline at end of file
diff --git a/pages/elastic-metal/api-cli/index.mdx b/pages/elastic-metal/api-cli/index.mdx
new file mode 100644
index 0000000000..c9efdf4727
--- /dev/null
+++ b/pages/elastic-metal/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Elastic Metal servers - API/CLI Documentation
+ description: Elastic Metal API/CLI Documentation
+content:
+ h1: API/CLI Documentation
+ paragraph: Elastic Metal API/CLI Documentation
+---
diff --git a/pages/elastic-metal/concepts.mdx b/pages/elastic-metal/concepts.mdx
new file mode 100644
index 0000000000..4caccd4b03
--- /dev/null
+++ b/pages/elastic-metal/concepts.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: Elastic Metal - Concepts
+ description: This page explains all the concepts related to Scaleway Elastic Metal servers
+content:
+ h1: Elastic Metal - Concepts
+ paragraph: This page explains all the concepts related to Scaleway Elastic Metal servers
+tags: elastic-metal rescue-mode private-networks remote-access az
+dates:
+ validation: 2024-08-12
+categories:
+ - bare-metal
+ - elastic-metal
+---
+
+## Elastic Metal server
+
+Scaleway Elastic Metal are dedicated physical servers you can order on-demand, like Instances. These servers can be used for large workloads, big data and applications that require increased security and dedicated resources.
+
+## Flexible IP
+
+Flexible IPs are additional public IP addresses that you can hold independently of any Elastic Metal server. They can be attached to and detached from any Elastic Metal server as you wish.
+
+You can keep several flexible IP addresses in your account, and they can either be IPv4 (single IP) or IPv6 (/64 IP block) addresses.
+
+When you delete a flexible IP address, it is disassociated from your account to be claimed by other users.
+
+## Image
+
+An image is a file that contains the OS, application data, and any files that might be related to your applications.
+
+If you do not know yet which image you want to run on the Elastic Metal, you can order a server without a preinstalled image.
+
+## Public IP
+
+Public IP addresses are routed on the internet. You can enter the public IP address of your Elastic Metal server into any browser connected to the internet, and access content being served from that Elastic Metal. You can think of public IP addresses like postal addresses for buildings - they are unique, and tell the routers directing traffic through the internet where to find a particular server.
+
+## Private Networks
+
+[Private Networks allow your Elastic Metal servers to communicate with other Scaleway resources](/elastic-metal/how-to/use-private-networks/) in an isolated and secure network without requiring a connection to the public internet.
+
+## Region and Availability Zone
+
+
+
+## Remote access
+
+Remote access allows you to access the keyboard, video, and mouse of the machine remotely by using [KVM over IP device](https://en.wikipedia.org/wiki/KVM_switch#KVM_over_IP_(IPKVM)). It enables you access to the machine even if the installed OS is not working properly, to debug the system, or to install your own OS from a remote ISO file.
+
+Remote access is available as an option on most Elastic Metal offers. Currently, remote access must be configured [via the API](https://www.scaleway.com/en/developers/api/elastic-metal/#path-bmc-access-start-bmc-access).
+
+## Rescue Mode
+
+Rescue mode restarts your server via the network on a minimal operating system. You can use it to debug a server and recover system data.
+
+Your server must be powered on and running to switch to rescue mode, which creates a ramdisk with the content of a downloaded `rootfs`.
+
+After disabling rescue mode, you have to reboot your server.
+
+## Tags
+
+Tags allow you to organize your resources by sorting and filtering your cloud assets in any organizational pattern you choose. This helps you arrange, control, and monitor your cloud resources. You can assign as many tags as you want to each Scaleway product.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/activate-remote-access.mdx b/pages/elastic-metal/how-to/activate-remote-access.mdx
new file mode 100644
index 0000000000..dcdb1eecb6
--- /dev/null
+++ b/pages/elastic-metal/how-to/activate-remote-access.mdx
@@ -0,0 +1,66 @@
+---
+meta:
+ title: How to activate remote access on an Elastic Metal server
+ description: Learn how to activate remote access on a Scaleway Elastic Metal server with this step-by-step guide.
+content:
+ h1: How to activate remote access on an Elastic Metal server
+ paragraph: Learn how to activate remote access on a Scaleway Elastic Metal server with this step-by-step guide.
+tags: remote-access elastic-metal
+dates:
+ validation: 2025-01-02
+ posted: 2022-03-30
+categories:
+ - bare-metal
+---
+
+Remote access is available on most Elastic Metal servers. This option allows you to access the keyboard, video, and mouse of the machine remotely through a KVM-over-IP device.
+
+Using remote access, you can access the machine for debugging purposes, even if the installed OS is not working properly. It is also possible to install an Operating System on the machine using a remote ISO file.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server compatible with [remote access](/elastic-metal/concepts/#remote-access)
+
+
+ Remote access is an **optional feature** and not available on all Elastic Metal servers. The following steps can be done only on Elastic Metal servers providing remote access.
+
+
+## Activating remote access
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the name of the server you want to access using the remote access option.
+3. Scroll down to **Remote access** in the server's information page. Then click **Activate**.
+
+ If you can not see the button to activate the remote access feature, it means that this option is not available for your Elastic Metal server.
+
+4. Read and accept the terms and conditions for the remote access feature. Tick the box to confirm you understood the conditions of the option, then click **Activate**.
+5. Enter the [IP address](https://www.whatsmyip.org/) of your internet connection and click **Create access**.
+
+
+
+ Make sure to enter the public IP address of your internet connection, as connections to the remote access device are limited to this IP address for security reasons. Currently, only IPv4 addresses are supported by the remote access feature.
+
+
+The connection details of your remote access displays. Use the credentials provided to log in at the connection URL.
+
+
+ * Each remote access session has an expiration date when the generated credentials become invalid for new connections. You have to regenerate access then.
+ * The remote access option remains active for 48 hours after activation, or until you [deactivate remote access](#deactivating-remote-access) from your console.
+
+
+## Renewing a remote access session
+
+Each remote access session has a limited lifetime for security reasons. To renew a remote access session, scroll to the **Remote access** section on your servers' information page. Then click **Create remote access**.
+
+### Resetting access credentials
+
+You can regenerate new access credentials at any time, even before your session has expired. To do so, click **Reset access** in the remote access session. It will reset the password and generate a new one.
+
+## Deactivating remote access
+
+To deactivate the remote access feature, scroll to the **Remote access** section on your server's information page. Then click **Disable remote access**.
+
+
diff --git a/pages/elastic-metal/how-to/add-virtual-mac-address.mdx b/pages/elastic-metal/how-to/add-virtual-mac-address.mdx
new file mode 100644
index 0000000000..578fb9ad75
--- /dev/null
+++ b/pages/elastic-metal/how-to/add-virtual-mac-address.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: How to add a virtual MAC address to a flexible IP
+ description: Learn how to add a virtual MAC address to a flexible IP for Scaleway Elastic Metal servers.
+content:
+ h1: How to add a virtual MAC address to a flexible IP
+ paragraph: This guide explains how to add a virtual MAC address to a flexible IP for Scaleway Elastic Metal servers.
+tags: virtual-mac, virtual-mac-address, flexible-ip
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Virtual MAC addresses act as virtual interface identifiers necessary for virtualization. When running multiple virtual machines on a single physical Elastic Metal server, you can configure the [MAC address](https://en.wikipedia.org/wiki/MAC_address) of the virtual network interface to match the virtual MAC associated with the [flexible IP](/elastic-metal/concepts/#flexible-ip), ensuring network connectivity for the virtual machine.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An installed Elastic Metal server ([how to create an Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server))
+
+
+ Virtual MAC addresses are only necessary for virtualization. If you plan to configure the flexible IP as a secondary interface on the host OS, a virtual MAC is not required.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab to navigate to flexible IP section. A list of your flexible IPs for Elastic Metal server displays.
+3. Click the next to the flexible IP you wish to configure. The configuration menu for the flexible IP will display.
+4. Click **More info** to see detailed information about the IP address.
+5. Configure the virtual MAC address:
+ - Scroll down to the **MAC address** section and click **Add MAC address**.
+ - Select the desired type of virtual MAC address (`VMware`, `XEN`, or `KVM`). It is recommended to choose the type that matches your virtualization technology.
+ - Confirm by clicking **Generate MAC Address**.
+
+
+ If the virtual MAC address is no longer needed, you can remove it from the flexible IP by clicking the **Delete** button.
+
+
+For more information on configuring the flexible IP on a virtual machine, refer to our [documentation](/elastic-metal/how-to/configure-flexible-ip/).
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx
new file mode 100644
index 0000000000..8c662f32fd
--- /dev/null
+++ b/pages/elastic-metal/how-to/adjust-available-bandwidth.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: How to adjust the available bandwidth for an Elastic Metal server
+ description: Discover step-by-step instructions for adjusting (upgrading or downgrading) the available bandwidth for your Elastic Metal server.
+content:
+ h1: How to adjust the available bandwidth for an Elastic Metal server
+ paragraph: Discover step-by-step instructions for adjusting (upgrading or downgrading) the available bandwidth for your Elastic Metal server.
+tags: elastic-metal bandwidth putty
+dates:
+ validation: 2025-01-06
+ posted: 2024-06-11
+---
+
+Every Elastic Metal server comes with a designated bandwidth allowance. Increase your server's connectivity with additional, high-performance bandwidth options of up to 25Gbps, all with unlimited traffic.
+
+
+
+- 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
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+## Upgrading bandwidth for your Elastic Metal server
+
+Follow these steps to boost the bandwidth of your Elastic Metal server:
+
+1. Navigate to **Elastic Metal** under the **Bare Metal** section in the [Scaleway console](https://console.scaleway.com) side menu. This action takes you to the Elastic Metal dashboard.
+2. Click the server name or the beside your desired server to access its information page.
+3. Click **Settings** to see a list of available configurations. Then click **Manage bandwidth** in the **Public bandwidth** section. A pop-up window appears.
+4. Choose the desired maximum bandwidth for your Elastic Metal server. The associated monthly fee displays on the right side of the pop-up.
+
+ The maximum available bandwidth for each Elastic Metal server is determined by the physical conditions of the network card installed, as specified in the offer description.
+
+5. Click **Continue** to confirm your selected bandwidth. A summary of your order displays
+6. Click **Update public bandwidth** to initiate the bandwidth upgrade process for your Elastic Metal server.
+
+ The initial month's fee for your chosen bandwidth option will be billed prorated.
+
+
+## Downgrading bandwidth for your Elastic Metal server
+
+To reduce the bandwidth for your Elastic Metal server, follow these steps:
+
+1. Access the **Elastic Metal** section within the **Bare Metal** category of the [Scaleway console](https://console.scaleway.com).
+2. Click the server name or the beside your desired server to access its information page.
+3. Navigate to **Settings** and then to the **Public bandwidth** section. Click **Manage bandwidth** to open a pop-up.
+4. Adjust the bandwidth to your desired level. The associated monthly fee will be adjusted accordingly.
+
+ Sliding the bar to the far left will reduce the bandwidth to the value initially included with your Elastic Metal server.
+
+5. Click **Continue** to confirm your selection after reviewing the order summary.
+6. Click **Update public bandwidth** to execute the bandwidth downgrade process.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/assets/scaleway-activate-remote-access.webp b/pages/elastic-metal/how-to/assets/scaleway-activate-remote-access.webp
new file mode 100644
index 0000000000..60c726f0e0
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-activate-remote-access.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-bm_logs.webp b/pages/elastic-metal/how-to/assets/scaleway-bm_logs.webp
new file mode 100644
index 0000000000..2120187d75
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-bm_logs.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-bm_remoteaccess.webp b/pages/elastic-metal/how-to/assets/scaleway-bm_remoteaccess.webp
new file mode 100644
index 0000000000..59921216b7
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-bm_remoteaccess.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-bmaas_rescue_mode.webp b/pages/elastic-metal/how-to/assets/scaleway-bmaas_rescue_mode.webp
new file mode 100644
index 0000000000..43cf38df04
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-bmaas_rescue_mode.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-boot-rescue.webp b/pages/elastic-metal/how-to/assets/scaleway-boot-rescue.webp
new file mode 100644
index 0000000000..de3bec4118
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-boot-rescue.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-configuration-page-microsoft-remote.webp b/pages/elastic-metal/how-to/assets/scaleway-configuration-page-microsoft-remote.webp
new file mode 100644
index 0000000000..68fcfe7445
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-configuration-page-microsoft-remote.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-create-bare-metal.webp b/pages/elastic-metal/how-to/assets/scaleway-create-bare-metal.webp
new file mode 100644
index 0000000000..4c326555fe
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-create-bare-metal.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-disable-remote-access.webp b/pages/elastic-metal/how-to/assets/scaleway-disable-remote-access.webp
new file mode 100644
index 0000000000..3be6e66ca3
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-disable-remote-access.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-cloud-server-reboot-normal.webp b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-cloud-server-reboot-normal.webp
new file mode 100644
index 0000000000..3532b9616e
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-cloud-server-reboot-normal.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-install.webp b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-install.webp
new file mode 100644
index 0000000000..7c93329fa3
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-install.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-list.webp b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-list.webp
new file mode 100644
index 0000000000..26928d15a7
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-list.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-rescue-credentials.webp b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-rescue-credentials.webp
new file mode 100644
index 0000000000..f6c82505d4
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-elastic-metal-rescue-credentials.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-elastic_metal_server_list.webp b/pages/elastic-metal/how-to/assets/scaleway-elastic_metal_server_list.webp
new file mode 100644
index 0000000000..471ef40326
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-elastic_metal_server_list.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-em-rescue-mode.webp b/pages/elastic-metal/how-to/assets/scaleway-em-rescue-mode.webp
new file mode 100644
index 0000000000..54ba854a36
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-em-rescue-mode.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-enable-smtp.webp b/pages/elastic-metal/how-to/assets/scaleway-enable-smtp.webp
new file mode 100644
index 0000000000..a6b2ab0365
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-enable-smtp.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flex-drag.gif b/pages/elastic-metal/how-to/assets/scaleway-flex-drag.gif
new file mode 100644
index 0000000000..2475097a80
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flex-drag.gif differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flex-ip-attached.webp b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-attached.webp
new file mode 100644
index 0000000000..9bfa3fb36c
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-attached.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flex-ip-order.webp b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-order.webp
new file mode 100644
index 0000000000..1aae832c6f
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-order.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flex-ip-tab.webp b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-tab.webp
new file mode 100644
index 0000000000..4728b308ff
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flex-ip-tab.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_allocated_multi_mac.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_allocated_multi_mac.webp
new file mode 100644
index 0000000000..1aa1755260
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_allocated_multi_mac.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_from_ip.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_from_ip.webp
new file mode 100644
index 0000000000..35f53bb0a4
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_from_ip.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_mac.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_mac.webp
new file mode 100644
index 0000000000..0750e02d03
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_copy_mac.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_mac_group_ready.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_mac_group_ready.webp
new file mode 100644
index 0000000000..4c9d961ff3
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_mac_group_ready.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_multi_mac.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_multi_mac.webp
new file mode 100644
index 0000000000..4ff1ab4f8b
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_multi_mac.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexible_vmac.webp b/pages/elastic-metal/how-to/assets/scaleway-flexible_vmac.webp
new file mode 100644
index 0000000000..a9ce1f16f7
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexible_vmac.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexip-display.webp b/pages/elastic-metal/how-to/assets/scaleway-flexip-display.webp
new file mode 100644
index 0000000000..08ec4a95d4
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexip-display.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-flexip_reverse.webp b/pages/elastic-metal/how-to/assets/scaleway-flexip_reverse.webp
new file mode 100644
index 0000000000..594cfeb99b
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-flexip_reverse.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-install-os.webp b/pages/elastic-metal/how-to/assets/scaleway-install-os.webp
new file mode 100644
index 0000000000..d2ec7e9f41
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-install-os.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_boot_device.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_boot_device.webp
new file mode 100644
index 0000000000..6c2817ca3c
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_boot_device.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_cd_connected.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_cd_connected.webp
new file mode 100644
index 0000000000..6aa906e678
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_cd_connected.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_connect_cd.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_connect_cd.webp
new file mode 100644
index 0000000000..eace323674
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_connect_cd.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_console_start.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_console_start.webp
new file mode 100644
index 0000000000..00dfacd046
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_console_start.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_create_session.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_create_session.webp
new file mode 100644
index 0000000000..e7fcc85222
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_create_session.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_install.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_install.webp
new file mode 100644
index 0000000000..ab4d90c859
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_install.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_interface.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_interface.webp
new file mode 100644
index 0000000000..1fbcd05933
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_interface.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_login.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_login.webp
new file mode 100644
index 0000000000..27701ce2ef
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_login.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_power_cycle.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_power_cycle.webp
new file mode 100644
index 0000000000..28409ca2eb
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_power_cycle.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_remote_access.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_remote_access.webp
new file mode 100644
index 0000000000..dc2f4b2987
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_remote_access.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-kvm_virtual_media_wizzard.webp b/pages/elastic-metal/how-to/assets/scaleway-kvm_virtual_media_wizzard.webp
new file mode 100644
index 0000000000..db2f266827
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-kvm_virtual_media_wizzard.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-putty-logged.webp b/pages/elastic-metal/how-to/assets/scaleway-putty-logged.webp
new file mode 100644
index 0000000000..ea19bb4fbd
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-putty-logged.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-putty-main.webp b/pages/elastic-metal/how-to/assets/scaleway-putty-main.webp
new file mode 100644
index 0000000000..46d9f9630f
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-putty-main.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-putty-security.webp b/pages/elastic-metal/how-to/assets/scaleway-putty-security.webp
new file mode 100644
index 0000000000..d1c3b0f6ac
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-putty-security.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-putty-ssh.webp b/pages/elastic-metal/how-to/assets/scaleway-putty-ssh.webp
new file mode 100644
index 0000000000..8b0ac2219a
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-putty-ssh.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-reboot-bare-metal-cloud-server.webp b/pages/elastic-metal/how-to/assets/scaleway-reboot-bare-metal-cloud-server.webp
new file mode 100644
index 0000000000..4e3fdc3cfb
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-reboot-bare-metal-cloud-server.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-remote-access-create-new.webp b/pages/elastic-metal/how-to/assets/scaleway-remote-access-create-new.webp
new file mode 100644
index 0000000000..8fca8c2216
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-remote-access-create-new.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-remote-access-feature.webp b/pages/elastic-metal/how-to/assets/scaleway-remote-access-feature.webp
new file mode 100644
index 0000000000..2537eb4a97
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-remote-access-feature.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-remote-access-ip.webp b/pages/elastic-metal/how-to/assets/scaleway-remote-access-ip.webp
new file mode 100644
index 0000000000..60b68a8ffa
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-remote-access-ip.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-rescue-credentials.webp b/pages/elastic-metal/how-to/assets/scaleway-rescue-credentials.webp
new file mode 100644
index 0000000000..3d66f8e87f
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-rescue-credentials.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-rescue_bmaas_off.webp b/pages/elastic-metal/how-to/assets/scaleway-rescue_bmaas_off.webp
new file mode 100644
index 0000000000..c51358dd7d
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-rescue_bmaas_off.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-rescue_switch_bmaas.webp b/pages/elastic-metal/how-to/assets/scaleway-rescue_switch_bmaas.webp
new file mode 100644
index 0000000000..667b79bde3
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-rescue_switch_bmaas.webp differ
diff --git a/pages/elastic-metal/how-to/assets/scaleway-warning-certificate-root-user.webp b/pages/elastic-metal/how-to/assets/scaleway-warning-certificate-root-user.webp
new file mode 100644
index 0000000000..57e30eee33
Binary files /dev/null and b/pages/elastic-metal/how-to/assets/scaleway-warning-certificate-root-user.webp differ
diff --git a/pages/elastic-metal/how-to/attach-detach-flexible-ip.mdx b/pages/elastic-metal/how-to/attach-detach-flexible-ip.mdx
new file mode 100644
index 0000000000..0c60053853
--- /dev/null
+++ b/pages/elastic-metal/how-to/attach-detach-flexible-ip.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: How to attach and detach a flexible IP to and from an Elastic Metal server
+ description: Learn how to attach and detach a flexible IP to and from a Scaleway Elastic Metal server.
+content:
+ h1: How to attach and detach a flexible IP to and from an Elastic Metal server
+ paragraph: This guide explains how to attach and detach a flexible IP to and from a Scaleway Elastic Metal server.
+tags: attach, detach, flexible-ip, elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+You can order up to 64 flexible IPs (IPv4 or IPv6) for each of your Elastic Metal servers. These [Elastic Metal flexible IPs](/elastic-metal/concepts/#flexible-ip) can be attached and detached from any of your Elastic Metal servers using the console's drag-and-drop interface.
+
+
+ Scaleway offers flexible IPs for [Elastic Metal servers](/elastic-metal/concepts/#elastic-metal-server), [Instances](/instances/concepts/#instance), and [Public Gateways](/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+- An Elastic Metal [flexible IP address](/elastic-metal/how-to/order-flexible-ip/)
+
+## How to attach a flexible IP to an Elastic Metal server
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab to display the list of available failover IPs.
+3. Drag and drop the flexible IP from the **Flexible IP** panel to your server in the **Elastic Metal servers** panel to attach it to a machine.
+
+ You can assign both flexible IPv4 and IPv6 addresses in the same way.
+
+4. Click **Validate** to confirm and complete the allocation.
+
+ If you are using virtual MAC groups, all flexible IPs sharing the same MAC address will be moved from one server to another.
+
+
+## How to detach a flexible IP from an Elastic Metal server
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab to display the list of available failover IPs.
+3. Drag and drop the flexible IP from your server in the **Elastic Metal servers** panel to the **Flexible IP** panel to detach it from the server.
+4. Click **Validate** to confirm and complete the detachment.
+
+## How to switch the destination host of a flexible IP for Elastic Metal servers
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab to display the list of failover IPs for Elastic Metal servers allocated to your account.
+3. Configure your services and the [flexible IP](/elastic-metal/how-to/configure-flexible-ip/) on the new server to ensure uninterrupted service availability.
+4. In the **Elastic Metal servers** panel, drag and drop the flexible IP from its current server to the new one to update its destination.
+5. Click **Validate** to complete the switch. The green dot will start blinking blue, indicating that the flexible IP destination is being updated. Once the configuration is updated, the blinking dot will turn back to green, indicating that the flexible IP is now routed to the new server.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/configure-disk-partitions.mdx b/pages/elastic-metal/how-to/configure-disk-partitions.mdx
new file mode 100644
index 0000000000..4f1281da9b
--- /dev/null
+++ b/pages/elastic-metal/how-to/configure-disk-partitions.mdx
@@ -0,0 +1,227 @@
+---
+meta:
+ title: How to configure custom disk partitioning on Scaleway Elastic Metal servers
+ description: Learn how to configure custom disk partitions on Scaleway Elastic Metal servers
+content:
+ h1: How to configure custom disk partitioning on Scaleway Elastic Metal servers
+ paragraph: This guide explains how to configure custom disk partitions on Scaleway Elastic Metal servers.
+tags: attach, detach, flexible-ip, elastic-metal
+dates:
+ validation: 2024-10-01
+ posted: 2024-10-01
+categories:
+ - bare-metal
+---
+
+Scaleway Elastic Metal servers come with a default partition layout, suitable for most users and intended to speed up and simplify the installation process of the server.
+However, if you have specific requirements, you can define custom partitioning of your machine using a JSON configuration during server installation.
+
+
+ You can change the partitioning of your server during installation or re-installation only.
+ Be aware that all your data will be deleted if you reinstall your server.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+## Example configuration
+
+During [server installation](/elastic-metal/) click **Advanced JSON** configuration in step 5 of the server creation wizard.
+You can then edit the partition configuration directly in the editor within your browser. The configuration is done via a JSON description of the partitioning.
+Below is an example of how to define a partitioning schema with RAID and NVMe disks.
+
+
+ - Disk Type Naming: Device names differ based on the disk type. For example, HDD/SSD will use `/dev/sdXXX`, while NVMe devices use `/dev/nvmeXXX`.
+ - UEFI Partition: The EFI partition should only exist if the server uses UEFI. If UEFI is not in use, this partition should be omitted.
+ - ZFS and LVM: ZFS is optional and can be configured if needed, while LVM should not be used for now due to functionality issues.
+
+
+
+ Refer to the Elastic Metal API documentation for a complete overview of the expected values for file system types, RAID configurations, and other related parameters required for partitioning. For more details, visit the [Scaleway Elastic Metal API Documentation – Default Partitioning Schema](https://www.scaleway.com/en/developers/api/elastic-metal/#path-partitioning-schemas-get-default-partitioning-schema).
+
+
+```json
+{
+ "partitioning_schema": {
+ "disks": [
+ {
+ "device": "/dev/nvme0n1",
+ "partitions": [
+ {
+ "label": "uefi",
+ "number": 1,
+ "size": 536870912
+ },
+ {
+ "label": "swap",
+ "number": 2,
+ "size": 4294967296
+ },
+ {
+ "label": "boot",
+ "number": 3,
+ "size": 536870912
+ },
+ {
+ "label": "root",
+ "number": 4,
+ "size": 64424509440
+ },
+ {
+ "label": "data",
+ "number": 5,
+ "size": 1850588790784
+ }
+ ]
+ },
+ {
+ "device": "/dev/nvme1n1",
+ "partitions": [
+ {
+ "label": "swap",
+ "number": 1,
+ "size": 4294967296
+ },
+ {
+ "label": "boot",
+ "number": 2,
+ "size": 536870912
+ },
+ {
+ "label": "root",
+ "number": 3,
+ "size": 64424509440
+ },
+ {
+ "label": "data",
+ "number": 4,
+ "size": 1850588790784
+ }
+ ]
+ }
+ ],
+ "raids": [
+ {
+ "name": "/dev/md0",
+ "level": "raid_level_1",
+ "devices": [
+ "/dev/nvme0n1p3",
+ "/dev/nvme1n1p2"
+ ]
+ },
+ {
+ "name": "/dev/md1",
+ "level": "raid_level_1",
+ "devices": [
+ "/dev/nvme0n1p4",
+ "/dev/nvme1n1p3"
+ ]
+ }
+ ],
+ "filesystems": [
+ {
+ "device": "/dev/nvme0n1p1",
+ "format": "fat32",
+ "mountpoint": "/boot/efi"
+ },
+ {
+ "device": "/dev/md0",
+ "format": "ext4",
+ "mountpoint": "/boot"
+ },
+ {
+ "device": "/dev/md1",
+ "format": "ext4",
+ "mountpoint": "/"
+ }
+ ],
+ "lvm": null,
+ "zfs": {
+ "pools": [
+ {
+ "name": "zpve",
+ "type": "mirror",
+ "devices": [
+ "/dev/nvme0n1p5",
+ "/dev/nvme1n1p4"
+ ],
+ "options": [
+ "ashift=12"
+ ],
+ "filesystem_options": []
+ }
+ ]
+ }
+ }
+}
+```
+
+## Explanation of key sections:
+
+- Disks:
+ - Each disk is specified with its device path (e.g., `/dev/nvme0n1` or `/dev/nvme1n1`).
+ - Partitions are defined with labels. The default value is `unknown_partition_label`, and possible values are: `uefi`, `legacy`, `root`, `boot`, `swap`, `data`, `home`, `raid`. Refer to the [API documentation](https://www.scaleway.com/en/developers/api/elastic-metal/#path-servers-install-an-elastic-metal-server) for full details.
+ - Each partition has a `number` and `size` in bytes.
+
+- RAID (Optional):
+ - If RAID is required, declare the disks and the desired RAID level. In this example, we are configuring two RAID-1 arrays, one for the boot partition and one for the root partition.
+ - Devices participating in each RAID array are specified by their partition paths (e.g., `/dev/nvme0n1p3` for partition 3 of the first NVMe disk).
+
+- File systems:
+ - Each partition is assigned a file system type and a mount point.
+ - For example, the `/boot/efi` partition is formatted with `fat32`, while `/boot` and `/` are formatted with `ext4`.
+
+- ZFS (Optional):
+ - ZFS can be configured if wished. In this example, a ZFS mirror is created using partitions from two NVMe devices.
+ - ZFS options such as `ashift=12` can be included for performance tuning, but they are optional.
+
+### Simple configuration (No RAID or ZFS)
+
+If you prefer a simpler configuration without RAID or ZFS, you can remove the `raids` and `zfs` sections. For example, if you only need a single disk setup with no RAID, declare just one disk with the partitions and file systems as shown below:
+
+```json
+{
+ "partitioning_schema": {
+ "disks": [
+ {
+ "device": "/dev/nvme0n1",
+ "partitions": [
+ {
+ "label": "swap",
+ "number": 1,
+ "size": 4294967296
+ },
+ {
+ "label": "boot",
+ "number": 2,
+ "size": 536870912
+ },
+ {
+ "label": "root",
+ "number": 3,
+ "size": 64424509440
+ }
+ ]
+ }
+ ],
+ "filesystems": [
+ {
+ "device": "/dev/nvme0n1p2",
+ "format": "ext4",
+ "mountpoint": "/boot"
+ },
+ {
+ "device": "/dev/nvme0n1p3",
+ "format": "ext4",
+ "mountpoint": "/"
+ }
+ ],
+ "raids": [],
+ "zfs": null,
+ "lvm": null
+ }
+}
+```
diff --git a/pages/elastic-metal/how-to/configure-flexible-ip.mdx b/pages/elastic-metal/how-to/configure-flexible-ip.mdx
new file mode 100644
index 0000000000..d2ec3de43f
--- /dev/null
+++ b/pages/elastic-metal/how-to/configure-flexible-ip.mdx
@@ -0,0 +1,140 @@
+---
+meta:
+ title: How to configure a flexible IP on an Elastic Metal server
+ description: This page explains configure a flexible IP on an Elastic Metal server
+content:
+ h1: How to configure a flexible IP on an Elastic Metal server
+ paragraph: This page explains configure a flexible IP on an Elastic Metal server
+tags: elastic-metal flexible-ip configuration
+dates:
+ validation: 2024-09-30
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Learn how to configure a [flexible IP address](/elastic-metal/concepts/#flexible-ip) on your Elastic Metal server. The configuration depends on the Linux distribution running on your machine. You can configure your flexible IP on machines running one of [Ubuntu Linux](#how-to-configure-a-flexible-ip-on-ubuntu-linux), [Debian Linux](#how-to-configure-a-flexible-ip-on-debian-linux) or [CentOS](#how-to-configure-a-flexible-ip-on-centos).
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+- A [flexible IP address](/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server
+
+
+ You can find information about the DNS resolver to use in each data center at the [network reference documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers).
+
+
+## How to configure a flexible IP on Ubuntu Linux
+
+Since the LTS release of Ubuntu Version 18.04 (Bionic Beaver) the recommended way to configure a flexible IP is by using [Netplan](https://netplan.io/). If you prefer a more traditional configuration, refer to the instructions for [flexible IP configuration on Debian](#how-to-configure-a-flexible-ip-on-debian-linux).
+
+1. Log into your server using SSH with a user having super-user rights.
+2. Open the file `/etc/netplan/01-netcfg.yaml` with superuser rights in your favorite text editor and configure the networking for your machine.
+
+ IP addresses in the configuration file have to be specified in CIDR
+ notation. The netmask is `/24` for the principal IP of the server and `/32`
+ for each flexible IP.
+
+ Your configuration file should look like the following example:
+
+ ```
+ network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ enp1s0f0:
+ addresses: [163.172.123.123/24, 212.83.123.123/32]
+ gateway4: 163.172.123.1
+ nameservers:
+ addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers)
+ ```
+
+
+ The interface name for your primary interface may be different from
+ `enp1s0f0`. You can use the `ip link show` command to determine the name of
+ your public internet interface.
+
+3. Once the file is edited as required, save it and quit the text editor. Then apply the configuration using the following command:
+ ```
+ sudo netplan apply
+ ```
+
+Your server now responds on both the primary IP address and the flexible IP address.
+
+## How to configure a flexible IP on Debian Linux
+
+1. Log into your server using SSH with a user having super-user rights.
+2. Open the file `/etc/network/interfaces` with superuser rights in your favorite text editor and configure the networking for your machine.
+3. Edit the file and add the flexible IP as shown in the following example:
+ ```sh
+ # This file describes the network interfaces available on your system
+ # and how to activate them. For more information, see interfaces(5).
+ # The loopback network interface
+ auto lo
+ iface lo inet loopback
+ # The primary network interface
+ auto eth0
+ iface eth0 inet static
+ address 195.154.123.123
+ netmask 255.255.255.0
+ gateway 195.154.123.1
+ auto eth0:0
+ iface eth0:0 inet static
+ address ip_flexible
+ netmask 255.255.255.255
+ ```
+
+
+ The interface name of your server might be different depending on the hardware
+ of the server. You can use the `ip link show` command to determine the name of
+ your public internet interface.
+
+4. Save the file and quit the editor.
+5. Bring the interface up using the `ifup` command:
+ ```sh
+ ifup eth0:0
+ ```
+
+Your server now responds on both the primary IP address and the flexible IP address.
+
+## How to configure a flexible IP on CentOS
+
+1. Log into your server using SSH using the `root` user.
+2. Copy the default network configuration file to create an alias:
+ ```sh
+ cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0:0
+ ```
+3. Open the file `/etc/sysconfig/network-scripts/ifcfg-eth0:0` in your favorite text editor and modify it as in the following example:
+ ```sh
+ DEVICE="eth0:0"
+ BOOTPROTO=static
+ IPADDR="my_flexible_ip"
+ NETMASK="255.255.255.255"
+ ONBOOT=yes
+ ```
+4. Save the file, exit the text editor and run the following command to reload the network configuration:
+ ```
+ /etc/init.d/network restart
+ ```
+Your server now responds on both the primary IP address and the flexible IP address.
+
+## How to configure a flexible IP in a virtual machine (VM)
+
+When you install your Elastic Metal server with a virtualization solution like VMware vSphere Hypervisor (ESXi) or Proxmox you can create multiple virtual machines on the physical server.
+
+To communicate on the Internet, each of your virtual machines needs an IP address. You can use flexible IPs to have additional IP addresses available for your virtual machines.
+
+Configure the networking of your VM's as follows:
+
+* IP address: Your flexible IP
+* Netmask: `255.255.255.255`
+* Gateway: `62.210.0.1`
+* DNS resolver: `51.159.47.28` and `51.159.47.26`
+
+
+ * The gateway of all flexible IPs is `62.210.0.1`. This allows you to move your VMs between your hypervisors without changing the network configuration of the virtual machine.
+ * When configuring a failover IP in a virtual machine, you must specify which route will be used by the VM. Refer to our [dedicated documentation](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines) for further information.
+
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx b/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx
new file mode 100644
index 0000000000..21c9f24a60
--- /dev/null
+++ b/pages/elastic-metal/how-to/configure-flexible-ipv6.mdx
@@ -0,0 +1,121 @@
+---
+meta:
+ title: How to configure a flexible IPv6 on an Elastic Metal server
+ description: Learn how to configure a flexible IPv6 on a Scaleway Elastic Metal server.
+content:
+ h1: How to configure a flexible IPv6 on an Elastic Metal server
+ paragraph: This guide explains how to configure a flexible IPv6 on a Scaleway Elastic Metal server.
+tags: configuration, flexible-ipv6, ipv6, elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2022-03-30
+categories:
+ - bare-metal
+---
+
+The configuration of a flexible IPv6 depends on the Linux distribution running on your Elastic Metal server. This guide covers the steps for configuring your flexible IPv6 on machines running Debian, Ubuntu, or CentOS.
+
+
+- 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
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+ Ensure your flexible IPv6 is [attached](/elastic-metal/how-to/attach-detach-flexible-ip/) to your Elastic Metal server before configuring it.
+
+
+
+ Information about the DNS resolver to use in each data center is available in the [network reference documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers).
+
+
+## How to configure IPv6 on Debian
+
+1. Open the network configuration file `/etc/network/interfaces` in a text editor and edit it as follows:
+ ```plaintext
+ auto eno1
+ iface eno1 inet6 static
+ address IPV6_ADDRESS
+ netmask 64
+ ```
+ Replace `eno1` with the correct internet interface name.
+
+2. Restart the network:
+ ```bash
+ sudo systemctl restart networking.service
+ ```
+
+
+ On Debian 9, the network interface is initialized with the command `allow-hotplug` by default. If the network restart fails with this configuration, initialize the network with `auto` to avoid the problem.
+
+
+## How to configure IPv6 on Ubuntu
+
+Ubuntu uses [netplan](https://netplan.io) for network configuration since Ubuntu 18.04 LTS. Netplan configuration files are written in [YAML](https://yaml.org) and located in the `/etc/netplan` directory. Refer to the official [netplan documentation](https://netplan.readthedocs.io/en/stable/examples/) for more information.
+
+1. Open the default configuration file `/etc/netplan/01-netcfg.yaml` in a text editor and edit it as follows:
+ ```yaml
+ # This is the network config written by 'subiquity'
+ network:
+ ethernets:
+ eno1:
+ critical: true
+ dhcp-identifier: mac
+ dhcp4: true
+ addresses: [ "IPV6_ADDRESS/64" ]
+ nameservers:
+ addresses:
+ - "2001:bc8:1008:1::16"
+ - "2001:bc8:1008:1::16"
+ search:
+ - online.net
+ version: 2
+ ```
+ - Replace `eno1` with the correct name of your internet interface.
+ - Replace the [IP addresses of the resolving DNS servers (nameservers)](/account/reference-content/scaleway-network-information/#dns-cache-servers) with the ones located in the same geographical location as your machine for best perfomances.
+
+
+ The configuration example above is valid for the main IP address of your Dedibox server. For IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), use the unique gateway for the failover IPv4.
+
+
+2. Check and validate your configuration file:
+ ```bash
+ sudo netplan try
+ ```
+
+3. Apply the new configuration:
+ ```bash
+ sudo netplan apply
+ ```
+
+4. Test the connection with a ping to an external host:
+ ```bash
+ ping6 google.com
+ ```
+
+## How to configure IPv6 on CentOS
+
+1. Open the automatically generated configuration file for your internet interface in a text editor, for example `/etc/sysconfig/network-scripts/ifcfg-eth0` and edit it as follows:
+ ```plaintext
+ # Generated by parse-kickstart
+ UUID=xxxxx
+ DNS1="51.159.47.28"
+ IPADDR="DEDIBOX_MAIN_IP"
+ GATEWAY="DEDIBOX_MAIN_IP_1" # The IPv4 gateway is your server's main IP address ending in .1 (e.g., if your server's IP is 62.210.16.123, the gateway is 61.210.16.1)
+ NETMASK="255.255.255.0"
+ IPV6ADDR="IPV6_ADDRESS/64"
+ IPV6_AUTOCONF="yes"
+ BOOTPROTO="static"
+ DEVICE="eth0"
+ ONBOOT="yes"
+ IPV6INIT="yes"
+ ```
+
+2. Restart the networking service:
+ ```bash
+ sudo systemctl restart network.service
+ ```
+
+3. Test the IPv6 connection with a ping to an external host:
+ ```bash
+ ping6 google.com
+ ```
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx b/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx
new file mode 100644
index 0000000000..37174e5c18
--- /dev/null
+++ b/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx
@@ -0,0 +1,199 @@
+---
+meta:
+ title: How to configure IPv6 virtual machines with Proxmox on Elastic Metal
+ description: This guide explains how to configure IPv6 virtual machines on Proxmox on Elastic Metal, including how to find and configure the IPv6 gateway.
+content:
+ h1: How to configure IPv6 virtual machines with Proxmox on Elastic Metal
+ paragraph: This guide explains how to configure IPv6 virtual machines on Proxmox on Elastic Metal, including how to find and configure the IPv6 gateway.
+tags: elastic-metal ipv6 virtual-machine proxmox
+dates:
+ validation: 2024-07-30
+ posted: 2024-07-30
+categories:
+ - bare-metal
+---
+
+When you install your server with a virtualization solution like Proxmox, you can create multiple virtual machines on the physical server and configure them to use flexible IPv6 addresses.
+
+This guide covers the steps for configuring the network interfaces on different distributions inside a virtual machine on a Proxmox host using flexible IPv6 addresses on Elastic Metal servers.
+
+
+ The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine.
+
+
+
+
+- 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
+- An [Elastic Metal server](/elastic-metal/how-to/create-server/) with a hypervisor (Proxmox) installed on it
+- A [flexible IPv6](/elastic-metal/how-to/order-flexible-ip/)
+- A [virtual MAC address](/elastic-metal/how-to/add-virtual-mac-address/)
+
+## Finding your IPv6 gateway
+
+1. Log into your virtual machine using SSH.
+
+2. Identify your network interface:
+ ```sh
+ ip a
+ ```
+ Take note of your network interface name (e.g., `ens18`).
+
+3. Find your IPv6 gateway:
+ ```sh
+ ip -6 route
+ ```
+ Look for the line that specifies the default route. It should look like the following:
+ ```
+ default via fe80::xxxx:xxxx:xxxx:xxxx dev ens18 proto static metric 1024 onlink
+ ```
+ The `fe80::xxxx:xxxx:xxxx:xxxx` part is your link-local IPv6 gateway address.
+
+## Ubuntu - Configuration with Netplan
+
+1. Open the Netplan configuration file:
+ ```sh
+ sudo nano /etc/netplan/01-netcfg.yaml
+ ```
+
+2. Create the network configuration:
+ ```yaml
+ network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ ens18:
+ dhcp4: false
+ dhcp6: false
+ accept-ra: no
+ addresses:
+ - FLEXIBLE_IPv4/32
+ - "FLEXIBLE_IPv6/64"
+ routes:
+ - to: 0.0.0.0/0
+ via: 62.210.0.1
+ on-link: true
+ - to: "::/0"
+ via: "LINK_LOCAL_IPv6_GATEWAY"
+ on-link: true
+ nameservers:
+ addresses:
+ - 51.159.47.28
+ - 51.159.47.26
+ ```
+ Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `LINK_LOCAL_IPv6_GATEWAY` with your actual IP addresses.
+
+3. Apply the configuration:
+ ```sh
+ sudo netplan apply
+ ```
+
+## Debian
+
+1. Edit the network interfaces file:
+ ```sh
+ sudo nano /etc/network/interfaces
+ ```
+
+2. Configure the network interface:
+ ```sh
+ auto ens18
+ iface ens18 inet static
+ address FLEXIBLE_IPv4
+ netmask 255.255.255.255
+ gateway 62.210.0.1
+ iface ens18 inet6 static
+ address FLEXIBLE_IPv6
+ netmask 64
+ gateway LINK_LOCAL_IPv6_GATEWAY
+ ```
+ Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `LINK_LOCAL_IPv6_GATEWAY` with your actual IP addresses.
+
+3. Set the DNS resolver:
+ ```sh
+ sudo nano /etc/resolv.conf
+ ```
+ 4. Add the following lines, then save and exit the file.
+ ```
+ nameserver 51.159.47.28
+ nameserver 51.159.47.26
+ ```
+
+5. Activate the network configuration:
+ ```sh
+ sudo ifup ens18
+ ```
+
+## CentOS
+
+1. Edit the network script file:
+ ```sh
+ sudo nano /etc/sysconfig/network-scripts/ifcfg-ens18
+ ```
+
+2. Configure the network interface:
+ ```
+ DEVICE=ens18
+ BOOTPROTO=none
+ ONBOOT=yes
+ USERCTL=no
+ IPV6INIT=yes
+ PEERDNS=yes
+ TYPE=Ethernet
+ NETMASK=255.255.255.255
+ IPADDR=FLEXIBLE_IPv4
+ IPV6ADDR=FLEXIBLE_IPv6
+ GATEWAY=62.210.0.1
+ DNS1=51.159.47.28
+ DNS2=51.159.47.26
+ ARP=yes
+ HWADDR=virtual:mac:address
+ ```
+ Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `virtual:mac:address` with your actual IP addresses and MAC address.
+
+3. Bring up the network interface:
+ ```sh
+ sudo ifup ens18
+ ```
+
+4. Find the IPv6 gateway:
+ ```sh
+ ip -6 route
+ ```
+
+## Debugging configuration issues
+
+If your IPv6 configuration does not work as expected, follow these steps to troubleshoot:
+
+1. Check the interface configuration:
+ ```sh
+ ip a
+ ip route
+ ip -6 route
+ ```
+
+2. Run a ping test:
+ ```sh
+ ping6 google.com
+ ```
+
+3. Check the DNS resolution:
+ ```sh
+ dig google.com
+ dig -6 google.com
+ ```
+
+4. Review your network logs:
+ ```sh
+ sudo journalctl -u systemd-networkd
+ ```
+
+5. Restart network services:
+ ```sh
+ sudo systemctl restart systemd-networkd
+ ```
+6. Verify the link-local address:
+ ```sh
+ ip -6 addr show dev ens18
+ ping6 LINK_LOCAL_IPv6_GATEWAY
+ ```
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx b/pages/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx
new file mode 100644
index 0000000000..0ce0db46cc
--- /dev/null
+++ b/pages/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: How to configure the reverse DNS of a flexible IP on Elastic Metal servers
+ description: Learn how to configure the reverse DNS of a flexible IP on Scaleway Elastic Metal servers.
+content:
+ h1: How to configure the reverse DNS of a flexible IP on Elastic Metal servers
+ paragraph: This guide explains how to configure the reverse DNS of a flexible IP on Scaleway Elastic Metal servers.
+tags: reverse-dns, reverse dns, flexible-ip, elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Reverse DNS (rDNS) is the opposite of classic forward DNS, mapping an IP address to a hostname. This is particularly useful for tasks such as sending emails from your Elastic Metal server.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+- A [flexible IP address](/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server
+
+
+ Ensure that a corresponding `A-Record` (IPv4) or `AAAA-Record` (IPv6) pointing to the IP address exists before editing the reverse DNS.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab to display the list of your failover IPs for Elastic Metal servers.
+3. Click **More** () next to the flexible IP you want to configure. The configuration menu for the flexible IP displays.
+4. Click **More info** to see detailed information about the IP address.
+5. Scroll down to the **Reverse** section and click **Add reverse** to add or edit the reverse DNS of the failover IP.
+
+ If a reverse DNS is already set on your failover IP, the button will be labeled **Edit reverse**.
+
+6. Enter the new reverse DNS and click **Edit reverse** to validate the changes.
+
+ When configuring the reverse DNS for a flexible IPv6, the configuration applies to the first IP (`XXXX:0`) of the /64 IP block.
+
diff --git a/pages/elastic-metal/how-to/connect-to-server.mdx b/pages/elastic-metal/how-to/connect-to-server.mdx
new file mode 100644
index 0000000000..6937ffdcb8
--- /dev/null
+++ b/pages/elastic-metal/how-to/connect-to-server.mdx
@@ -0,0 +1,105 @@
+---
+meta:
+ title: How to connect to your Elastic Metal server via SSH or remote desktop
+ description: Learn how to connect to your Elastic Metal server on Linux, macOS, or Windows using SSH or Remote Desktop for secure remote access.
+content:
+ h1: How to connect to your Elastic Metal server via SSH or remote desktop
+ paragraph: Learn how to connect to your Elastic Metal server on Linux, macOS, or Windows using SSH or Remote Desktop for secure remote access.
+tags: elastic-metal server connection putty
+dates:
+ validation: 2024-08-19
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+This page shows you how to connect to your Scaleway Elastic Metal server via SSH. Thanks to the SSH key you created and uploaded, you can use a terminal application on your local computer to remotely connect to your Elastic Metal server as root. This enables you to use your server as you wish.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+## How to connect to an Elastic Metal server from OSX (Mac) and Linux
+
+1. Open a terminal program.
+2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_rsa`) and `your_server_ip` with the IP address of your Elastic Metal server.
+ ```bash
+ ssh -i ~/.ssh/your_private_key root@your_server_ip
+ ```
+
+
+ To find the IP address of your Elastic Metal server, log into the Scaleway console and click **Elastic Metal** in the Bare Metal section of the side menu. A list of your Elastic Metal servers and their associated IP addresses will display.
+
+3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' can't be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+ You are now connected to your Elastic Metal server.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+
+## How to connect to an Elastic Metal server from Windows
+
+To connect to your Elastic Metal server from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+1. Download and install PuTTY [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html)
+2. Launch PuTTY on your computer. The main screen of the application displays:
+
+3. Enter your Elastic Metal server's IP address in the **Hostname** field.
+
+ To find the IP address of your Elastic Metal server, log into the Scaleway console and
+ click **Elastic Metal** in the Bare Metal section of the side menu. A list of your
+ Elastic Metal servers and their associated IP addresses will display.
+
+
+4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. Do this by expanding **Connection**, then **SSH**, and finally clicking on **Auth**:
+
+5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/).
+6. Click **Open** at the bottom of the screen to open a connection to the Elastic Metal server. Upon the first connection, PuTTY asks you to allow the connection to the host.
+7. Click **OK** to confirm.
+
+
+ The terminal window displays.
+8. Enter the username `root` and press **Enter** to authenticate against the server with your SSH key.
+
+
+ You are now connected to your Elastic Metal server.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+## How to connect to a Windows server using remote access
+
+To connect to your Elastic Metal server running Windows, you need to download a remote access tool. In this tutorial, we use [Microsoft Remote Desktop](https://apps.apple.com/us/app/microsoft-remote-desktop/id1295203466?mt=12).
+
+1. [Create an Elastic Metal server](/elastic-metal/how-to/create-server/) and choose a Windows image to run on it.
+
+ - Windows images are not available for the Aluminium range of Elastic Metal servers.
+ - Make sure you save your password securely after creating your Elastic Metal server.
+
+2. Download Microsoft Remote Desktop and launch it on your computer.
+
+ - [Download Microsoft Remote Desktop for OSX](https://apps.apple.com/us/app/microsoft-remote-desktop/id1295203466?mt=12).
+ - [Download Microsoft Remote Desktop for Windows](https://apps.microsoft.com/store/detail/microsoft-remote-desktop/9WZDNCRFJ3PS?hl=en-us&gl=us).
+ - Microsoft Remote Desktop is not available with Linux. Feel free to use any other remote desktop client to initiate your connection.
+
+3. Click **Add PC**. A configuration page displays.
+
+4. Enter your Elastic Metal server's IP address in the **PC name** field and click **Add**.
+5. Right-click your newly added PC and select **Connect**.
+6. When prompted, enter `Administrateur` in the **Username** field and the password from step 1 in the **Password** field.
+7. Click **Continue**. You are redirected to the Windows Server Manager.
+
+You are now connected to your Elastic Metal server running Windows.
+
+
diff --git a/pages/elastic-metal/how-to/create-server.mdx b/pages/elastic-metal/how-to/create-server.mdx
new file mode 100644
index 0000000000..47ea80fd0f
--- /dev/null
+++ b/pages/elastic-metal/how-to/create-server.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: How to Create an Elastic Metal server
+ description: Learn how to create an Elastic Metal server on Scaleway.
+content:
+ h1: How to Create an Elastic Metal server
+ paragraph: This guide walks you through the steps to create an Elastic Metal server on Scaleway.
+tags: elastic-metal, server
+dates:
+ validation: 2024-08-12
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Scaleway [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) provide on-demand dedicated servers similar to cloud instances. These servers are ideal for large workloads, big data, and applications requiring enhanced security and dedicated resources.
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+
+### Steps to create an Elastic Metal server
+
+1. Go to **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal server creation page displays.
+2. Click **Create Elastic Metal server**. The server creation wizard will launch.
+3. Complete the server creation wizard:
+ - Select the geographical region for your server by choosing an Availability Zone.
+
+ Currently, Elastic Metal servers are available in:
+ - Amsterdam, Netherlands (`AMS-1`, `AMS-2`)
+ - Paris, France (`PAR-1`, `PAR-2`)
+ - Warsaw, Poland (`WAW-2`, `WAW-3`)
+
+ - Choose your preferred billing method: **hourly** or **monthly**.
+ - Select a server configuration from the available options.
+ - Choose an OS to run on your server or opt for no preinstalled image.
+ - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration.
+ - Enter a name and, optionally, add tags to identify your server.
+ - Add your SSH key (required if installing an image on your server). Depending on the OS image, you may also be asked to configure the panel user for your server.
+ - Optionally, configure the available public bandwidth for your server. This option may not be available for all offers.
+ - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/vpc/concepts/#private-networks)
+ - Review the estimated environmental footprint of your Elastic Metal server.
+
+ For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page.
+
+ - Review the estimated cost based on your selected configuration.
+
+4. Click **Create Elastic Metal server** to finalize your order.
+
+You can monitor the delivery progress from the list of Elastic Metal servers in the console.
diff --git a/pages/elastic-metal/how-to/create-virtual-mac-group.mdx b/pages/elastic-metal/how-to/create-virtual-mac-group.mdx
new file mode 100644
index 0000000000..d4e3a043ef
--- /dev/null
+++ b/pages/elastic-metal/how-to/create-virtual-mac-group.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to create a virtual MAC group for Elastic Metal servers
+ description: This page explains how to create a virtual MAC group for Scaleway Elastic Metal servers
+content:
+ h1: How to create a virtual MAC group for Elastic Metal servers
+ paragraph: This page explains how to create a virtual MAC group for Scaleway Elastic Metal servers
+tags: virtual-mac mac-group elastic-metal
+dates:
+ validation: 2024-07-22
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+If you want to assign multiple flexible IPs to one virtual machine, you can create virtual MAC groups. A virtual MAC group contains at least two flexible IPs that share the same virtual MAC address.
+
+Once the virtual MAC group is active, IPs that share the same MAC address are linked together. Moving one IP of the group will automatically move all IPs within the group from one Elastic Metal server to another.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- [Created](/elastic-metal/how-to/create-server/) and [installed](/elastic-metal/how-to/install-server/) an Elastic Metal server
+- [Ordered more than one flexible IP](/elastic-metal/how-to/order-flexible-ip/)
+
+
+ You need to have at least two flexible IPs in your account to create a virtual MAC group.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab.
+3. Verify that at least one flexible IP is assigned to one of your servers.
+4. Drag and drop the second flexible IP from the **Flexible IPs** section to your Elastic Metal server.
+5. Click , then **Generate Mac**, and select **Associate with an existing MAC address from this server**.
+6. Choose the IP to copy the MAC address from in the list of available IPs and click **Generate MAC Address** to confirm:
+
+Creation of the virtual MAC group begins. Once ready, the status indicator becomes green.
+
+The IPs are now linked together in a virtual MAC group and share the same virtual MAC address. They can be assigned to the same virtual machine to provide a multi-IP environment.
+
+When moving one of the IPs of the group to another server, all other IPs within the group are automatically moved to the same server.
+
+To remove a flexible IP from a virtual MAC group, click , then **Generate MAC** and generate a new MAC address as described in the [adding a virtual MAC Address](/elastic-metal/how-to/add-virtual-mac-address/) documentation.
+
+
diff --git a/pages/elastic-metal/how-to/enable-smtp.mdx b/pages/elastic-metal/how-to/enable-smtp.mdx
new file mode 100644
index 0000000000..1a46a7907b
--- /dev/null
+++ b/pages/elastic-metal/how-to/enable-smtp.mdx
@@ -0,0 +1,41 @@
+---
+meta:
+ title: How to enable SMTP for Elastic Metal servers
+ description: Learn how to enable SMTP for Scaleway Elastic Metal servers.
+content:
+ h1: How to enable SMTP for Elastic Metal servers
+ paragraph: This guide explains how to enable SMTP for Scaleway Elastic Metal servers.
+tags: enable, smtp, elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2022-05-04
+categories:
+ - bare-metal
+---
+
+By default, the SMTP ports (25, 465, 587) for outgoing emails on your Elastic Metal server are closed and cannot be reached from our infrastructure.
+
+If you want to send emails from your server, you can enable SMTP for each Availability Zone from the console.
+
+
+- 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
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+- [Verified your identity](/account/how-to/verify-identity/)
+
+
+ This guide explains how to enable SMTP on Elastic Metal servers. If you need to enable SMTP on other resources, refer to our documentation on [how to send emails from your Instance](/instances/how-to/send-emails-from-your-instance/) and [how to enable SMTP on Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp).
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section on the side menu of the [Scaleway console](https://console.scaleway.com).
+
+2. Click the **General Settings** tab. The SMTP configuration displays.
+
+ You must [verify your identity](/account/how-to/verify-identity/) before you can enable the SMTP ports.
+
+3. Toggle the switch to **ON** beside each Availability Zone for which you want to enable SMTP.
+
+
+ If SMTP is not available for a specific Availability Zone, the zone will be greyed out.
+
+
diff --git a/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx b/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx
new file mode 100644
index 0000000000..cb8cf74002
--- /dev/null
+++ b/pages/elastic-metal/how-to/get-use-loyalty-reward.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to get and use a loyalty reward
+ description: This page explains how to use the loyalty reward for Scaleway Elastic Metal servers
+content:
+ h1: How to get and use a loyalty reward
+ paragraph: This page explains how to use the loyalty reward for Scaleway Elastic Metal servers
+tags: elastic-metal payback commitment fee
+dates:
+ validation: 2025-01-02
+ posted: 2022-12-01
+categories:
+ - bare-metal
+---
+
+When you order an Elastic Metal server with monthly billing, you pay a commitment fee to cover the setup cost of your machine. This fee grants you a lower monthly price and gives you the right to receive a loyalty reward if your server is up and running for 12 consecutive months without termination.
+
+The value of the reward is a cloud service voucher in the sum of the commitment fees paid at the time of purchase. The voucher is valid for six months, and you can use it for all Scaleway Cloud products except the Bare Metal category (hourly and monthly Elastic Metal, Apple Silicon, and their associated options). You receive the reward once per physical server, and it is automatically added to your Scaleway account.
+
+
+
+- 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
+- An Elastic Metal server that has been up and running for 12 consecutive months
+
+
+The following rules apply to the loyalty reward:
+
+* You are entitled to the loyalty reward:
+ * Once you have kept your Elastic Metal server running for 12 consecutive months without stopping,
+ * Once per physical server in your account.
+
+* The loyalty reward:
+ * Corresponds to the sum of the commitment fee paid when the server was ordered (excl. taxes).
+ * Is usable for all cloud resources except Bare Metal servers and their related options.
+ * Is valid for six months.
+ * Is splittable over several months.
+
+
+ The reward is available for six months and can be consumed pro rata per month or all at once. For example, if you received €49 of credit and consumed €15 of cloud resources during the first month, we will roll over the remaining €34 in the next month.
+
+
+
+ The loyalty reward is a cloud service voucher that can be used to consume Scaleway Cloud resources (except Bare Metal servers and their associated options). It is not possible to get a cash refund of the commitment fees.
+
+
+
diff --git a/pages/elastic-metal/how-to/index.mdx b/pages/elastic-metal/how-to/index.mdx
new file mode 100644
index 0000000000..cb0ccf1325
--- /dev/null
+++ b/pages/elastic-metal/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Elastic Metal servers - How Tos
+ description: Elastic Metal How Tos
+content:
+ h1: Elastic Metal - How Tos
+ paragraph: Elastic Metal How Tos
+---
diff --git a/pages/elastic-metal/how-to/install-server.mdx b/pages/elastic-metal/how-to/install-server.mdx
new file mode 100644
index 0000000000..a5b9d5e7ab
--- /dev/null
+++ b/pages/elastic-metal/how-to/install-server.mdx
@@ -0,0 +1,43 @@
+---
+meta:
+ title: How to install an Elastic Metal server from the Scaleway console
+ description: Learn how to install an Elastic Metal server from the Scaleway console.
+content:
+ h1: How to install an Elastic Metal server from the Scaleway console
+ paragraph: This guide explains how to install an Elastic Metal server from the Scaleway console.
+tags: elastic-metal, server, installation
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Scaleway [Elastic Metal](https://www.scaleway.com/en/elastic-metal/) allows you to order dedicated servers on-demand, similar to cloud Instances. These servers are ideal for large workloads, big data, and applications requiring enhanced security and dedicated resources.
+
+If you ordered your server without a preinstalled operating system, you can install an OS once the Elastic Metal server is delivered to your account.
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+ This procedure is not necessary if you preinstalled an OS on your Elastic Metal server during its creation.
+
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click **Install** next to the server you want to install. The server installation wizard displays.
+3. Select the operating system you want to install on the machine.
+
+ Elastic Metal servers are installed with a default partition layout. For custom partitioning, you can manually reinstall your server using [remote access](/elastic-metal/how-to/activate-remote-access/).
+
+4. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys. Select the keys to grant access to the server by checking the corresponding boxes.
+5. Click **Install server** to begin the installation process.
+
+ The OS installation can take up to one hour. You will be able to access the machine once the installation is complete.
+
+
+To view more details about your server, click its name in the Elastic Metal servers list. This will display detailed information about the machine, including its IP address, labels, and description.
diff --git a/pages/elastic-metal/how-to/kubernetes-on-riscv.mdx b/pages/elastic-metal/how-to/kubernetes-on-riscv.mdx
new file mode 100644
index 0000000000..3c3069ca99
--- /dev/null
+++ b/pages/elastic-metal/how-to/kubernetes-on-riscv.mdx
@@ -0,0 +1,47 @@
+---
+meta:
+ title: How to run Kubernetes nodes on RISC-V
+ description: This page explains how to use your Scaleway EM-RV1 Elastic Metal server as a Kosmos Kubernetes node
+content:
+ h1: How to run Kubernetes nodes on RISC-V
+ paragraph: This page explains how to use your Scaleway EM-RV1 Elastic Metal server as a Kosmos Kubernetes node
+tags: kosmos riscv elastic-metal
+dates:
+ validation: 2024-09-23
+ posted: 2024-03-22
+categories:
+ - bare-metal
+---
+
+
+
+ - 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 Kosmos cluster](/kubernetes/how-to/create-kosmos-cluster/) on which you have [configured a pool of external nodes](/kubernetes/how-to/edit-kosmos-cluster/#how-to-configure-external-nodes-to-join-the-cluster)
+ - [Created an Elastic Metal RV1 server](/elastic-metal/how-to/create-server/)
+ - [Created an API key](/iam/how-to/create-api-keys/) with the `KubernetesExternalNodeRegister` permission set.
+ - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+
+RISC-V is not yet officially supported in Kubernetes, but to let you test this technology with Kube containers, we have prepared an image with the necessary pre-built binaries.
+
+With Scaleway Kosmos and our Elastic Metal RV1, you can follow this guide to launch RISC-V containers on Kubernetes effortlessly, and in just a few minutes.
+
+1. [Install the Elastic Metal server](/elastic-metal/how-to/install-server/) with the `Kosmos` image.
+2. Go to the **Nodes** tab of your Kosmos cluster and click **Add external node**.
+3. Take note of the `POOL_ID` and `POOL_REGION` as you will need them in the following steps. Ignore the instructions on the page to connect your server to the pool.
+
+4. [Connect to your Elastic Metal RV1 server via SSH](/elastic-metal/how-to/connect-to-server/).
+5. Export noted env variables and secret key.
+
+ ```
+ export POOL_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+ export POOL_REGION=xx-xxx
+ export SCW_SECRET_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+ ```
+
+6. Run the node agent.
+
+ ```
+ sudo -E ./node-agent_linux_riscv64 -loglevel 0 -no-controller && sleep 10
+
+7. **Restart** your server.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/order-flexible-ip.mdx b/pages/elastic-metal/how-to/order-flexible-ip.mdx
new file mode 100644
index 0000000000..9286874c23
--- /dev/null
+++ b/pages/elastic-metal/how-to/order-flexible-ip.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to order a flexible IP for Elastic Metal servers
+ description: Learn how to order a flexible IP for Scaleway Elastic Metal servers.
+content:
+ h1: How to order a flexible IP for Elastic Metal servers
+ paragraph: This guide explains how to order a flexible IP for Scaleway Elastic Metal servers.
+tags: flexible-ip, flexible ip, elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+[Flexible IP addresses for Elastic Metal servers](/elastic-metal/concepts/#flexible-ip) are additional IP addresses available for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/).
+They allow you to move an IP from one server to another without changing your entire configuration. Flexible IPs can also be used as additional IP addresses to create virtual machines on your Elastic Metal server.
+
+
+ Scaleway offers flexible IPs for [Elastic Metal servers](/elastic-metal/concepts/#elastic-metal-server), [Instances](/instances/concepts/#instance), and [Public Gateways](/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the **Flexible IPs** tab at the top of the page to display the flexible IP configuration page.
+3. Click **+ Order flexible IP**. The order dialog displays.
+ - Select either:
+ - A flexible IPv4 (a single IPv4 address (`/32`) that can be routed to any of your Elastic Metal servers in the same Availability Zone)
+ - A flexible IPv6 (a `/64` IPv6 subnet that can be routed to any of your Elastic Metal servers in the same Availability Zone)
+4. Optionally, enter a description and tags to facilitate the management of your flexible IPs. Tags allow you to filter IP addresses in the Scaleway console.
+5. Click **Order a flexible IP** to confirm.
+
+The flexible IP will be assigned to your account and will appear in the list of your Elastic Metal flexible IPs.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/reboot-server.mdx b/pages/elastic-metal/how-to/reboot-server.mdx
new file mode 100644
index 0000000000..0ac757e0e0
--- /dev/null
+++ b/pages/elastic-metal/how-to/reboot-server.mdx
@@ -0,0 +1,34 @@
+---
+meta:
+ title: How to reboot your Elastic Metal server
+ description: This page explains how to reboot your Scaleway Elastic Metal server
+content:
+ h1: How to reboot your Elastic Metal server
+ paragraph: This page explains how to reboot your Scaleway Elastic Metal server
+tags: reboot elastic-metal reboot-server
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+If your [Elastic Metal server](https://www.scaleway.com/en/elastic-metal/) is no longer reachable from the internet or does not work as expected, you can reboot it from the [Scaleway console](https://console.scaleway.com). The reboot feature launches a power-cycle on the physical hardware and restarts the machine.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the name of the server you want to reboot.
+3. Click the **Reboot** button on the server information page.
+4. Select the **Normal** reboot mode and confirm by clicking **Reboot Elastic Metal server**.
+
+ Rebooting your server may corrupt your data if there are unwritten files. Your software will not be stopped before the server is being rebooted, and you should use this feature only when your server is not reachable over the internet.
+
+
+
diff --git a/pages/elastic-metal/how-to/reinstall-server.mdx b/pages/elastic-metal/how-to/reinstall-server.mdx
new file mode 100644
index 0000000000..e13c2a7811
--- /dev/null
+++ b/pages/elastic-metal/how-to/reinstall-server.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to reinstall an Elastic Metal server
+ description: This page explains how to install a Scaleway Elastic Metal server
+content:
+ h1: How to reinstall an Elastic Metal server
+ paragraph: This page explains how to install a Scaleway Elastic Metal server
+tags: reinstall elastic-metal
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+An Elastic Metal server can be reinstalled at any time from the [Scaleway console](https://console.scaleway.com). This can be useful when you want to run a different image on the machine or if you want to have a fresh installation.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+ Reinstalling your server permanently erases the disk and all its data. Make sure to have a backup before reinstalling your server.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click next to the server you want to reinstall. A drop-down menu displays.
+3. Click **Reinstall** in the menu to enter the installation wizard.
+4. Choose the operating system that you want to install on the machine.
+5. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it displays in the list of keys. Choose the keys to grant access to the server by ticking or unticking the corresponding checkbox.
+6. Click **Reinstall server** to launch the installation. It will take about 10 minutes to complete.
+
+
diff --git a/pages/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx b/pages/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx
new file mode 100644
index 0000000000..a381499afd
--- /dev/null
+++ b/pages/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: How to send metrics & logs from Elastic Metal servers to Cockpit
+ description: Learn to monitor Elastic Metal servers by sending metrics and logs to Scaleway Cockpit for real-time performance insights.
+content:
+ h1: How to send metrics & logs from Elastic Metal servers to Cockpit
+ paragraph: Learn to monitor Elastic Metal servers by sending metrics and logs to Scaleway Cockpit for real-time performance insights.
+tags: metrics grafana cockpit elastic-metal
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-13
+categories:
+ - bare-metal
+---
+
+Monitoring your dedicated servers with [Scaleway Cockpit](/cockpit/quickstart/) offers detailed information about performance and health, ensuring optimal functionality and proactive issue resolution.
+
+Cockpit provides a user-friendly interface for real-time monitoring of CPU, memory, disk usage, and network activity, enhancing the reliability and performance of bare metal servers.
+
+
+
+- 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
+- An [Elastic Metal](/elastic-metal/quickstart/) or [Dedibox](/dedibox-scaleway/quickstart/) server running on a Linux operating system
+
+
+* Having the default configuration on your agents might lead to more of your resources’ metrics being sent, a high consumption and a high bill at the end of the month.
+* Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information.
+
+
+## Accessing Cockpit
+
+1. Create a token with the `push` permission for metrics/logs to Cockpit by following the instructions provided [in the dedicated documentation](/cockpit/how-to/create-token/).
+2. Configure the Grafana Agent to push metrics/logs to Cockpit. Refer to the [official documentation](/cockpit/api-cli/configuring-grafana-agent/) for detailed instructions.
+
+ For efficient cost management and near real-time resource monitoring, it is recommended to set the interval to 1 minute.
+
+3. [Retrieve your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/), then use them to [access your Cockpit dashboards](/cockpit/how-to/access-grafana-and-managed-dashboards/).
+
+## Importing dashboards
+
+To monitor your bare metal servers, you can import pre-configured dashboards from the Grafana dashboard repository. One such dashboard is the Node Exporter Full dashboard, offering detailed server metrics. Follow these steps to import it:
+
+1. Visit the [Node Exporter Full dashboard](https://grafana.com/grafana/dashboards/12486-node-exporter-full/) on the Grafana dashboard repository.
+2. Copy the dashboard ID by clicking **Copy ID**.
+3. In Cockpit, navigate to the **Dashboards** section.
+4. Click **Import** and paste the copied dashboard ID.
+5. Follow the prompts to complete the import process.
+
+This process allows you to push metrics and logs to Scaleway’s Cockpit (Grafana) and monitor your Elastic Metal servers with real-time tracking of their health and performance.
+
+
diff --git a/pages/elastic-metal/how-to/shutdown-server.mdx b/pages/elastic-metal/how-to/shutdown-server.mdx
new file mode 100644
index 0000000000..e162e5ecaf
--- /dev/null
+++ b/pages/elastic-metal/how-to/shutdown-server.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: How to shut down an Elastic Metal server
+ description: This page explains how to shut down a Scaleway Elastic Metal server
+content:
+ h1: How to shut down an Elastic Metal server
+ paragraph: This page explains how to shut down a Scaleway Elastic Metal server
+tags: shut-down elastic-metal
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+An Elastic Metal server can be shut down from the [Scaleway console](https://console.scaleway.com). This powers off the physical server.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click next to the server you want to shut down. A drop-down menu displays.
+3. Click **Power off** in the menu.
+4. Confirm that you have shut down the operating system and click **Power off Elastic Metal server** to power off the server.
+
+ Make sure to stop your operating system by executing the `halt` command
+ before shutting off the server. Otherwise, you risk damaging the file system
+ and causing data loss.
+
+
+
diff --git a/pages/elastic-metal/how-to/use-private-networks.mdx b/pages/elastic-metal/how-to/use-private-networks.mdx
new file mode 100644
index 0000000000..d1cb5bdea4
--- /dev/null
+++ b/pages/elastic-metal/how-to/use-private-networks.mdx
@@ -0,0 +1,177 @@
+---
+meta:
+ title: How to use Private Networks with Elastic Metal servers
+ description: This page explains how to use Private Networks with Elastic Metal servers
+content:
+ h1: How to use Private Networks with Elastic Metal servers
+ paragraph: This page explains how to use Private Networks with Elastic Metal servers
+tags: private-networks elastic-metal private networks
+dates:
+ validation: 2024-09-30
+ posted: 2022-01-17
+categories:
+ - bare-metal
+---
+
+[Private Networks](/vpc/concepts/#private-networks) allow your Elastic Metal servers to communicate in an isolated and secure network without needing to be connected to the public internet. This is an optional-billed feature, available with our Elastic Metal server ranges.
+
+Each server can be connected to one or several Private Networks, letting you build your own network topologies. Private Networks' built-in DHCP server manages the allocation of private IP addresses for Elastic Metal servers (and other resources) when they are attached to the network.
+
+Private Networks allow your Elastic Metal servers to communicate with other Scaleway resources in an isolated and secure network, without the need of being connected to the public internet.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to enable and disable the Private Networks feature
+
+
+ The Private Networks feature must be enabled on a per-server basis.
+
+
+You can enable/disable Private Networks on compatible Elastic Metal servers either during creation of the server, or afterward.
+
+### During the creation of your Elastic Metal server
+
+You can choose to enable the Private Networks feature during the [creation of your Elastic Metal server](/elastic-metal/how-to/create-server/). Simply use the toggle icon when prompted by the creation wizard to enable the feature. If you do not enable the feature, it remains disabled by default.
+
+### After the creation of your Elastic Metal server
+
+1. Navigate to the **Elastic Metal servers** page of the [Scaleway console](https://console.scaleway.com/elastic-metal/servers). A list of your Elastic Metal servers displays.
+2. Click the server for which you want to enable/disable the Private Networks feature. The server's **Overview** page displays.
+3. Scroll to the **Private Networks feature** panel.
+4. Click **Enable** or **Disable** to enable/disable the Private Networks feature as required.
+5. Confirm the action when prompted.
+
+ Private Networks for Elastic Metal servers is a billable feature, and will be billed hourly or monthly depending on the type of Elastic Metal server you chose. If your Elastic Metal server is billed monthly and you disable the Private Networks feature after previously enabling it, you will still be billed for the feature for the current calendar month.
+
+
+## How to attach and detach Elastic Metal servers to a Private Network
+
+You can attach/detach Elastic Metal servers to a Private Network from either the Elastic Metal section of the console, or the VPC section.
+
+You can also reserve IP addresses with IPAM and attach them to specific MAC addresses, to facilitate the attachment of virtual machines hosted on your server, to Private Networks. See the IPAM documentation on [reserving a private IP with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address) for more information.
+
+### From the Elastic Metal section of the console
+
+1. Navigate to the **Elastic Metal** page of the [Scaleway console](https://console.scaleway.com/elastic-metal/servers). A list of your Elastic Metal servers displays.
+2. Click the server you want to attach/detach from a Private Network.
+3. Click the **Private Networks** tab.
+4. Click **Attach to a Private Network** and continue to step 5. Otherwise, to detach your server from a Private Network, click the icon next to the Private Network and confirm the action when prompted.
+5. Either:
+ - Select **Attach to an existing Private Network**, and choose a network from the drop-down list to attach your server to. Remember, only Private Networks in the same region as your server will be displayed.
+ - Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create.
+
+ The Private Network will have default settings, meaning:
+ - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region
+ - It has an auto-generated [CIDR block](/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network.
+
+6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network.
+7. Click **Attach to Private Network** to confirm.
+
+### From the VPC section of the console
+
+Creating a new Private Network from the VPC section of the console allows you to control which VPC you create it in, and to optionally create a custom CIDR block for the network.
+
+See our dedicated documentation [how to create a Private Network](/vpc/how-to/create-private-network/) and [how to attach resources](/vpc/how-to/attach-resources-to-pn/) from the VPC section of the console.
+
+## How to configure the network interface on your Elastic Metal server for Private Networks
+
+You must configure the virtual network interface on each Elastic Metal server you have added to a Private Network. Traffic from the public internet and traffic from a Private Network will pass through the same network interface of the Elastic Metal server. We must therefore separate the traffic by adding a VLAN interface.
+
+
+ The following commands show how to configure the network interface on an Elastic Metal server running Ubuntu. For other operating systems, check the distributor's documentation.
+
+
+1. Make a note of your Elastic Metal server's VLAN ID. You can view this in the **Private Networks** tab of the Elastic Metal server in question.
+2. [Connect to your Elastic Metal server via SSH](/elastic-metal/how-to/connect-to-server/).
+3. Find the network interface using the `ip link show` command:
+ ```bash
+ ip link show
+ ```
+ The output will vary depending on the server, but here is an example:
+
+ ```
+ 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 2: eno1: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
+ link/ether 9c:b6:54:bb:6c:64 brd ff:ff:ff:ff:ff:ff
+ 3: eno2: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
+ link/ether 9c:b6:54:bb:6c:65 brd ff:ff:ff:ff:ff:ff
+ ```
+
+ In this case, the network interface is identified by `eno1`.
+4. Enter the following command to add a virtual link to the network interface. Replace `1234` with the VLAN ID you noted down in step 1 and `eno1` (if necessary) with the relevant network interface name identified in step 3.
+ ```bash
+ sudo ip link add link eno1 name eno1.1234 type vlan id 1234
+ ```
+5. Enter the following command to bring up the virtual link. Make the necessary replacements for `eno1` and `1234` as you did previously.
+ ```
+ sudo ip link set eno1.1234 up
+ ```
+
+ If DHCP is [activated on your Private Network](/vpc/how-to/activate-dhcp/) and you are using a DHCP client, you do not need to continue to the next step. Your Elastic Metal server should be assigned an IP address which is compatible with our [internal IPAM](/vpc/concepts/#ipam).
+
+ If you have not activated DHCP or do not have a DHCP client, proceed to the next step to manually configure an IP address.
+
+
+ If you are running multiple virtual machines on an Elastic Metal server, our managed DHCP is not currently able to distribute IP addresses to your virtual machines. We recommend that you use the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/) to book IP addresses for your virtual machines, and assign them manually.
+
+
+6. Enter the following command to assign an IP address. Make the necessary replacements for `eno1` and `1234` as you did previously.
+ ```bash
+ sudo ip addr add 10.10.10.10/24 dev eno1.1234
+ ```
+7. Optionally persist this configuration across reboots by creating a new netplan configuration. Make the necessary replacements for `eno1` and `1234` as you did previously.
+ ```yaml
+ # e.g.: /etc/netplan/51-private-networks.yaml
+ network:
+ version: 2
+ vlans:
+ eno1.1234:
+ id: 1234
+ link: eno1
+ addresses:
+ - 10.10.10.10/24
+ ```
+
+ - To test your configuration before applying it, use the `sudo netplan try` command. Once tested, apply the configuration with `sudo netplan apply`.
+ - Ensure that you have defined the same adapter name (`eno1`) for the default network interface in the default Netplan configuration file (`/etc/netplan/50-cloud-init.yaml`) before applying the new configuration.
+
+
+## How to configure the Private Network on Windows Server 2019
+
+1. Log into your server as `Administrateur` using the Remote Desktop client.
+
+ The default language of Windows Server installations is French. Make sure to use the user `Administrateur` when connecting to your server. If required, you can [change the language of the operating system](/dedicated-servers/how-to/change-win-server-language/).
+
+2. Launch the **Server Manager** application.
+3. Click **Local Server** in the menu on the left. Then click **NIC Teaming** in the **Properties** section.
+4. Click **Tasks** > **New Team**. Enter a team name of your choice (e.g. `default`) and tick the checkbox **NIC1**. Then click **OK**.
+5. Select the **Team interfaces** tab in the **Adapters and Interfaces** section. Click **Tasks** > **Add interface**. A pop-up displays.
+6. Enter a name for the new interface (e.g. `default - VLAN 1234` if your VLAN ID is 1234). Select **Specific VLAN** and enter the ID of your VLAN (e.g. 1234). Click **OK** to confirm.
+
+ Two network interfaces display: Your VLAN and `default`. Make sure to keep the default network, otherwise you will lose access to your server via the public internet.
+
+7. Click **Start** > **Execute** and type `ncpa.cpl`. Then click **OK** to open the network connection manager.
+8. Click on your VLAN network connection and right-click on it to open the menu. Click **Properties** to display the connection properties.
+9. Select **Internet Protocol version 4 (TCP/IPv4)** and click **Properties**. A pop-up displays.
+10. Click **Use the following IP address** and configure the IPv4 configuration of your Private Network. Then click **OK** to save your configuration.
+11. Click **Close** to close the network interface properties.
+
+ You completed the configuration of your Private Network on Windows Server 2019.
+
+ You can use the `ipconfig` command to verify your IP configuration from a command prompt.
+
+
+## How to delete a Private Network
+
+
+ Before deleting a Private Network, you must detach all resources attached to it.
+
+
+See our dedicated documentation [how to delete a Private Network](/vpc/how-to/delete-private-network/).
+
+
diff --git a/pages/elastic-metal/how-to/use-rescue-mode.mdx b/pages/elastic-metal/how-to/use-rescue-mode.mdx
new file mode 100644
index 0000000000..55ca878852
--- /dev/null
+++ b/pages/elastic-metal/how-to/use-rescue-mode.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: How to use rescue mode on Elastic Metal servers
+ description: This page explains how to use rescue mode on Elastic Metal servers
+content:
+ h1: How to use rescue mode on Elastic Metal servers
+ paragraph: This page explains how to use rescue mode on Elastic Metal servers
+tags: elastic-metal rescue-mode
+dates:
+ validation: 2024-08-13
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Rescue mode allows you to boot an [Elastic Metal server](https://www.scaleway.com/en/elastic-metal/) from the network. It loads a rescue operating system based on [Ubuntu Linux](https://ubuntu.com/) that runs entirely in the server's RAM. This enables you to perform maintenance and data recovery operations, even if the machine is otherwise unreachable in its normal mode.
+
+
+ This documentation specifically covers rescue mode for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/). If you need to use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/), please refer to the corresponding [documentation](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode).
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. This opens the Elastic Metal dashboard.
+
+2. Select the machine you want to reboot into rescue mode from the list of your Elastic Metal servers. Click the server's name to access its information page.
+
+3. Scroll down to the **Rescue mode** section and click **Boot in rescue mode** to start the reboot process.
+
+
+ Rebooting your server may result in data corruption if there are unwritten files. The server's software will not be stopped before the reboot, so only use this feature when your server is not reachable over the internet.
+
+
+
+ Depending on your server's hardware model, the reboot process may take several minutes.
+
+
+4. After the server has rebooted, use a terminal application to log into the server via SSH using the credentials provided in your console:
+
+
+
+ ```
+ ssh rescue@
+ ```
+
+
+ Rescue mode uses the SSH keys registered for your Elastic Metal server for authentication. You can log in using the `rescue` user and your SSH key. If you have lost your private key, you can still access your server using the password displayed in the console.
+
+
+You are now logged into rescue mode and can perform maintenance tasks on the server. Rescue mode is based on Ubuntu, so you can execute commands as you would on any Ubuntu Linux system.
+
+
+
+
+ Rescue mode runs entirely in the server's RAM. To access files on the hard disk, you need to mount it.
+
+
+## Rebooting back to normal mode
+
+After completing maintenance, you can reboot the server back into its normal operating system.
+
+To do this, click **Switch to normal mode** in the rescue mode section of the server's details page. The server will reboot into its installed operating system and should be available in normal mode within a few minutes.
\ No newline at end of file
diff --git a/pages/elastic-metal/how-to/view-the-event-logs.mdx b/pages/elastic-metal/how-to/view-the-event-logs.mdx
new file mode 100644
index 0000000000..9cb722bbe1
--- /dev/null
+++ b/pages/elastic-metal/how-to/view-the-event-logs.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: How to view the event logs of an Elastic Metal server
+ description: This page explains how to view the event logs of a Scaleway Elastic Metal server
+content:
+ h1: How to view the event logs of an Elastic Metal server
+ paragraph: This page explains how to view the event logs of a Scaleway Elastic Metal server
+tags: elastic-metal event-log
+dates:
+ validation: 2024-08-05
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the name of the server whose logs you want to see. The server details page displays.
+3. Click the **Logs** tab.
+
+ A list of operations executed on your Elastic Metal server is shown. These logs include tasks like start, stop, and re-installation of the server.
+
+
diff --git a/pages/elastic-metal/index.mdx b/pages/elastic-metal/index.mdx
new file mode 100644
index 0000000000..ae013641c9
--- /dev/null
+++ b/pages/elastic-metal/index.mdx
@@ -0,0 +1,86 @@
+---
+meta:
+ title: Elastic Metal Documentation
+ description: Dive into Scaleway Elasitc Metal with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/elastic-metal/quickstart.mdx b/pages/elastic-metal/quickstart.mdx
new file mode 100644
index 0000000000..d94c8bcc1e
--- /dev/null
+++ b/pages/elastic-metal/quickstart.mdx
@@ -0,0 +1,80 @@
+---
+meta:
+ title: Elastic Metal - Quickstart
+ description: This page shows you how to get started with Scaleway Elastic Metal.
+content:
+ h1: Elastic Metal - Quickstart
+ paragraph: This page shows you how to get started with Scaleway Elastic Metal.
+tags: elastic-metal server
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - bare-metal
+---
+
+Scaleway Elastic Metal are dedicated physical servers you can order on-demand, like Instances. These servers are ideal for large workloads, big data, and applications that require increased security and dedicated resources. You can install an OS or other [image](/elastic-metal/concepts/#image) on your Elastic Metal server and connect to it via SSH to use it as you require. You can power off the server when you are not using or delete it from your account once you have finished with it.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+
+## How to create an Elastic Metal server
+
+1. Go to **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal server creation page displays.
+2. Click **Create Elastic Metal server**. The server creation wizard will launch.
+3. Complete the server creation wizard:
+ - Select the geographical region for your server by choosing an Availability Zone.
+
+ Currently, Elastic Metal servers are available in:
+ - Amsterdam, Netherlands (`AMS-1`, `AMS-2`)
+ - Paris, France (`PAR-1`, `PAR-2`)
+ - Warsaw, Poland (`WAW-2`, `WAW-3`)
+
+ - Choose your preferred billing method: **hourly** or **monthly**.
+ - Select a server configuration from the available options.
+ - Choose an OS to run on your server or opt for no preinstalled image.
+ - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration.
+ - Enter a name and, optionally, add tags to identify your server.
+ - Add your SSH key (required if installing an image on your server). Depending on the OS image, you may also be asked to configure the panel user for your server.
+ - Optionally, configure the available public bandwidth for your server. This option may not be available for all offers.
+ - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/vpc/concepts/#private-networks)
+ - Review the estimated environmental footprint of your Elastic Metal server.
+
+ For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page.
+
+ - Review the estimated cost based on your selected configuration.
+
+4. Click **Create Elastic Metal server** to finalize your order.
+
+You can monitor the delivery progress from the list of Elastic Metal servers in the console.
+
+## How to install an Elastic Metal server
+
+
+ This action is useful if you created your server without a preinstalled operating system. You can proceed with the installation once the Elastic Metal server is in a `Ready` state.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the side menu.
+2. Choose the Elastic Metal server you want to install from the list.
+3. Click **Install** to launch the OS installation wizard.
+4. Choose the operating system that you want to install on the machine.
+5. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key).
+
+ If you have already [uploaded an SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys.
+
+6. Check the corresponding boxes to grant access to the server.
+7. Click **Install server**.
+
+## How to power off an Elastic Metal server
+
+
+ Before powering off an Elastic Metal server, first you should power off its operating system by connecting to the server and executing the `halt` command.
+
+
+1. Click **Elastic Metal** in the **Bare Metal** section of the side menu.
+2. Click next to the server you want to power off.
+3. Click **Power off** in the drop-down menu.
+4. Click **Power off Elastic Metal server**.
\ No newline at end of file
diff --git a/pages/elastic-metal/reference-content/elastic-metal-datasheet.mdx b/pages/elastic-metal/reference-content/elastic-metal-datasheet.mdx
new file mode 100644
index 0000000000..a755686ff3
--- /dev/null
+++ b/pages/elastic-metal/reference-content/elastic-metal-datasheet.mdx
@@ -0,0 +1,234 @@
+---
+meta:
+ title: Elastic Metal server datasheet
+ description: This page shows the technical characteristics of the different Elastic Metal offers.
+content:
+ h1: Elastic Metal server datasheet
+ paragraph: This page shows the technical characteristics of the different Elastic Metal offers.
+tags: elastic-metal server
+dates:
+ validation: 2025-02-01
+ posted: 2023-12-18
+categories:
+ - bare-metal
+---
+
+This datasheet provides a concise overview of the performance, technical features, components, materials, and associated documentation for the different Elastic Metal server offers.
+
+
+The **Max. NIC bandwidth** indicates the overall capacity of the physical network interface adapter on the Elastic Metal server.
+The **Public bandwidth** refers to the designated internet bandwidth for the server, while the **Private bandwidth** signifies the permitted bandwidth for the server within Private Networks.
+It is important to note that both public internet and Private Networks use the same physical network interface.
+
+
+## Aluminium range
+
+### Server EM-A210R-HDD
+
+| Server EM-A210R-HDD | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD Ryzen PRO 3600 6C/12T 3.6 GHz |
+| **RAM** | 16 GiB DDR4 ECC |
+| **Disk** | 2 x 1 TB HDD SATA |
+| **Max. NIC bandwidth** | 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones** | PAR1, PAR2, AMS1 |
+
+### Server EM-A315X-SSD
+
+| Server EM-A315X-SSD | |
+|-----------------------|-----------------------------------|
+| **CPU** | Intel Xeon E5 1410 v2 4C/8T 2.8 GHz |
+| **RAM** | 64 GiB DDR3 ECC |
+| **Disk** | 2 x 1 TB SSD SATA |
+| **Max. NIC bandwidth** | 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1 |
+
+### Server EM-A410X-SSD
+
+| Server EM-A410X-SSD | |
+|-----------------------|-----------------------------------|
+| **CPU** | Intel Xeon E5 1650 6C/12T 3.2 GHz |
+| **RAM** | 64 GiB DDR3 ECC |
+| **Disk** | 2 x 1 TB SSD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2 |
+
+## Beryllium range
+
+### Server EM-B111X-SATA
+
+| Server EM-B111X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2620 or equivalent 6C/12T 2 GHz |
+| **RAM** | 192 GiB DDR3 ECC |
+| **Disk** | 2 x 8 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2 |
+
+### Server EM-B112X-SSD
+
+| Server EM-B112X-SSD | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2620 or equivalent 6C/12T 2 GHz |
+| **RAM** | 192 GiB DDR3 ECC |
+| **Disk** | 2 x 1 TB SSD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1 |
+
+### Server EM-B211X-SATA
+
+| Server EM-B211X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2670 or equivalent 8C/16T 2.6 GHz |
+| **RAM** | 192 GiB DDR3 ECC |
+| **Disk** | 2 x 8 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B212X-SSD
+
+| Server EM-B212X-SSD | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2670 or equivalent 8C/16T 2.6 GHz |
+| **RAM** | 192 GiB DDR3 ECC |
+| **Disk** | 2 x 1 TB SSD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1 |
+
+### Server EM-B220E-NVME
+
+| Server EM-B220E-NVME | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD EPYC 7232P 8C/16T 3.1 GHz |
+| **RAM** | 64 GiB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe |
+| **Max. NIC bandwidth**| 10 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 10 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B311X-SATA
+
+| Server EM-B311X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2670 v2 10C/20T 2.5 GHz |
+| **RAM** | 256 GiB DDR3 ECC |
+| **Disk** | 2 x 12 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B312X-SSD
+
+| Server EM-B312X-SSD | |
+|-----------------------|-----------------------------------|
+| **CPU** | 2 x Intel Xeon E5 2670 v2 10C/20T 2.5 GHz |
+| **RAM** | 256 GiB DDR3 ECC |
+| **Disk** | 2 x 1 TB SSD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B320E-NVME
+
+| Server EM-B320E-NVME | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD EPYC 7232P 8C/16T 3.1 GHz |
+| **RAM** | 128 GiB DDR4 ECC |
+| **Disk** | 2 x 2 TB NVMe |
+| **Max. NIC bandwidth**| 10 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 10 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B420E-NVME
+
+| Server EM-B420E-NVME | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD EPYC 7272 12C/24T 2.9 GHz |
+| **RAM** | 128 GiB DDR4 ECC |
+| **Disk** | 2 x 1 TB NVMe |
+| **Max. NIC bandwidth**| 10 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 10 Gbps |
+| **Availability Zones**| PAR2 |
+
+### Server EM-B520E-NVME
+
+| Server EM-B520E-NVME | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD EPYC 7272 12C/24T 2.9 GHz |
+| **RAM** | 256 GiB DDR4 ECC |
+| **Disk** | 2 x 2 TB NVMe |
+| **Max. NIC bandwidth**| 10 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 10 Gbps |
+| **Availability Zones**| PAR2 |
+
+## Iridium range
+
+### Server EM-I210E-NVME
+
+| Server EM-I210E-NVME | |
+|-----------------------|-----------------------------------|
+| **CPU** | AMD EPYC 7313P 16C/32T 3 GHz |
+| **RAM** | 128 GiB DDR4 ECC |
+| **Disk** | 2 x 1.92 TB NVMe |
+| **Max. NIC bandwidth**| 10 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 10 Gbps |
+| **Availability Zones**| PAR1, PAR2 |
+
+## Lithium range
+
+### Server EM-L101X-SATA
+
+| Server EM-L101X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | Intel Xeon E5 1410 v2 4C/8T 2.8 GHz |
+| **RAM** | 96 GiB DDR3 ECC |
+| **Disk** | 2 x 6 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1, WAW2 |
+
+### Server EM-L105X-SATA
+
+| Server EM-L105X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | Intel Xeon E5 1410 v2 4C/8T 2.8 GHz |
+| **RAM** | 96 GiB DDR3 ECC |
+| **Disk** | 4 x 6 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1 |
+
+### Server EM-L110X-SATA
+
+| Server EM-L110X-SATA | |
+|-----------------------|-----------------------------------|
+| **CPU** | Intel Xeon E5 1410 v2 4C/8T 2.8 GHz |
+| **RAM** | 96 GiB DDR3 ECC |
+| **Disk** | 4 x 12 TB HDD SATA |
+| **Max. NIC bandwidth**| 1 Gbps |
+| **Public bandwidth** | 1 Gbps |
+| **Private bandwidth** | 1 Gbps |
+| **Availability Zones**| PAR1, PAR2, AMS1 |
diff --git a/pages/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx b/pages/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx
new file mode 100644
index 0000000000..7235e11537
--- /dev/null
+++ b/pages/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx
@@ -0,0 +1,183 @@
+---
+meta:
+ title: Elastic Metal RV1 guidelines
+ description: This page provides guidelines to use your EM-RV1 server.
+content:
+ h1: Elastic Metal RV1 guidelines
+ paragraph: This page provides guidelines to use your EM-RV1 server.
+tags: elastic-metal server riscv em-rv1
+dates:
+ validation: 2024-09-16
+ posted: 2024-03-15
+categories:
+ - bare-metal
+---
+
+## Boot process
+
+EM-RV1 servers do not support standard UEFI or BIOS boot, therefore the boot
+process might slightly differ from other servers. At boot, the bootloader
+expects the eMMC to be partitioned as GPT, and will look for a `boot.itb` file
+in the first or second partition. The partition that contains this boot file
+must be formatted as FAT32.
+
+This `boot.itb` file is in fact a [FIT Image](https://docs.u-boot.org/en/latest/usage/fit/source_file_format.html)
+that must contain the following sections:
+
+ - **kernel**: A Linux kernel image.
+ - **fdt**: A [device tree](https://en.wikipedia.org/wiki/Devicetree).
+ - **opensbi**: The SBI as defined by [RISC-V SBI
+ specification](https://github.com/riscv-non-isa/riscv-sbi-doc/).
+ - **env**: A text-based environment file that defines the following keys:
+ - `usr_bootargs`: Command-line arguments to pass to the kernel.
+ - `usr_has_ramdisk`: Set to `1` if we should load the ramdisk from the FIT
+ image.
+ - **ramdisk** (optional): A ramdisk image.
+
+The following section will explain in details how to create your own boot FIT image.
+
+## Boot a custom kernel
+
+In this section, you will build a boot image based off a close-to-mainline
+Linux kernel.
+
+
+ Mainline Linux is not fully compatible with EM-RV1 servers yet.
+
+
+
+
+- Installed an EM-RV1 server with Ubuntu
+- Proficient knowledge of Linux systems
+- A few hours of availability to build a Linux kernel
+
+1. Connect to your EM-RV1 server using SSH.
+2. Install the build dependencies.
+ ```bash
+ sudo apt update
+ sudo apt install -y \
+ autoconf bc bison dwarves flex gawk git make \
+ libelf-dev libssl-dev \
+ u-boot-tools device-tree-compiler \
+ xz-utils
+ ```
+3. Clone the projects to build.
+ ```bash
+ git clone --depth=1 https://github.com/revyos/th1520-linux-kernel.git linux
+ git clone https://github.com/revyos/thead-opensbi.git opensbi
+ git clone https://github.com/scaleway/em-rv1.git
+ ```
+4. Build the Linux kernel.
+ ```bash
+ cd linux/
+ make revyos_defconfig
+ # This can take several hours.
+ make -j
+ sudo make modules_install
+ cd ..
+ ```
+5. Build OpenSBI.
+ ```bash
+ cd opensbi/
+ make PLATFORM=generic -j
+ cd ..
+ ```
+6. Build and install the FIT image.
+ ```bash
+ cd em-rv1/fit/
+
+ # Build the device tree
+ cpp \
+ -nostdinc \
+ -I ../linux/arch/riscv/boot/dts/thead/ \
+ -I ../linux/include/ \
+ -undef \
+ -x assembler-with-cpp \
+ em-rv1-c4m16s128-a.dts \
+ | dtc -o em-rv1-c4m16s128-a.dtb
+
+ # Build the FIT image
+ sudo mv /boot/boot.itb /boot/boot.itb.bak
+ sudo mkimage -f em-rv1-c4m16s128-a-boot.its /boot/boot.itb
+
+ cd -
+ ```
+7. Reboot the server to load the new kernel.
+
+## Update the kernel
+
+Due to hardware specificities, it is not possible to use the kernel provided by
+major Linux distributions directly on EM-RV1 servers. Instead, we provide a
+custom upgrade channel. Follow the steps below to update your kernel:
+
+1. [Reboot your EM-RV1 server in rescue mode](/elastic-metal/how-to/use-rescue-mode/).
+2. Log into the machine over SSH using the `rescue` user.
+3. Update the kernel:
+ ```bash
+ sudo rv1 update-kernel
+ ```
+
+
+ If you prefer to run a more recent Linux kernel instead of the
+ vendor-provided kernel, you can append the `--tree mainline` option.
+
+ Although we do not recommend it, you can also enable support for vector
+ instructions with the `--enable-vector` flag. Be aware that this feature
+ makes your system vulnerable to the
+ [GhostWrite](https://ghostwriteattack.com/) attack and implements an
+ unratified version of RISC-V vector instructions (RVV 0.7.1) which requires
+ specific development efforts.
+
+ For a comprehensive list of options, refer to `rv1 update-kernel --help`.
+
+4. Wait for the update to complete. This step can take a few minutes.
+5. Reboot the server in normal mode.
+
+
+If you are updating from kernel version `5.10.113-scw0` or lower, note that
+newer kernels disable vector instructions by default. Refer to the process
+above if you still wish to keep them enabled.
+
+
+
+## Android
+
+### Remote access
+
+This guide will help you get a remote access on the Android distribution
+installed on your EM-RV1 server.
+
+
+
+- Installed [Android Platform
+ tools](https://developer.android.com/tools/releases/platform-tools) on your
+ local machine
+- Installed [scrcpy](https://github.com/Genymobile/scrcpy#get-the-app) on your
+ local machine
+- Installed the Android image on your EM-RV1 server
+
+1. Open a SSH tunnel to the ADB daemon running on your server:
+ ```bash
+ ssh -L '5555:localhost:5555' root@
+ ```
+ Make sure you keep this session open in the background during the next
+ steps.
+2. In a new local shell, connect your local ADB client to the remote daemon
+ through the SSH tunnel you created in the previous step:
+ ```bash
+ adb connect localhost:5555
+ ```
+3. Start a `scrcpy` session on this ADB session:
+ ```bash
+ scrcpy -s localhost:5555
+ ```
+
+
+Once connected to the ADB daemon, you can use common ADB commands from your
+local computer. For example, you can install an APK on the remote machine with
+the following command:
+
+```bash
+adb -s localhost:5555 install path/to/app.apk
+```
+
diff --git a/pages/elastic-metal/reference-content/elastic-metal-stock-levels.mdx b/pages/elastic-metal/reference-content/elastic-metal-stock-levels.mdx
new file mode 100644
index 0000000000..7fc2951818
--- /dev/null
+++ b/pages/elastic-metal/reference-content/elastic-metal-stock-levels.mdx
@@ -0,0 +1,27 @@
+---
+meta:
+ title: Elastic Metal Server stock levels explained
+ description: Learn about the different stock levels for Elastic Metal servers displayed in the Scaleway API and console, including availability, low stock, and out-of-stock statuses.
+content:
+ h1: Elastic Metal Server stock levels explained
+ paragraph: Learn about the different stock levels for Elastic Metal servers displayed in the Scaleway API and console, including availability, low stock, and out-of-stock statuses.
+tags: elastic-metal server
+dates:
+ validation: 2024-08-19
+ posted: 2024-02-14
+categories:
+ - bare-metal
+---
+
+The Elastic Metal API and the Scaleway console may display stock levels for Elastic Metal servers. Below are the available stock level statuses:
+
+- **Available**: Indicates that there is sufficient stock available to meet the demand for this offer.
+- **Low Stock**: Indicates a reduced stock level. Typically, this means there are 5 or fewer machines of this offer available. However, there are exceptions:
+ - For EM-T210E-NVME, the threshold is 2 machines.
+ - For EM-T510X-NVME, the threshold is 1 machine.
+- **Temporarily out of stock**: Signifies that the offer is currently sold out. Restocking will occur as soon as possible.
+
+ If an offer is **temporarily out of stock**, the API response will be `"stock" : "empty"`.
+
+
+If you have any further questions, feel free to contact our [support team](https://console.scaleway.com/support/tickets/create?for=elastic-metal).
\ No newline at end of file
diff --git a/pages/elastic-metal/reference-content/end-of-support-esxi.mdx b/pages/elastic-metal/reference-content/end-of-support-esxi.mdx
new file mode 100644
index 0000000000..115629c9e0
--- /dev/null
+++ b/pages/elastic-metal/reference-content/end-of-support-esxi.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: End of VMware ESXi support on Scaleway Elastic Metal and Dedibox servers
+ description: Learn about the end of support of VMware ESXi images on Scaleway Elastic Metal and Dedibox servers.
+content:
+ h1: End of VMware ESXi support on Scaleway Elastic Metal and Dedibox servers
+ paragraph: Learn about the end of support of VMware ESXi images on Scaleway Elastic Metal and Dedibox servers.
+tags: elastic-metal server dedibox vmware esxi
+dates:
+ validation: 2024-11-22
+ posted: 2024-11-22
+categories:
+ - bare-metal
+---
+
+Following Broadcom's acquisition of VMware and the subsequent change in its licensing policy, Broadcom has discontinued the general availability of its free vSphere Hypervisor (ESXi).
+As a result, we have removed this image from automatic installation on our Elastic Metal and Dedibox servers.
+
+This change does not affect servers currently running ESXi images. However, it will no longer be possible to reinstall ESXi on existing Elastic Metal or Dedibox servers or install it on new servers using Scaleway-provided ESXi images.
+
+
+ For more information about Broadcom's decision to retire the vSphere Free Edition images, refer to their official knowledge base article: [End Of General Availability of the free vSphere Hypervisor (ESXi 7.x and 8.x)](https://knowledge.broadcom.com/external/article?legacyId=2107518).
+
+
+You may still be able to install ESXi on Elastic Metal or Dedibox servers using the [KVM-over-IP](/dedibox-kvm-over-ip/quickstart/) system. However, note that we cannot provide support for its configuration or operation.
+
+For the best experience, we recommend using one of the officially supported hypervisors:
+
+- [Proxmox VE](/tutorials/configure-failover-proxmox/)
+- [Microsoft Hyper-V](/tutorials/configure-vm-hyperv/)
\ No newline at end of file
diff --git a/pages/elastic-metal/reference-content/index.mdx b/pages/elastic-metal/reference-content/index.mdx
new file mode 100644
index 0000000000..b8845ff7be
--- /dev/null
+++ b/pages/elastic-metal/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Elastic Metal servers - Additional content
+ description: Elastic Metal additional content
+content:
+ h1: Elastic Metal - Additional content
+ paragraph: Elastic Metal additional content
+---
\ No newline at end of file
diff --git a/pages/elastic-metal/reference-content/shared-responsibility-model.mdx b/pages/elastic-metal/reference-content/shared-responsibility-model.mdx
new file mode 100644
index 0000000000..662f4f1dd1
--- /dev/null
+++ b/pages/elastic-metal/reference-content/shared-responsibility-model.mdx
@@ -0,0 +1,118 @@
+---
+meta:
+ title: Scaleway Bare Metal Shared Responsibility Model
+ description: Learn about the shared responsibility model for Scaleway Bare Metal services, outlining the roles of Scaleway and users in managing server security, backups, and compliance.
+content:
+ h1: Scaleway Bare Metal Shared Responsibility Model
+ paragraph: Learn about the shared responsibility model for Scaleway Bare Metal services, outlining the roles of Scaleway and users in managing server security, backups, and compliance.
+tags: bare metal shared responsibility
+dates:
+ validation: 2025-01-20
+ posted: 2024-07-18
+categories:
+ - bare-metal
+---
+
+On this page, we outline the roles and responsibilities for maintaining and securing your Bare Metal servers.
+Our shared responsibility model clarifies the division of duties between Scaleway and our users, ensuring clarity in managing server availability, backups, configurations, and security measures.
+By understanding this shared responsibility, you can optimize the performance, reliability, and security of your Scaleway Bare Metal services.
+
+## Product resiliency
+
+### Availability
+
+Bare Metal Products target the following power supplies and connectivity SLOs:
+
+* For Dedibox servers:
+ * Start: 99.9% availability
+ * Pro and Store: 99.95% availability
+ * Core: 99.99% availability
+* For Elastic Metal servers:
+ * Aluminium: 99.9% availability
+ * Beryllium and Lithium: 99.95% availability
+ * Iridium: 99.99% availability
+* For Apple silicon servers:
+ * Mac mini: 99.95% availability
+
+The detailed SLAs measurements and guarantees can be found at [Service Level Agreement for Bare Metal Services](https://www.scaleway.com/en/bare-metal/sla/).
+
+Once the resource is in your hands, we have no access to the machine and therefore no way to monitor its operation.
+In case of any operational issues, we invite you to consult our [documentation](/bare-metal/) or [create a ticket](https://console.scaleway.com/support/tickets/create) with our support team. We will then do our utmost to ensure that you regain access to your resources as quickly as possible.
+
+### Backups and snapshots
+
+You are fully responsible for managing your machine and its data.
+
+It is your responsibility to ensure data redundancy if necessary, by relying on backups or internal server redundancy through solutions such as RAID.
+
+In the event of a disk or a hardware failure, we cannot guarantee that you will regain access to your machine and data. The failure may require a complete replacement of the machine. Therefore, it is your responsibility to ensure in advance that you have a backup or redundancy of your data on another server.
+**We cannot be held responsible for the loss of your data.**
+
+Backups and snapshots must be configured by you. Please refer to our documentation for assistance in setting up backups for [Dedibox](/dedicated-servers/how-to/use-dedibackup-ftp-backup/), [Elastic Metal](/faq/elastic-metal/#how-do-i-back-up-an-elastic-metal-server), and [Apple silicon](/faq/apple-silicon/#how-can-i-back-up-my-mac-mini).
+Restoring snapshots or backups needs to be triggered by you.
+
+## Configuration and version management
+
+### Installation and configuration
+
+We provide a range of Linux, Windows and macOS server distributions for automatic installation from the Scaleway console. These distributions come with a default configuration designed for standard use cases, ensuring security, usage efficiency, and reliability. During the setup of your machine, you can modify and customize this initial configuration. However, you are responsible for any impact on your server's availability, security, or performance.
+
+Apple Silicon servers, in particular, are enrolled with a Scaleway-operated mobile device management server. Removing the enrolment, or any of the associated configuration profiles, may impact Scaleway's ability to monitor & restart your server on your behalf, for instance, in case of power loss.
+
+In the event that you use a custom image, it is your responsibility to ensure a reliable and secure configuration of your machine.
+
+### Updates and version management
+
+We regularly provide OS version updates, allowing you to upgrade your environment if desired. It is your responsibility to update your machine to the desired version and thus maintain its compatibility with all internal and external resources at Scaleway.
+
+If you perform manual upgrades without reinstalling your machine with an image provided by Scaleway, it is your responsibility to ensure the reliability and stability of your machine's configuration.
+
+### Usage compliance
+
+You are responsible for the proper use of your resources. In this regard, you are responsible for maintaining the use of your server in accordance with Scaleway's compliance policy, as well as those of the various operating systems you use.
+
+
+ It is your responsibility to inform yourself beforehand about the permitted and prohibited use cases for your server and to adhere to them throughout your usage.
+
+
+## Data protection
+
+### Encryption in transit
+
+Bare Metal servers support SSH connections to secure your communication with the server. You remain responsible for configuring SSH keys.
+
+### Data encryption
+
+You are responsible for encrypting the disks on your server. We are not responsible for data encryption, especially in cases of sensitive applications or additional security requirements.
+
+### Data deletion
+
+When you delete your server, we are responsible for removing all of your data. To ensure their protection, the deleted server remains attached to your account and is therefore inaccessible to anyone else until all of your data has been erased and the cleaning process has been completed with a 100% success rate.
+
+In the event of a defective storage disk, it will be destroyed to ensure the confidentiality of your data.
+
+### Scaleway access
+
+We do not have the technical capability to access your machine once it is installed, nor the data stored on it. We have no visibility into your use of the server and its configuration. Therefore, it is your responsibility to ensure the security of your machine and data.
+
+## Identity and access management
+
+Elastic Metal servers provide [IAM permissions](/iam/reference-content/permission-sets/) sets which allow or restrict specific actions a user or application can perform, such as creating or deleting Elastic Metal servers. You remain responsible for giving these permissions to the relevant users or applications and reviewing these accesses frequently.
+
+Dedibox servers provide [outsourcing services features](https://www.scaleway.com/en/dedibox/outsourcing/), allowing you to delegate resource management. You remain responsible for giving access and management permissions to the relevant users or outsourcing providers and reviewing these accesses frequently.
+
+Managing access and permissions for creating, modifying, using, and deleting a resource remains in any case your responsibility.
+
+## Platform security
+
+Our security guarantees are available at [https://www.scaleway.com/en/security-and-resilience/](https://www.scaleway.com/en/security-and-resilience/), and our certifications and commitments are available in our [Trust Center](https://security.scaleway.com/).
+
+## Security best practices
+
+For optimal security, we recommend that you:
+
+* replace and strengthen your password after installation,
+* use an SSH key to access your machine, rather than using username and password authentication,
+* check and update the firewall and filtering rules if necessary,
+* regularly update the operating system to take advantage of configuration updates and security patches,
+* limit access to the preconfigured VNC server and access it through tunneled SSH connections (for Apple silicon servers).
\ No newline at end of file
diff --git a/pages/elastic-metal/troubleshooting/assets/scaleway-proxmox-permit-ssh.webp b/pages/elastic-metal/troubleshooting/assets/scaleway-proxmox-permit-ssh.webp
new file mode 100644
index 0000000000..d2617523e2
Binary files /dev/null and b/pages/elastic-metal/troubleshooting/assets/scaleway-proxmox-permit-ssh.webp differ
diff --git a/pages/elastic-metal/troubleshooting/assets/scaleway_enable_ssh_esxi.webp b/pages/elastic-metal/troubleshooting/assets/scaleway_enable_ssh_esxi.webp
new file mode 100644
index 0000000000..8e21a2f8cb
Binary files /dev/null and b/pages/elastic-metal/troubleshooting/assets/scaleway_enable_ssh_esxi.webp differ
diff --git a/pages/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx b/pages/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx
new file mode 100644
index 0000000000..dcb66f3f6e
--- /dev/null
+++ b/pages/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx
@@ -0,0 +1,94 @@
+---
+meta:
+ title: Enabling SSH on Elastic Metal servers running virtualization distributions
+ description: This page explains how to enable SSH on Elastic Metal servers running virtualization distributions
+content:
+ h1: Enabling SSH on Elastic Metal servers running virtualization distributions
+ paragraph: This page explains how to enable SSH on Elastic Metal servers running virtualization distributions
+tags: proxmox elastic-metal ssh esxi virtualization
+categories:
+ - bare-metal
+ - elastic-metal
+dates:
+ validation: 2024-09-30
+ posted: 2023-03-09
+---
+
+Elastic Metal servers support the installation of virtualization solutions Proxmox and ESXi. These solutions can be managed from either a web interface or a management tool, and therefore direct SSH access to machines running one of these solutions is disabled by default. However, you can enable SSH for advanced management tasks if required.
+
+
+ Enabling full SSH access to Proxmox or ESXi may cause security vulnerabilities on your installation. Be careful, and take extra precaution when you enable SSH.
+
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) with Proxmox VE
+
+## Enabling SSH on Proxmox VE
+
+Proxmox VE is a complete, open-source server management platform for virtualization. It combines the KVM hypervisor and Linux Containers (LXC), storage and networking features - manageable through a web-based user interface. However, SSH connections to the Proxmox VE host are disabled by default for security reasons.
+
+If you require SSH access to your Elastic Metal server, you can enable SSH on your machine after the installation of Proxmox from the Scaleway console.
+
+1. Log in to the Proxmox web interface of your Elastic Metal server.
+
+ You can find the URL of the Proxmox VE interface on the overview page of your Elastic Metal server in the Scaleway console.
+
+2. Select your server in the Data center view of Proxmox.
+3. Click **Shell** in the server view to open a shell in the web interface.
+4. Open the file `/etc/ssh/sshd_config` in a text editor.
+5. Go to the line `#PermitRootLogin` and uncomment it by removing the `#`. Change the option to yes:
+ ```
+ [...]
+ PermitRootLogin yes
+ [...]
+ ```
+
+6. Save the file and quit the text editor.
+7. Restart the SSH service to enable SSH login.
+ ```
+ systemctl restart ssh
+ ```
+ You can now use SSH on your Elastic Metal server. Use the login `root` and your Proxmox password when connecting to the machine.
+
+## Enabling SSH on ESXi
+
+
+ Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Please note that the following content is provided as-is, without any guarantee of functionality.
+We suggest considering alternative hypervisors such as Proxmox. You can learn how to [deploy virtual machines with Proxmox on Scaleway Dedibox](/tutorials/configure-failover-proxmox/).
+
+
+VMware ESXi is a bare metal hypervisor that allows you to install multiple virtual machines on your Elastic Metal server. It can be configured from an easy-to-use web interface.
+
+1. Log in to the ESXi web interface of your Elastic Metal server.
+
+ You can find the URL of the ESXi interface on the overview page of your Elastic Metal server in the Scaleway console.
+
+2. From the **Host** dashboard, click **Actions** > **Services** > **Enable Secure Shell (SSH)**. SSH is enabled.
+
+3. Log into your server using SSH.
+
+ ```
+ ssh root@my-exsi-host
+ ```
+ The ESXi shell displays. You can now perform administrative tasks on the machine.
+ ```
+ The time and date of this login have been sent to the system logs.
+
+ WARNING:
+ All commands run on the ESXi shell are logged and may be included in
+ support bundles. Do not provide passwords directly on the command line.
+ Most tools can prompt for secrets or accept them from standard input.
+
+ VMware offers supported, powerful system administration tools.
+ See www.vmware.com/go/sysadmintools for details.
+
+ The ESXi Shell can be disabled by an administrative user. See the
+ vSphere Security documentation for more information.
+ [root@my-esxi-host:~]
+ ```
+4. Disable SSH from the host dashboard. Click **Actions** > **Services** > **Disable Secure Shell (SSH)**. SSH is disabled.
+
+ It is recommended to disable SSH access when not in use, to avoid potential security vulnerabilities related to the access.
+
\ No newline at end of file
diff --git a/pages/elastic-metal/troubleshooting/index.mdx b/pages/elastic-metal/troubleshooting/index.mdx
new file mode 100644
index 0000000000..cc075219d0
--- /dev/null
+++ b/pages/elastic-metal/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Elastic Metal - Troubleshooting
+ description: Elastic Metal Troubleshooting
+content:
+ h1: Elastic Metal - Troubleshooting
+ paragraph: Elastic Metal Troubleshooting
+---
\ No newline at end of file
diff --git a/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx b/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx
new file mode 100644
index 0000000000..b2027eabb8
--- /dev/null
+++ b/pages/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx
@@ -0,0 +1,122 @@
+---
+meta:
+ title: Replacing a failed drive in a RAID1 software RAID
+ description: Learn how to safely replace a failed drive in a RAID1 software RAID configuration on Scaleway Elastic Metal servers
+content:
+ h1: Replacing a failed drive in a RAID1 software RAID
+ paragraph: Learn how to safely replace a failed drive in a RAID1 software RAID configuration on Scaleway Elastic Metal servers
+tags: RAID elastic-metal failed-drive RAID1 mdadm
+categories:
+ - bare-metal
+ - elastic-metal
+dates:
+ validation: 2025-01-02
+ posted: 2022-08-26
+---
+
+RAID1 configurations offer redundancy by mirroring data across two drives. If one drive fails, the other continues operating, ensuring data integrity. This guide explains how to replace a failed drive and rebuild the RAID1 array using the `mdadm` utility.
+
+Each Elastic Metal server uses a RAID1 configuration after installation from the Scaleway console. If you want to change the RAID configuration of the server, you can modify the RAID array using [rescue mode](/elastic-metal/how-to/use-rescue-mode/).
+
+
+
+- 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
+- An Elastic Metal server with at least two disks in RAID1
+
+## Removing the failed disk from the RAID configuration
+
+
+ We recommend [backing up your data](/en/docs/tutorials/restic-s3-backup/) before proceeding.
+
+
+1. Boot server in [rescue mode](/elastic-metal/how-to/use-rescue-mode/) from the Scaleway console.
+2. Log in to the server using the rescue account:
+ ```
+ ssh em-XXX@
+ ```
+
+
+ The rescue credentials are available from your server's status page in the Scaleway console.
+
+3. Run the following command to make sure all disk caches are written to the disk:
+ ```
+ sync
+ ```
+4. Mark the failed disk as failed using `mdadm`:
+ ```
+ mdadm --manage /dev/md0 --fail /dev/sdb2
+ ```
+5. Visualize the existing `mdadm` RAID devices by running the following command:
+ ```
+ cat /proc/mdstat
+ ```
+
+ An output as follows displays:
+
+ ```sh
+ Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
+ md126 : active (auto-read-only) raid1 sdb3[1] sda3[0]
+ 974869504 blocks super 1.2 [2/2] [UU]
+ resync=PENDING
+ bitmap: 8/8 pages [32KB], 65536KB chunk
+
+ md127 : active (auto-read-only) raid1 sdb2[1](F) sda2[0]
+ 523264 blocks super 1.2 [2/2] [UU]
+
+ unused devices:
+ ```
+
+ The faulty device is marked with `(F)`.
+6. Remove the failed disk using the `mdadm --manage` command:
+ ```sh
+ mdadm --manage /dev/md0 --remove /dev/sdb2
+ ```
+7. Contact the technical support to replace the failed disk with a working one.
+
+
+ If the command fails due to the device being busy, ensure the disk is unmounted and re-check the status.
+
+
+## Adding the replacement disk to the RAID
+
+1. Once the failed disk is replaced, copy the partition table of the source disk to the new disk:
+ ```
+ sfdisk -d /dev/sda | sfdisk /dev/sdb
+ ```
+
+ The `sfdisk` command above replaces the entire partition table on the new disk with the one of the source disk. Modify the command if you require preserving other partition information on the disk.
+
+2. Create a mirror of the source disk using the `mdadm` command:
+ ```
+ mdadm --manage /dev/md0 --add /dev/sdb2
+ ```
+3. Verify the status of the configuration:
+ ```
+ mdadm --detail /dev/md0
+ ```
+
+ Use the following command to show the progress of the recovery of the mirror disk:
+ ```
+ cat /proc/mdstat
+ ```
+
+
+## Post-replacement checks
+
+1. Check for consistency in the RAID setup:
+ ```
+ cat /proc/mdstat
+ ```
+2. Monitor the RAID health and status regularly:
+ ```
+ mdadm --detail /dev/md0
+ ```
+3. Set up email alerts to detect RAID issues early:
+ ```
+ mdadm --monitor --scan --daemonise --mail=root@example.com
+ ```
+
+
+ Regularly monitoring RAID health prevents unexpected failures and data loss.
+
\ No newline at end of file
diff --git a/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx b/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx
new file mode 100644
index 0000000000..db758b61dc
--- /dev/null
+++ b/pages/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx
@@ -0,0 +1,126 @@
+---
+meta:
+ title: Resetting the Administrator password on Windows Server OS
+ description: Learn how to securely reset the Administrator password on Windows Server Elastic Metal servers using rescue mode.
+content:
+ h1: Resetting the Administrator password on Windows Server OS
+ paragraph: Learn how to securely reset the Administrator password on Windows Server Elastic Metal servers using rescue mode.
+tags: windows rescue password reset administrator
+categories:
+ - bare-metal
+ - elastic-metal
+dates:
+ validation: 2025-01-02
+ posted: 2023-12-14
+---
+
+During the installation or reinstallation of an Elastic Metal server with a Windows Server operating system, an administrator password is set by you (Administrator account).
+
+If you have lost this password, you can reset it via rescue mode. This guide explains the steps to securely reset the Administrator password and regain access to your server.
+
+
+
+- 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
+- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)
+
+## Removing the old Administrator password
+
+
+ We recommend [backing up your data](/tutorials/restic-s3-backup/) before proceeding.
+
+
+1. Reboot your Elastic Metal server into [rescue mode](/elastic-metal/how-to/use-rescue-mode/).
+2. Log into rescue mode.
+3. Install the packages `ntfs-3g` and `chntpw` using the APT package manager.
+ ```
+ sudo apt install ntfs-3g chntpw
+ ```
+4. Mount the Windows system partition.
+ ```
+ sudo ntfsfix /dev/sda2
+ ```
+5. List the user accounts configured in Windows:
+ ```
+ sudo chntpw -l /mnt/Windows/System32/config/SAM
+ ```
+ An output similar to the following displays:
+ ```
+ chntpw version 1.00 140201, (c) Petter N Hagen
+ Hive name (from header): <\SystemRoot\System32\Config\SAM>
+ ROOT KEY at offset: 0x001020 * Subkey indexing type is: 686c
+ File size 65536 [10000] bytes, containing 7 pages (+ 1 headerpage)
+ Used for data: 343/38728 blocks/bytes, unused: 32/6104 blocks/bytes.
+
+ | RID -|---------- Username ------------| Admin? |- Lock? --|
+ | 01f4 | Administrator | ADMIN | dis/lock |
+ | 01f7 | DefaultAccount | | dis/lock |
+ | 01f5 | Invit� | | dis/lock |
+ | 01f8 | WDAGUtilityAccount | | dis/lock |
+ ```
+
+ The administrator account of your server can either be `Administrator` or `Administrateur` depending on the installation.
+
+6. Edit the `Administrator` account by running the following command:
+ ```
+ sudo chntpw -u Administrator /mnt/Windows/System32/config/SAM
+ ```
+ A menu displays as follows:
+ ```
+ ================= USER EDIT ====================
+
+ RID : 0500 [01f4]
+ Username: Administrator
+ fullname:
+ comment : User account with administrative privileges
+ homedir :
+
+ 00000220 = Administrators (which has 1 members)
+
+ Account bits: 0x0010 =
+ [ ] Disabled | [ ] Homedir req. | [ ] Passwd not req. |
+ [ ] Temp. duplicate | [X] Normal account | [ ] NMS account |
+ [ ] Domain trust ac | [ ] Wks trust act. | [ ] Srv trust act |
+ [ ] Pwd don't expir | [ ] Auto lockout | [ ] (unknown 0x08) |
+ [ ] (unknown 0x10) | [ ] (unknown 0x20) | [ ] (unknown 0x40) |
+
+ Failed login count: 5, while max tries is: 0
+ Total login count: 2
+
+ - - - - User Edit Menu:
+ 1 - Clear (blank) user password
+ 2 - Unlock and enable user account [probably locked now]
+ 3 - Promote user (make user an administrator)
+ 4 - Add user to a group
+ 5 - Remove user from a group
+ q - Quit editing user, back to user select
+ Select: [q] >
+ ```
+7. Type `1` and press enter to clear the user password:
+ ```
+ Select: [q] > 1
+ Password cleared!
+ ```
+8. Type `q` and press `Enter` to quit. A summary of the edited files displays:
+ ```
+ Hives that have changed:
+ # Name
+ 0
+ Write hive files? (y/n) [n] :
+ ```
+9. Type `y` and press `Enter` to confirm the writing of the files.
+ ```
+ Write hive files? (y/n) [n] : y
+ 0 - OK
+ ```
+10. Reboot the server back into [normal mode](/elastic-metal/how-to/use-rescue-mode/#rebooting-back-to-normal-mode).
+
+## Setting a new Administrator password
+
+1. [Activate remote access](/elastic-metal/how-to/activate-remote-access/) on your server to connect via the KVM over IP device.
+2. Open the remote console to access the screen output.
+3. Open the start menu and select the `Administrator` username to access user settings.
+4. Click the password panel, then **Add** to create a new password.
+5. Enter the new password, confirm it, and set a reminder.
+6. Exit the remote console.
+ You can now log into your server using the Remote Desktop Viewer and the new password.
\ No newline at end of file
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-cross-funct-it-equip.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-cross-funct-it-equip.webp
new file mode 100644
index 0000000000..49fcbd5dab
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-cross-funct-it-equip.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-customer-it-equip.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-customer-it-equip.webp
new file mode 100644
index 0000000000..cc18306836
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-customer-it-equip.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv-manuf.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv-manuf.webp
new file mode 100644
index 0000000000..b584a7dbcd
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv-manuf.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv.webp
new file mode 100644
index 0000000000..763320eee3
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-dc-techenv.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-network.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-network.webp
new file mode 100644
index 0000000000..37b6db7c87
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-network.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-non-it-cross-funct.webp b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-non-it-cross-funct.webp
new file mode 100644
index 0000000000..08f4359926
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-allocation-rules-non-it-cross-funct.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-co2eq-formula.webp b/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-co2eq-formula.webp
new file mode 100644
index 0000000000..6d9fcce729
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-co2eq-formula.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-order-summary.webp b/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-order-summary.webp
new file mode 100644
index 0000000000..474e5d0e5e
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-env-footprint-order-summary.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-env-impact-estimation-az.webp b/pages/environmental-footprint/additional-content/assets/scaleway-env-impact-estimation-az.webp
new file mode 100644
index 0000000000..e9d0b8b294
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-env-impact-estimation-az.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-focus-on-cross-func-it-equipment.webp b/pages/environmental-footprint/additional-content/assets/scaleway-focus-on-cross-func-it-equipment.webp
new file mode 100644
index 0000000000..2f22356660
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-focus-on-cross-func-it-equipment.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-leaves-rating-env-foot.webp b/pages/environmental-footprint/additional-content/assets/scaleway-leaves-rating-env-foot.webp
new file mode 100644
index 0000000000..511ad67cd3
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-leaves-rating-env-foot.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-overall-env-footprint-calc.webp b/pages/environmental-footprint/additional-content/assets/scaleway-overall-env-footprint-calc.webp
new file mode 100644
index 0000000000..24e7a33d59
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-overall-env-footprint-calc.webp differ
diff --git a/pages/environmental-footprint/additional-content/assets/scaleway-select-a-server-env-foot.webp b/pages/environmental-footprint/additional-content/assets/scaleway-select-a-server-env-foot.webp
new file mode 100644
index 0000000000..a92d5fbcc5
Binary files /dev/null and b/pages/environmental-footprint/additional-content/assets/scaleway-select-a-server-env-foot.webp differ
diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx
new file mode 100644
index 0000000000..2c89a18b37
--- /dev/null
+++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx
@@ -0,0 +1,84 @@
+ ---
+meta:
+ title: Understanding environmental footprint estimation
+ description: This page explains how to understand the environmental footprint estimation of Elastic Metal servers.
+content:
+ h1: Understanding environmental footprint estimation
+ paragraph: This page explains how to understand the environmental footprint estimation of Elastic Metal servers.
+tags: environmental-footprint impact environment datacentre
+dates:
+ validation: 2024-10-30
+ posted: 2024-10-30
+categories:
+ - environmental-footprint
+---
+
+
+The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).
+
+This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next.
+
+
+When you [order an Elastic Metal server](/elastic-metal/how-to/create-server/), you can see the estimated impact of your Elastic Metal server of choice before you order. In this page, we explain how the estimation is measured.
+
+
+ The estimation described on this page is based on the calculation methodology detailed in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page.
+
+
+## Availability Zone footprint estimation
+
+When you select your Elastic Metal server's Availability Zone, you can see the quantity of CO2 equivalent (CO2e) emitted per kW consumed for each zone.
+
+
+
+This data is determined by the [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts/#pue-power-usage-effectiveness) of the data center and the [energy mix](/environmental-footprint/concepts/#energy-mix) of the country in which the data center is located.
+
+
+ We use [Ember's](https://ember-climate.org/) Electricity Data Explorer to determine the impact linked to the energy mix. The energy mix can be very different from one country to another depending on the origin of the electricity used. We can see on [Electricity Maps' Environmental Impact by Zone map](https://app.electricitymaps.com/map) the significant differences that there can be between countries.
+
+
+The estimation is represented by three green leaf icons:
+
+ - When the three leaves are dark green, this means that the AZ has the lowest quantity of CO2e emitted per kW consumed, and each kw consumed in your Elastic Metal has a lower impact.
+ - When two leaves are dark green, this means that the AZ has a low quantity of CO2e emitted per kW consumed
+ - When only one leaf is dark green, the AZ has a bigger quantity of CO2e emitted per kW consumed
+
+
+ When you hover your cursor over the leaves or when you select the AZ, you can see the detail of the environmental footprint estimation in kgCO₂e/kw.
+
+
+
+ The AZ footprint estimation is a straightforward calculation of CO₂ emissions per kW of electricity consumed, based on the energy mix and the data center’s Power Usage Effectiveness (PUE) specific to that AZ. For example, in an AZ like PAR-2, each kW consumed may have an impact of 0.065 kgCO₂e.
+
+ Meanwhile, the offer footprint estimation is a more complex calculation that combines the AZ-specific data with additional factors relevant to the specific offer. This calculation considers not just energy consumption but also other elements, which are outlined in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page, to reflect a comprehensive impact specific to the offer rather than just adding up kW-based impacts.
+
+
+## Elastic Metal offers footprint estimation
+
+For Elastic Metal offers, the environmental footprint estimation considers the impact of the **manufacturing** and **use** of all the elements that allow the service to work, such as network, cross-IT equipment and stock, and non-IT elements in addition to the manufacturing and use of the server itself. The AZ you chose in the previous step will impact the **use** by multiplying each kw consumed by each of these elements by the value indicated.
+
+
+ For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page.
+
+
+For usage, we rely on an estimate of electricity consumption. This estimation is based on tests carried out by the Hardware team at Scaleway. Each range of offers was tested using different compute configurations, to ensure coverage of a variety of possible power consumption set ups.
+
+These different computing configurations allow us to simulate enough use cases to have an idea of the power consumption, but the actual consumption will depend on how the server is used in practice.
+
+We estimate the measure the server's electricity consumption and then calculate its estimated impact based on the energy mix of the selected zone and the data center's PUE.
+
+The estimation is represented by three green leaf icons:
+
+
+
+ - When the three leaves are dark green, this means that the offer has the lowest environmental impact
+ - When two leaves are dark green, this means that the offer has a low environmental impact
+ - When only one leaf is dark green, the offer has a bigger environmental impact
+
+
+ When you hover your cursor over the leaves or when you select an offer, you can see the detail of the environmental footprint estimation in kgCO₂e per hour or per month, depending on the billing method chosen.
+
+
+A summary of the total environmental footprint estimation for the selected offer is shown before the order summary. We also add an indication to help you imagine what this impact is, such as `≈ 35 km by car`.
+
+
\ No newline at end of file
diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx
new file mode 100644
index 0000000000..64d4693336
--- /dev/null
+++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx
@@ -0,0 +1,193 @@
+---
+meta:
+ title: Environmental Footprint calculation breakdown
+ description: This page explains how Scaleway calculates the environmental footprint of its products and services in detail.
+content:
+ h1: Environmental Footprint calculation breakdown
+ paragraph: This page explains how Scaleway calculates the environmental footprint of its products and services in detail.
+tags: environmental-footprint impact environment datacentre
+dates:
+ validation: 2024-09-11
+ posted: 2024-09-11
+categories:
+ - environmental-footprint
+---
+
+
+The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).
+
+This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next.
+
+
+This page details the methodology used to calculate the environmental footprint of Scaleway cloud services, and Bare Metal offers. This methodology ensures transparency and precision, as it provides reliable estimations covering a full lifecycle analysis.
+
+
+The environmental impact data may vary over time due to updates in data center efficiency (PUE), energy mix, changes to our internal infrastructure or refinements in the calculation method. These updates ensure improved accuracy and transparency.
+
+
+## Methodology overview
+
+Our calculation methodology was developed in collaboration with the green IT specialist consultancy firm [IJO](https://ijo.tech/index.html), ensuring a rigorous and expert-validated approach to assessing environmental impact accurately and transparently.
+
+Our Methodology is based on the [ADEME (French Government Agency for Ecological Transition) Product Category Rules (PCR) for Datacenter and Cloud services](https://librairie.ademe.fr/produire-autrement/6105-methodological-standard-for-the-environmental-assessment-of-datacenter-it-hosting-services-and-cloud-services.html), which provide a standardized framework for calculating and reporting the environmental impact of data centers and cloud services. These rules are designed to ensure consistency, transparency, and comparability in the assessment of environmental footprints across the industry.
+
+The ADEME PCR specifies the methodology for conducting [Life Cycle Analysis (LCA)](/environmental-footprint/concepts/#life-cycle-analysis-lca) for data center operations, which includes the evaluation of energy consumption, greenhouse gas emissions, resource usage, and other environmental impacts associated with the lifecycle of data center infrastructures and cloud services. This lifecycle covers all stages from raw material extraction, manufacturing, and transportation, to the use and end-of-life disposal of data center equipment.
+The stages of the lifecycle that are really significant in the total impact of a server are its manufacturing and its use. We will therefore focus on these two stages in the rest of this documentation.
+
+By adhering to PCR guidelines, we provide reliable and standardized environmental impact data. This facilitates better decision-making for both providers and consumers of data center and cloud services, as it allows for clear comparisons and informed choices regarding sustainability.
+
+In addition, to provide an even more comprehensive and realistic assessment, we have extended this methodology to include several additional elements integral to our operations' overall environmental impact.
+
+These additional elements cover:
+
+- **Cross-functional IT equipment** - Servers and storage devices dedicated to the enterprise as a whole, managing offers, or equipment held in stock. This includes:
+ - **Enterprise servers and storage devices** - IT equipment dedicated to Scaleway's internal digital services
+ - **Servers and storage devices for managing offers** - IT equipment for management and supervision of Scaleway offers
+ - **Servers and storage equipment in stock** - IT equipment in stock and waiting to be commissioned
+- **Non-IT cross-functional elements** - all components necessary for the smooth operation of our company, such as office facilities, employee transportation, and other logistics. Refer to our [2024 Environmental Impact Report](https://www.scaleway.com/en/environmental-leadership/?utm_source=linkedin&utm_medium=social&utm_term=&utm_content=&utm_campaign=default) for more information about these components.
+
+By integrating these additional factors into the PCR Data center and cloud methodology, we ensure that our calculations reflect a more complete and transparent view of our environmental impact.
+
+
+
+
+## Detailed calculation breakdown
+
+
+
+The final calculation of the environmental impact considers several critical factors to provide a thorough and accurate assessment. This includes considering the manufacturing processes for data centers and related technical components, network machines, and servers directly used by customers. Additionally, the assessment accounts for servers dedicated to IT tools and those maintained in stock.
+
+The usage phase also includes every data center [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts/#pue-power-usage-effectiveness), which is multiplied by the impact related to electricity consumption of network servers, customer-used servers, and servers used for transversal IT tools. This approach ensures that both the direct and indirect energy consumption associated with data center operations is accurately represented.
+
+Our calculations of the impact of electricity consumption are based on a 'location-based' approach, although we have PPA (Power Purchase Agreements) type contracts for each of our data centers, we have chosen not to take them into account in accordance with ADEME guidelines.
+
+Furthermore, the calculation will integrate the environmental impact of all elements necessary for the proper functioning of the enterprise. This includes the office premises, employee transportation, and other logistical aspects.
+
+The details of the calculations for each of these elements are detailed below.
+
+### Definition of the variables
+
+
+
+All calculations will use the following variables:
+
+
+ The acronyms used below are based on the French phrases for these terms.
+
+
+- [dU](/environmental-footprint/concepts/#du-duration-of-use): duration of use of the equipment included in the study
+- [DDV](/environmental-footprint/concepts/#ddvdc-data-center-lifespan): lifespan
+- [PuissEqt](/environmental-footprint/concepts/#puisseqt-rated-power): rated power of the equipment
+- [PuissCommDC](/environmental-footprint/concepts/#puisscommdc): proportion of the data center's installed power reserved by customers
+- [FE](/environmental-footprint/concepts/#emission-factor): emission factor
+- [%mutualization](/environmental-footprint/concepts/#mutualization): mutualization factor
+
+
+ Refer to the [Environmental Footprint concepts page](/environmental-footprint/concepts/) for more information about each of the concepts above.
+
+
+### Data center and technical environment
+
+
+
+To calculate the impact of the data center and the technical environment, it is necessary to have either a preliminary study carried out by the hardware suppliers and data center administrators or a quote including all the components. Without such a study, we have chosen to use [ADEME data](https://data.ademe.fr/) to evaluate the impact of the construction of the data center and technical environment (air conditioning and power supply system).
+
+To allocate the environmental impact of the manufacturing of the data center and the technical environment we multiply the proportion of the data center lifespan that corresponds to the device's usage time by the specific equipment's power usage relative to the total power reserved by customers in the data center by the data center emission factor.
+
+#### Calculation example
+
+For the use of an Elastic Metal server with a power of 110w for 100 hours in a 2000m2 data center which has a power of 3000 kw (3e+6w) and a lifespan of 25 years (219 000 hours) and considering via ADEME estimates that the impact of the manufacturing of this data center and its technical environment is 3.3e+6 kgCo2e, we make the following calculation:
+
+```math
+DC&TEenv = (100 / 219 000) * (110 / 3e+6w) * 3,3e+6 = 0,055 kgCO2e
+```
+
+Therefore 0,011 kgCO2e is added to the total manufacturing impact for the use of this server.
+
+### Network
+
+
+
+To calculate the environmental impact of your large-scale use of the products, we include part of the impact of manufacturing the network machines that are necessary for the operation of our products. To do this, we divide the impact of manufacturing network equipment over its entire lifespan and attribute this impact based on the energy consumption of the equipment used in order to assign a proportional share of the environmental impact to each piece of equipment. Finally, we estimate the impact of manufacturing the equipment using the [boavizta database](https://boavizta.org/).
+
+For the use of network machines induced by your use of Scaleway products, we take into account the energy consumption of the network machines and multiply it by the emission factor linked to the production of this energy that we recover thanks to the [EMBER database](https://ember-climate.org/). We then attribute this share of impact to each machine according to its energy consumption.
+
+### Customer servers
+
+To accurately calculate the environmental impact of each server used directly for Scaleway offers, we will implement specific allocation rules tailored to each product. These rules will ensure that the impact is precisely distributed according to the unique usage patterns and resource demands of different products.
+
+Each product will have its own set of criteria to allocate the environmental footprint, considering factors such as server utilization rates, operational timeframes, and the specific technical requirements of the product. By customizing the allocation rules for each offering, we can ensure a more accurate and fair representation of the environmental impact associated with each product.
+
+#### Bare Metal
+
+
+
+For bare metal servers, the allocation of environmental impact is straightforward due to the direct association between a user and a server. The environmental impact of a bare metal server is entirely attributed to the user utilizing it. This encompasses the energy consumption during its operation, as well as a portion of the impact from the server's manufacturing process.
+
+The manufacturing impact is prorated based on the server's lifespan and the duration of its use by the customer. By dividing the total manufacturing impact by the expected lifetime of the server and then allocating it according to the specific usage period, we ensure that each user is accountable for their fair share of the server's overall environmental footprint.
+
+
+ Currently, our calculations for Elastic Metal GPU servers do not include the environmental impact of GPU manufacturing due to insufficient data from the manufacturer. While the impact of CPUs, RAM, disk, and energy consumption is accounted for, the absence of GPU manufacturing data means the figures provided today are underestimated.
+
+ We will update our methodology as soon as more reliable data on GPU manufacturing becomes available.
+
+
+#### Calculation example
+
+For the use of an Elastic Metal server, with a lifespan of 6 years (52 560 hours) and power of 110w, for 100 hours and considering via Boavizta estimates that the impact of the manufacturing of this server is 850 kgCo2e, we make the following calculation:
+
+```math
+ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e
+```
+
+Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server.
+
+### Cross-IT equipment & stock
+
+
+
+Our calculation will also incorporate the environmental footprint of all transversal tools essential for the functioning of the Scaleway.
+
+To determine their manufacturing impact, we add the environmental footprint of each machine hosting these transversal tools over the duration of customer usage. This aggregated impact will then be divided by the total number of customers. A "customer" is defined as an active organization, that is to say an organization which consumes and which is billed.
+
+To determine stock manufacturing impact, we will divide the sum of the impact of all hardware components in stock by the total number of servers.
+
+
+### Non-IT cross-functional elements
+
+
+
+Finally, our comprehensive environmental impact calculation will include the "Non-IT cross-functional elements." This category encompasses the environmental footprint of all other essential components required for Scaleway's operations, such as office facilities, employee transportation, the company cafeteria, and various logistical aspects.
+
+To integrate this into the overall calculation, we will first get the total environmental impact of these non-IT elements from Scaleway Impact report. This total impact will then be divided by the number of customers. This approach ensures that every customer shares a portion of the environmental burden associated with maintaining the broader operational infrastructure, thereby providing a complete and transparent picture of Scaleway's environmental footprint.
+
+### Water consumption
+
+Providing water consumption metrics is essential in the context of cloud services hosted in data centers because water plays a key role in cooling systems, which ensure the optimal operating temperatures for servers. The amount of water consumed depends on factors such as the temperature, humidity, and the design of the cooling system. For instance, in hot and dry climates, water consumption tends to be higher. At Scaleway, we choose our data centers also taking this criterion into account to reduce water consumption as much as possible.
+
+This data is availlable for:
+* FR-PAR-1
+* FR-PAR-2
+* FR-PAR-3
+* NL-AMS-1
+
+For each Scaleway product or service in these Availability Zones, we calculate the water consumption based on its energy consumption.
+
+To estimate the water consumption by multiplying the total energy consumption for each service by the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness), as such:
+
+```math
+Water Consumption (liters) = Energy Consumption (kWh) × WUE (liters/kWh)
+```
+
+#### Calculation example
+
+At Scaleway we currently collect power consumption metrics for Elastic Metal servers. Using an Elastic Metal server as an example, we can assume that:
+
+- A server consumes 500 kWh of energy per month.
+- The WUE of the data center (PAR-DC5) is 0,014 liters/kWh.
+
+Therefore, the total water consumption for the server would be:
+
+```
+500 kWh × 0.014 liters/kWh = 7 liters/month
+```
\ No newline at end of file
diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx
new file mode 100644
index 0000000000..53db45290e
--- /dev/null
+++ b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx
@@ -0,0 +1,59 @@
+---
+meta:
+ title: Environmental footprint calculator product integration
+ description: Discover the Scaleway Products that integrate the Environmental Footprint calculator.
+content:
+ h1: Environmental footprint calculator product integration
+ paragraph: Discover the Scaleway Products that integrate the Environmental Footprint calculator.
+tags: environmental-footprint calculator
+dates:
+ validation: 2025-01-14
+ posted: 2025-01-14
+categories:
+ - environmental-footprint
+---
+
+The following tables provide details about the Scaleway products that currently integrate the [environmental footprint calculator](/environmental-footprint/additional-content/environmental-footprint-calculator) and the products that will integrate it in the future, by order of integration.
+
+## Product integration available
+
+| **Product Name** | **Environmental Footprint calculator available** |
+|----------------------------|---------------------------------|
+| Elastic Metal | **Yes** |
+
+## Planned product integration
+
+| **Product Name** | **Environmental Footprint calculator available** |
+|----------------------------|---------------------------------|
+| Apple Silicon | **Not integrated yet** |
+| Dedibox | **Not integrated yet** |
+| Instances | **Not integrated yet** |
+| GPU Instances | **Not integrated yet** |
+| Kubernetes | **Not integrated yet** |
+| Container Registry | **Not integrated yet** |
+| Managed Inference | **Not integrated yet** |
+| Generative APIs | **Not integrated yet** |
+| Object Storage | **Not integrated yet** |
+| Block Storage | **Not integrated yet** |
+| Managed Databases for PostgreSQL and MySQL | **Not integrated yet** |
+| Serverless Functions | **Not integrated yet** |
+| Serverless Containers | **Not integrated yet** |
+| Serverless Jobs | **Not integrated yet** |
+| Serverless SQL Databases | **Not integrated yet** |
+| VPC | **Not integrated yet** |
+| Public Gateways | **Not integrated yet** |
+| Load Balancers | **Not integrated yet** |
+| Domains and DNS | **Not integrated yet** |
+| IPAM | **Not integrated yet** |
+| Edge Services | **Not integrated yet** |
+| Transactional Email | **Not integrated yet** |
+| IoT Hub | **Not integrated yet** |
+| Web Hosting | **Not integrated yet** |
+| Cockpit | **Not integrated yet** |
+| Secret Manager | **Not integrated yet** |
+| NATS | **Not integrated yet** |
+| Queues | **Not integrated yet** |
+| Redis™ | **Not integrated yet** |
+| Topics and Events | **Not integrated yet** |
+| Quantum | **Not integrated yet** |
+
diff --git a/pages/environmental-footprint/additional-content/index.mdx b/pages/environmental-footprint/additional-content/index.mdx
new file mode 100644
index 0000000000..7e30de5598
--- /dev/null
+++ b/pages/environmental-footprint/additional-content/index.mdx
@@ -0,0 +1,9 @@
+---
+meta:
+ title: Environmental Footprint Additional Content
+ description: Discover Scaleway's Environmental Footprint Additional Content
+content:
+ h1: Environmental Footprint Additional Content
+ paragraph: Environmental Footprint Additional Content
+---
+
diff --git a/pages/environmental-footprint/concepts.mdx b/pages/environmental-footprint/concepts.mdx
new file mode 100644
index 0000000000..5251a8162c
--- /dev/null
+++ b/pages/environmental-footprint/concepts.mdx
@@ -0,0 +1,84 @@
+---
+meta:
+ title: Environmental Footprint - Concepts
+ description: Understand the fundamental concepts of the Environmental Footprint calculator at Scaleway.
+content:
+ h1: Concepts
+ paragraph: Understand the fundamental concepts of the Environmental Footprint calculator at Scaleway.
+tags: environmental-footprint impact environment datacentre
+dates:
+ validation: 2024-09-11
+---
+
+## DDV_DC (Data center Lifespan)
+
+This value indicates the lifespan of a data center; if the value is not available, it can be estimated. For example `DDV_DC` = 25 years.
+
+## dU (Duration of use)
+
+As defined by the [ADEME Product Category Rules (PCR)](https://librairie.ademe.fr/produire-autrement/6105-methodological-standard-for-the-environmental-assessment-of-datacenter-it-hosting-services-and-cloud-services.html), the dU or duration of use, is the measurement that indicates the time a Scaleway resource such as an Elastic Metal server is used.
+
+## Emission factor
+
+An emission factor is a coefficient that relates the amount of CO2eq emitted to a specific activity that generates that emission.
+This coefficient is used at Scaleway to estimate CO2eq emissions from various sources.
+
+## Energy mix
+
+The distribution of various energy sources used to meet a region or country's energy needs. An energy mix typically includes a combination of fossil fuels (such as coal, oil, and natural gas), renewable sources (such as wind, solar, hydroelectric, and geothermal), and sometimes nuclear energy.
+
+## Environmental impact
+
+Environmental impact refers to the set of effects that a human activity or product has on the environment.
+
+In the context of digital services, and more specifically cloud infrastructures such as Scaleway's, this impact includes several main factors:
+
+ - **CO2 emissions (kgCO2eq)** - This is the amount of carbon dioxide (and other greenhouse gases) emitted directly or indirectly by the manufacture, use, and management of servers and other equipment necessary for the operation of cloud services. CO2 emissions are measured in kilograms of CO2 equivalent (kgCO2eq).
+ - **Energy consumption** - This is the electrical energy consumed by servers and associated infrastructures (networks, cooling, etc.) to ensure the proper functioning of cloud services. Energy consumption is a key factor because the production and use of electricity are often associated with CO2 emissions, depending on the energy sources used (fossil, renewable, etc.).
+ - **Water consumption** - Water is used in data center cooling systems to keep servers at an optimal temperature. Water Usage Effectiveness (WUE) is an indicator that measures the amount of water used in relation to the energy efficiency of a data center.
+
+In short, the environmental impact is an estimated measure all the resources consumed and emissions generated by an activity or product, with the aim of minimizing negative impacts on the environment and promoting more sustainable practices.
+
+## Life Cycle Analysis (LCA)
+Life Cycle Analysis (LCA) is a method of assessing the environmental impact of a product, service or process throughout its life cycle, from the extraction of materials to the end of life.
+
+Typical stages of LCA include:
+ - Extraction and processing of raw materials
+ - Product manufacturing
+ - Distribution and transportation
+ - Consumer use
+ - End of life (recycling, disposal, etc.)
+
+For each stage of the life cycle, the environmental impact is assessed based on different indicators, such as energy consumption, greenhouse gas emissions, water consumption, waste production, etc.
+
+In the context of Scaleway, the LCA can be used to assess the environmental impact of the entire life cycle of cloud services, including the extraction of raw materials for the manufacturing of hardware equipment, energy production to power data centers, the manufacturing and distribution of IT equipment, the use of cloud services by customers, and the end of life of equipment. Data on energy consumption, greenhouse gas emissions, water consumption, waste production, etc., must also be collected and analyzed for each stage of the life cycle.
+
+## Mutualization
+
+This factor is equivalent to [PuissEqt](/environmental-footprint/concepts/#puisseqt-rated-power) and PuissDisponibleDC, which is the nominal power available for Scaleway at the data center. For shared equipment, such as management servers and network equipment of the data center, this factor is applied.
+
+## PuissCommDC
+
+This value is defined by the ADEME PCR as the proportion of a data center's installed power reserved for users.
+
+## PUE (Power Usage Effectiveness)
+
+PUE is a key indicator used to measure the energy efficiency of data centers. It was created by [The Green Grid](https://www.thegreengrid.org/), an organization dedicated to improving the energy efficiency of data centers.
+
+The PUE represents the ratio between the total amount of energy consumed by a data center and the energy used directly to power IT equipment (servers, storage, networks).
+
+It is a key factor in estimating the energy efficiency of data centers and, by extension, their environmental impact. The lower the PUE, the more energy-efficient the data center, which translates into lower greenhouse gas emissions and better sustainability performance.
+
+## PuissEqt (Rated power)
+
+This value is defined by the ADEME PCR as how much electrical power a particular device or piece of equipment consumes while it is operating. If a server requires 500 watts of power to run, then the PuissEqt for this server is 500 watts.
+
+## Water Usage Effectiveness
+
+Water Usage Effectiveness (WUE) is a metric used to measure the water consumption efficiency of a data center. It is defined as the amount of water used by a data center in liters, per kilowatt-hour (kWh) of energy consumed.
+
+The calculation is performed using the following formula:
+
+```
+WUE = Total Water Used (liters) ÷ Total IT Energy Consumption (kWh)
+```
\ No newline at end of file
diff --git a/pages/environmental-footprint/how-to/assets/scaleway-env-foot-dashboard.webp b/pages/environmental-footprint/how-to/assets/scaleway-env-foot-dashboard.webp
new file mode 100644
index 0000000000..18e583a785
Binary files /dev/null and b/pages/environmental-footprint/how-to/assets/scaleway-env-foot-dashboard.webp differ
diff --git a/pages/environmental-footprint/how-to/assets/scaleway-env-footprint-order-summary.webp b/pages/environmental-footprint/how-to/assets/scaleway-env-footprint-order-summary.webp
new file mode 100644
index 0000000000..474e5d0e5e
Binary files /dev/null and b/pages/environmental-footprint/how-to/assets/scaleway-env-footprint-order-summary.webp differ
diff --git a/pages/environmental-footprint/how-to/assets/scaleway-env-monthly-report-detailed.webp b/pages/environmental-footprint/how-to/assets/scaleway-env-monthly-report-detailed.webp
new file mode 100644
index 0000000000..4f44372802
Binary files /dev/null and b/pages/environmental-footprint/how-to/assets/scaleway-env-monthly-report-detailed.webp differ
diff --git a/pages/environmental-footprint/how-to/assets/scaleway-env-report-glossary.webp b/pages/environmental-footprint/how-to/assets/scaleway-env-report-glossary.webp
new file mode 100644
index 0000000000..0960259057
Binary files /dev/null and b/pages/environmental-footprint/how-to/assets/scaleway-env-report-glossary.webp differ
diff --git a/pages/environmental-footprint/how-to/index.mdx b/pages/environmental-footprint/how-to/index.mdx
new file mode 100644
index 0000000000..2a05a218d6
--- /dev/null
+++ b/pages/environmental-footprint/how-to/index.mdx
@@ -0,0 +1,9 @@
+---
+meta:
+ title: Environmental Footprint How tos
+ description: Discover Scaleway's Environmental Footprint How tos
+content:
+ h1: Environmental Footprint How tos
+ paragraph: Environmental Footprint How tos
+---
+
diff --git a/pages/environmental-footprint/how-to/track-monthly-footprint.mdx b/pages/environmental-footprint/how-to/track-monthly-footprint.mdx
new file mode 100644
index 0000000000..a8f1d9a6b9
--- /dev/null
+++ b/pages/environmental-footprint/how-to/track-monthly-footprint.mdx
@@ -0,0 +1,58 @@
+---
+meta:
+ title: How to understand and track your monthly environmental footprint report
+ description: Learn to interpret and track your monthly environmental footprint report easily.
+content:
+ h1: How to understand and track your monthly environmental footprint report
+ paragraph: Learn to interpret and track your monthly environmental footprint report easily.
+tags: environmental-footprint impact environment datacenter
+dates:
+ validation: 2024-10-30
+ posted: 2024-10-30
+categories:
+ - environmental-footprint
+---
+
+
+The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).
+
+
+
+
+- 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
+
+
+ The monthly report shows the total environmental footprint of your Scaleway Organization. However, Elastic Metal servers are currently the only product considered in the calculation. Therefore, **only results related to Elastic Metal servers are shown in the report**.
+
+
+1. Click **Environmental Footprint** in the Organization drop-down menu to go to the **Environmental Footprint Overview** page. The **Environmental Footprint** dashboard appears, displaying the list of your current and past monthly reports.
+
+2. Click the next to the month for the report you want to download.
+ The monthly report is downloaded to your local computer in PDF format.
+3. Open the PDF file.
+4. Read through the document, considering the following elements on the page:
+
+
+
+ - **1.** The start and end date of the period being tracked (month).
+ - **2.** The name of your Organization.
+ - **3.** The total carbon footprint of your Organization per month, which takes into account the impact of the **manufacture** and **use** of all the components that run your active Scaleway products in relation to each service's useful life.
+
+ For a detailed description of how the carbon emissions are calculated, refer to the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page.
+
+ - **4.** The total water consumption of your Organization per month, which is calculated on the basis of the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness) of the data centers in which each of your services are located, as well as the services' electricity consumption.
+
+ For a detailed description of how the water consumption is calculated, refer to the [Water Consumption section](/environmental-footprint/additional-content/environmental-footprint-calculator/#water-consumption) of the Environmental Footprint calculation breakdown documentation page.
+
+ - **5.** The total water consumption and carbon footprint of each of your Projects.
+ - **6.** The total water consumption and carbon footprint per geographical location (Region and Availability Zone)
+ - **7.** The total water consumption and carbon footprint of each of your products.
+
+For both the carbon emissions, and the water consumption, the power consumption of your active resources is used in the calculation. The way you use your resources has a direct impact on power consumption. Therefore, results may vary greatly from one month to another.
+
+For example, if you start your Elastic Metal server on the 15th of the month and leave it running until the end of the month, the data will be calculated for the 15 days of use, not for the whole month. If you leave the server on, non-stop, in the following month, the impact data will be calculated for a full month.
+
+
+ Currently, for the electricity consumption, which is part of the calculation, we rely on estimates based on internal tests in which the Elastic Metal servers were tested in different configurations. We will soon provide an electricity consumption agent to get your exact electricity consumption and provide more accurate reports.
+
\ No newline at end of file
diff --git a/pages/environmental-footprint/index.mdx b/pages/environmental-footprint/index.mdx
index 509656a572..ee4c8ddc73 100644
--- a/pages/environmental-footprint/index.mdx
+++ b/pages/environmental-footprint/index.mdx
@@ -1,8 +1,38 @@
---
meta:
- title: Discover Scaleway's Environmental Footprint
- description: Discover Scaleway's Environmental Footprint
-content:
- h1: Discover Scaleway's Environmental Footprint
- paragraph: Discover Scaleway's Environmental Footprint
----
\ No newline at end of file
+ title: Environmental Footprint Documentation
+ description: Dive into Scaleway Environmental Footprint calculator with our quickstart guide, how-tos, and more.
+---
+
+
+
+
+The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).
+
+This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next.
+
+
+## Getting Started
+
+
+
+
+
\ No newline at end of file
diff --git a/pages/generative-apis/api-cli/index.mdx b/pages/generative-apis/api-cli/index.mdx
new file mode 100644
index 0000000000..5756c6b229
--- /dev/null
+++ b/pages/generative-apis/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Generative APIs - API/CLI
+ description: Generative APIs API/CLI
+content:
+ h1: Generative APIs - API/CLI
+ paragraph: Generative APIs API/CLI
+---
\ No newline at end of file
diff --git a/pages/generative-apis/api-cli/understanding-errors.mdx b/pages/generative-apis/api-cli/understanding-errors.mdx
new file mode 100644
index 0000000000..09ef5b8381
--- /dev/null
+++ b/pages/generative-apis/api-cli/understanding-errors.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Understanding errors
+ description: This page explains how to understand errors with Generative APIs
+content:
+ h1: Understanding errors
+ paragraph: This page explains how to understand errors with Generative APIs
+tags: generative-apis ai-data understanding-data
+dates:
+ validation: 2024-10-31
+ posted: 2024-09-02
+---
+
+Scaleway uses conventional HTTP response codes to indicate the success or failure of an API request.
+In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error caused by the information provided, and codes in the 5xx range show an error from Scaleway servers.
+
+If the response code is not within the 2xx range, the response will contain an error object structured as follows:
+
+```
+{
+ "error": string,
+ "status": number,
+ "message": string
+}
+```
+
+Below are usual HTTP error codes:
+
+- 400 - **Bad Request**: The format or content of your payload is incorrect. The body may be too large, or fail to parse, or the content-type is mismatched.
+- 401 - **Unauthorized**: The `authorization` header is missing. Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/)
+- 403 - **Forbidden**: Your API key does not exist or does not have the necessary permissions to access the requested resource. Find required permission sets in [this page](/generative-apis/api-cli/using-generative-apis/)
+- 404 - **Route Not Found**: The requested resource could not be found. Check your request is being made to the correct endpoint.
+- 422 - **Model Not Found**: The `model` key is present in the request payload, but the corresponding model is not found.
+- 422 - **Missing Model**: The `model` key is missing from the request payload.
+- 429 - **Too Many Requests**: You are exceeding your current quota for the requested model, calculated in requests per minute. Find rate limits on [this page](/generative-apis/reference-content/rate-limits/)
+- 429 - **Too Many Tokens**: You are exceeding your current quota for the requested model, calculated in tokens per minute. Find rate limits on [this page](/generative-apis/reference-content/rate-limits/)
+- 500 - **API error**: An unexpected internal error has occurred within Scaleway's systems. If the issue persists, please [open a support ticket](https://console.scaleway.com/support/tickets/create).
+
+For streaming responses via SSE, 5xx errors may occur after a 200 response has been returned.
\ No newline at end of file
diff --git a/pages/generative-apis/api-cli/using-chat-api.mdx b/pages/generative-apis/api-cli/using-chat-api.mdx
new file mode 100644
index 0000000000..2fe2f11cc5
--- /dev/null
+++ b/pages/generative-apis/api-cli/using-chat-api.mdx
@@ -0,0 +1,93 @@
+---
+meta:
+ title: Using Chat API
+ description: This page explains how to use the Chat API to query models
+content:
+ h1: Using Chat API
+ paragraph: This page explains how to use the Chat API to query models
+tags: generative-apis ai-data chat-api
+dates:
+ validation: 2024-09-03
+ posted: 2024-09-03
+---
+
+Scaleway Generative APIs are designed as a drop-in replacement for the OpenAI APIs. If you have an LLM-driven application that uses one of OpenAI's client libraries, you can easily configure it to point to Scaleway Chat API, and get your existing applications running using open-weight instruct models hosted at Scaleway.
+
+## Create chat completion
+
+Creates a model response for the given chat conversation.
+
+**Request sample:**
+
+```
+curl --request POST \
+ --url https://api.scaleway.ai/v1/chat/completions \
+ --header 'Authorization: Bearer ${SCW_SECRET_KEY}' \
+ --header 'Content-Type: application/json' \
+ --data '{
+ "model": "llama-3.1-8b-instruct",
+ "messages": [
+ {
+ "role": "system",
+ "content": ""
+ },
+ {
+ "role": "user",
+ "content": ""
+ }
+ ],
+ "max_tokens": integer,
+ "temperature": float,
+ "top_p": float,
+ "presence_penalty": float,
+ "stop": "",
+ "stream": boolean,
+ }'
+```
+
+
+## Headers
+
+Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/).
+
+## Body
+
+### Required parameters
+
+| Param | Type | Description |
+| ------------- |-------------|-------------|
+| **messages** | array of objects | A list of messages comprising the conversation so far. |
+| **model** | string | The name of the model to query. |
+
+Our chat API is OpenAI compatible. Use OpenAI’s [API reference](https://platform.openai.com/docs/api-reference/chat/create) for more detailed information on the usage.
+
+### Supported parameters
+
+- temperature
+- top_p
+- max_tokens
+- stream
+- stream_options
+- presence_penalty
+- [response_format](/generative-apis/how-to/use-structured-outputs)
+- logprobs
+- stop
+- seed
+- [tools](/generative-apis/how-to/use-function-calling)
+- [tool_choice](/generative-apis/how-to/use-function-calling)
+
+### Unsupported parameters
+
+- frequency_penalty
+- n
+- top_logprobs
+- logit_bias
+- user
+
+If you have a use case requiring one of these unsupported parameters, please [contact us via Slack](https://slack.scaleway.com/) on #ai channel.
+
+## Going further
+
+1. [Python code examples](/generative-apis/how-to/query-language-models/#querying-language-models-via-api) to query text models using Scaleway's Chat API
+2. [How to use structured outputs](/generative-apis/how-to/use-structured-outputs) with the `response_format` parameter
+3. [How to use function calling](/generative-apis/how-to/use-function-calling) with `tools` and `tool_choice`
\ No newline at end of file
diff --git a/pages/generative-apis/api-cli/using-embeddings-api.mdx b/pages/generative-apis/api-cli/using-embeddings-api.mdx
new file mode 100644
index 0000000000..e81b4e0875
--- /dev/null
+++ b/pages/generative-apis/api-cli/using-embeddings-api.mdx
@@ -0,0 +1,57 @@
+---
+meta:
+ title: Using Embeddings API
+ description: This page explains how to use the Embeddings API
+content:
+ h1: Using Embeddings API
+ paragraph: This page explains how to use the Embeddings API
+tags: generative-apis ai-data embeddings-api
+dates:
+ validation: 2024-09-03
+ posted: 2024-09-03
+---
+
+Scaleway Generative APIs are designed as a drop-in replacement for the OpenAI APIs. If you have clustering or classification tasks already using one of OpenAI's client libraries, you can easily configure it to point to Scaleway Embeddings API, and get your existing applications running with open-weight embedding models hosted at Scaleway.
+
+## Create embeddings
+
+Get a vector representation of a given input that can be easily consumed by machine learning models and algorithms.
+
+**Request sample:**
+
+```
+curl --request POST \
+ --url https://api.scaleway.ai/v1/embeddings \
+ --header 'Authorization: Bearer ${SCW_SECRET_KEY}' \
+ --header 'Content-Type: application/json'
+ --data '{
+ "model": "sentence-t5-xxl",
+ "input": ""
+ }'
+```
+
+## Headers
+
+Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/).
+
+## Body
+
+### Required parameters
+
+| Param | Type | Description |
+| ------------- |-------------|-------------|
+| **input** | string or array | Input text to embed, encoded as a string or array of strings. It cannot be an empty string. |
+| **model** | string | The name of the model to query. |
+
+Our embeddings API is OpenAI compatible. Use OpenAI’s [API reference](https://platform.openai.com/docs/api-reference/embeddings) for more detailed information on the usage.
+
+### Unsupported parameters
+
+- encoding_format (default float)
+- dimensions
+
+If you have a use case requiring one of these unsupported parameters, please [contact us via Slack](https://slack.scaleway.com/) on #ai channel.
+
+
+ Check our [Python code examples](/generative-apis/how-to/query-embedding-models/#querying-embedding-models-via-api) to query embedding models using Scaleway's Embeddings API.
+
\ No newline at end of file
diff --git a/pages/generative-apis/api-cli/using-generative-apis.mdx b/pages/generative-apis/api-cli/using-generative-apis.mdx
new file mode 100644
index 0000000000..1181ad3608
--- /dev/null
+++ b/pages/generative-apis/api-cli/using-generative-apis.mdx
@@ -0,0 +1,79 @@
+---
+meta:
+ title: Using Generative APIs
+ description: This page explains how to use Generative APIs
+content:
+ h1: Using Generative APIs
+ paragraph: This page explains how to use Generative APIs
+tags: generative-apis ai-data embeddings-api
+dates:
+ validation: 2024-08-28
+ posted: 2024-08-28
+---
+
+## Access
+
+- A valid [API key](/iam/how-to/create-api-keys/) is needed.
+
+## Authentication
+
+All requests to the Scaleway Generative APIs must include an `Authorization` HTTP header with your API key prefixed by `Bearer`.
+
+We recommend exporting your secret key as an environment variable, which you can then pass directly in your curl request as follows. Remember to replace the example value with *your own API secret key*.
+
+```
+export SCW_SECRET_KEY=720438f9-fcb9-4ebb-80a7-808ebf15314b
+```
+
+Run the following curl request once you have exported your environment variable:
+
+```
+curl -X GET \
+ -H "Authorization: Bearer ${SCW_SECRET_KEY}" \
+ "https://api.scaleway.ai/v1/models"
+```
+
+When using the OpenAI Python SDK, the API key is set once during client initialization, and the SDK automatically manages the inclusion of the Authorization header in all API requests.
+In contrast, when directly integrating with the Scaleway Generative APIs, you are responsible for manually setting the Authorization header with the API key for each request to ensure proper authentication.
+
+## Content types
+
+Scaleway Generative APIs accept JSON in request bodies and returns JSON in response bodies.
+You will want to send the `Content-Type: application/json` HTTP header in your POST requests.
+
+```
+curl --request POST \
+ --url https://api.scaleway.ai/v1/chat/completions \
+ --header "Authorization: Bearer ${SCW_SECRET_KEY}" \
+ --header "Content-Type: application/json" \
+ --data '{}'
+```
+
+## Permissions
+
+Permissions define the actions a user or an application can perform on Scaleway Generative APIs. They are managed using Scaleway’s [Identity and Access Management](/iam/quickstart/) interface.
+
+[Owner](/iam/concepts/#owner) status or certain [IAM permissions](/iam/concepts/#permission) allow you to perform actions in the intended Organization.
+
+Querying AI models hosted by Scaleway Generative APIs will require any of the following [permission sets](/iam/concepts/#permission-set):
+
+- **GenerativeApisModelAccess**
+- **GenerativeApisFullAccess**
+- **AllProductsFullAccess**
+
+## Projects
+
+You can scope your Generative APIs consumption to a [Project](identity-and-access-management/iam/concepts/#project). This is helpful to restrict IAM users’ access to only the Project they are working on, or to isolate your bills between Projects.
+
+1. Find your Project ID in your [Project settings](https://console.scaleway.com/project/settings)
+2. Insert your Project ID in the Generative APIs service URL, for example:
+
+```
+https://api.scaleway.ai/78e655b5-feb0-417c-bb3f-8c448bd0e8da/v1
+```
+
+The Project ID is hidden for the default Project.
+
+
+
+
diff --git a/pages/generative-apis/api-cli/using-models-api.mdx b/pages/generative-apis/api-cli/using-models-api.mdx
new file mode 100644
index 0000000000..4987f47713
--- /dev/null
+++ b/pages/generative-apis/api-cli/using-models-api.mdx
@@ -0,0 +1,27 @@
+---
+meta:
+ title: Using Models API
+ description: This page explains how to use the Models API
+content:
+ h1: Using Models API
+ paragraph: This page explains how to use the Models API
+tags: generative-apis ai-data embeddings-api
+dates:
+ validation: 2024-09-02
+ posted: 2024-09-02
+---
+
+Scaleway Generative APIs are designed as drop-in replacement for the OpenAI APIs.
+The Models API allows you to easily list the various AI models available at Scaleway.
+
+## List models
+
+Lists the available models, and provides basic information about each one.
+
+**Request sample:**
+
+```
+curl -s \
+ --url "https://api.scaleway.ai/v1/models" \
+ --header "Authorization: Bearer ${SCW_SECRET_KEY}"
+```
\ No newline at end of file
diff --git a/pages/generative-apis/concepts.mdx b/pages/generative-apis/concepts.mdx
new file mode 100644
index 0000000000..8b2e247f41
--- /dev/null
+++ b/pages/generative-apis/concepts.mdx
@@ -0,0 +1,81 @@
+---
+meta:
+ title: Generative APIs - Concepts
+ description: This page explains all the concepts related to Generative APIs
+content:
+ h1: Generative APIs - Concepts
+ paragraph: This page explains all the concepts related to Generative APIs
+tags:
+dates:
+ validation: 2024-08-27
+categories:
+ - ai-data
+---
+
+## API rate limits
+
+API rate limits define the maximum number of requests a user can make to the Generative APIs within a specific time frame. Rate limiting helps to manage resource allocation, prevent abuse, and ensure fair access for all users. Understanding and adhering to these limits is essential for maintaining optimal application performance using these APIs.
+
+## Context window
+
+A context window is the maximum amount of prompt data considered by the model to generate a response. Using models with high context length, you can provide more information to generate relevant responses. The context is measured in tokens.
+
+## Function calling
+
+Function calling allows a large language model (LLM) to interact with external tools or APIs, executing specific tasks based on user requests. The LLM identifies the appropriate function, extracts the required parameters, and returns the results as structured data, typically in JSON format.
+
+## Embeddings
+
+Embeddings are numerical representations of text data that capture semantic information in a dense vector format. In Generative APIs, embeddings are essential for tasks such as similarity matching, clustering, and serving as inputs for downstream models. These vectors enable the model to understand and generate text based on the underlying meaning rather than just the surface-level words.
+
+## Error handling
+
+Error handling refers to the strategies and mechanisms in place to manage and respond to errors during API requests. This includes handling network issues, invalid inputs, or server-side errors. Proper error handling ensures that applications using Generative APIs can gracefully recover from failures and provide meaningful feedback to users.
+
+## Parameters
+
+Parameters are settings that control the behavior and performance of generative models. These include temperature, max tokens, and top-p sampling, among others. Adjusting parameters allows users to tweak the model's output, balancing factors like creativity, accuracy, and response length to suit specific use cases.
+
+## Inter-token Latency (ITL)
+
+The inter-token latency (ITL) corresponds to the average time elapsed between two generated tokens. It is usually expressed in milliseconds.
+
+## JSON mode
+
+JSON mode allows you to guide the language model in outputting well-structured JSON data.
+To activate JSON mode, provide the `response_format` parameter with `{"type": "json_object"}`.
+JSON mode is useful for applications like chatbots or APIs, where a machine-readable format is essential for easy processing.
+
+## Prompt Engineering
+
+Prompt engineering involves crafting specific and well-structured inputs (prompts) to guide the model towards generating the desired output. Effective prompt design is crucial for generating relevant responses, particularly in complex or creative tasks. It often requires experimentation to find the right balance between specificity and flexibility.
+
+## Retrieval Augmented Generation (RAG)
+
+Retrieval Augmented Generation (RAG) is a technique that enhances generative models by integrating information retrieval methods. By fetching relevant data from external sources before generating a response, RAG ensures that the output is more accurate and contextually relevant, especially in scenarios requiring up-to-date or specific information.
+
+## Stop words
+
+Stop words are a parameter set to tell the model to stop generating further tokens after one or more chosen tokens have been generated. This is useful for controlling the end of the model output, as it will cut off at the first occurrence of any of these strings.
+
+## Streaming
+
+Streaming is a parameter allowing responses to be delivered in real-time, showing parts of the output as they are generated rather than waiting for the full response. Scaleway is following the [Server-sent events](https://html.spec.whatwg.org/multipage/server-sent-events.html#server-sent-events) standard. This behavior usually enhances user experience by providing immediate feedback and a more interactive conversation.
+
+## Structured outputs
+
+Structured outputs enable you to format the model's responses to suit specific use cases. To activate structured outputs, provide the `response_format` parameter with `"type": "json_schema"` and define its `"json_schema": {}`.
+By customizing the structure, such as using lists, tables, or key-value pairs, you ensure that the data returned is in a form that is easy to extract and process.
+By specifying the expected response format through the API, you can make the model consistently deliver the output your system requires.
+
+## Temperature
+
+Temperature is a parameter that controls the randomness of the model's output during text generation. A higher temperature produces more creative and diverse outputs, while a lower temperature makes the model's responses more deterministic and focused. Adjusting the temperature allows users to balance creativity with coherence in the generated text.
+
+## Time to First Token (TTFT)
+
+Time to First Token (TTFT) measures the time elapsed from the moment a request is made to the point when the first token of the generated text is returned. TTFT is a crucial performance metric for evaluating the responsiveness of generative models, especially in interactive applications where users expect immediate feedback.
+
+## Tokens
+
+Tokens are the basic units of text that a generative model processes. Depending on the tokenization strategy, these can be words, subwords, or even characters. The number of tokens directly affects the context window size and the computational cost of using the model. Understanding token usage is essential for optimizing API requests and managing costs effectively.
diff --git a/pages/generative-apis/how-to/index.mdx b/pages/generative-apis/how-to/index.mdx
new file mode 100644
index 0000000000..bd5bdc9f85
--- /dev/null
+++ b/pages/generative-apis/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Generative APIs - How Tos
+ description: Generative APIs How Tos
+content:
+ h1: Generative APIs - How Tos
+ paragraph: Generative APIs How Tos
+---
\ No newline at end of file
diff --git a/pages/generative-apis/how-to/query-code-models.mdx b/pages/generative-apis/how-to/query-code-models.mdx
new file mode 100644
index 0000000000..b81e329d51
--- /dev/null
+++ b/pages/generative-apis/how-to/query-code-models.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: How to query code models
+ description: Learn how to interact with powerful language models specialized in code using Scaleway's Generative APIs service.
+content:
+ h1: How to query code models
+ paragraph: Learn how to interact with powerful language models specialized in code using Scaleway's Generative APIs service.
+tags: generative-apis ai-data language-models code-models chat-completions-api
+dates:
+ validation: 2024-12-09
+ posted: 2024-12-09
+---
+
+Scaleway's Generative APIs service allows users to interact with powerful code models hosted on the platform.
+
+Code models are inherently [language models](/generative-apis/how-to/query-language-models/) specialized in **understanding code**, **generating code** and **fixing code**.
+
+As such, they will be available through the same interfaces as language models:
+- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time.
+- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api)
+
+For more information on how to query language models, read [our dedicated documentation](/generative-apis/how-to/query-language-models/).
+
+Code models are also ideal AI assistants when **added to IDEs** (integrated development environments).
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- An IDE such as Visual Studio Code or JetBrains
+
+## Install Continue in your IDE
+
+[Continue](https://www.continue.dev/) is an [open-source code assistant](https://github.com/continuedev/continue) to connect AI models to your IDE.
+
+To get Continue, simply hit `install` in your IDE's marketplace:
+- [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Continue.continue)
+- [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/22707-continue)
+
+## Configure Scaleway as an API provider in Continue
+
+Continue's `config.json` file will set models and providers allowed for chat, autocompletion etc.
+Here is an example configuration with Scaleway's OpenAI-compatible provider:
+
+```json
+"models": [
+ {
+ "model": "qwen2.5-coder-32b-instruct",
+ "title": "Qwen2.5-coder",
+ "provider": "scaleway",
+ "apiKey": "###SCW SECRET KEY###"
+ }
+]
+```
+
+
+ The config.json file is typically stored as `~/.continue/config.json` on Linux/macOS systems, and `%USERPROFILE%\.continue\config.json` on Windows.
+
+
+Read more about how to set up your `config.json` on the [official Continue documentation](https://docs.continue.dev/reference).
+
diff --git a/pages/generative-apis/how-to/query-embedding-models.mdx b/pages/generative-apis/how-to/query-embedding-models.mdx
new file mode 100644
index 0000000000..fd2e4345b6
--- /dev/null
+++ b/pages/generative-apis/how-to/query-embedding-models.mdx
@@ -0,0 +1,79 @@
+---
+meta:
+ title: How to query embedding models
+ description: Learn how to interact with embedding models using Scaleway's Generative APIs service.
+content:
+ h1: How to query embedding models
+ paragraph: Learn how to interact with embedding models using Scaleway's Generative APIs service.
+tags: generative-apis ai-data embedding-models embeddings-api
+dates:
+ validation: 2024-10-30
+ posted: 2024-08-28
+---
+
+
+Scaleway's Generative APIs service allows users to interact with embedding models hosted on the platform.
+The embedding API provides a simple interface for generating vector representations (embeddings) based on your input data.
+The embedding service is OpenAI compatible. Refer to OpenAI's [embedding documentation](https://platform.openai.com/docs/api-reference/embeddings) for more detailed information.
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- Python 3.7+ installed on your system
+
+## Querying embedding models via API
+
+The embedding model inputs text and outputs a vector (list) of floating point numbers to use for tasks like similarity comparisons and search.
+The instructions below show you how to query the model programmatically using the OpenAI SDK.
+
+### Installing the OpenAI SDK
+
+First, ensure you have the OpenAI SDK installed in your development environment. You can install it using pip:
+
+```bash
+pip install openai
+```
+
+### Initializing the client
+
+Initialize the OpenAI client with your base URL and API key:
+
+```python
+from openai import OpenAI
+
+# Initialize the client with your base URL and API key
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API key from Scaleway
+)
+```
+
+### Generating embeddings with bge-multilingual-gemma2
+
+You can now generate embeddings using the `bge-multilingual-gemma2` model, such as the following example:
+
+```python
+# Generate embeddings using the 'bge-multilingual-gemma2' model
+embedding_response = client.embeddings.create(
+ input= "Artificial Intelligence is transforming the world.",
+ model= "bge-multilingual-gemma2"
+)
+
+# Output the embedding vector
+print(embedding_response.data[0].embedding)
+```
+
+This code sends input text to the `bge-multilingual-gemma2` embedding model and returns a vector representation of the text. The `bge-multilingual-gemma2` model is specifically designed for generating high-quality sentence embeddings.
+
+### Model parameters and their effects
+
+The following parameters can be adjusted to influence the output of the embedding model:
+
+- **`input`** (string or array of strings): The text or data you want to convert into vectors.
+- **`model`** (string): The specific embedding model to use, find all our [supported models](/generative-apis/reference-content/supported-models).
+
+
+ If you encounter an error such as "Forbidden 403" refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips.
+
diff --git a/pages/generative-apis/how-to/query-language-models.mdx b/pages/generative-apis/how-to/query-language-models.mdx
new file mode 100644
index 0000000000..237c0a9f93
--- /dev/null
+++ b/pages/generative-apis/how-to/query-language-models.mdx
@@ -0,0 +1,174 @@
+---
+meta:
+ title: How to query language models
+ description: Learn how to interact with powerful language models using Scaleway's Generative APIs service.
+content:
+ h1: How to query language models
+ paragraph: Learn how to interact with powerful language models using Scaleway's Generative APIs service.
+tags: generative-apis ai-data language-models chat-completions-api
+dates:
+ validation: 2024-10-30
+ posted: 2024-08-28
+---
+
+Scaleway's Generative APIs service allows users to interact with powerful language models hosted on the platform.
+
+There are several ways to interact with language models:
+- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time.
+- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api)
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- Python 3.7+ installed on your system
+
+## Accessing the Playground
+
+Scaleway provides a web playground for instruct-based models hosted on Generative APIs.
+
+1. Navigate to **Generative APIs** under the **AI** section of the [Scaleway console](https://console.scaleway.com/) side menu. The list of models you can query displays.
+2. Click the name of the chat model you want to try. Alternatively, click next to the chat model, and click **Try model** in the menu.
+
+The web playground displays.
+
+## Using the playground
+1. Enter a prompt at the bottom of the page, or use one of the suggested prompts in the conversation area.
+2. Edit the hyperparameters listed on the right column, for example the default temperature for more or less randomness on the outputs.
+3. Switch models at the top of the page, to observe the capabilities of chat models offered via Generative APIs.
+4. Click **View code** to get code snippets configured according to your settings in the playground.
+
+## Querying language models via API
+
+The [Chat API](/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations.
+
+You can query the models programmatically using your favorite tools or languages.
+In the following example, we will use the OpenAI Python client.
+
+### Installing the OpenAI SDK
+
+Install the OpenAI SDK using pip:
+
+```bash
+pip install openai
+```
+
+### Initializing the client
+
+Initialize the OpenAI client with your base URL and API key:
+
+```python
+from openai import OpenAI
+
+# Initialize the client with your base URL and API key
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API secret key from Scaleway
+)
+```
+
+### Generating a chat completion
+
+You can now create a chat completion, for example with the `llama-3.1-8b-instruct` model:
+
+```python
+# Create a chat completion using the 'llama-3.1-8b-instruct' model
+response = client.chat.completions.create(
+ model="llama-3.1-8b-instruct",
+ messages=[{"role": "user", "content": "Describe a futuristic city with advanced technology and green energy solutions."}],
+ temperature=0.2, # Adjusts creativity
+ max_tokens=100, # Limits the length of the output
+ top_p=0.7 # Controls diversity through nucleus sampling. You usually only need to use temperature.
+)
+
+# Print the generated response
+print(response.choices[0].message.content)
+```
+
+This code sends a message to the model and returns an answer based on your input. The `temperature`, `max_tokens`, and `top_p` parameters control the response's creativity, length, and diversity, respectively.
+
+A conversation style may include a default system prompt. You may set this prompt by setting the first message with the role system. For example:
+
+```python
+[
+ {
+ "role": "system",
+ "content": "You are Xavier Niel."
+ },
+ {
+ "role": "user",
+ "content": "Hello, what is your name?"
+ }
+]
+```
+
+### Model parameters and their effects
+
+The following parameters will influence the output of the model:
+
+- **`messages`**: A list of message objects that represent the conversation history. Each message should have a `role` (e.g., "system", "user", "assistant") and `content`.
+- **`temperature`**: Controls the output's randomness. Lower values (e.g., 0.2) make the output more deterministic, while higher values (e.g., 0.8) make it more creative.
+- **`max_tokens`**: The maximum number of tokens (words or parts of words) in the generated output.
+- **`top_p`**: Recommended for advanced use cases only. You usually only need to use temperature. `top_p` controls the diversity of the output, using nucleus sampling, where the model considers the tokens with top probabilities until the cumulative probability reaches `top_p`.
+- **`stop`**: A string or list of strings where the model will stop generating further tokens. This is useful for controlling the end of the output.
+
+
+ If you encounter an error such as "Forbidden 403" refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips.
+
+
+## Streaming
+
+By default, the outputs are returned to the client only after the generation process is complete. However, a common alternative is to stream the results back to the client as they are generated. This is particularly useful in chat applications, where it allows the client to view the results incrementally as each token is produced.
+Following is an example using the chat completions API:
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API key from Scaleway
+)
+response = client.chat.completions.create(
+ model="llama-3.1-8b-instruct",
+ messages=[{
+ "role": "user",
+ "content": "Sing me a song",
+ }],
+ stream=True,
+)
+
+for chunk in response:
+ if chunk.choices and chunk.choices[0].delta.content:
+ print(chunk.choices[0].delta.content, end="")
+```
+
+## Async
+
+The service also supports asynchronous mode for any chat completion.
+
+```python
+
+import asyncio
+from openai import AsyncOpenAI
+
+client = AsyncOpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API key from Scaleway
+)
+
+async def main():
+ stream = await client.chat.completions.create(
+ model="llama-3.1-8b-instruct",
+ messages=[{
+ "role": "user",
+ "content": "Sing me a song",
+ }],
+ stream=True,
+ )
+ async for chunk in stream:
+ if chunk.choices and chunk.choices[0].delta.content:
+ print(chunk.choices[0].delta.content, end="")
+
+asyncio.run(main())
+```
diff --git a/pages/generative-apis/how-to/query-vision-models.mdx b/pages/generative-apis/how-to/query-vision-models.mdx
new file mode 100644
index 0000000000..be6d5321d3
--- /dev/null
+++ b/pages/generative-apis/how-to/query-vision-models.mdx
@@ -0,0 +1,247 @@
+---
+meta:
+ title: How to query vision models
+ description: Learn how to interact with powerful vision models using Scaleway's Generative APIs service.
+content:
+ h1: How to query vision models
+ paragraph: Learn how to interact with powerful vision models using Scaleway's Generative APIs service.
+tags: generative-apis ai-data vision-models chat-completions-api
+dates:
+ validation: 2024-10-30
+ posted: 2024-10-30
+---
+
+Scaleway's Generative APIs service allows users to interact with powerful vision models hosted on the platform.
+
+
+ Vision models can understand and analyze images, not generate them.
+
+
+There are several ways to interact with vision models:
+- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/generative-apis/how-to/query-vision-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time.
+- Via the [Chat API](/generative-apis/how-to/query-vision-models/#querying-vision-models-via-the-api)
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- Python 3.7+ installed on your system
+
+## Accessing the playground
+
+Scaleway provides a web playground for vision models hosted on Generative APIs.
+
+1. Navigate to **Generative APIs** under the **AI** section of the [Scaleway console](https://console.scaleway.com/) side menu. The list of models you can query displays.
+2. Click the name of the vision model you want to try. Alternatively, click next to the vision model, and click **Try model** in the menu.
+
+The web playground displays.
+
+## Using the playground
+1. Upload one or multiple images to the prompt area at the bottom of the page. Enter a prompt, for example, to describe the image(s) you attached.
+2. Edit the hyperparameters listed on the right column, for example the default temperature for more or less randomness on the outputs.
+3. Switch models at the top of the page, to observe the capabilities of chat and vision models offered via Generative APIs.
+4. Click **View code** to get code snippets configured according to your settings in the playground.
+
+## Querying vision models via the API
+
+The [Chat API](/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations.
+
+You can query the vision models programmatically using your favorite tools or languages.
+Vision models take both text and images as inputs.
+
+
+ Unlike traditional language models, vision models will take a content array for the user role, structuring text and images as inputs.
+
+
+In the following example, we will use the OpenAI Python client.
+
+### Installing the OpenAI SDK
+
+Install the OpenAI SDK using pip:
+
+```bash
+pip install openai
+```
+
+### Initializing the client
+
+Initialize the OpenAI client with your base URL and API key:
+
+```python
+from openai import OpenAI
+
+# Initialize the client with your base URL and API key
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API secret key from Scaleway
+)
+```
+
+### Generating a chat completion
+
+You can now create a chat completion, for example with the `pixtral-12b-2409` model:
+
+```python
+# Create a chat completion using the 'pixtral-12b-2409' model
+response = client.chat.completions.create(
+ model="pixtral-12b-2409",
+ messages=[
+ {
+ "role": "user",
+ "content": [
+ {"type": "text", "text": "What is this image?"},
+ {"type": "image_url", "image_url": {"url": "https://picsum.photos/id/32/512/512"}},
+ ] # Vision models will take a content array with text and image_url objects.
+
+ }
+ ],
+ temperature=0.7, # Adjusts creativity
+ max_tokens=2048, # Limits the length of the output
+ top_p=0.9 # Controls diversity through nucleus sampling. You usually only need to use temperature.
+)
+
+# Print the generated response
+print(response.choices[0].message.content)
+```
+
+This code sends messages, prompts and images, to the vision model and returns an answer based on your input. The `temperature`, `max_tokens`, and `top_p` parameters control the response's creativity, length, and diversity, respectively.
+
+A conversation style may include a default system prompt. You may set this prompt by setting the first message with the role system. For example:
+
+```python
+[
+ {
+ "role": "system",
+ "content": "You are Xavier Niel."
+ }
+]
+```
+
+### Passing images to Pixtral
+
+1. **Image URLs**: If the image is available online, you can just include the image URL in your request as demonstrated above. This approach is simple and does not require any encoding.
+2. **Base64 encoded**: image Base64 encoding is a standard way to transform binary data, like images, into a text format, making it easier to transmit over the internet.
+
+The following Python code sample shows you how to encode an image in base64 format and pass it to your request payload.
+
+```python
+import base64
+from io import BytesIO
+from PIL import Image
+
+def encode_image(img):
+ buffered = BytesIO()
+ img.save(buffered, format="JPEG")
+ encoded_string = base64.b64encode(buffered.getvalue()).decode("utf-8")
+ return encoded_string
+
+img = Image.open("path_to_your_image.jpg")
+base64_img = encode_image(img)
+
+payload = {
+ "messages": [
+ {
+ "role": "user",
+ "content": [
+ {
+ "type": "text",
+ "text": "What is this image?"
+ },
+ {
+ "type": "image_url",
+ "image_url": {
+ "url": f"data:image/jpeg;base64,{base64_img}"
+ }
+ }
+ ]
+ }
+ ],
+ ... # other parameters
+}
+
+```
+
+### Model parameters and their effects
+
+The following parameters will influence the output of the model:
+
+- **`messages`**: A list of message objects that represent the conversation history. Each message should have a `role` (e.g., "system", "user", "assistant") and `content`. The content is an array that can contain text and/or image objects.
+- **`temperature`**: Controls the output's randomness. Lower values (e.g., 0.2) make the output more deterministic, while higher values (e.g., 0.8) make it more creative.
+- **`max_tokens`**: The maximum number of tokens (words or parts of words) in the generated output.
+- **`top_p`**: Recommended for advanced use cases only. You usually only need to use temperature. `top_p` controls the diversity of the output, using nucleus sampling, where the model considers the tokens with top probabilities until the cumulative probability reaches `top_p`.
+- **`stop`**: A string or list of strings where the model will stop generating further tokens. This is useful for controlling the end of the output.
+
+
+ If you encounter an error such as "Forbidden 403", refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips.
+
+
+## Streaming
+
+By default, the outputs are returned to the client only after the generation process is complete. However, a common alternative is to stream the results back to the client as they are generated. This is particularly useful in chat applications, where it allows the client to view the results incrementally as each token is produced.
+The following example shows how to use the chat completion API:
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API key from Scaleway
+)
+response = client.chat.completions.create(
+ model="pixtral-12b-2409",
+ messages=[{
+ "role": "user",
+ "content": [
+ {"type": "text", "text": "What is this image?"},
+ {"type": "image_url", "image_url": {"url": "https://picsum.photos/id/32/512/512"}},
+ ]
+ }],
+ stream=True,
+)
+
+for chunk in response:
+ if chunk.choices and chunk.choices[0].delta.content:
+ print(chunk.choices[0].delta.content, end="")
+```
+
+## Async
+
+The service also supports asynchronous mode for any chat completion.
+
+```python
+
+import asyncio
+from openai import AsyncOpenAI
+
+client = AsyncOpenAI(
+ base_url="https://api.scaleway.ai/v1", # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API key from Scaleway
+)
+
+async def main():
+ stream = await client.chat.completions.create(
+ model="pixtral-12b-2409",
+ messages=[{
+ "role": "user",
+ "content": [
+ {"type": "text", "text": "What is this image?"},
+ {"type": "image_url", "image_url": {"url": "https://picsum.photos/id/32/512/512"}},
+ ]
+ }],
+ stream=True,
+ )
+ async for chunk in stream:
+ if chunk.choices and chunk.choices[0].delta.content:
+ print(chunk.choices[0].delta.content, end="")
+
+asyncio.run(main())
+```
+
+## Frequently Asked Questions
+
+#### Is there a limit to the size of each image?
+The only limitation is in context window (1 token for each 16x16 pixel).
+
+#### What is the maximum amount of images per conversation?
+Each conversation can handle up to 12 images (per request). Attempting to add a 13th image will result in a 400 Bad Request error.
diff --git a/pages/generative-apis/how-to/use-function-calling.mdx b/pages/generative-apis/how-to/use-function-calling.mdx
new file mode 100644
index 0000000000..a9729433a0
--- /dev/null
+++ b/pages/generative-apis/how-to/use-function-calling.mdx
@@ -0,0 +1,332 @@
+---
+meta:
+ title: How to use function calling
+ description: Learn how to implement function calling capabilities using Scaleway's Chat Completions API service.
+content:
+ h1: How to use function calling
+ paragraph: Learn how to enhance AI applications by integrating external tools using Scaleway's Chat Completions API service.
+tags: chat-completions-api
+dates:
+ validation: 2024-11-18
+ posted: 2024-09-24
+---
+
+Scaleway's Chat Completions API supports function calling as introduced by OpenAI.
+
+## What is function calling?
+
+Function calling allows a large language model (LLM) to interact with external tools or APIs, executing specific tasks based on user requests. The LLM identifies the appropriate function, extracts the required parameters, and returns the tool call to be done as structured data, typically in JSON format. While errors can occur, custom parsers or tools like LlamaIndex and LangChain can help ensure valid results.
+
+
+
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- Python 3.7+ installed on your system
+
+## Supported models
+
+All the [chat models](/generative-apis/reference-content/supported-models/#chat-models) hosted by Scaleway support function calling.
+
+## Understanding function calling
+
+Function calling consists of three main components:
+- **Tool definitions**: JSON schemas that describe available functions and their parameters
+- **Tool selection**: Automatic or manual selection of appropriate functions based on user queries
+- **Tool execution**: Processing function calls and handling their responses
+
+The workflow typically follows these steps:
+1. Define available tools using JSON schema
+2. Send system and user query along with tool definitions
+3. Process model's function selection
+4. Execute selected functions
+5. Return results to model for final response
+
+## Code examples
+
+
+ Before diving into the code examples, ensure you have the necessary libraries installed:
+ ```bash
+ pip install openai
+ ```
+
+
+We will demonstrate function calling using a flight scheduling system that allows users to check available flights between European airports.
+
+### Basic function definition
+
+First, let's define our flight schedule function and its schema:
+
+```python
+from openai import OpenAI
+import json
+
+def get_flight_schedule(departure_airport: str, destination_airport: str, departure_date: str) -> dict:
+ """
+ Retrieves flight schedules between two European airports on a specific date.
+ """
+ # Mock flight schedule data
+ flights = {
+ "CDG-LHR-2024-11-01": [
+ {"flight_number": "AF123", "airline": "Air France", "departure_time": "08:00", "arrival_time": "09:00"},
+ {"flight_number": "BA456", "airline": "British Airways", "departure_time": "10:00", "arrival_time": "11:00"},
+ {"flight_number": "LH789", "airline": "Lufthansa", "departure_time": "14:00", "arrival_time": "15:00"}
+ ],
+ "AMS-MUC-2024-11-01": [
+ {"flight_number": "KL101", "airline": "KLM", "departure_time": "07:30", "arrival_time": "09:00"},
+ {"flight_number": "LH202", "airline": "Lufthansa", "departure_time": "12:00", "arrival_time": "13:30"}
+ ]
+ }
+
+ key = f"{departure_airport}-{destination_airport}-{departure_date}"
+ return flights.get(key, {"error": "No flights found for this route and date."})
+
+# Define the tool specification
+tools = [{
+ "type": "function",
+ "function": {
+ "name": "get_flight_schedule",
+ "description": "Get available flights between two European airports on a specific date",
+ "parameters": {
+ "type": "object",
+ "properties": {
+ "departure_airport": {
+ "type": "string",
+ "description": "The IATA code of the departure airport (e.g., CDG, LHR)"
+ },
+ "destination_airport": {
+ "type": "string",
+ "description": "The IATA code of the destination airport"
+ },
+ "departure_date": {
+ "type": "string",
+ "description": "The date of departure in YYYY-MM-DD format"
+ }
+ },
+ "required": ["departure_airport", "destination_airport", "departure_date"]
+ }
+ }
+}]
+```
+
+### Simple function call example
+
+Here is how to implement a basic function call:
+
+```python
+# Initialize the OpenAI client
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1",
+ api_key=""
+)
+
+# Create a simple query
+messages = [
+ {
+ "role": "system",
+ "content": "You are a helpful flight assistant."
+ },
+ {
+ "role": "user",
+ "content": "What flights are available from CDG to LHR on November 1st, 2024?"
+ }
+]
+
+# Make the API call
+response = client.chat.completions.create(
+ model="llama-3.1-70b-instruct",
+ messages=messages,
+ tools=tools,
+ tool_choice="auto"
+)
+```
+
+
+ The model automatically decides which functions to call. However, you can specify a particular function by using the `tool_choice` parameter. In the example above, you can replace `tool_choice=auto` with `tool_choice={"type": "function", "function": {"name": "get_flight_schedule"}}` to explicitly call the desired function.
+
+
+
+ Some models must be told they can use external functions in the system prompt. If you do not provide a system prompt when using tools, Scaleway will automatically add one that works best for that specific model.
+
+
+### Multi-turn conversation handling
+
+For more complex interactions, you will need to handle multiple turns of conversation:
+
+```python
+# Process the tool call
+if response.choices[0].message.tool_calls:
+ tool_call = response.choices[0].message.tool_calls[0]
+
+ # Execute the function
+ if tool_call.function.name == "get_flight_schedule":
+ function_args = json.loads(tool_call.function.arguments)
+ function_response = get_flight_schedule(**function_args)
+
+ # Add results to the conversation
+ messages.extend([
+ {
+ "role": "assistant",
+ "content": None,
+ "tool_calls": [tool_call]
+ },
+ {
+ "role": "tool",
+ "name": tool_call.function.name,
+ "content": json.dumps(function_response),
+ "tool_call_id": tool_call.id
+ }
+ ])
+
+ # Get final response
+ final_response = client.chat.completions.create(
+ model="llama-3.1-70b-instruct",
+ messages=messages
+ )
+ print(final_response.choices[0].message.content)
+```
+
+### Parallel function calling
+
+
+ Meta models do not support parallel tool calls.
+
+
+In addition to one function call described above, you can also call multiple functions in a single turn.
+This section shows an example for how you can use parallel function calling.
+
+Define the tools:
+
+```
+def open_floor_space(floor_number: int) -> bool:
+ """Opens up the specified floor for party space by unlocking doors and moving furniture."""
+ print(f"Floor {floor_number} is now open party space!")
+ return True
+
+def set_lobby_vibe(party_mode: bool) -> str:
+ """Switches lobby screens and lighting to party mode."""
+ status = "party mode activated!" if party_mode else "back to business mode"
+ print(f"Lobby is now in {status}")
+ return "The lobby is ready to party!"
+
+def prep_snack_station(activate: bool) -> bool:
+ """Converts the cafeteria into a snack and drink station."""
+ print(f"Snack station is {'open and stocked!' if activate else 'closed.'}")
+ return True
+```
+
+Define the specifications:
+
+```
+tools = [
+ {
+ "type": "function",
+ "function": {
+ "name": "open_floor_space",
+ "description": "Opens up an entire floor for the party",
+ "parameters": {
+ "type": "object",
+ "properties": {
+ "floor_number": {
+ "type": "integer",
+ "description": "Which floor to open up"
+ }
+ },
+ "required": ["floor_number"]
+ }
+ }
+ },
+ {
+ "type": "function",
+ "function": {
+ "name": "set_lobby_vibe",
+ "description": "Transform lobby atmosphere into party mode",
+ "parameters": {
+ "type": "object",
+ "properties": {
+ "party_mode": {
+ "type": "boolean",
+ "description": "True for party, False for business"
+ }
+ },
+ "required": ["party_mode"]
+ }
+ }
+ },
+ {
+ "type": "function",
+ "function": {
+ "name": "prep_snack_station",
+ "description": "Set up the snack and drink station",
+ "parameters": {
+ "type": "object",
+ "properties": {
+ "activate": {
+ "type": "boolean",
+ "description": "True to open, False to close"
+ }
+ },
+ "required": ["activate"]
+ }
+ }
+ }
+]
+```
+
+Next, call the model with proper instructions
+
+```
+system_prompt = """
+You are an office party control assistant. When asked to transform the office into a party space, you should:
+1. Open up a floor for the party
+2. Transform the lobby into party mode
+3. Set up the snack station
+Make all these changes at once for an instant office party!
+"""
+
+messages = [
+ {"role": "system", "content": system_prompt},
+ {"role": "user", "content": "Turn this office building into a party!"}
+]
+```
+
+## Best practices
+
+When implementing function calling, follow these guidelines for optimal results:
+
+1. **Function design**
+ - Keep function names clear and descriptive
+ - Limit the number of functions to 7 or fewer per conversation
+ - Use detailed parameter descriptions in your JSON schema
+
+2. **Parameter handling**
+ - Always specify required parameters
+ - Use appropriate data types and validation
+ - Include example values in parameter descriptions
+
+3. **Error handling**
+ - Implement robust error handling for function execution
+ - Return clear error messages that the model can interpret
+ - Handle edge cases gracefully
+
+4. **Performance optimization**
+ - Set appropriate temperature values (lower for more precise function calls)
+ - Cache frequently accessed data when possible
+ - Minimize the number of turns in multi-turn conversations
+
+
+ For production applications, always implement proper error handling and input validation. The examples above focus on the happy path for clarity.
+
+
+## Further resources
+
+For more information about function calling and advanced implementations, refer to these resources:
+
+- [OpenAI Function Calling Guide](https://platform.openai.com/docs/guides/function-calling)
+- [JSON Schema Specification](https://json-schema.org/specification)
+- [Chat Completions API Reference](/generative-apis/api-cli/using-chat-api/)
+
+Function calling significantly extends the capabilities of language models by allowing them to interact with external tools and APIs.
+
+
+ We can't wait to see what you will build with function calls. Tell us what you are up to, share your experiments on Scaleway's [Slack community](https://slack.scaleway.com/) #ai
+
\ No newline at end of file
diff --git a/pages/generative-apis/how-to/use-structured-outputs.mdx b/pages/generative-apis/how-to/use-structured-outputs.mdx
new file mode 100644
index 0000000000..e3d7bd6dba
--- /dev/null
+++ b/pages/generative-apis/how-to/use-structured-outputs.mdx
@@ -0,0 +1,251 @@
+---
+meta:
+ title: How to use structured outputs
+ description: Learn how to get consistent JSON format responses using Scaleway's Chat Completions API service.
+content:
+ h1: How to use structured outputs
+ paragraph: Learn how to get consistent JSON format responses using Scaleway's Chat Completions API service.
+tags: chat-completions-api
+dates:
+ validation: 2024-10-30
+ posted: 2024-09-17
+---
+
+
+Structured outputs allow users to get consistent, machine-readable JSON format responses from language models.
+JSON, as a widely-used format, enables seamless integration with a variety of platforms and applications. Its interoperability is crucial for developers aiming to incorporate AI functionality into their current systems with minimal adjustments.
+
+By specifying a response format when using the [Chat Completions API](/generative-apis/api-cli/using-chat-api/), you can ensure that responses are returned in a JSON structure.
+There are two main modes for generating JSON: **Object Mode** (schemaless) and **Schema Mode** (deterministic, structured output).
+
+There are several ways to interact with language models:
+- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time.
+- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api)
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/) for API authentication
+- Python 3.7+ installed on your system
+
+## Types of structured outputs
+
+- **JSON mode** (schemaless):
+ - Type: `{"type": "json_object"}`
+ - This mode is non-deterministic and allows the model to output a JSON object without strict validation.
+ - Useful for flexible outputs when you expect the model to infer a reasonable structure based on your prompt.
+ - JSON mode is older and has been used by developers since early API implementations.
+
+- **Structured outputs (schema mode)** (deterministic/structured):
+ - Type `{"type": "json_schema"}`
+ - This mode enforces a strict schema format, where the output adheres to the predefined structure.
+ - Supports complex types and validation mechanisms as per the [JSON schema specification](https://json-schema.org/specification/).
+ - Structured outputs is a newer feature implemented by OpenAI in 2024 to enable stricter, schema-based response formatting.
+
+
+ - All LLMs on the Scaleway library support **JSON mode** and **Structured outputs**, however, the quality of results will vary in the schemaless JSON mode.
+ - JSON mode: It is important to explicitly ask the model to generate a JSON output either in system prompt or user prompt. To prevent infinite generations, model providers most often encourage users to ask the model for short JSON objects.
+ - Structured outputs: Scaleway supports the [JSON schema specification](https://json-schema.org/specification/) including nested schemas composition (`anyOf`, `allOf`, `oneOf` etc), `$ref`, `all` types, and regular expressions.
+
+
+## Code examples
+
+
+ Before diving into the code examples, ensure you have the necessary libraries installed:
+ ```bash
+ pip install openai pydantic
+ ```
+
+
+The following Python examples demonstrate how to use both **JSON mode** and **Structured outputs** to generate structured responses.
+
+We will send to our LLM a voice note transcript in order to structure it.
+Below is our base code:
+
+```python
+import json
+from openai import OpenAI
+from pydantic import BaseModel, Field
+
+# Set your preferred model
+MODEL = "llama-3.1-8b-instruct"
+
+# Set your API key
+API_KEY = ""
+
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1",
+ api_key=API_KEY,
+)
+
+# Define the schema for the output using Pydantic
+class VoiceNote(BaseModel):
+ title: str = Field(description="A title for the voice note")
+ summary: str = Field(description="A short one sentence summary of the voice note.")
+ actionItems: list[str] = Field(description="A list of action items from the voice note")
+
+# Transcript to use for the output
+TRANSCRIPT = (
+ "Good evening! It's 6:30 PM, and I'm just getting home from work. I have a few things to do "
+ "before I can relax. First, I'll need to water the plants in the garden since they've been in the sun all day. "
+ "Then, I'll start preparing dinner. I think a simple pasta dish with some garlic bread should be good. "
+ "While that's cooking, I'll catch up on a couple of phone calls I missed earlier."
+)
+```
+
+### Using JSON mode (schemaless)
+
+In JSON mode, you can prompt the model to output a JSON object without enforcing a strict schema.
+
+```python
+extract = client.chat.completions.create(
+ messages=[
+ {
+ "role": "system",
+ "content": "The following is a voice message transcript. Only answer in JSON.",
+ },
+ {
+ "role": "user",
+ "content": TRANSCRIPT,
+ },
+ ],
+ model=MODEL,
+ response_format={
+ "type": "json_object",
+ },
+)
+output = json.loads(extract.choices[0].message.content)
+print(json.dumps(output, indent=2))
+```
+
+Output example:
+```json
+{
+ "current_time": "6:30 PM",
+ "tasks": [
+ {
+ "task": "water the plants in the garden",
+ "priority": "high"
+ },
+ {
+ "task": "prepare dinner (pasta with garlic bread)",
+ "priority": "high"
+ },
+ {
+ "task": "catch up on phone calls",
+ "priority": "medium"
+ }
+ ]
+}
+```
+
+### Using structured outputs with JSON schema (Pydantic)
+
+Using [Pydantic](https://docs.pydantic.dev/latest/concepts/models/), users can define the schema as a Python class and enforce the model to return results adhering to this schema.
+
+```python
+extract = client.chat.completions.create(
+ messages=[
+ {
+ "role": "system",
+ "content": "The following is a voice message transcript. Only answer in JSON.",
+ },
+ {
+ "role": "user",
+ "content": TRANSCRIPT,
+ },
+ ],
+ model=MODEL,
+ response_format={
+ "type": "json_schema",
+ "json_schema": {
+ "name": "VoiceNote",
+ "schema": VoiceNote.model_json_schema(),
+ }
+ },
+)
+output = json.loads(extract.choices[0].message.content)
+print(json.dumps(output, indent=2))
+```
+
+Output example:
+```json
+{
+ "title": "To-Do List",
+ "summary": "Returning from work, need to complete tasks before relaxing",
+ "actionItems": [
+ "Water garden",
+ "Prepare dinner: pasta dish with garlic bread",
+ "Catch up on missed phone calls"
+ ]
+}
+```
+
+### Using structured outputs with JSON schema (manual definition)
+
+Alternatively, users can manually define the JSON schema inline when calling the model.
+
+```python
+extract = client.chat.completions.create(
+ messages=[
+ {
+ "role": "system",
+ "content": "The following is a voice message transcript. Only answer in JSON.",
+ },
+ {
+ "role": "user",
+ "content": TRANSCRIPT,
+ },
+ ],
+ model=MODEL,
+ response_format={
+ "type": "json_schema",
+ "json_schema": {
+ "name": "VoiceNote",
+ "schema": {
+ "type": "object",
+ "properties": {
+ "title": {"type": "string"},
+ "summary": {"type": "string"},
+ "actionItems": {
+ "type": "array",
+ "items": {"type": "string"}
+ }
+ },
+ "additionalProperties": False,
+ "required": ["title", "summary", "actionItems"]
+ }
+ }
+ }
+)
+output = json.loads(extract.choices[0].message.content)
+print(json.dumps(output, indent=2))
+```
+
+Output example:
+```json
+{
+ "title": "Evening Routine",
+ "actionItems": [
+ "Water the plants",
+ "Cook dinner (pasta and garlic bread)",
+ "Make phone calls"
+ ],
+ "summary": "Made a list of tasks to accomplish before relaxing tonight"
+}
+```
+
+
+ When using the OpenAI SDKs like in the examples above, you are expected to set `additionalProperties` to false, and to specify all your properties as required.
+
+
+## Conclusion
+
+Using structured outputs with LLMs can significantly enhance data handling in your applications.
+By choosing between JSON mode and Structured outputs with JSON schema, you control the consistency and structure of the model's responses to suit your specific needs.
+
+- **JSON mode** is flexible but less predictable.
+- **Structured outputs** provide strict adherence to a predefined schema, ensuring consistency.
+
+Experiment with both methods to determine which best fits your application's requirements.
diff --git a/pages/generative-apis/index.mdx b/pages/generative-apis/index.mdx
new file mode 100644
index 0000000000..bbd6030701
--- /dev/null
+++ b/pages/generative-apis/index.mdx
@@ -0,0 +1,53 @@
+---
+meta:
+ title: Generative APIs Documentation
+ description: Dive into Scaleway Generative APIs with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## Changelog
+
+
diff --git a/pages/generative-apis/quickstart.mdx b/pages/generative-apis/quickstart.mdx
new file mode 100644
index 0000000000..b0248294b4
--- /dev/null
+++ b/pages/generative-apis/quickstart.mdx
@@ -0,0 +1,109 @@
+---
+meta:
+ title: Generative APIs - Quickstart
+ description: Get started with Scaleway Generative APIs for powerful AI-driven content generation. Follow this guide to set up, configure, and make your first API request.
+content:
+ h1: Generative APIs - Quickstart
+ paragraph: Get started with Scaleway Generative APIs for powerful AI-driven content generation. Follow this guide to set up, configure, and make your first API request.
+tags: generative-apis ai-data quickstart
+dates:
+ validation: 2024-10-30
+ posted: 2024-09-04
+categories:
+ - ai-data
+---
+
+Generative APIs offer seamless access to pre-configured, serverless endpoints of leading AI models.
+No need to configure hardware or deploy your own models.
+
+Hosted in European data centers and priced competitively per million tokens used, these APIs enable efficient and scalable integration of AI capabilities into your applications.
+
+
+ This service is free while in beta. [Specific terms and conditions](https://www.scaleway.com/en/contracts/) apply.
+
+
+
+
+ - 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
+ - A valid [API key](/iam/how-to/create-api-keys/)
+ - Python 3.7+ installed on your system
+
+## Start with the Generative APIs Playground
+
+Scaleway provides a web playground for instruct-based models hosted on Generative APIs.
+
+### Accessing the Playground
+1. Navigate to **Generative APIs** under the **AI** section of the [Scaleway console](https://console.scaleway.com/) side menu. The list of models you can query displays.
+2. Click the name of the chat model you want to try. Alternatively, click next to the chat model, and click **Try model** in the menu.
+
+The web playground displays.
+
+### Using the playground
+1. Enter a prompt at the bottom of the page, or use one of the suggested prompts in the conversation area.
+2. Edit the hyperparameters listed on the right column, for example the default temperature for more or less randomness on the outputs.
+3. Switch models at the top of the page, to observe the capabilities of chat models offered via Generative APIs.
+4. Click **View code** to get code snippets configured according to your settings in the playground.
+
+## Install the OpenAI Python SDK
+
+To start using Generative APIs in your code, you can install the OpenAI Python SDK. Run the following command:
+
+```sh
+pip install openai
+```
+
+
+ Ensure Python is installed on your local machine. If you need to install Python, download it from [python.org](https://www.python.org/downloads/).
+
+
+## Configure and set your API key and service URL
+
+1. Have your [API key](/iam/how-to/create-api-keys/) ready or generate a new one from the Scaleway console.
+2. Use the following code in your Python script:
+
+```py
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1", # # Scaleway's Generative APIs service URL
+ api_key="" # Your unique API secret key from Scaleway
+)
+```
+
+Make sure that you replace `` with the API key obtained from your Scaleway account.
+
+
+ It is recommended to store your API keys securely using environment variables or [secret management tools](/secret-manager/) to prevent unauthorized access.
+
+
+## Send your first API request
+
+You are now ready to make your first API request. Below is an example of generating a description of a futuristic city:
+
+```py
+from openai import OpenAI
+
+# Initialize the client with your base URL and API key
+client = OpenAI(
+ base_url="https://api.scaleway.ai/v1",
+ api_key=""
+)
+
+# Create a chat completion for Llama 3.1 8b instruct
+completion = client.chat.completions.create(
+ model="llama-3.1-8b-instruct",
+ messages=[{"role": "user", "content": "Describe a futuristic city with advanced technology and green energy solutions."}],
+ temperature=0.7,
+ max_tokens=100
+)
+
+# Output the result
+print(completion.choices[0].message.content)
+```
+
+This very simple example demonstrates how the Chat API can be used to generate creative content based on your prompts.
+
+## Going further
+
+Now that you are familiar with the basics, explore the full potential of Generative APIs by customizing your API requests. Refer to our [How-to guides](/generative-apis/how-to/) for more advanced features and usage.
diff --git a/pages/generative-apis/reference-content/data-privacy.mdx b/pages/generative-apis/reference-content/data-privacy.mdx
new file mode 100644
index 0000000000..07de9fcc41
--- /dev/null
+++ b/pages/generative-apis/reference-content/data-privacy.mdx
@@ -0,0 +1,91 @@
+---
+meta:
+ title: Understand the Generative APIs Privacy Policy
+ description: This Privacy Policy outlines how Scaleway processes personal data when you use Generative APIs.
+content:
+ h1: Generative APIs Privacy Policy
+ paragraph: This page explains how Scaleway processes personal data when you use Generative APIs.
+tags: generative-apis ai-data data-privacy
+dates:
+ validation: 2024-09-19
+ posted: 2024-09-19
+---
+
+This Privacy Policy outlines how Scaleway ("we," "us," or "our") processes personal data when you use our AI services (hereinafter "Generative APIs"). This policy supplements the Scaleway [General Privacy Policy](https://www.scaleway.com/en/privacy-policy/).
+Any terms defined in the General Data Protection Regulation (GDPR) (EU Regulation 2016/679) or our [General Privacy Policy](https://www.scaleway.com/en/privacy-policy/) have the same meaning here.
+
+Generative APIs comply with the General Data Protection Regulation (GDPR), ensuring that all personal data is processed in accordance with European Union laws. This includes implementing strong data protection measures, maintaining transparency in data processing activities, and ensuring customers’ rights are upheld.
+
+## 1. Data Processor
+
+The data processor for the Generative APIs service is Scaleway, with its registered office at 8 RUE DE LA VILLE L'EVÊQUE 75008 PARIS 8. We collect and process your personal data strictly to provide access and functionality to AI services.
+
+## 2. Data collection and processing
+
+We collect and process the following categories of data:
+
+- Account information: To access Generative APIs, you must create a customer account. We collect identifying personal data (e.g., name, email) to manage your account and API access.
+- API usage data: When you use Generative APIs, we collect certain anonymized data to monitor performance and improve our service. This includes:
+ - API request metadata (HTTP calls, status codes, timestamps, etc.)
+ - Token counts (input/output specific to large language models (LLMs), without prompt details)
+ - Parameters defined by the user, **excluding the actual content of the prompts (system, user, etc.)**
+
+## 3. How we use your data
+
+The personal data collected is used exclusively for:
+
+- Providing access to the Generative API services.
+- Generating and managing API keys.
+- Monitoring and improving the Generative API service through anonymized data for statistical analysis.
+
+
+- We do not collect, read, reuse, or analyze the content of your inputs, prompts, or outputs generated by the API.
+- Your data is not accessible to other Scaleway customers.
+- Your data is not accessible to the creators of the underlying large language models (LLMs).
+- Your data is not accessible to third-party products, or services.
+
+
+## 4. Data Retention
+
+- Account data: Personal data related to your account is retained in accordance with our [General Privacy Policy](https://www.scaleway.com/en/privacy-policy/).
+- API usage data: Aggregated and anonymized data is stored for up to 6 months for performance monitoring and improvement.
+
+## 5. Data Transfers and Sharing
+
+Your personal data may be stored in the following region: Paris, France.
+
+Your personal data is not shared with third parties except:
+
+- When necessary for service delivery (e.g., payment processing, support).
+- When required by law or in response to valid legal requests.
+
+As a European company, Scaleway’s AI services are not subject to extraterritorial laws such as the American Cloud Act. This means that your data hosted in Europe is protected by European laws, which provide a high level of data sovereignty and security.
+
+## 6. Data Security
+
+We implement appropriate technical and organizational security measures to protect your data against unauthorized access, alteration, disclosure, or destruction.
+
+- Standard security measures
+ - Secured authentication
+ - Complex password
+ - 2FA (customer's choice)
+ - SSH Key
+ - Deletion with secured erasure code
+ - Manage accessibility with security groups
+ - Physical server security
+- AI service security measures
+ - Hosting: Scaleway maintains full control over the Generative APIs service, hosting the models on its infrastructure in Europe without interaction with third-party services.
+ - Encryption: All traffic between the customer and the inference service is encrypted using in-transit TLS encryption to ensure data protection during transmission.
+ - Endpoint Security: Public-facing endpoints are secured with API key tokens.
+
+## 7. Exercising Your Rights
+
+You have a right of access, rectification of inaccurate or incomplete data, deletion for eligible data as well as a right of restriction of processing under certain circumstances and portability.
+
+You can exercise your rights directly in the privacy section of your Scaleway account. For additional questions you can contact the address privacy@scaleway.com.
+For more details on your rights, please refer to our [General Privacy Policy](https://www.scaleway.com/en/privacy-policy/).
+If you believe that your rights have not been respected, you can also file a complaint [with the competent supervisory authority](https://www.edpb.europa.eu/about-edpb/about-edpb/members_fr).
+
+## 8. Policy Updates
+
+This policy may be updated as needed to comply with regulatory requirements. Updates will be communicated on this page, with the most recent changes being effective as of the date posted.
diff --git a/pages/generative-apis/reference-content/index.mdx b/pages/generative-apis/reference-content/index.mdx
new file mode 100644
index 0000000000..68ec995c05
--- /dev/null
+++ b/pages/generative-apis/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Generative APIs - Additional content
+ description: Generative APIs - Additional content
+content:
+ h1: Generative APIs - Additional content
+ paragraph: Generative APIs - Additional content
+---
\ No newline at end of file
diff --git a/pages/generative-apis/reference-content/model-lifecycle.mdx b/pages/generative-apis/reference-content/model-lifecycle.mdx
new file mode 100644
index 0000000000..1a0e6cff49
--- /dev/null
+++ b/pages/generative-apis/reference-content/model-lifecycle.mdx
@@ -0,0 +1,32 @@
+---
+meta:
+ title: Understand Generative APIs model lifecycle
+ description: Learn about the lifecycle of generative AI models in Scaleway. This page explains how each status affects model usage and updates, ensuring you are informed about transitions and how to access the latest model versions.
+content:
+ h1: Model lifecycle
+ paragraph: This page explains how each status affects model usage and updates.
+tags: generative-apis ai-data model-lifecyle
+dates:
+ validation: 2024-09-02
+ posted: 2024-09-02
+---
+
+Scaleway is dedicated to updating and offering the latest versions of generative AI models, ensuring improvements in capabilities, accuracy, and safety.
+
+As new versions of models are introduced, you have the opportunity to explore them through the Scaleway console.
+
+A model provided through Scaleway Generative APIs may be classified into one of these statuses: `Active`, `Deprecated`, or `End-of-Life` (EOL).
+
+- **Active**: This status indicates that the model version is under continuous development by the provider, with ongoing updates that may include bug fixes and enhancements.
+- **Deprecated**: A model version is designated deprecated when a newer, more efficient version is available. Scaleway assigns an EOL date to these deprecated versions. Although deprecated versions remain usable, it's recommended to transition to an active version by the EOL date.
+- **EOL**: At this stage, the model version is retired and no longer accessible for use. Any attempts to utilize an End-of-Life version will not be successful.
+
+
+ In the Scaleway console, a model version’s status is marked as either **Active** or **Deprecated**.
+
+
+We guarantee support for new models for at least 8 months starting from their regional launch. Customers will receive a 3-month notice before any model is marked as End-of-Life (EOL).
+
+
+ Following the EOL date, information regarding the model version remains exclusively available on our [dedicated documentation page](/generative-apis/reference-content/supported-models/#deprecated-models).
+
diff --git a/pages/generative-apis/reference-content/rate-limits.mdx b/pages/generative-apis/reference-content/rate-limits.mdx
new file mode 100644
index 0000000000..f51b8b9df6
--- /dev/null
+++ b/pages/generative-apis/reference-content/rate-limits.mdx
@@ -0,0 +1,48 @@
+---
+meta:
+ title: What are Rate limits with Scaleway Generative APIs
+ description: Find our service limits in tokens per minute and queries per minute
+content:
+ h1: Rate limits
+ paragraph: Find our service limits in tokens per minute and queries per minute
+tags: generative-apis ai-data rate-limits
+dates:
+ validation: 2024-12-09
+ posted: 2024-08-27
+---
+
+## What are the limits?
+
+Any model served through Scaleway Generative APIs gets limited by:
+- Tokens per minute
+- Queries per minute
+
+
+These limits only apply if you created a Scaleway Account and registered a valid payment method. Otherwise, stricter limits apply to ensure usage stays within Free Tier only.
+
+
+### Chat models
+
+| Model string | Requests per minute | Total tokens per minute |
+|-----------------|-----------------|-----------------|
+| `llama-3.1-8b-instruct` | 300 | 100K |
+| `llama-3.1-70b-instruct` | 300 | 100K |
+| `mistral-nemo-instruct-2407`| 300 | 100K |
+| `pixtral-12b-2409`| 300 | 100K |
+| `qwen2.5-32b-instruct`| 300 | 100K |
+
+### Embedding models
+
+| Model string | Requests per minute | Input tokens per minute |
+|-----------------|-----------------|-----------------|
+| `sentence-t5-xxl` | 100 | 200K |
+| `bge-multilingual-gemma2` | 100 | 200K |
+
+## Why do we set rate limits?
+
+These limits safeguard against abuse or misuse of Scaleway Generative APIs, helping to ensure fair access to the API with consistent performance.
+
+## How can I increase the rate limits?
+
+We actively monitor usage and will improve rates based on feedback.
+If you need to increase your rate limits, contact us via the support team, providing details on the model used and specific use case.
diff --git a/pages/generative-apis/reference-content/supported-models.mdx b/pages/generative-apis/reference-content/supported-models.mdx
new file mode 100644
index 0000000000..cc31b9a562
--- /dev/null
+++ b/pages/generative-apis/reference-content/supported-models.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: Supported models
+ description: This page lists which open-source chat or embedding models Scaleway is currently hosting
+content:
+ h1: Supported models
+ paragraph: Generative APIs offer serverless AI models hosted at Scaleway - no need to configure hardware or deploy your own models
+tags: generative-apis ai-data supported-models
+dates:
+ validation: 2025-01-02
+ posted: 2024-09-02
+---
+
+
+ This service is free while in beta. [Specific terms and conditions](https://www.scaleway.com/en/contracts/) apply.
+
+
+Our [Chat API](/generative-apis/how-to/query-language-models) has built-in support for the most popular instruct models.
+
+## Chat models
+
+| Provider | Model string | Context window (Tokens) | Maximum output (Tokens)| License | Model card |
+|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|
+| Meta | `llama-3.3-70b-instruct` | 128k | 4096 | [Llama 3.3 Community](https://www.llama.com/llama3_3/license/) | [HF](https://huggingface.co/meta-llama/Llama-3.3-70B-Instruct) |
+| Meta | `llama-3.1-70b-instruct` | 128k | 4096 | [Llama 3.1 Community](https://llama.meta.com/llama3_1/license/) | [HF](https://huggingface.co/meta-llama/Llama-3.1-70B-Instruct) |
+| Meta | `llama-3.1-8b-instruct` | 128k | 16384 | [Llama 3.1 Community](https://llama.meta.com/llama3_1/license/) | [HF](https://huggingface.co/meta-llama/Llama-3.1-8B-Instruct) |
+| Mistral | `mistral-nemo-instruct-2407` | 128k | 8192 | [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | [HF](https://huggingface.co/mistralai/Mistral-Nemo-Instruct-2407) |
+| Mistral | `pixtral-12b-2409` | 128k | 4096 | [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | [HF](https://huggingface.co/mistralai/Pixtral-12B-2409) |
+| Qwen | `qwen2.5-coder-32b-instruct` | 128k | 8192 | [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0) | [HF](https://huggingface.co/Qwen/Qwen2.5-Coder-32B-Instruct) |
+
+
+
+ If you are unsure which chat model to use, we currently recommend Llama 3.1 8B Instruct (`llama-3.1-8b-instruct`) to get started.
+
+
+
+ Missing a model? [Tell us what you would like to see here](https://feature-request.scaleway.com/?tags=ai-services), and we might add it shortly.
+
+
+## Embedding models
+
+Our [Embeddings API](/generative-apis/how-to/query-embedding-models) provides built-in support for the following models, hosted in Scaleway data centers, available via serverless endpoints.
+
+| Provider | Model string | Model size | Embedding dimension | Context window | License | Model card |
+|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|
+| BAAI | `bge-multilingual-gemma2` | 9B | 3584 | 4096 | [Gemma](https://ai.google.dev/gemma/terms) | [HF](https://huggingface.co/BAAI/bge-multilingual-gemma2) |
+
+## Request a model
+
+**Do not see a model you want to use?** [Tell us or vote for what you would like to add here.](https://feature-request.scaleway.com/?tags=ai-services)
+
+## Deprecated models
+
+Scaleway's model lifecyle is introduced on our [dedicated documentation page](/generative-apis/reference-content/model-lifecycle/).
+
+| Provider | Model string | EOL date
+|-----------------|-----------------|-----------------|
+| SBERT | `sentence-t5-xxl` | 26 February, 2025 |
+
+## EOL models
+
+This section will list models that are retired and no longer accessible for use.
diff --git a/pages/generative-apis/troubleshooting/fixing-common-issues.mdx b/pages/generative-apis/troubleshooting/fixing-common-issues.mdx
new file mode 100644
index 0000000000..3a9ecd1b5a
--- /dev/null
+++ b/pages/generative-apis/troubleshooting/fixing-common-issues.mdx
@@ -0,0 +1,87 @@
+---
+meta:
+ title: Fixing common issues with Generative APIs
+ description: This page lists common issues that you may encounter while using Scaleway's Generative APIs, their causes and recommended solutions.
+content:
+ h1: Fixing common issues with Generative APIs
+ paragraph: Generative APIs offer serverless AI models hosted at Scaleway - no need to configure hardware or deploy your own models
+tags: generative-apis ai-data common-issues
+dates:
+ validation: 2025-01-16
+ posted: 2025-01-16
+---
+
+Below are common issues that you may encounter when using Generative APIs, their causes, and recommended solutions.
+
+## 429: Too Many Requests - You exceeded your current quota of requests/tokens per minute
+
+### Cause
+- You performed too many API requests over a given minute
+- You consumed too many tokens (input and output) with your API requests over a given minute
+
+### Solution
+- [Ask our support](https://console.scaleway.com/support/tickets/create) to raise your quota
+- Smooth out your API requests rate by limiting the number of API requests you perform in parallel
+- Reduce the size of the input or output tokens processed by your API requests
+- Use [Managed Inference](/managed-inference/), where these quota do not apply (your throughput will be only limited by the amount of Inference Deployment your provision)
+
+
+## 504: Gateway Timeout
+
+### Cause
+- The query is too long to process (even if context-length stays [between supported context window and maximum tokens](https://www.scaleway.com/en/docs/generative-apis/reference-content/supported-models/))
+- The model goes into an infinite loop while processing the input (which is a known structural issue with several AI models)
+
+### Solution
+- Set a stricter **maximum token limit** to prevent overly long responses.
+- Reduce the size of the input tokens, or split the input into multiple API requests.
+- Use [Managed Inference](/managed-inference/), where no query timeout is enforced.
+
+## Structured output (e.g., JSON) is not working correctly
+
+### Cause
+- Incorrect field naming in the request, such as using `"format"` instead of the correct `"response_format"` field.
+- Lack of a JSON schema, which can lead to ambiguity in the output structure.
+
+### Solution
+- Ensure the proper field `"response_format"` is used in the query.
+- Provide a JSON schema in the request to guide the model's structured output.
+- Refer to the [documentation on structured outputs](/generative-apis/how-to/use-structured-outputs/) for examples and additional guidance.
+
+
+## Multiple "role": "user" successive messages
+
+### Cause
+- Successive messages with `"role": "user"` are sent in the API request instead of alternating between `"role": "user"` and `"role": "assistant"`.
+
+### Solution
+- Ensure the `"messages"` array alternates between `"role": "user"` and `"role": "assistant"`.
+- If multiple `"role": "user"` messages need to be sent, concatenate them into one `"role": "user"` message or intersperse them with appropriate `"role": "assistant"` responses.
+
+#### Example error message (for Mistral models)
+```json
+{
+ "object": "error",
+ "message": "After the optional system message, conversation roles must alternate user/assistant/user/assistant/...",
+ "type": "BadRequestError",
+ "param": null,
+ "code": 400
+}
+```
+
+## Best practices for optimizing model performance
+
+### Input size management
+- Avoid overly long input sequences; break them into smaller chunks if needed.
+- Use summarization techniques for large inputs to reduce token count while maintaining relevance.
+
+### Use proper parameter configuration
+- Double-check parameters like `"temperature"`, `"max_tokens"`, and `"top_p"` to ensure they align with your use case.
+- For structured output, always include a `"response_format"` and, if possible, a detailed JSON schema.
+
+### Debugging silent errors
+- For cases where no explicit error is returned:
+ - Verify all fields in the API request are correctly named and formatted.
+ - Test the request with smaller and simpler inputs to isolate potential issues.
+
+
diff --git a/pages/generative-apis/troubleshooting/index.mdx b/pages/generative-apis/troubleshooting/index.mdx
new file mode 100644
index 0000000000..6b9669bbeb
--- /dev/null
+++ b/pages/generative-apis/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Generative APIs - Troubleshooting
+ description: Generative APIs - Troubleshooting
+content:
+ h1: Generative APIs - Troubleshooting
+ paragraph: Generative APIs - Troubleshooting
+---
\ No newline at end of file
diff --git a/pages/gpu/assets/scaleway-jupyter-lab.webp b/pages/gpu/assets/scaleway-jupyter-lab.webp
new file mode 100644
index 0000000000..1440010610
Binary files /dev/null and b/pages/gpu/assets/scaleway-jupyter-lab.webp differ
diff --git a/pages/gpu/concepts.mdx b/pages/gpu/concepts.mdx
new file mode 100644
index 0000000000..d9bbd6667e
--- /dev/null
+++ b/pages/gpu/concepts.mdx
@@ -0,0 +1,174 @@
+---
+meta:
+ title: GPU Instances - Concepts
+ description: This page explains all the concepts related to Scaleway GPU Instances
+content:
+ h1: GPU Instances - Concepts
+ paragraph: This page explains all the concepts related to Scaleway GPU Instances
+tags: instance gpu gpu-instance docker nvidia pipenv
+dates:
+ validation: 2024-08-05
+categories:
+ - compute
+---
+
+
+ GPU Instances share many concepts in common with traditional Instances. See also the [Instances Concepts page](/instances/concepts/) for more information.
+
+
+## AI-enabled applications
+
+These applications will feature conversational and multimodal user interfaces (UIs) that will revolutionize interactions within smart spaces, smart robots, and autonomous vehicles.
+The proliferation of AI-enabled applications and innovative use cases is poised to bring transformative changes to various domains, including business, social interactions, and human-machine interfaces.
+
+## Automatic mixed precision
+
+Mixed precision is an emerging technique allowing training with half-precision while retaining the network's accuracy achieved with single precision.
+This innovative technique, known as mixed-precision, combines both single- and half-precision representations.
+Major AI frameworks (such as TensorFlow and PyTorch) have embraced this approach, offering automatic mixed-precision support to accelerate AI training on NVIDIA GPUs with minimal code adjustments.
+
+## BF16
+
+BF16, or Brain Floating Point 16, is a numerical format optimized for neural network computations.
+It strikes a balance between range and precision, making it efficient for deep learning tasks while maintaining accuracy.
+BF16 uses 1 bit for the sign, 8 bits for the exponent, and 7 bits for the mantissa (fractional part). This format provides a wider range than IEEE 754 half-precision (FP16) while still maintaining better precision than integer formats.
+It was introduced to address the limitations of FP16 for deep learning tasks, offering improved efficiency and accuracy for training and running neural network models.
+
+## CUDA
+
+CUDA is a parallel computing platform and API model created by NVIDIA. CUDA is an acronym for **C**ompute **U**nified **D**evice **A**rchitecture.
+
+## Data-centric AI
+
+Data-Centric AI delves into diverse data and analytics techniques, aiming to derive insights from business, Internet of Things (IoT), and sensor data.
+Additionally, it seeks to enhance AI-enabled decisions, making them not only more accurate but also explainable and ethical.
+In this context, the trustworthiness of AI systems, which operate with varying degrees of autonomy, is essential, and their risks need to be effectively managed.
+
+## Docker
+
+[Docker](https://www.docker.com/) is a platform as a service (PaaS) tool, that uses OS-level virtualization to deliver software in packages called containers.
+Scaleway provides a number of pre-built Docker images, which allow you to [run a Docker container on your GPU Instance](/gpu/how-to/use-gpu-with-docker/) and access a preinstalled Pipenv environment ideal for your AI projects.
+
+## Flexpoint
+
+Flexpoint is a numerical representation format tailored for efficient computations in machine learning and neural networks.
+It offers a dynamic range and adaptable precision, optimizing both accuracy and computational efficiency.
+This format's flexibility in bit allocation makes it well-suited for tasks where balancing precision and performance is crucial.
+
+## FP8
+
+FP8, or Quarter Precision, uses an **8**-bit **f**loating-**p**oint representation. It offers even greater speed and memory efficiency at the cost of reduced precision compared to FP16, FP32, or FP64.
+FP8 is often used in specialized applications where extremely fast calculations are required, such as some forms of real-time graphics rendering. However, it may not be suitable for tasks that demand high numerical accuracy.
+
+## FP16
+
+FP16, or Half Precision, uses a **16**-bit **f**loating-**p**oint representation in GPUs. While it offers reduced precision compared to FP32 and FP64, it excels in terms of speed and memory efficiency.
+FP16 is commonly used in deep learning and neural network training, where fast matrix operations are crucial.
+Although it may introduce some numerical instability, techniques like mixed-precision training can mitigate these issues by combining FP16 with higher precision formats for specific operations, achieving a balance between speed and accuracy.
+
+## FP32
+
+FP32, or Single Precision, is a **32**-bit **f**loating-**p**oint representation used in GPUs. It provides a balance between precision and performance, making it the standard for most graphics rendering and general-purpose GPU computing tasks.
+FP32 GPUs are capable of handling a wide range of applications, including gaming, machine learning, and scientific computing, with good numerical accuracy and faster computation compared to FP64.
+
+## FP64
+
+FP64, or Double Precision, refers to a **64**-bit **f**loating-**p**oint representation used in GPUs. It offers high precision for numerical calculations, making it suitable for scientific simulations, engineering, and financial applications where precision is critical.
+Double-precision GPUs perform arithmetic operations with high accuracy but are generally slower compared to lower-precision counterparts due to the larger data size.
+
+## Generative AI
+
+Generative AI involves AI methods that learn representations from data and use them to create entirely new artifacts while retaining similarities to the original data.
+These artifacts can be applied for both positive and negative purposes.
+Generative AI has the ability to generate fresh media content, such as text, images, videos, and audio, as well as synthetic data and models of physical objects.
+Additionally, it finds applications in fields like drug discovery and material design.
+
+## GPU
+
+**G**raphical **P**rocessing **U**nit (GPU) became a go-to term for the specialized electronic circuits, designed to power graphics on a machine. The term was popularized in the late 1990s by the chip manufacturer NVIDIA. GPUs were originally produced primarily to drive high-quality gaming experiences, producing life-like digital graphics. Today, those capabilities are being harnessed more broadly for data processing, artificial intelligence, rendering and video encoding.
+
+## Model-centric AI
+
+Model-centric AI focuses on the most promising and emerging techniques that will pave the way for future groundbreaking advancements in the field of AI.
+These techniques include foundation models, composite AI, physics-informed AI, neuromorphic computing, and biology-inspired algorithms.
+By leveraging these innovative approaches, Model-centric AI aims to drive revolutionary progress in the world of artificial intelligence.
+
+## Nvidia
+
+Nvidia is a brand of GPU for the gaming and professional markets. Scaleway GPU Instances are equipped with NVidia GPUs.
+
+## Inference and training
+
+At a high level, working with deep neural networks involves a two-stage process.
+First, the neural network undergoes training, where its parameters are determined by using labeled examples of inputs and corresponding desired outputs.
+Then, the trained network is deployed for inference, utilizing the learned parameters to classify, recognize, and process unfamiliar inputs.
+
+## Moore's Law
+
+Moore's law, originally observed by Intel co-founder Gordon Moore in 1965, describes a consistent trend wherein the number of transistors per square inch on integrated circuits doubles every year since their inception.
+However, over the past decade, Moore's law has shown signs of deceleration, mainly due to the rapid advancement of GPU architectures, which have outpaced the rate of CPU performance-per-watt growth.
+
+## MXNet
+
+MXNet is a modern, open-source deep learning framework employed for the training and deployment of deep neural networks.
+It provides scalability, facilitating swift model training, while also supporting a versatile programming model and multiple languages.
+
+## PetaFLOPS
+
+PetaFLOPS is a unit of computing speed equal to one thousand million million (10^15) floating-point operations per second.
+
+## Pipenv
+
+Pipenv is a package and dependency manager for Python projects. It harnesses the power of different existing tools, bringing their functionalities together:
+
+- `pip` for Python package management
+- `pyenv` for Python version management
+- `Virtualenv` for creating different virtual Python environments
+- `Pipfile` for managing project dependencies
+
+Pipenv is preinstalled on all of Scaleway's AI Docker images for GPU Instances, making it easy to [use virtual environments](/gpu/how-to/use-pipenv/). Pipenv replaces Anaconda for this purpose.
+
+## PyTorch
+
+PyTorch is a GPU-accelerated tensor computational framework with a Python front end.
+It provides a seamless integration with popular Python libraries like NumPy, SciPy, and Cython, allowing for easy extension of its functionality.
+
+## Responsible and human-centric AI
+
+Responsible and Human-centric AI emphasizes the positive impact of AI on individuals and society, while also addressing the need to manage and mitigate AI-related risks.
+It encourages vendors to adopt ethical and responsible practices in their AI implementations.
+Additionally, it advocates for combining AI with a human touch and common sense to ensure a more holistic and beneficial AI experience for everyone.
+
+## Scratch storage
+
+Scratch storage refers to a type of temporary storage space used in computing systems, particularly in high-performance computing (HPC) environments and supercomputers.
+It is used for short-term cache storage of data that is being actively processed, but it is not meant for long-term or permanent storage.
+Scratch storage is an ephemeral storage solution that does not support features like snapshots, backups, or restores.
+
+
+ Scratch storage does not survive once the server is stopped: doing a full stop/start cycle will erase the scratch data. However, doing a simple reboot or using the stop in place function will keep the data.
+
+
+## Structural sparsity
+
+Modern AI networks are characterized by their substantial size, as they contain millions or even billions of parameters.
+However, not all these parameters are indispensable for precise predictions, and certain ones of these parameters can be transformed into zeros, resulting in "sparse" models that maintain accuracy.
+Although the sparsity feature in the A100 and H100 GPUs primarily enhances AI inference, it also contributes to improved model training performance.
+
+## TensorFlow
+
+TensorFlow is an open-source machine learning software library designed to address a diverse array of tasks.
+Initially developed by Google, it caters to their requirements for creating and training neural networks capable of detecting and interpreting patterns and correlations, akin to human learning and reasoning processes.
+
+## Tensor Cores
+
+NVIDIA's V100, A100, H100, L4, and L40 GPUs are equipped with Tensor Cores, which significantly enhance the performance of matrix-multiplication operations, crucial for neural network training and inferencing.
+These Tensor Cores and their associated data paths are engineered to substantially increase floating-point compute throughput while incurring only modest area and power costs.
+
+## TeraFLOPS
+
+TeraFLOPS is a unit of computing power equal to one trillion (10^12) floating-point operations per second.
+
+## TF32
+
+TF32 is a new precision that functions similarly to FP32. It provides remarkable speed improvements of up to 10X for AI tasks, all without necessitating any alterations to the existing code.
\ No newline at end of file
diff --git a/pages/gpu/how-to/assets/scaleway-jupyter-gpu-instance.webp b/pages/gpu/how-to/assets/scaleway-jupyter-gpu-instance.webp
new file mode 100644
index 0000000000..a00502ad7e
Binary files /dev/null and b/pages/gpu/how-to/assets/scaleway-jupyter-gpu-instance.webp differ
diff --git a/pages/gpu/how-to/assets/scaleway-jupyter-lab.webp b/pages/gpu/how-to/assets/scaleway-jupyter-lab.webp
new file mode 100644
index 0000000000..1440010610
Binary files /dev/null and b/pages/gpu/how-to/assets/scaleway-jupyter-lab.webp differ
diff --git a/pages/gpu/how-to/assets/scaleway-multi-instance-gpu.webp b/pages/gpu/how-to/assets/scaleway-multi-instance-gpu.webp
new file mode 100644
index 0000000000..dd439fb4cc
Binary files /dev/null and b/pages/gpu/how-to/assets/scaleway-multi-instance-gpu.webp differ
diff --git a/pages/gpu/how-to/create-manage-gpu-instance.mdx b/pages/gpu/how-to/create-manage-gpu-instance.mdx
new file mode 100644
index 0000000000..3229a74809
--- /dev/null
+++ b/pages/gpu/how-to/create-manage-gpu-instance.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: How to create and manage a GPU Instance
+ description: This page explains how to create and manage a GPU Instance
+content:
+ h1: How to create and manage a GPU Instance
+ paragraph: This page explains how to create and manage a GPU Instance
+tags: gpu-instance gpu instance
+dates:
+ validation: 2024-09-02
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+Scaleway GPU Instances feature dedicated high-end Nvidia GPUs, making them optimal for tasks such as data processing, artificial intelligence, rendering, and video encoding.
+
+Once you've created your GPU Instance, [connecting to it via SSH](/instances/how-to/connect-to-instance/) allows you to use our [pre-configured Docker images](/gpu/how-to/use-gpu-with-docker/), providing instant access to a [preinstalled environment](/gpu/how-to/use-preinstalled-env/) with your preferred AI libraries and tools already set up.
+
+Moreover, GPU Instances offer all the functionalities of our standard Instances, including [flexible IPs](/instances/how-to/use-flexips/), [Security Groups](/instances/how-to/use-security-groups/), [Private Networks](/instances/how-to/use-private-networks/), backups, and more.
+
+When you have completed your calculations using the GPU Instance, [deletion can be done through the Scaleway console](/instances/how-to/delete-instance/), API, or our CLI tools.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+
+## How to create a GPU Instance
+
+1. Navigate to **Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers).
+2. Click **+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers).
+3. Follow these steps to configure your GPU Instance:
+ - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed.
+ - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information.
+ - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers.
+ - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements.
+
+ * The recommended minimum volume size for GPU OS images is 125 GB.
+ * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/)
+
+ - **Network Configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance.
+ - **Instance Name and Tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently.
+ - **Advanced Options**: Configure `cloud-init` settings if required, or leave them at default values.
+ - **SSH Keys**: Verify the SSH keys that will grant you access to your Instance.
+ - **Estimated Cost**: Review the estimated cost of your GPU Instance based on the selected specifications.
+4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use.
+
+## How to connect to a GPU Instance
+
+See our documentation on [how to connect to your Instance via SSH](/instances/how-to/connect-to-instance/).
+
+Once you have connected via SSH, you can [launch a Docker container](/gpu/how-to/use-gpu-with-docker/) to start working on your AI projects.
+
+## How to use Instance features
+
+For instructions on using any type of GPU Instance feature, including flexible IPs, placement groups, Private Networks, backups, and much more, check out our full [Instance how-to documentation](/instances/how-to/).
+
+## How to delete a GPU Instance
+
+See our documentation on [how to delete your Instance](/instances/how-to/delete-instance/).
\ No newline at end of file
diff --git a/pages/gpu/how-to/index.mdx b/pages/gpu/how-to/index.mdx
new file mode 100644
index 0000000000..5d2d9ad3dd
--- /dev/null
+++ b/pages/gpu/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: GPU Instances - How Tos
+ description: GPU Instances How Tos
+content:
+ h1: GPU Instances - How Tos
+ paragraph: GPU Instances How Tos
+---
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-gpu-with-docker.mdx b/pages/gpu/how-to/use-gpu-with-docker.mdx
new file mode 100644
index 0000000000..9e955c14ec
--- /dev/null
+++ b/pages/gpu/how-to/use-gpu-with-docker.mdx
@@ -0,0 +1,185 @@
+---
+meta:
+ title: How to access the GPU with Docker on Scaleway GPU Instances
+ description: Learn how to efficiently access and use GPUs with Docker on Scaleway GPU Instances.
+content:
+ h1: How to access the GPU with Docker on Scaleway GPU Instances
+ paragraph: Learn how to efficiently access and use GPUs with Docker on Scaleway GPU Instances.
+tags: gpu docker
+dates:
+ validation: 2025-01-20
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+Docker is a platform as a service (PaaS) tool that uses OS-level virtualization to deliver applications in packages called containers. Each container is isolated from the others and each of them bundles their own software, libraries, and configuration files.
+
+Unlike virtual machines, containers share the services of a single operating system kernel. This reduces unnecessary overhead and makes them lightweight and portable. Docker containers can run on any computer running macOS, Windows, or Linux, either on-premises or in a public cloud environment, such as Scaleway.
+
+All [Scaleway GPU Instances](https://www.scaleway.com/en/gpu-instances/) come with prebuilt Docker images which can be launched as soon as you connect to your Instance. Each image provides a different AI environment. When you launch one of these images, you are in your chosen environment within seconds with all your favorite Python packages already installed. Using Docker for your AI projects in this way allows you to ensure that your working environments are both **isolated** and **portable**, since they are in containers that can be easily transferred between machines.
+
+You can also run Docker images provided by other sources and use them with your GPU Instance - for instance, you might want to use Docker images provided by NVIDIA, Google, etc. Alternatively, you could also choose to build your own Docker images.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/)
+
+## How to get started on a GPU Instance with Docker
+
+1. [Connect](/instances/how-to/connect-to-instance/) to your GPU Instance via SSH.
+2. Choose a Docker image from the containers shipped with your GPU Instance. See our [additional content](/gpu/reference-content/docker-images/) for more information about the available Docker images, including the specific commands to run each of them.
+3. Use the following command to pull/run the Docker container. Remember to replace `[OPTIONS]` with any relevant options parameters, and `` with the image name and tag of your chosen image, as shown in the additional content linked above:
+ ```
+ docker run --rm -it [OPTIONS] [COMMAND]
+ ```
+
+
+ Once you have run your Docker container, you may find it useful to refer to our documentation on using [pipenv](/gpu/how-to/use-pipenv/) and the container's [preinstalled environment](/gpu/how-to/use-preinstalled-env/) for more help.
+
+
+## How to map volumes
+
+We recommend that you map volumes from your GPU Instance to your Docker containers, so that your work is not lost when you exit the Docker container. For increased data redundancy, we also recommend storing the directories you map to your Docker containers on [Block Storage](/block-storage/quickstart/).
+
+### How to map local volumes
+
+You can map directories from your GPU Instance's Local Storage to your Docker container, using the `-v :` flag. See the example command below:
+
+```bash
+docker run -it --rm -v /root/mydata/:/workspace nvidia/cuda:11.2.1-runtime-ubuntu20.04
+
+# use the `exit` command for exiting this docker container
+```
+
+In the above example, everything in the `/root/mydata` directory on the Instance will be available in the Docker container, in a directory called `/workspace`. Everything then created, deleted, or modified in the `/workspace` directory will be mapped back to `/root/mydata` on the Instance, and remain there after the container is exited.
+
+
+ When you connect to your GPU Instance, you are probably connecting as the `root` user. Once you then run and enter the Scaleway Docker container, the user `jovyan` is used to run Jupyter Lab. You should therefore adjust the user access rights of your local folder on your GPU Instance OS so that files can be read and written from and to the container as required. This can be achieved by setting the ownership of the directory to map on your GPU Instance OS to the user/group `1000:100`, as used by the user `jovyan` in Jupyter Lab.
+
+
+
+
+ In the following example, we create a directory called `my-data`, create a "Hello World" text file inside that directory, then use the `chown` command to set appropriate ownership for the directory before running the Docker container and specifying the mapped directories. The "Hello World" file is then available inside the Docker container:
+
+ ```bash
+ mkdir -p /root/my-data/
+ echo "Hello World" > /root/my-data/hello.txt
+ chown -R 1000:100 /root/my-data
+ docker run --runtime=nvidia --rm -it -p 8888:8888 -v /root/my-data/:/home/jovyan/ai/my-data rg.fr-par.scw.cloud/scw-ai/tensorflow:latest
+ ```
+
+
+### How to map Block Storage volumes
+
+You can also map [Block Storage](https://www.scaleway.com/en/block-storage/) volumes into your containers. Block Storage is fully backed by SSDs. These three-time replicated, high-speed drives allow up to 5,000 IOPS. Once [attached](/block-storage/how-to/attach-a-volume/) and [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) in the host OS of the GPU Instance, you can map the volume like a local volume, as we did above.
+
+
+ [Block Storage](/block-storage/quickstart/) volumes are independent of your GPU Instance and provide three-time replicated storage. It is recommended to use Block Storage for storing your datasets, training logs, model source code, etc.
+
+
+## Most common Docker commands
+
+Below is a list of the most common commands you use when dealing with Docker containers:
+
+| Command | Usage | Description |
+|---------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **docker login** | `docker login ` | This command is used to login to Docker's default repository (Docker Hub) or any other private Docker registry |
+| **docker pull** | `docker pull ` | This command is used to pull images from the Docker Hub. |
+| **docker run** | `docker run -it -d ` | This command is used to create and execute a container from an image. |
+| **docker ps** | `docker ps` | This command is used to list all running containers. |
+| **docker ps** | `docker ps -a` | This command is used to display all running and exited containers. |
+| **docker exec** | `docker exec -it bash` | This command is used to access the `bash` command prompt on a running container with the ID ``. |
+| **docker stop** | `docker stop ` | This command is used to stop a running container with the ID ``. This command allows the container to shut down gracefully. |
+| **docker kill** | `docker kill ` | This command is used to "kill" a running container with the ID ``. This command ends the execution of the container immediately. |
+| **docker build** | `docker build ` | This command is used to build a new image from a specified Dockerfile. |
+| **docker commit** | `docker commit ` | This command is used to create a new local image of an edited container. |
+| **docker tag** | `docker tag ` or `docker tag /` | This command is used to tag a local image (necessary before pushing to a registry). An image can have multiple tags, like a specific version or "latest". |
+| **docker push** | `docker push ` | This command is used to push a local image to a remote repository. |
+| **docker images** | `docker images` | This command is used to list all available Docker images on the local system. |
+| **docker rm** | `docker rm ` | This command is used to remove a stopped container from the local system. |
+| **docker rmi** | `docker rmi ` | This command is used to delete an image from the Local Storage. |
+| docker version| `docker --version` | This command is used to display information about the currently installed version of Docker. |
+
+For more information regarding the `docker run` command, refer to the [official documentation](https://docs.docker.com/engine/reference/run/).
+
+## How to map ports using Docker
+
+The default behavior of Docker when running a container using `docker run`, is to not publish any internal ports of the container to the outside world. To access services on a container outside of Docker, you have to map the container's internal ports using the `--publish` or `-p` flag.
+
+| Flag value | Description |
+|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `-p 8080:80` | This flag maps TCP port 80 in the container to port 8080 on the Docker host. |
+| `-p 192.168.1.100:8080:80` | This flag maps TCP port 80 in the container to port 8080 on the Docker host for connections to host IP 192.168.1.100. |
+| `-p 8080:80/udp` | This flag maps UDP port 80 in the container to port 8080 on the Docker host. |
+| `-p 8080:80/tcp -p 8080:80/udp` | This flag maps TCP port 80 in the container to TCP port 8080 on the Docker host and maps UDP port 80 in the container to UDP port 8080 on the Docker host. |
+
+
+## How to access the GPU from the inside of a Docker container
+
+You can access the GPU of your Instance from the inside of a Docker container using the preinstalled `nvidia-docker` tool.
+
+With a "vanilla" Docker setup, you need to manually specify the *Nvidia runtime* when launching a Docker container. That way, you can use the GPU inside your container. Check the following example to get an idea of what it looks like:
+
+```
+docker run --runtime=nvidia -it --rm nvidia/cuda:11.2.1-runtime-ubuntu20.04 nvidia-smi
+```
+
+
+ You can omit this option if using the “Ubuntu Focal GPU OS11” Operating System image with your GPU Instance, as this option is set by default in the Docker configuration files.
+
+
+If your Instance has several GPUs, you can specify which GPU(s) to use with the container via the Docker CLI using either the `--gpus` option (starting with Docker 19.03) or using the environment variable `NVIDIA_VISIBLE_DEVICES`.
+
+
+The possible values of the `NVIDIA_VISIBLE_DEVICES` variable are:
+
+| Possible values | Description |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------|
+| `0`,`1`,`2`, (or `GPU-UUID`) | a comma-separated list of GPU UUID(s) or index(es). |
+| `all` | all GPUs will be accessible. This is the default value. |
+| `none` | no GPUs will be accessible, but driver capabilities will be enabled. |
+| `void or empty or unset` | nvidia-container-runtime will have the same behavior as run (i.e. neither GPUs nor capabilities are exposed). |
+
+
+ When using the `--gpus` option to specify the GPUs, the device parameter should be used. This is shown in the examples below. The format of the device parameter should be encapsulated within single quotes, followed by double quotes for the devices you want enumerated to the container. For example: `'"device=2,3"'` will enumerate GPUs 2 and 3 to the container.
+
+ When using the `NVIDIA_VISIBLE_DEVICES` variable, you may need to set `--runtime` to `nvidia`, unless already set as default.
+
+
+### Example commands
+
+* Starting a GPU-enabled CUDA container (using `--gpus`)
+ ```bash
+ docker run --runtime=nvidia -it --rm --gpus all nvidia/cuda:11.2.1-runtime-ubuntu20.04 nvidia-smi
+ ```
+
+* Starting a GPU-enabled container using `NVIDIA_VISIBLE_DEVICES` and specify the nvidia runtime
+ ```bash
+ docker run --runtime=nvidia -it --rm --e NVIDIA_VISIBLE_DEVICES=all nvidia/cuda:11.2.1-runtime-ubuntu20.04 nvidia-smi
+ ```
+
+* Starting a GPU-enabled [Tensorflow](https://www.tensorflow.org/) container with a Jupyter notebook using `NVIDIA_VISIBLE_DEVICES` and map the port `88888` to access the web GUI:
+ ```bash
+ docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=all -it --rm -p 8888:8888 tensorflow/tensorflow:latest-gpu-jupyter
+ ```
+
+* Query the GPU UUID of the first GPU using nvidia-smi and then specifying that to the container:
+ ```bash
+ nvidia-smi -i 0 --query-gpu=uuid --format=csv
+ uuid
+ GPU-18a3e86f-4c0e-cd9f-59c3-55488c4b0c24
+
+ docker run -it --rm --gpus device=GPU-b40b736a-9a07-9cf6-d9da-ed22a1ae16c5 nvidia/cuda:11.2.1-runtime-ubuntu20.04 nvidia-smi
+ ```
+
+## How to push and list Docker images stored on your Scaleway Registry
+
+
+ GPU Instances are compatible with [Scaleway Container Registry](/container-registry/quickstart/). You can create a Container Registry to store and pull your own Docker images.
+
+
+See [detailed information](/container-registry/how-to/pull-images/) on how to pull your own custom Docker images on your GPU Instance.
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-mig-with-kubernetes.mdx b/pages/gpu/how-to/use-mig-with-kubernetes.mdx
new file mode 100644
index 0000000000..06696d00da
--- /dev/null
+++ b/pages/gpu/how-to/use-mig-with-kubernetes.mdx
@@ -0,0 +1,397 @@
+---
+meta:
+ title: How to use NVIDIA MIG technology with Kubernetes
+ description: This section provides information about MIG with Kubernetes
+content:
+ h1: How to use NVIDIA MIG technology with Kubernetes
+ paragraph: This section provides information about MIG with Kubernetes
+tags: NVIDIA H100 MIG multi-instance gpu
+dates:
+ validation: 2025-01-13
+ posted: 2023-09-19
+categories:
+ - compute
+---
+
+
+ * Scaleway offers MIG-compatible GPU Instances such as H100 PCIe GPU Instances
+ * NVIDIA uses the term *GPU instance* to designate a MIG partition of a GPU (MIG= Multi-Instance GPU).
+ * To avoid confusion, we use the term GPU Instance in this document to refer to the Scaleway GPU Instance, and *MIG partition* in the context of the MIG feature.
+
+
+NVIDIA Multi-Instance GPU (MIG) is a powerful feature that allows you to divide a single NVIDIA GPU into multiple smaller partitions, each with its dedicated GPU resources, such as memory and compute units.
+This technology is particularly valuable in Kubernetes (K8s) environments, where efficient resource allocation is crucial for running diverse workloads efficiently.
+
+In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernetes cluster. We cover the steps required to set up and configure MIG-enabled GPUs to use with Kubernetes, to maximize GPU usage and ensure workload isolation and performance predictability.
+
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- A [Kubernetes cluster](/kubernetes/quickstart/#how-to-create-a-kubernetes-cluster) with a [GPU Instance](https://www.scaleway.com/en/gpu-instances/) as node
+
+
+ MIG is fully supported on [Scaleway managed Kubernetes](/kubernetes/quickstart/) clusters (Kapsule and Kosmos).
+
+
+## Configure MIG partitions inside a Kubernetes cluster
+
+1. Find the name of the pods running the Nvidia Driver:
+ ```
+ % kubectl get pods -n kube-system
+ NAME READY STATUS RESTARTS AGE
+ cilium-operator-fbff794f4-kff42 1/1 Running 0 4h13m
+ cilium-sfkgc 1/1 Running 0 4h12m
+ cilium-w768l 1/1 Running 0 4h2m
+ coredns-7449449ddc-plr8m 1/1 Running 0 4h11m
+ csi-node-44xll 2/2 Running 0 4h2m
+ csi-node-pg7vd 2/2 Running 0 4h12m
+ gpu-feature-discovery-dgjlx 1/1 Running 0 20m
+ gpu-operator-6b8db67bfb-2b5f8 1/1 Running 0 4h11m
+ konnectivity-agent-mhcqt 1/1 Running 0 4h12m
+ konnectivity-agent-vrgqg 1/1 Running 0 4h2m
+ kube-proxy-th6g8 1/1 Running 0 4h12m
+ kube-proxy-xcdlj 1/1 Running 0 4h2m
+ metrics-server-59fb595596-4xlbb 1/1 Running 0 4h11m
+ node-problem-detector-cqxnn 1/1 Running 0 4h2m
+ node-problem-detector-kr8v5 1/1 Running 0 4h12m
+ nvidia-container-toolkit-daemonset-2jtn8 1/1 Running 0 4h1m
+ nvidia-cuda-validator-kcgzv 0/1 Completed 0 20m
+ nvidia-dcgm-exporter-5bn4w 1/1 Running 0 20m
+ nvidia-device-plugin-daemonset-vvm8s 1/1 Running 0 20m
+ nvidia-device-plugin-validator-gk6pt 0/1 Completed 0 20m
+ nvidia-driver-daemonset-8t89m 1/1 Running 0 4h1m
+ nvidia-gpu-operator-node-feature-discovery-master-6fb7d946phbmb 1/1 Running 0 4h11m
+ nvidia-gpu-operator-node-feature-discovery-worker-49bwd 1/1 Running 0 4h11m
+ nvidia-gpu-operator-node-feature-discovery-worker-xtnnb 1/1 Running 0 4h2m
+ nvidia-mig-manager-gf492 1/1 Running 0 3h58m
+ nvidia-operator-validator-m4686 1/1 Running 0 20m
+ ```
+
+2. Check the status of NVIDIA SMI in the NVIDIA driver container:
+ ```
+ % kubectl exec nvidia-driver-daemonset-8t89m -t -n kube-system -- nvidia-smi -L
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ ```
+ MIG is currently disabled.
+
+3. Find the name of the H100 GPU node:
+ ```
+ % kubectl get nodes
+ NAME STATUS ROLES AGE VERSION
+ scw-k8s-jovial-dubinsky-default-8dcea9ad52bc47 Ready 4h12m v1.27.4
+ scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 Ready 4h3m v1.27.4
+ ```
+4. Configure two `3g.40gb` MIG partitions by adding a label on the GPU node:
+ ```
+ % kubectl label nodes scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 nvidia.com/mig.config=all-3g.40gb --overwrite
+ node/scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 labeled
+ ```
+5. Check the status of NVIDIA SMI in the NVIDIA driver container:
+ ```
+ % kubectl exec nvidia-driver-daemonset-8t89m -t -n kube-system -- nvidia-smi -L
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 3g.40gb Device 0: (UUID: MIG-3f77eb92-98ee-5f05-8aef-9ec3d3c24b9d)
+ MIG 3g.40gb Device 1: (UUID: MIG-13088296-f5a2-5f84-9e37-6105abda4b4f)
+ ```
+ Two MIG `3g.40gb` partitions are available now.
+
+## Reconfigure MIG partitions inside a Kubernetes cluster
+
+1. Reconfigure the GPU into seven MIG `1g.10gb` partitions by overwriting the existing labels:
+ ```
+ % kubectl label nodes scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 nvidia.com/mig.config=all-1g.10gb --overwrite
+ node/scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 labeled
+ ```
+
+2. Check the status of NVIDIA SMI in the NVIDIA driver container:
+ ```
+ % kubectl exec nvidia-driver-daemonset-8t89m -t -n kube-system -- nvidia-smi -L
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-222504cc-4a15-589b-8ec8-dbc02e6fb378)
+ MIG 1g.10gb Device 1: (UUID: MIG-fdfd2afa-5cbd-5d1d-b1ae-6f0e13cc0ff8)
+ MIG 1g.10gb Device 2: (UUID: MIG-b2925bc6-41ca-5ccd-bf5e-24259386f88e)
+ MIG 1g.10gb Device 3: (UUID: MIG-083c76fc-5d21-5322-9d50-c8e21a01852f)
+ MIG 1g.10gb Device 4: (UUID: MIG-13d8a181-5bc1-5527-9a0f-9c3f9cc1d89e)
+ MIG 1g.10gb Device 5: (UUID: MIG-db99bb81-dde3-5c95-9778-daa291fce210)
+ MIG 1g.10gb Device 6: (UUID: MIG-2d636152-57c2-5e73-9654-b1d21d6d21fb)
+ ```
+ Seven MIG `1g.10gb` partitions are available now.
+
+3. Look at the NVIDIA labels on the node (note the label `nvidia.com/mig.config=all-1g.10gb` and `nvidia.com/gpu.product=NVIDIA-H100-PCIe-MIG-1g.10gb`):
+ ```
+ % kubectl describe nodes scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 | grep "nvidia.com/"
+ nvidia.com/cuda.driver.major=525
+ nvidia.com/cuda.driver.minor=105
+ nvidia.com/cuda.driver.rev=17
+ nvidia.com/cuda.runtime.major=12
+ nvidia.com/cuda.runtime.minor=0
+ nvidia.com/gfd.timestamp=1692810266
+ nvidia.com/gpu-driver-upgrade-state=upgrade-done
+ nvidia.com/gpu.compute.major=9
+ nvidia.com/gpu.compute.minor=0
+ nvidia.com/gpu.count=7
+ nvidia.com/gpu.deploy.container-toolkit=true
+ nvidia.com/gpu.deploy.dcgm=true
+ nvidia.com/gpu.deploy.dcgm-exporter=true
+ nvidia.com/gpu.deploy.device-plugin=true
+ nvidia.com/gpu.deploy.driver=true
+ nvidia.com/gpu.deploy.gpu-feature-discovery=true
+ nvidia.com/gpu.deploy.mig-manager=true
+ nvidia.com/gpu.deploy.node-status-exporter=true
+ nvidia.com/gpu.deploy.nvsm=true
+ nvidia.com/gpu.deploy.operator-validator=true
+ nvidia.com/gpu.engines.copy=1
+ nvidia.com/gpu.engines.decoder=1
+ nvidia.com/gpu.engines.encoder=0
+ nvidia.com/gpu.engines.jpeg=1
+ nvidia.com/gpu.engines.ofa=0
+ nvidia.com/gpu.family=hopper
+ nvidia.com/gpu.machine=SCW-H100-1-80G
+ nvidia.com/gpu.memory=9856
+ nvidia.com/gpu.multiprocessors=14
+ nvidia.com/gpu.present=true
+ nvidia.com/gpu.product=NVIDIA-H100-PCIe-MIG-1g.10gb
+ nvidia.com/gpu.replicas=1
+ nvidia.com/gpu.slices.ci=1
+ nvidia.com/gpu.slices.gi=1
+ nvidia.com/mig.capable=true
+ nvidia.com/mig.config=all-1g.10gb
+ nvidia.com/mig.config.state=success
+ nvidia.com/mig.strategy=single
+ nvidia.com/gpu-driver-upgrade-enabled: true
+ nvidia.com/gpu: 7
+ nvidia.com/gpu: 7
+ nvidia.com/gpu 0 0
+ ```
+
+## Deploy containers that use NVIDIA MIG technology partitions
+
+1. Write a deployment file to deploy 8 pods executing NVIDIA SMI.
+ Open a text editor of your choice and create a deployment file `deploy-mig.yaml`, then paste the following content into the file, save it, and exit the editor:
+ ```yaml
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-1
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-2
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-3
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-4
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-5
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-6
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-7
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+
+ ---
+
+ apiVersion: v1
+ kind: Pod
+ metadata:
+ name: test-8
+ spec:
+ restartPolicy: OnFailure
+ containers:
+ - name: gpu-test
+ image: nvcr.io/nvidia/pytorch:23.07-py3
+ command: [ "nvidia-smi" ]
+ args: ["-L" ]
+ resources:
+ limits:
+ nvidia.com/gpu: 1
+ nodeSelector:
+ nvidia.com/gpu.product : NVIDIA-H100-PCIe-MIG-1g.10gb
+ ```
+
+2. Deploy the pods:
+ ```
+ % kubectl create -f deploy-mig.yaml
+ pod/test-1 created
+ pod/test-2 created
+ pod/test-3 created
+ pod/test-4 created
+ pod/test-5 created
+ pod/test-6 created
+ pod/test-7 created
+ pod/test-8 created
+ ```
+
+3. Display the logs of the pods. The pods print their UUID with the `nvidia-smi` command:
+ ```
+ % kubectl get -f deploy-mig.yaml -o name | xargs -I{} kubectl logs {}
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-2d636152-57c2-5e73-9654-b1d21d6d21fb)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-db99bb81-dde3-5c95-9778-daa291fce210)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-13d8a181-5bc1-5527-9a0f-9c3f9cc1d89e)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-b2925bc6-41ca-5ccd-bf5e-24259386f88e)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-fdfd2afa-5cbd-5d1d-b1ae-6f0e13cc0ff8)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-222504cc-4a15-589b-8ec8-dbc02e6fb378)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-083c76fc-5d21-5322-9d50-c8e21a01852f)
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ MIG 1g.10gb Device 0: (UUID: MIG-fdfd2afa-5cbd-5d1d-b1ae-6f0e13cc0ff8)
+ ```
+ As you can see, seven pods have been executed on different MIG partitions, while the eighth pod had to wait for one of the seven MIG partitions to become available to be executed.
+
+4. Clean the deployment:
+ ```
+ % kubectl delete -f deploy-mig.yaml
+ pod "test-1" deleted
+ pod "test-2" deleted
+ pod "test-3" deleted
+ pod "test-4" deleted
+ pod "test-5" deleted
+ pod "test-6" deleted
+ pod "test-7" deleted
+ pod "test-8" deleted
+ ```
+
+## Disable MIG inside a Kubernetes cluster
+
+1. Disable MIG by overwriting the Kubernetes labels:
+ ```
+ % kubectl label nodes scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 nvidia.com/mig.config=all-disabled --overwrite
+ node/scw-k8s-jovial-dubinsky-pool-h100-93a072191d38 labeled
+ ```
+
+2. Check the status of NVIDIA SMI in the driver pod:
+ ```
+ % kubectl exec nvidia-driver-daemonset-8t89m -t -n kube-system -- nvidia-smi -L
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-717ef73c-2d43-4fdc-76d2-1cddef4863bb)
+ ```
+ MIG is disabled and the whole GPU is available.
+
+
+ To enable autoscaling with [Kubernetes Kapsule](/kubernetes/quickstart/), it is necessary to designate a tag for the node pool. This tag will be automatically inherited as a label by all nodes within that pool.
+ Therefore, to create a node pool offering H100 nodes configured with the label `nvidia.com/mig.config=all-3g.40g`, simply assign the tag `noprefix=nvidia.com/mig.config=all-3g.40gb` to the corresponding Kapsule node pool.
+ All nodes added by the autoscaler will automatically receive the label `MIG`. Note, that updates to a tag may take up to five minutes to fully propagate.
+
+
+For more information about NVIDIA MIG, refer to the official [NVIDIA MIG user guide](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/) and the [Kubernetes GPU operator documentation](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/23.6.1/gpu-operator-mig.html).
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-nvidia-mig-technology.mdx b/pages/gpu/how-to/use-nvidia-mig-technology.mdx
new file mode 100644
index 0000000000..0e942d64d8
--- /dev/null
+++ b/pages/gpu/how-to/use-nvidia-mig-technology.mdx
@@ -0,0 +1,341 @@
+---
+meta:
+ title: How to use the NVIDIA MIG technology on GPU Instances
+ description: This section provides information about NVIDIA's MIG technology
+content:
+ h1: How to use the NVIDIA MIG technology on GPU Instances
+ paragraph: This section provides information about NVIDIA's MIG technology
+tags: NVIDIA H100 MIG multi-instance gpu
+dates:
+ validation: 2025-01-13
+ posted: 2023-08-31
+categories:
+ - compute
+---
+
+
+ * Scaleway offers MIG-compatible GPU Instances such as H100 PCIe GPU Instances
+ * NVIDIA uses the term *GPU instance* to designate a MIG partition of a GPU (MIG= Multi-Instance GPU)
+ * To avoid confusion, we will use the term GPU Instance in this document to designate the Scaleway GPU Instance, and *MIG partition* in the context of the MIG feature.
+
+
+NVIDIA Multi-Instance GPU (MIG) is a technology introduced by NVIDIA to enhance the utilization and flexibility of their data center GPUs, specifically designed for virtualization and multi-tenant environments.
+
+It allows a single physical GPU to be partitioned into up to seven smaller Instances, each of which operates as an independent MIG partition with its own dedicated resources, such as memory, compute cores, and video outputs.
+MIG ensures one client cannot impact the work or scheduling of other clients and provides enhanced isolation for customers.
+
+
+
+With MIG, you can see and schedule jobs on virtual MIG partitions as if they were physical GPUs. MIG works with Linux operating systems and containers using Docker Engine, with support for Kubernetes and virtual machines using hypervisors such as Red Hat Virtualization and VMware vSphere.
+
+MIG also provides you with the following benefits:
+
+* **Resource sharing:** MIG allows multiple users or workloads to share a single physical GPU, which can lead to better resource utilization and cost savings.
+* **Complete isolation:** Each MIG partition is isolated from the others, ensuring that workloads running on one Instance do not interfere with or impact the performance of workloads in other Instances. With MIG, each MIG partition's processors have separate and isolated paths through the entire memory system - the on-chip crossbar ports, L2 cache banks, memory controllers, and DRAM address buses are all assigned uniquely to an individual Instance.
+* **Guaranteed resources:** MIG partitions can be configured with specific resource allocations, providing dedicated performance to different workloads. This is especially important in multi-tenant environments.
+
+For more information about NVIDIA MIG, refer to the official [MIG documentation](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/).
+
+
+
+- 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
+- An [MIG-compatible GPU Instance](/gpu/how-to/create-manage-gpu-instance/)
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+
+## How to enable MIG on a GPU Instance
+
+By default, the MIG feature of NVIDIA GPUs is disabled. To use it with your GPU Instance, you need to activate MIG.
+
+1. [Connect to your GPU Instance](/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance) as root using SSH.
+2. Check the status of the MIG mode of your Instance running `nvidia-smi`. It shows that MIG mode is disabled:
+ ```s
+ root@my-h100-instance:~# nvidia-smi -i 0
+ Tue Aug 22 11:58:39 2023
+ +-----------------------------------------------------------------------------+
+ | NVIDIA-SMI 525.125.06 Driver Version: 525.125.06 CUDA Version: 12.0 |
+ |-------------------------------+----------------------+----------------------+
+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
+ | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
+ | | | MIG M. |
+ |===============================+======================+======================|
+ | 0 NVIDIA H100 PCIe On | 00000000:01:00.0 Off | 0 |
+ | N/A 40C P0 51W / 350W | 0MiB / 81559MiB | 0% Default |
+ | | | Disabled |
+ +-------------------------------+----------------------+----------------------+
+ ```
+2. Run the following command to enable MIG mode on the GPU:
+ ```s
+ root@my-h100-instance:~# sudo nvidia-smi -i 0 -mig 1
+ Enabled MIG Mode for GPU 00000000:01:00.0
+ All done.
+ ```
+3. Run the following command to verify that MIG mode is enabled on the GPU:
+ ```s
+ root@my-h100-instance:~# nvidia-smi -i 0 --query-gpu=pci.bus_id,mig.mode.current --format=csv
+ pci.bus_id, mig.mode.current
+ 00000000:01:00.0, Enabled
+ ```
+ MIG is now enabled for the GPU Instance.
+
+## How to list MIG Profiles
+The NVIDIA driver provides several predefined profiles you can choose from while setting up the MIG (Multi-Instance GPU) feature on the H100.
+
+These profiles determine the sizes and functionalities available of the MIG partitions that users can generate. Additionally, the driver supplies details regarding placements, which specify the types and quantities of Instances that can be established.
+
+Refer to the official documentation for more information about the supported [MIG profiles on H100 GPU Instances](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/#h100-profiles).
+
+1. Run the command `nvidia-smi mig -lgip` to retrieve a list of the available MIG profiles for the Instance. An output similar to the following displays:
+ ```s
+ root@my-h100-instance:~# nvidia-smi mig -lgip
+ +-----------------------------------------------------------------------------+
+ | GPU instance profiles: |
+ | GPU Name ID Instances Memory P2P SM DEC ENC |
+ | Free/Total GiB CE JPEG OFA |
+ |=============================================================================|
+ | 0 MIG 1g.10gb 19 7/7 9.62 No 14 1 0 |
+ | 1 1 0 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 1g.10gb+me 20 1/1 9.62 No 14 1 0 |
+ | 1 1 1 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 1g.20gb 15 4/4 19.50 No 14 1 0 |
+ | 1 1 0 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 2g.20gb 14 3/3 19.50 No 30 2 0 |
+ | 2 2 0 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 3g.40gb 9 2/2 39.25 No 46 3 0 |
+ | 3 3 0 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 4g.40gb 5 1/1 39.25 No 62 4 0 |
+ | 4 4 0 |
+ +-----------------------------------------------------------------------------+
+ | 0 MIG 7g.80gb 0 1/1 79.00 No 114 7 0 |
+ | 8 7 1 |
+ +-----------------------------------------------------------------------------+
+ ```
+2. Run the following command to list the possible placements available. The syntax of the placement is `{}:` and shows the placement of the instances on the GPU.
+ ```s
+ root@my-h100-instance:~# nvidia-smi mig -lgipp
+ GPU 0 Profile ID 19 Placements: {0,1,2,3,4,5,6}:1
+ GPU 0 Profile ID 20 Placements: {0,1,2,3,4,5,6}:1
+ GPU 0 Profile ID 15 Placements: {0,2,4,6}:2
+ GPU 0 Profile ID 14 Placements: {0,2,4}:2
+ GPU 0 Profile ID 9 Placements: {0,4}:4
+ GPU 0 Profile ID 5 Placement : {0}:4
+ GPU 0 Profile ID 0 Placement : {0}:8
+ ```
+
+## How to partition the GPU into several MIG partitions
+
+1. Run the following command to divide the H100 GPU Instance into four slices (MIG partitions):
+ ```s
+ root@my-h100-instance:~# sudo nvidia-smi mig -cgi 9,19,19,19 -C
+ Successfully created GPU instance ID 2 on GPU 0 using profile MIG 3g.40gb (ID 9)
+ Successfully created compute instance ID 0 on GPU 0 GPU instance ID 2 using profile MIG 3g.40gb (ID 2)
+ Successfully created GPU instance ID 7 on GPU 0 using profile MIG 1g.10gb (ID 19)
+ Successfully created compute instance ID 0 on GPU 0 GPU instance ID 7 using profile MIG 1g.10gb (ID 0)
+ Successfully created GPU instance ID 8 on GPU 0 using profile MIG 1g.10gb (ID 19)
+ Successfully created compute instance ID 0 on GPU 0 GPU instance ID 8 using profile MIG 1g.10gb (ID 0)
+ Successfully created GPU instance ID 9 on GPU 0 using profile MIG 1g.10gb (ID 19)
+ Successfully created compute instance ID 0 on GPU 0 GPU instance ID 9 using profile MIG 1g.10gb (ID 0)
+ ```
+
+ The command `nvidia-smi mig -cgi 9,19,19,19 -C` is used to manage NVIDIA MIG partitions and their configurations using the NVIDIA System Management Interface (`nvidia-smi`) tool.
+
+ Here is a breakdown of the components of the command:
+
+ * `nvidia-smi`: is the command-line tool provided by NVIDIA to interact with and manage NVIDIA GPUs.
+ * `mig`: is a subcommand of `nvidia-smi` specifically used for managing MIG partitions. MIG (Multi-Instance GPU) allows a single NVIDIA GPU to be partitioned into multiple smaller instances, each with its own memory, compute, and other resources.
+ * `-cgi 9,19,19,19`: this flag specifies the MIG partition configuration. The numbers following the flag represent the MIG partitions for each of the four MIG device slices. In this case, there are four slices with configurations 9, 19, 19, and 19 compute instances each. These numbers correspond to the profile IDs retrieved previously. Note that you can use either of the following:
+ * Profile ID (e.g. 9, 14, 5)
+ * Short name of the profile (e.g. `3g.40gb`)
+ * Full profile name of the instance (e.g. `MIG 3g.40gb`)
+ * `-C`: this flag automatically creates the corresponding compute instances for the MIG partitions.
+
+ The command instructs the `nvidia-smi` tool to set up a MIG configuration where the GPU is divided into four slices, each containing different numbers of MIG partition configurations as specified: an MIG 3g.40gb (Profile ID 9) for the first slice, and an MIG 1g.10gb (Profile ID 19) for each of the remaining three slices.
+
+
+ - Running CUDA workloads on the GPU requires the creation of MIG partitions along with their corresponding compute instances. Just enabling MIG mode on the GPU is not enough to achieve this.
+ - MIG devices are not retained after a system reboot, meaning that resetting your GPU or system requires you to set up MIG configurations again. You can use the [NVIDIA MIG Partition Editor](https://github.com/nvidia/mig-parted) (`mig-parted`) tool for automated assistance in this process.
+ With it, you can create a systemd service, which can be used to reestablish the MIG geometry when the system starts up.
+
+
+2. Run the following command to verify the MIG configuration of the GPU:
+ ```s
+ root@my-h100-instance:~# sudo nvidia-smi mig -lgi
+ +-------------------------------------------------------+
+ | GPU instances: |
+ | GPU Name Profile Instance Placement |
+ | ID ID Start:Size |
+ |=======================================================|
+ | 0 MIG 1g.10gb 19 7 0:1 |
+ +-------------------------------------------------------+
+ | 0 MIG 1g.10gb 19 8 1:1 |
+ +-------------------------------------------------------+
+ | 0 MIG 1g.10gb 19 9 2:1 |
+ +-------------------------------------------------------+
+ | 0 MIG 3g.40gb 9 2 4:4 |
+ +-------------------------------------------------------+
+ ```
+3. Display the UUID of each of your MIG partitions:
+ ```s
+ root@my-h100-instance:~# nvidia-smi -L
+ GPU 0: NVIDIA H100 PCIe (UUID: GPU-7cd6d4d6-9fa8-13be-3c42-09a1b2280a02)
+ MIG 3g.40gb Device 0: (UUID: MIG-da06d78f-7534-56a0-a062-62fef012be91)
+ MIG 1g.10gb Device 1: (UUID: MIG-8aa1fc52-9818-58ec-bc64-8f0cae121bb4)
+ MIG 1g.10gb Device 2: (UUID: MIG-42fa9c93-1430-5ccc-b623-c02fb93b7f5a)
+ MIG 1g.10gb Device 3: (UUID: MIG-6d96b431-44ba-5360-80b0-9359561c927d)
+ ```
+
+4. Run `nvidia-smi` on three 1g.10gb MIG partitions to display their characteristics:
+ * MIG 1g.10gb 1
+ ```s
+ root@my-h100-instance:~# sudo docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=MIG-8aa1fc52-9818-58ec-bc64-8f0cae121bb4 nvidia/cuda:11.0.3-base-ubuntu20.04 nvidia-smi
+ Tue Aug 22 12:53:40 2023
+ +-----------------------------------------------------------------------------+
+ | NVIDIA-SMI 525.125.06 Driver Version: 525.125.06 CUDA Version: 12.0 |
+ |-------------------------------+----------------------+----------------------+
+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
+ | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
+ | | | MIG M. |
+ |===============================+======================+======================|
+ | 0 NVIDIA H100 PCIe On | 00000000:01:00.0 Off | On |
+ | N/A 40C P0 52W / 350W | N/A | N/A Default |
+ | | | Enabled |
+ +-------------------------------+----------------------+----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | MIG devices: |
+ +------------------+----------------------+-----------+-----------------------+
+ | GPU GI CI MIG | Memory-Usage | Vol| Shared |
+ | ID ID Dev | BAR1-Usage | SM Unc| CE ENC DEC OFA JPG|
+ | | | ECC| |
+ |==================+======================+===========+=======================|
+ | 0 7 0 0 | 6MiB / 9856MiB | 14 0 | 1 0 1 0 1 |
+ | | 0MiB / 16383MiB | | |
+ +------------------+----------------------+-----------+-----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | Processes: |
+ | GPU GI CI PID Type Process name GPU Memory |
+ | ID ID Usage |
+ |=============================================================================|
+ | No running processes found |
+ +-----------------------------------------------------------------------------+
+ ```
+ * MIG 1g.10gb 2
+ ```s
+ root@my-h100-instance:~# sudo docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=MIG-42fa9c93-1430-5ccc-b623-c02fb93b7f5a nvidia/cuda:11.0.3-base-ubuntu20.04 nvidia-smi
+ Tue Aug 22 12:54:11 2023
+ +-----------------------------------------------------------------------------+
+ | NVIDIA-SMI 525.125.06 Driver Version: 525.125.06 CUDA Version: 12.0 |
+ |-------------------------------+----------------------+----------------------+
+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
+ | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
+ | | | MIG M. |
+ |===============================+======================+======================|
+ | 0 NVIDIA H100 PCIe On | 00000000:01:00.0 Off | On |
+ | N/A 40C P0 52W / 350W | N/A | N/A Default |
+ | | | Enabled |
+ +-------------------------------+----------------------+----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | MIG devices: |
+ +------------------+----------------------+-----------+-----------------------+
+ | GPU GI CI MIG | Memory-Usage | Vol| Shared |
+ | ID ID Dev | BAR1-Usage | SM Unc| CE ENC DEC OFA JPG|
+ | | | ECC| |
+ |==================+======================+===========+=======================|
+ | 0 8 0 0 | 6MiB / 9856MiB | 14 0 | 1 0 1 0 1 |
+ | | 0MiB / 16383MiB | | |
+ +------------------+----------------------+-----------+-----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | Processes: |
+ | GPU GI CI PID Type Process name GPU Memory |
+ | ID ID Usage |
+ |=============================================================================|
+ | No running processes found |
+ +-----------------------------------------------------------------------------+
+ ```
+ * MIG 1g.10gb 3
+ ```s
+ root@my-h100-instance:~# sudo docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=MIG-6d96b431-44ba-5360-80b0-9359561c927d nvidia/cuda:11.0.3-base-ubuntu20.04 nvidia-smi
+ Tue Aug 22 12:54:54 2023
+ +-----------------------------------------------------------------------------+
+ | NVIDIA-SMI 525.125.06 Driver Version: 525.125.06 CUDA Version: 12.0 |
+ |-------------------------------+----------------------+----------------------+
+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
+ | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
+ | | | MIG M. |
+ |===============================+======================+======================|
+ | 0 NVIDIA H100 PCIe On | 00000000:01:00.0 Off | On |
+ | N/A 40C P0 53W / 350W | N/A | N/A Default |
+ | | | Enabled |
+ +-------------------------------+----------------------+----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | MIG devices: |
+ +------------------+----------------------+-----------+-----------------------+
+ | GPU GI CI MIG | Memory-Usage | Vol| Shared |
+ | ID ID Dev | BAR1-Usage | SM Unc| CE ENC DEC OFA JPG|
+ | | | ECC| |
+ |==================+======================+===========+=======================|
+ | 0 9 0 0 | 6MiB / 9856MiB | 14 0 | 1 0 1 0 1 |
+ | | 0MiB / 16383MiB | | |
+ +------------------+----------------------+-----------+-----------------------+
+
+ +-----------------------------------------------------------------------------+
+ | Processes: |
+ | GPU GI CI PID Type Process name GPU Memory |
+ | ID ID Usage |
+ |=============================================================================|
+ | No running processes found |
+ +-----------------------------------------------------------------------------+
+ ```
+5. Launch a Jupyter Notebook within a Docker container on the MIG 3g.40gb MIG partition. Once initiated, you can reach it by connecting to port 8888 using the public IP of your GPU Instance.
+ ```s
+ root@my-h100-instance:~# sudo docker run --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=MIG-da06d78f-7534-56a0-a062-62fef012be9 -p 8888:8888 jupyter/minimal-notebook
+ ```
+
+
+
+## How to delete MIG partitions
+
+Once you have finished your jobs, you can delete the MIG partitions.
+
+1. Run the following command to remove all MIG partitions and their corresponding compute instances:
+ ```s
+ root@my-h100-instance:~# sudo nvidia-smi mig -dci && sudo nvidia-smi mig -dgi
+ Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 7
+ Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 8
+ Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 9
+ Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 2
+ Successfully destroyed GPU instance ID 7 from GPU 0
+ Successfully destroyed GPU instance ID 8 from GPU 0
+ Successfully destroyed GPU instance ID 9 from GPU 0
+ Successfully destroyed GPU instance ID 2 from GPU 0
+ ```
+2. Verify that the MIG partitions have been removed by running the `nvidia-smi` command:
+ ```s
+ +-----------------------------------------------------------------------------+
+ | MIG devices: |
+ +------------------+----------------------+-----------+-----------------------+
+ | GPU GI CI MIG | Memory-Usage | Vol| Shared |
+ | ID ID Dev | BAR1-Usage | SM Unc| CE ENC DEC OFA JPG|
+ | | | ECC| |
+ |==================+======================+===========+=======================|
+ | No MIG devices found |
+ +-----------------------------------------------------------------------------+
+ ```
+
+## How to disable MIG on a GPU Instance
+
+To disable MIG on your H100 GPU Instance, run the following command:
+```s
+root@my-h100-instance:~# nvidia-smi -mig 0
+Disabled MIG Mode for GPU 00000000:01:00.0
+All done.
+```
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-pipenv.mdx b/pages/gpu/how-to/use-pipenv.mdx
new file mode 100644
index 0000000000..ad3281145c
--- /dev/null
+++ b/pages/gpu/how-to/use-pipenv.mdx
@@ -0,0 +1,148 @@
+---
+meta:
+ title: How to use Pipenv to create virtual environments on Scaleway GPU Instances
+ description: Learn how to use Pipenv to create and manage virtual environments for your Python projects on Scaleway GPU Instances.
+content:
+ h1: How to use Pipenv to create virtual environments on Scaleway GPU Instances
+ paragraph: This guide explains how to use Pipenv to create and manage virtual environments for Python projects on Scaleway GPU Instances.
+tags: Pipenv, virtual environment, GPU, Python
+dates:
+ validation: 2025-01-20
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+Pipenv is a powerful package and dependency manager for Python projects. It combines the functionalities of several tools:
+
+- **pip** for managing Python packages
+- **pyenv** for managing Python versions
+- **Virtualenv** for creating isolated Python environments
+- **Pipfile** for managing project dependencies
+
+**Pipenv is preinstalled on all Scaleway AI Docker images for GPU Instances.** When you launch one of these Docker images, you are placed in an activated Pipenv virtual environment with preinstalled packages and tools. You can also create your own virtual environments using Pipenv.
+
+
+
+### 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
+- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/)
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+
+## Accessing the preinstalled Pipenv virtual environment
+
+Refer to our [dedicated documentation](/gpu/how-to/use-preinstalled-env/#working-with-the-preinstalled-environment-on-ubuntu-focal-gpu-os-11) on how to access the Pipenv virtual environment from your Scaleway GPU Instance.
+
+## Managing packages with Pipenv
+
+You can view, install, uninstall, and update packages using simple `pipenv` commands:
+
+1. View installed packages and dependencies:
+
+ ```sh
+ pipenv graph
+ ```
+
+2. Install a new package:
+
+ ```sh
+ pipenv install
+ ```
+
+
+ To install a specific version of a package, use the command `pipenv install ~=1.2`.
+
+
+3. Uninstall a package:
+
+ ```sh
+ pipenv uninstall
+ ```
+
+4. Update a package:
+
+ ```sh
+ pipenv update
+ ```
+
+
+ To update all packages, simply run `pipenv update`.
+
+
+
+ Be aware that installing and updating packages may cause conflicts with the existing virtual environment installation.
+
+
+## Understanding Pipfiles
+
+Each Pipenv virtual environment has a Pipfile that details project dependencies, replacing the typical `requirements.txt` file. When you create a Pipenv environment, a Pipfile is automatically generated.
+
+1. View Pipfile contents:
+
+ ```sh
+ cat Pipfile
+ ```
+
+ The Pipfile includes:
+ - `source`: Package sources
+ - `packages`: Required packages for production and development
+ - `dev-packages`: Required packages for development only
+ - `requires`: Required Python version
+
+ Packages installed with `pipenv install ` are added to the Pipfile. This allows others to install dependencies from the Pipfile with `pipenv install`.
+
+2. View Pipfile.lock contents:
+
+ ```sh
+ cat Pipfile.lock
+ ```
+
+ The Pipfile.lock specifies package versions to prevent breaking changes from dependency upgrades.
+
+## Creating your own virtual environments
+
+1. Connect to your GPU Instance via SSH and launch a Scaleway AI Docker container.
+
+ You will be in the `~/ai` directory with the virtual environment activated.
+
+2. Exit the current virtual environment:
+
+ ```sh
+ exit
+ ```
+
+3. Navigate to the home directory:
+
+ ```sh
+ cd ~
+ ```
+
+4. Create a new project directory and navigate into it:
+
+ ```sh
+ mkdir my-proj && cd my-proj
+ ```
+
+
+ To avoid losing your virtual environment upon exiting the container, create this folder in a directory [mapped to one of your GPU Instance's local volumes](/gpu/how-to/use-gpu-with-docker#how-to-map-local-volumes).
+
+
+5. Create a new virtual environment and generate a Pipfile:
+
+ ```sh
+ pipenv install
+ ```
+
+6. Activate the virtual environment:
+
+ ```sh
+ pipenv shell
+ ```
+
+ Your prompt should indicate you are in the activated `my-proj` Pipenv virtual environment.
+
+## Going further
+
+For more information, refer to the [official Pipenv documentation](https://docs.pipenv.org/).
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-preinstalled-env.mdx b/pages/gpu/how-to/use-preinstalled-env.mdx
new file mode 100644
index 0000000000..a44a440850
--- /dev/null
+++ b/pages/gpu/how-to/use-preinstalled-env.mdx
@@ -0,0 +1,112 @@
+---
+meta:
+ title: How to use the preinstalled environment
+ description: This page explains how to use the preinstalled environment on a Scaleway Docker image for a GPU Instance
+content:
+ h1: How to use the preinstalled environment
+ paragraph: This page explains how to use the preinstalled environment
+tags: preinstalled environment preinstalled-environment gpu
+dates:
+ validation: 2025-01-13
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+GPU Instances have different types of preinstalled environments, depending on the OS image you chose during [creation of the Instance](/gpu/how-to/create-manage-gpu-instance/):
+
+| OS image | Image release type | Preinstalled on image | Working environment |
+|:----------------------:|:------------------:|:---------------------------------------------------------------:|------------------------------------------------|
+| Ubuntu Focal GPU OS 12 | Latest | Nvidia drivers, Nvidia Docker environment (launch Docker container to access working environment) | Pipenv virtual environment accessed via Docker |
+
+Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation on which you can [launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/). This gives you access to a preinstalled Python environment managed with pipenv. A number of useful AI core packages and tools are installed, including `scipy`, `numpy`, `scikit-learn`, `jupyter`, `tensorflow`, and the Scaleway SDK. Depending on the [Docker image you choose](/gpu/reference-content/docker-images/), other packages and tools will also be preinstalled, providing a convenient framework environment for you so that you can begin work immediately.
+
+
+
+- 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
+- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/)
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account
+
+## Working with the preinstalled environment on Ubuntu Bionic ML legacy images
+
+1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/).
+
+ You are now directly within the conda `ai` preinstalled environment.
+2. Use the [official conda documentation](https://docs.conda.io/projects/conda/en/latest/commands.html) if you need any help managing your conda environment.
+
+ For a full, detailed list of the Python packages and versions preinstalled in this environment, look at the content of the `/root/conda-ai-env-requirements.frozen` file.
+
+
+ As Docker is also preinstalled, you could choose to [launch one of Scaleway's ready-made Docker images](/gpu/how-to/use-gpu-with-docker/) to access our latest working environments, if you wish.
+3. Type `exit` to disconnect from your GPU Instance when you have finished your work.
+
+## Working with the preinstalled environment on Ubuntu Focal GPU OS 12
+
+1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/).
+
+ You are now connected to your Instance, and see your OS. A minimum of packages, including Docker, are installed. Pipenv is **not** preinstalled here. You must launch a Scaleway AI Docker container to access the preinstalled Pipenv environment.
+2. [Launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/).
+
+ You are now in the `ai` directory of the Docker container, in the activated Pipenv virtual environment, and can get right to work!
+
+
+ Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/gpu/how-to/use-pipenv/).
+
+
+### Launching an application in your local browser
+
+Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](https://www.tensorflow.org/tensorboard) and [Code Server](https://code-server.dev/), require a browser to run. You can launch these from the `ai` virtual environment of your Docker container, and view them in the browser of your local machine. This is thanks to the possibility of adding port mapping arguments when launching a container with the `docker run` command. In our example, we added the port mapping arguments `-p 8888:8888 -p 6006:6006` when we launched our container, mapping `8888:8888` for Jupyter Lab and `6006:6006` for Tensorboard.
+
+
+ Code Server runs in Jupyter Lab via Jupyter Hub, so does not need port mapping in this case. You can add other port mapping arguments for other applications as you wish.
+
+
+1. Launch an application. Here, we launch Jupyter Lab:
+
+ `jupyter-lab`
+
+ Within the output, you should see something similar to the following:
+
+ ```
+ [I 2022-04-06 11:38:40.554 ServerApp] Serving notebooks from local directory: /home/jovyan/ai
+ [I 2022-04-06 11:38:40.554 ServerApp] Jupyter Server 1.15.6 is running at:
+ [I 2022-04-06 11:38:40.554 ServerApp] http://7d783f7cf615:8888/lab?token=e0c21db2665ac58c3cf124abf43927a9d27a811449cb356b
+ [I 2022-04-06 11:38:40.555 ServerApp] or http://127.0.0.1:8888/lab?token=e0c21db2665ac58c3cf124abf43927a9d27a811449cb356b
+ [I 2022-04-06 11:38:40.555 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
+ ```
+
+
+ Jupyter Lab is launched automatically when you run any Scaleway container image. You will see a message upon start-up telling you how to access the notebook in your browser. To override Jupyter Lab being launched automatically in this way, add `/bin/bash` to the end of your `docker run` command, e.g. `docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/pytorch:latest /bin/bash`. This preempts the launch of Jupyter Lab at container startup, and replaces it with the specified command, in this case, a bash shell.
+
+2. Open a browser window on your local computer, and enter the following URL. Replace `` with the IP address of your Scaleway GPU Instance, and `` with the token shown in the last lines of terminal output after the `jupyter-lab` command.
+ ```
+ :8888/lab?token=
+ ```
+
+
+ You can find the IP address of your Instance in the Scaleway console. In the side menu, click **Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays.
+
+
+ Jupyter Lab now displays in your browser. You can use the Notebook, Console, or other features as required:
+
+
+
+ You can display the GPU Dashboard in Jupyter Lab to view information about CPU and GPU resource usage. This is accessed via the **System Dashboards** icon on the left side menu (the third icon from the top).
+3. Use CTRL+C in the terminal window of your GPU Instance / Docker container to close the Jupyter server when you have finished.
+
+### Exiting the preinstalled environment and the container
+
+When you are in the activated Pipenv virtual environment, your command line prompt will normally be prefixed by the name of the environment. Here, for example, from `(ai) jovyan@d73f1fa6bf4d:~/ai` we see that we are in the activated `ai` environment, and from `jovyan@d73f1fa6bf4d:~/ai` that we are in the `~/ai` directory of our container:
+
+1. Type `exit` to leave the preinstalled `ai` environment.
+
+ You are now outside the preinstalled virtual environment.
+2. Type `exit` again to exit the Docker container.
+
+ Your prompt should now look similar to the following. You are still connected to your GPU Instance, but you have left the Docker container:
+
+ ```
+ root@scw-name-of-instance:~#
+ ```
+3. Type `exit` once more to disconnect from your GPU Instance.
\ No newline at end of file
diff --git a/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx b/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx
new file mode 100644
index 0000000000..05938b51d0
--- /dev/null
+++ b/pages/gpu/how-to/use-scratch-storage-h100-instances.mdx
@@ -0,0 +1,66 @@
+---
+meta:
+ title: How to use scratch storage on H100 and L40S and L40S GPU Instances
+ description: This page explains how to use scratch storage on H100 and L40S GPU Instances
+content:
+ h1: How to use scratch storage on H100 and L40S GPU Instances
+ paragraph: This page explains how to use scratch storage on H100 and L40S GPU Instances
+tags: H100 L40S gpu scratch-storage scratch storage
+dates:
+ validation: 2025-01-13
+ posted: 2023-09-18
+categories:
+ - compute
+---
+
+Scaleway H100 and L40S GPU Instances are equipped with additional scratch storage. This form of temporary Local Storage operates differently from our regular Local Storage.
+
+Scratch storage temporarily accommodates data during computational or data processing tasks. It is commonly used for storing intermediate results, processing input data, or holding output data before that data is moved to more permanent storage.
+
+Unlike conventional storage, scratch storage lacks features like snapshots, backups, or restores. Furthermore, it is not designed for downloading images; its main function is to serve as a cache. Typically, data in scratch storage is deleted once the computation or processing task concludes.
+
+Scaleway's H100 and L40S GPU Instances use NVMe disks for their scratch storage, which are fine-tuned for high-speed data access. This design ensures fast read and write speeds, which is crucial for applications demanding extensive data processing capabilities.
+
+
+ Scratch storage does not survive once the server is stopped: doing a full stop/start cycle will erase the scratch data. However, doing a simple reboot or using the stop in place function will keep the data.
+
+
+## What can I use scratch storage for?
+
+For example, it may take several minutes to fetch a large image, a delay that impedes the user's ability to promptly initiate model training.
+This delay becomes particularly problematic in the realm of AI, where even a 400 GB dataset is considered relatively small.
+
+To address this issue, we have implemented scratch storage. Unlike traditional storage, with scratch storage, you do not need to download the entire image (which cannot be used for backup restoration as a result). Scratch storage boasts the capability to feed data into the GPU at a significantly accelerated rate. This enhancement allows us to provide the GPU with a substantial amount of scratch storage, ensuring a swifter and more efficient data input process.
+This enhancement allows us to provide the GPU with a substantial amount of scratch storage, ensuring a swifter and more efficient data input process.
+
+
+ The maximum possible size for scratch storage is
+ * for L40S-1-48G Instances: 1.6 TB
+ * for L40S-2-48G Instances: 3.2 TB
+ * for L40S-4-48G Instances: 6.4 TB
+ * for L40S-8-48G Instances: 12.8 TB
+ * for H100-1-80G Instances: 3 TB
+ * for H100-2-80G Instances: 6 TB
+
+
+## How can I add scratch storage to my GPU Instance using the Scaleway CLI or console?
+Scratch storage is automatically added when creating H100 and L40S Instances.
+
+## How can I add scratch storage to my GPU Instance when using the API?
+You need to add an extra volume, for example:
+ ```
+ "volumes":{"1":{"name":"scratch-volume","volume_type":"scratch","size":3000000000000}}
+ ```
+
+## How can I add scratch storage to my GPU Instance using Terraform?
+ ```
+ resource “scaleway_instance_volume” “scratch_volume” {
+ size_in_gb = 3000
+ type = “scratch”
+ }
+ resource “scaleway_instance-server” “myserver” {
+ type = “H100-1-80G”
+ image = “ubuntu_jammy_gpu_os_12”
+ additional_volume_ids = [scaleway_instance_volume.scratch_volume.id]
+ }
+ ```
\ No newline at end of file
diff --git a/pages/gpu/index.mdx b/pages/gpu/index.mdx
new file mode 100644
index 0000000000..83720a0e28
--- /dev/null
+++ b/pages/gpu/index.mdx
@@ -0,0 +1,77 @@
+---
+meta:
+ title: GPU Instances Documentation
+ description: Dive into Scaleway GPU Instances with our quickstart guides, how-tos, tutorials, and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+## Changelog
+
+
+
diff --git a/pages/gpu/quickstart.mdx b/pages/gpu/quickstart.mdx
new file mode 100644
index 0000000000..e23b7ece7d
--- /dev/null
+++ b/pages/gpu/quickstart.mdx
@@ -0,0 +1,123 @@
+---
+meta:
+ title: GPU Instances - Quickstart
+ description: This page shows you how to get started with Scaleway GPU Instances.
+content:
+ h1: GPU Instances - Quickstart
+ paragraph: This page shows you how to get started with Scaleway GPU Instances.
+tags: instance gpu-instance
+dates:
+ validation: 2024-09-02
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+
+
+Scaleway GPU Instances are virtual compute instances equipped with dedicated high-end Nvidia graphics processing units (GPUs). They are ideal for data processing, artificial intelligence, rendering, and video encoding. After you have created your GPU Instance, you can [connect to it via SSH](/instances/how-to/connect-to-instance/) and run one of our ready-made [Docker images](/gpu/how-to/use-gpu-with-docker/) to access a [preinstalled environment](/gpu/how-to/use-preinstalled-env/) with all your [favorite AI libraries and tools](/gpu/reference-content/docker-images/) preinstalled.
+
+In addition to this, GPU Instances have all the features of our regular Instances, including [flexible IPs](/instances/how-to/use-flexips/), [security groups](/instances/how-to/use-security-groups/), [Private Networks](/instances/how-to/use-private-networks/), [backups](/instances/how-to/create-a-backup/) and more. When you are done using your GPU Instance, you can easily [delete it](/instances/how-to/delete-instance/) from the Scaleway console.
+
+## How to create a GPU Instance
+
+1. Navigate to **Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers).
+2. Click **+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers).
+3. Follow these steps to configure your GPU Instance:
+ - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed.
+ - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information.
+ - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled Nvidia drivers and an Nvidia Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers.
+ - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements.
+
+ * The recommended minimum volume size for GPU OS images is 125 GB.
+ * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/)
+
+ - **Network configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance.
+ - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently.
+ - **Advanced options**: Configure `cloud-init` settings if required, or leave them at default values.
+ - **SSH keys**: Verify the SSH keys that will grant you access to your Instance.
+ - **Estimated cost**: Review the estimated cost of your GPU Instance based on the selected specifications.
+4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use.
+
+## How to connect to your GPU Instance
+
+See our documentation on [how to connect to your Instance via SSH](/instances/how-to/connect-to-instance/).
+
+## How to launch a Docker container
+
+To access a preinstalled working environment with all your favorite Python packages, you need to launch a Docker container.
+
+
+ If you created your GPU Instance with one of the legacy Ubuntu Bionic ML OS images, once you connect to your Instance you are already in a preinstalled ready-to-use Python environment, managed with conda. You do not need to follow the steps for launching a Docker container.
+
+
+1. Choose one of our [Docker AI images](/gpu/reference-content/docker-images/) (eg Tensorflox, Pytorch, Jax) based on your needs.
+2. Run the following command to launch the Docker container. In the following example, we launch a container based on the **Tensorflow** image:
+ ```sh
+ docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/tensorflow:latest /bin/bash
+ ```
+
+## How to use the preinstalled environment
+
+When you run your Docker container as shown above, the container launches and you are taken to its `ai` directory, where the Pipenv virtual environment is already activated.
+
+
+ Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/gpu/how-to/use-pipenv/).
+
+
+### Launching an application in your local browser
+
+Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](https://www.tensorflow.org/tensorboard) and [Code Server](https://code-server.dev/), require a browser to run. You can launch these from the `ai` virtual environment of your Docker container, and view them in the browser of your local machine. This is possible thanks to the addition of port mapping arguments when launching a container with the `docker run` command. In our example, we added the port mapping arguments `-p 8888:8888 -p 6006:6006` when we launched our container, mapping `8888:8888` for Jupyter Lab and `6006:6006` for Tensorboard.
+
+
+ Code Server runs in Jupyter Lab via Jupyter Hub and does not need port mapping in this case. You can add other port mapping arguments for other applications as you wish.
+
+
+1. Launch an application. Here, we launch Jupyter Lab:
+
+ `jupyter-lab`
+
+ Within the output, you should see something similar to the following:
+
+ ```
+ [I 2022-04-06 11:38:40.554 ServerApp] Serving notebooks from local directory: /home/jovyan/ai
+ [I 2022-04-06 11:38:40.554 ServerApp] Jupyter Server 1.15.6 is running at:
+ [I 2022-04-06 11:38:40.554 ServerApp] http://7d783f7cf615:8888/lab?token=e0c21db2665ac58c3cf124abf43927a9d27a811449cb356b
+ [I 2022-04-06 11:38:40.555 ServerApp] or http://127.0.0.1:8888/lab?token=e0c21db2665ac58c3cf124abf43927a9d27a811449cb356b
+ [I 2022-04-06 11:38:40.555 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
+ ```
+
+
+ Jupyter Lab is launched automatically when you run any Scaleway container image. You will see a message upon start up telling how to access the notebook in your browser. To override Jupyter Lab being launched automatically in this way, add `/bin/bash` to the end of your `docker run` command, e.g. `docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/pytorch:latest /bin/bash`. This preempts the launch of Jupyter Lab at container startup and replaces it with the specified command. In this case, a bash shell.
+
+2. On your local computer, open a browser window and enter the following URL. Replace `` with the IP address of your Scaleway GPU Instance, and `` with the token shown displayed in the last lines of terminal output after the `jupyter-lab` command
+ ```
+ :8888/lab?token=
+ ```
+
+
+ You can find the IP address of your Instance in the Scaleway console. In the side menu, click **Instances** to see a list of your Instances. The IP address of each of them is shown in the list that displays.
+
+
+ Jupyter Lab now displays in your browser. You can use the Notebook, Console, or other features as required:
+
+
+
+ You can display the GPU Dashboard in Jupyter Lab to view information about CPU and GPU resource usage. This is accessed via the **System Dashboards** icon on the left side menu (third icon from the top).
+3. Use CTRL+C in the terminal window of your GPU Instance / Docker container to close down the Jupyter server when you have finished.
+
+## Exiting the preinstalled environment and the Docker container
+
+When you are in the activated Pipenv virtual environment, your command line prompt will normally be prefixed by the name of the environment. Here, for example, from `(ai) jovyan@d73f1fa6bf4d:~/ai` we see that we are in the activated `ai` environment, and from `jovyan@d73f1fa6bf4d:~/ai` that we are in the `~/ai` directory of our container:
+
+1. Type `exit` the following command to leave the preinstalled `ai` environment.
+
+ You are now outside the preinstalled virtual environment.
+2. Type `exit` again to exit the Docker container.
+
+ Your prompt should now look similar to the following. You are still connected to your GPU Instance, but you have left the Docker container:
+
+ ```
+ root@scw-name-of-instance:~#
+ ```
+3. Type `exit` once more to disconnect from your GPU Instance.
\ No newline at end of file
diff --git a/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.pdf b/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.pdf
new file mode 100644
index 0000000000..0a25b84ee2
Binary files /dev/null and b/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.pdf differ
diff --git a/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.webp b/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.webp
new file mode 100644
index 0000000000..cc03d669b6
Binary files /dev/null and b/pages/gpu/reference-content/assets/scaleway-gpu-comparisation.webp differ
diff --git a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx
new file mode 100644
index 0000000000..dc317df561
--- /dev/null
+++ b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx
@@ -0,0 +1,126 @@
+---
+meta:
+ title: Choosing the right GPU Instance type
+ description: This page provides information about how to choose a Scaleway GPU Instance type
+content:
+ h1: Choosing the right GPU Instance type
+ paragraph: This section provides information about how to choose a Scaleway GPU Instance type
+tags: NVIDIA GPU cloud instance
+dates:
+ validation: 2024-10-14
+ posted: 2022-08-31
+categories:
+ - compute
+---
+
+A GPU Instance refers to a virtual computing environment provided by Scaleway that offers access to powerful Graphics Processing Units (GPUs) over the internet.
+GPUs are specialized hardware originally designed for rendering graphics in video games and other 3D applications.
+However, their massively parallel architecture makes them ideal for various high-performance computing tasks, such as deep learning, massive machine learning, data processing, scientific simulations, and more.
+
+Scaleway GPU Instances' availability has revolutionized how researchers, developers, and organizations train complex machine-learning models faster and more efficiently.
+It empowers European AI startups, giving them the tools (without the need for a huge CAPEX investment) to create products that revolutionize how we work and live.
+
+## How to choose the right GPU Instance type
+
+Scaleway provides a range of GPU Instance offers, from [GPU RENDER Instances](https://www.scaleway.com/en/gpu-render-instances/) and [H100 PCIe Instances](https://www.scaleway.com/en/h100-pcie-try-it-now/) to [custom build clusters](https://www.scaleway.com/en/ai-supercomputers/). There are several factors to consider when choosing the right GPU Instance type to ensure that it meets your performance, budget, and scalability requirements.
+Below, you will find a guide to help you make an informed decision:
+
+* **Workload requirements:** Identify the nature of your workload. Are you running machine learning, deep learning, high-performance computing (HPC), data analytics, or graphics-intensive applications? Different Instance types are optimized for different types of workloads. For example, the H100 is not designed for graphics rendering. However, other models are. As [stated by Tim Dettmers](https://timdettmers.com/2023/01/30/which-gpu-for-deep-learning/), “Tensor Cores are most important, followed by the memory bandwidth of a GPU, the cache hierarchy, and only then FLOPS of a GPU.”. For more information, refer to the [NVIDIA GPU portfolio](https://docs.nvidia.com/data-center-gpu/line-card.pdf).
+* **Performance requirements:** Evaluate the performance specifications you need, such as the number of GPUs, GPU memory, processing power, and network bandwidth. You need a lot of memory and fast storage for demanding tasks like training larger Deep Learning models.
+* **GPU type:** Scaleway offers different GPU types, such as various NVIDIA GPUs. Each GPU has varying levels of performance, memory, and capabilities. Choose a GPU that aligns with your specific workload requirements.
+* **GPU memory:** GPU memory bandwidth is an important criterion influencing overall performance. Then, larger GPU memory (VRAM) is crucial for memory-intensive tasks like training larger deep learning models, especially when using larger batch sizes. Modern GPUs offer specialized data formats designed to optimize deep learning performance. These formats, including Bfloat16, [FP8](https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html), int8 and int4, enable the storage of more data in memory and can enhance performance (for example, moving from FP16 to FP8 can double the number of TFLOPS). To make an informed decision, it is thus crucial to select the appropriate architecture. Options range from Pascal and Ampere to Ada Lovelace and Hopper. Ensuring that the GPU possesses sufficient memory capacity to accommodate your specific workload is essential, preventing any potential memory-related bottlenecks. Equally important, is matching the GPU's memory type to the nature of your workload.
+* **CPU and RAM:** A powerful CPU can be beneficial for tasks that involve preprocessing or post-processing. Sufficient system memory is also crucial to prevent memory-related bottlenecks or to cache your data in RAM.
+* **GPU driver and software compatibility:** Ensure that the GPU Instance type you choose supports the GPU drivers and software frameworks you need for your workload. This includes CUDA libraries, machine learning frameworks (TensorFlow, PyTorch, etc.), and other specific software tools. For all [Scaleway GPU OS images](/gpu/reference-content/docker-images/), we offer a driver version that enables the use of all GPUs, from the oldest to the latest models. As is the NGC CLI, `nvidia-docker` is preinstalled, enabling containers to be used with CUDA, cuDNN, and the main deep learning frameworks.
+* **Scaling:** Consider the scalability requirements of your workload. The most efficient way to scale up your workload is by using:
+ * Bigger GPU
+ * Up to 2 PCIe GPU with [H100 Instances](https://www.scaleway.com/en/h100-pcie-try-it-now/) or 8 PCIe GPU with [L4](https://www.scaleway.com/en/l4-gpu-instance/) or [L4OS](https://www.scaleway.com/en/contact-l40s/) Instances.
+ * An HGX-based server setup with 8x NVlink GPUs
+ * A [supercomputer architecture](https://www.scaleway.com/en/ai-supercomputers/) for a larger setup for workload-intensive tasks
+ * Another way to scale your workload is to use [Kubernetes and MIG](/gpu/how-to/use-nvidia-mig-technology/): You can divide a single H100 GPU into as many as 7 MIG partitions. This means that instead of employing seven P100 GPUs to set up seven K8S pods, you could opt for a single H100 GPU with MIG to effectively deploy all seven K8S pods.
+* **Online resources:** Check for online resources, forums, and community discussions related to the specific GPU type you are considering. This can provide insights into common issues, best practices, and optimizations.
+
+Remember that there is no one-size-fits-all answer, and the right GPU Instance type will depend on your workload’s unique requirements and budget. It is important that you regularly reassess your choice as your workload evolves. Depending on which type best fits your evolving tasks, you can easily migrate from one GPU Instance type to another.
+
+## GPU Instances and AI Supercomputer comparison table
+
+### Scaleway GPU Instances types overview
+
+| | **[RENDER-S](https://www.scaleway.com/en/gpu-render-instances/)** | **[H100-1-80G](https://www.scaleway.com/en/h100-pcie-try-it-now/)** | **[H100-2-80G](https://www.scaleway.com/en/h100-pcie-try-it-now/)** |
+|---------------------------------------------------------------------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| GPU Type | 1x [P100](https://www.nvidia.com/en-us/data-center/tesla-p100/) PCIe3 | 1x [H100](https://resources.nvidia.com/en-us-tensor-core/nvidia-tensor-core-gpu-datasheet) PCIe5 | 2x [H100](https://resources.nvidia.com/en-us-tensor-core/nvidia-tensor-core-gpu-datasheet) PCIe5 |
+| NVIDIA architecture | Pascal 2016 | Hopper 2022 | Hopper 2022 |
+| Tensor Cores | N/A | Yes | Yes |
+| Performance (training in FP16 Tensor Cores) | (No Tensor Cores : 9,3 TFLOPS FP32) | 1513 TFLOPS | 2x 1513 TFLOPS |
+| VRAM | 16 GB CoWoS HBM2 (Memory bandwidth: 732 GB/s) | 80 GB HBM2E (Memory bandwidth: 2TB/s) | 2x80 GB HBM2E (Memory bandwidth: 2TB/s) |
+| CPU Type | Intel Xeon Gold 6148 (2.4 GHz) | AMD EPYC™ 9334 (2.7GHz) | AMD EPYC™ 9334 (2.7GHz) |
+| vCPUs | 10 | 24 | 48 |
+| RAM | 42 GB DDR3 | 240 GB DDR5 | 480 GB DDR5 |
+| Storage | Block/Local | Block | Block |
+| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | No | Yes (3 TB NVMe) | Yes (6 TB NVMe) |
+| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | Yes | Yes |
+| Bandwidth | 1 Gbps | 10 Gbps | 20 Gbps |
+| Better used for | Image / Video encoding (4K) | 7B LLM Fine-Tuning / Inference | 70B LLM Fine-Tuning / Inference |
+| What they are not made for | Large models (especially LLM) | Graphic or video encoding use cases | Graphic or video encoding use cases |
+
+| | **[L4-1-24G](https://www.scaleway.com/en/l4-gpu-instance/)** | **[L4-2-24G](https://www.scaleway.com/en/l4-gpu-instance/)** | **[L4-4-24G](https://www.scaleway.com/en/l4-gpu-instance/)** | **[L4-8-24G](https://www.scaleway.com/en/l4-gpu-instance/)** |
+|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
+| GPU Type | 1x [L4](https://www.nvidia.com/en-us/data-center/l4/) PCIe4 | 2x [L4](https://www.nvidia.com/en-us/data-center/l4/) PCIe4 | 4x [L4](https://www.nvidia.com/en-us/data-center/l4/)PCIe4 | 8x [L4](https://www.nvidia.com/en-us/data-center/l4/) PCIe4 |
+| NVIDIA architecture | Lovelace 2022 | Lovelace 2022 | Lovelace 2022 | Lovelace 2022 |
+| Tensor Cores | Yes | Yes | Yes | Yes |
+| Performance (training in FP16 Tensor Cores) | 242 TFLOPS | 2x 242 TFLOPS | 4x 242 TFLOPS | 8x 242 TFLOPS |
+| VRAM | 24 GB RAM GDDR6 (Memory bandwidth: 300 GB/s) | 2x 24 GB RAM GDDR6 (Memory bandwidth: 300 GB/s) | 4x 24 GB RAM GDDR6 (Memory bandwidth: 300 GB/s) | 8x 24 GB RAM GDDR6 (Memory bandwidth: 300 GB/s) |
+| CPU Type | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz |
+| vCPUs | 8 | 16 | 32 | 64 |
+| RAM | 48 GB DDR4 | 96 GB DDR4 | 192 GB DDR4 | 384 GB DDR4 |
+| Storage | Block | Block | Block | Block |
+| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | No | No | No | No |
+| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No |
+| Bandwidth | 2.5 Gbps | 5 Gbps | 10 Gbps | 20 Gbps |
+| Better used for | Image Enconding (8K) | Video Enconding (8K) | 7B LLM Inference | 70B LLM Inference |
+| What they are not made for | Training of LLM | Training of LLM | Training of LLM | Training of LLM |
+
+| | **[L40S-1-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-2-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-4-48G](https://www.scaleway.com/en/contact-l40s/)** | **[L40S-8-48G](https://www.scaleway.com/en/contact-l40s/)** |
+|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GPU Type | 1x [L40S 48GB PCIe](https://www.nvidia.com/en-us/data-center/l40s/) | 2x [L40S 48GB PCIe](https://www.nvidia.com/en-us/data-center/l40s/) | 4x [L40S 48GB PCIe](https://www.nvidia.com/en-us/data-center/l40s/) | 8x [L40S 48GB PCIe](https://www.nvidia.com/en-us/data-center/l40s/) |
+| NVIDIA architecture | Lovelace 2022 | Lovelace 2022 | Lovelace 2022 | Lovelace 2022 |
+| Tensor Cores | Yes | Yes | Yes | Yes |
+| Performance (training in FP16 Tensor Cores) | 362 TFLOPS | 724 TFLOPS | 1448 TFLOPS | 2896 TFLOPS |
+| VRAM | 48 GB GDDR6 (Memory bandwidth: 864 GB/s) | 2x 48 GB = 96 GB GDDR6 (Memory bandwidth: 864 GB/s) | 4x 48 GB = 192 GB GDDR6 (Memory bandwidth: 864 GB/s) | 8x 48 GB = 384 GB GDDR6 (Memory bandwidth: 864 GB/s) |
+| CPU Type | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz) | AMD EPYC™ 7413 (2.65GHz) |
+| vCPUs | 8 | 16 | 32 | 64 |
+| RAM | 96 GB DDR4 | 192 GB DDR4 | 384 GB DDR4 | 768 GB DDR4 |
+| Storage | Block | Block | Block | Block |
+| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | Yes (~1,6 TB NVMe) | Yes (~3,2 TB NVMe) | Yes (~6,4 TB NVMe) | Yes (~12,8 TB NVMe) |
+| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No |
+| Bandwidth | 2,5 Gbps | 5 Gbps | 10 Gbps | 20 Gbps |
+| Use cases | GenAI (Image/Video) | GenAI (Image/Video) | 7B Text-to-image model fine-tuning / Inference | 70B text-to-image model fine-tuning / Inference |
+| What they are not made for | | | | |
+
+### Scaleway AI Supercomputer
+| | **[Custom build clusters](https://www.scaleway.com/en/ai-supercomputers/)** (2DGX H100, 16 H100 GPUs) | **[Custom build clusters](https://www.scaleway.com/en/ai-supercomputers/)** (127 DGX H100, 1016 H100 GPUs) |
+|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
+| GPU Type | 16x [H100](https://resources.nvidia.com/en-us-tensor-core/nvidia-tensor-core-gpu-datasheet) (SXM5) | 1,016x [H100](https://resources.nvidia.com/en-us-tensor-core/nvidia-tensor-core-gpu-datasheet) (SXM5) |
+| NVIDIA architecture | Hopper 2022 | Hopper 2022 |
+| Tensor Cores | Yes | Yes |
+| Performance in PFLOPs FP8 Tensor Core | Up to 63.2 PFLOPS | Up to 4,021.3 PFLOPS |
+| VRAM | 1280 GB (total cluster) | 81,280GB (total cluster) |
+| CPU Type | Dual Intel® Xeon® Platinum 8480C Processors (3.8 GHz) | Dual Intel® Xeon® Platinum 8480C Processors (3.8 GHz) |
+| Total CPU cores | 224 cores (total cluster) | 14,224 cores (total cluster) |
+| RAM | 4 TB (total cluster) | 254 TB (total cluster) |
+| Storage | 64TB of a3i DDN low latency storage | 1.8 PB of a3i DDN low latency storage |
+| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | Yes | Yes |
+| Inter-GPU bandwidth | Infiniband 400 Gb/s | Infiniband 400 Gb/s |
+
+### NVIDIA GH200 Superchip
+
+| | **[GH200 Grace Hopper™](https://www.scaleway.com/en/contact-gh200/)** |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GPU Type | NVIDIA [GH200 Grace Hopper™ Superchip](https://www.nvidia.com/en-us/data-center/grace-hopper-superchip/) |
+| NVIDIA architecture | GH200 Grace Hopper™ Architecture |
+| Performance | 990 TFLops (in FP166 Tensor Core) |
+| Specifications | - GH200 SuperChip with 72 ARM Neoverse V2 cores
- 480 GB of LPDDR5X DRAM
- 96GB of HBM3 GPU memory
(Memory is fully merged for up to 576GB of global usable memory) |
+| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | Yes |
+| Inter-GPU bandwidth (for clusters up to 256 GH200) | NVlink Switch System 900 GB/s |
+| Format & Features | Single chip up to GH200 clusters. (For larger setup needs, [contact us](https://www.scaleway.com/en/contact-ai-supercomputers/)) |
+| Use cases | - Extra large LLM and DL model inference
- HPC |
+| What they are not made for | - Graphism
- (Training) |
\ No newline at end of file
diff --git a/pages/gpu/reference-content/docker-images.mdx b/pages/gpu/reference-content/docker-images.mdx
new file mode 100644
index 0000000000..5164ae3fe4
--- /dev/null
+++ b/pages/gpu/reference-content/docker-images.mdx
@@ -0,0 +1,91 @@
+---
+meta:
+ title: Scaleway Docker AI images
+ description: Discover detailed information about Scaleway's Docker images for AI development.
+content:
+ h1: Docker AI images
+ paragraph: Discover detailed information about Scaleway's Docker images for AI development.
+tags: docker docker-image tensorflow pytorch jax rapids
+dates:
+ validation: 2025-01-20
+ posted: 2022-03-25
+categories:
+ - compute
+---
+
+Scaleway offers a range of ready-to-use AI Docker images. These Docker images can be used with all GPU Instance OS images.
+
+You can pull the images from our Container Registry as follows:
+
+```sh
+docker pull rg.fr-par.scw.cloud/scw-ai/
+```
+
+Our tag names follow the pattern `:YYMM-py3`, where `YY` and `MM` refer to the year and month the image was built. One exception to this is the tag used for the Tensorflow image, which is `:YYMM-tf2-py3`.
+
+The latest images are also tagged with the `:latest` tag.
+
+Initial tags will start with 2204-py3 (April 2022). Check out the [Scaleway Changelog](/changelog/) to be informed of Docker AI images updates.
+
+All our images are based on CUDA 12.2 and cuDNN8.
+
+
+ When using the “Ubuntu Jammy GPU OS 12” image with your Instance, you can omit the *NVIDIA runtime* option.
+
+
+The following commands show how to launch a container based on each of our various Docker images:
+
+## Tensorflow
+
+```sh
+docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/tensorflow:latest /bin/bash
+```
+
+The main libraries included in the Tensorflow image are Tensorflow 2, Tensorboard, Autokeras, Numpy, Scikit-Learn, Scipy, Pandas, Matplotlib, Plotly, Bokeh, Seaborn, CatBoost, XGBoost, Pillow, ONNX, Spacy, Nvidia Dali, Optuna, HuggingFace Transformers and HuggingFace-Hub, Weights and Biases, JupyterLab, Code Server and JupyterLab Nvidia Dashboard.
+
+## Pytorch
+
+```sh
+docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/pytorch:latest /bin/bash
+```
+
+The main libraries included in the Pytorch image are Pytorch, Torch Audio, Torch Vision, Fast AI, Pytorch Lightning, Tensorboard, Numpy, Scikit-Learn, Scipy, Pandas, Matplotlib, Plotly, Bokeh, Seaborn, CatBoost, XGBoost, Pillow, Plotly, ONNX, Spacy, Nvidia Dali, Optuna, HuggingFace Transformers and HuggingFace-Hub, Weights and Biases, JupyterLab, Code Server and JupyterLab Nvidia Dashboard.
+
+## Jax
+
+```sh
+docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/jax:latest /bin/bash
+```
+
+The main libraries included in the Jax image are Jax, Numpy, Scikit-Learn, Scipy, Pandas, Matplotlib, Plotly, Bokeh, Seaborn, CatBoost, XGBoost, Pillow, ONNX, JupyterLab, Code Server and JupyterLab Nvidia Dashboard.
+
+## RAPIDS
+
+
+ This image is built on top of the official RAPIDS Docker image, which relies on Anaconda.
+
+
+```sh
+docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/rapids:latest /bin/bash
+
+```
+
+The main libraries included in the RAPIDS image are cuDF, cuML, cuGraph, cuxfilter, cuspatial, cusignal, Dask, Numpy, Scikit-Learn, Scipy, Pandas, Matplotlib, Plotly, Bokeh, Seaborn, CatBoost, XGBoost, Pillow, ONNX, JupyterLab and JupyterLab Nvidia Dashboard.
+
+
+
+ As the official RAPIDS Docker image uses Anaconda, make sure the "rapids" conda environment is activated to use Rapids libraries:
+
+ ```
+ jovyan@561f14e37a44:~/ai$ conda activate rapids
+ (rapids) jovyan@561f14e37a44:~/ai$ jupyter lab
+ ```
+
+
+## "All" (Experimental)
+
+If there are no dependency issues when building the image, the **all** image will try to include all the above-listed libraries into a single Docker image (except RAPIDS).
+
+```sh
+docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/all:latest /bin/bash
+```
\ No newline at end of file
diff --git a/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx b/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx
new file mode 100644
index 0000000000..f1ca1d8402
--- /dev/null
+++ b/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx
@@ -0,0 +1,49 @@
+---
+meta:
+ title: Scaleway GPU Instances internet and Block Storage bandwidth overview
+ description: Find detailed information about the internet and Block Storage bandwidth for each GPU Instance type at Scaleway.
+content:
+ h1: Scaleway GPU Instances internet and Block Storage bandwidth overview
+ paragraph: Find detailed information about the internet and Block Storage bandwidth for each GPU Instance type at Scaleway.
+tags: instance
+dates:
+ validation: 2025-01-07
+ posted: 2025-01-07
+categories:
+ - compute
+---
+
+
+Scaleway GPU Instances are designed to deliver **high-performance computing** for AI/ML workloads, rendering, scientific simulations, and visualization tasks.
+This guide provides a detailed overview of their **internet and Block Storage bandwidth capabilities** to help you choose the right instance for your GPU-powered workloads.
+
+### Why bandwidth matters for GPU Instances
+
+GPU workloads often involve processing large datasets, requiring high-bandwidth networking and storage access.
+- **Internet bandwidth**: Determines how fast your Instance can send or receive data from external sources, enabling smooth data transfers for model training or streaming.
+- **Block bandwidth**: Impacts data access speeds for datasets stored in Block Storage, optimizing performance for AI pipelines, rendering workflows, and other data-intensive applications.
+
+
+ Bandwidth specifications listed here are for informational purposes only. To validate the exact bandwidth capacity of your GPU Instance, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve GPU Instance specifications.
+
+
+
+ To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
+
+
+## GPU Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-------------------|-------------------------|---------------------|
+| H100-1-80G | 10 Gbit/s | 2 GiB/s |
+| H100-2-80G | 20 Gbit/s | 4 GiB/s |
+| L40S-1-48G | 2.5 Gbit/s | 1 GiB/s |
+| L40S-2-48G | 5 Gbit/s | 1.5 GiB/s |
+| L40S-4-48G | 10 Gbit/s | 2.5 GiB/s |
+| L40S-8-48G | 20 Gbit/s | 5 GiB/s |
+| L4-1-24G | 2.5 Gbit/s | 1 GiB/s |
+| L4-2-24G | 5 Gbit/s | 1.5 GiB/s |
+| L4-4-24G | 10 Gbit/s | 2.5 GiB/s |
+| L4-8-24G | 20 Gbit/s | 5 GiB/s |
+| GPU-3070-S | 2.5 Gbit/s | 1 GiB/s |
+| RENDER-S | 2 Gbit/s | 1 GiB/s |
diff --git a/pages/gpu/reference-content/index.mdx b/pages/gpu/reference-content/index.mdx
new file mode 100644
index 0000000000..477e60003a
--- /dev/null
+++ b/pages/gpu/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: GPU Instances - Additional content
+ description: GPU Instances additional content
+content:
+ h1: GPU Instances - Additional content
+ paragraph: GPU Instances additional content
+---
\ No newline at end of file
diff --git a/pages/gpu/reference-content/kubernetes-gpu-time-slicing.mdx b/pages/gpu/reference-content/kubernetes-gpu-time-slicing.mdx
new file mode 100644
index 0000000000..cfce68b262
--- /dev/null
+++ b/pages/gpu/reference-content/kubernetes-gpu-time-slicing.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: NVIDIA GPU time-slicing with Kubernetes
+ description: Learn how NVIDIA GPU time-slicing with Kubernetes enables efficient GPU resource sharing among containers or pods. Explore operational procedures, management, and comparisons with MIG technology.
+content:
+ h1: NVIDIA GPU time-slicing with Kubernetes
+ paragraph: Learn how NVIDIA GPU time-slicing with Kubernetes enables efficient GPU resource sharing among containers or pods. Explore operational procedures, management, and comparisons with MIG technology.
+tags: gpu nvidia
+dates:
+ validation: 2024-11-18
+ posted: 2023-03-25
+categories:
+ - compute
+---
+
+NVIDIA GPUs are powerful hardware commonly used for model training, deep learning, scientific simulations, and data processing tasks. On the other hand, Kubernetes (K8s) is a container orchestration platform that helps manage and deploy containerized applications.
+
+Time-slicing in the context of NVIDIA GPUs and Kubernetes refers to sharing a physical GPU among multiple containers or pods in a Kubernetes cluster.
+
+The technology involves partitioning the GPU's processing time into smaller intervals and allocating those intervals to different containers or pods. This technique allows multiple workloads to run on the same physical GPU, effectively sharing its resources while providing isolation between the different workloads.
+
+## Operational procedures of GPU time-slicing in Kubernetes
+
+Time-slicing NVIDIA GPUs with Kubernetes involves:
+* Dynamically allocating and sharing GPU resources among multiple containers or pods in a cluster.
+* Allowing each pod or container to use the GPU for a specific time interval before switching to another.
+* Efficiently using the available GPU capacity.
+
+This allows multiple workloads to use the GPU by taking turns in rapid succession.
+
+* **GPU sharing:** Time-slicing involves sharing a single GPU among containers or pods by allocating small time intervals. Sharing is achieved by rapidly switching between different containers or pods, allowing them to use the GPU for a short duration before moving on to the next workload.
+* **GPU context switching:** Refers to saving one workload's state, loading another's, and resuming processing. Modern GPUs are designed to handle context switching efficiently.
+
+## Management of GPU time-slicing within the Kubernetes cluster
+
+Several elements within the Kubernetes cluster oversee the time-slicing of GPUs:
+* **GPU scheduling:** Kubernetes employs a scheduler that determines which containers or pods get access to GPUs and when. This scheduling is based on resource requests, limits, and the available GPUs on the nodes in the cluster.
+* **GPU device plugin:** Kubernetes uses the NVIDIA GPU device plugin to expose the GPUs available on each node to the cluster's scheduler. This plugin helps the scheduler make informed decisions about GPU allocation.
+* **Container GPU requests and limits:** When defining a container or pod in Kubernetes, you can specify GPU requests and limits. The requests represent the minimum required GPU resources, while the limits define the maximum allowed GPU usage. These values guide the Kubernetes scheduler in making placement decisions.
+
+ ## Time-slicing compared to MIG
+
+The most recent versions of NVIDIA GPUs introduce [Multi-instance GPU (MIG) mode](/gpu/how-to/use-nvidia-mig-technology/). Fully integrated into Kubernetes in 2020, MIG allows a single GPU to be partitioned into smaller, predefined instances, essentially resembling miniaturized GPUs.
+These instances provide memory and fault isolation directly at the hardware level. Instead of using the entire native GPU, you can run workloads on one of these predefined instances, enabling shared GPU access.
+
+Kubernetes GPU time-slicing divides the GPU resources at the container level within a Kubernetes cluster. Multiple containers (pods) share a single GPU, whereas MIG divides the GPU resources at the hardware level. Each MIG instance behaves like a separate GPU.
+While time-slicing facilitates shared GPU access across a broader user spectrum, it comes with a trade-off. It sacrifices the memory and fault isolation advantages inherent to MIG. Additionally, it presents a solution to enable shared GPU access on earlier GPU generations lacking MIG support.
+Combining MIG and time-slicing is feasible to expand the scope of shared access to MIG instances.
+
+For more information and examples about NVIDIA GPUs time-slicing using Kubernetes, refer to the [official documentation](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/23.6.0/gpu-sharing.html).
+
+
+ Using time-slicing for GPUs with Kubernetes could bring overhead due to context-switching, potentially affecting GPU-intensive operations' performance.
+ This means that this strategy suits best when strict isolation is not necessary and workloads do not strongly depend on extended GPU usage.
+
\ No newline at end of file
diff --git a/pages/gpu/reference-content/understanding-nvidia-fp8.mdx b/pages/gpu/reference-content/understanding-nvidia-fp8.mdx
new file mode 100644
index 0000000000..a1f209822d
--- /dev/null
+++ b/pages/gpu/reference-content/understanding-nvidia-fp8.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: Understanding the NVIDIA FP8 format
+ description: This section provides information about NVIDIA FP8 (8-bit floating point) format
+content:
+ h1: Understanding the NVIDIA FP8 format
+ paragraph: This section provides information about NVIDIA FP8 (8-bit floating point) format
+tags: NVIDIA FP8 GPU cloud
+dates:
+ validation: 2024-10-14
+ posted: 2023-10-23
+categories:
+ - compute
+---
+
+Scaleway offers GPU Instances featuring [L4, L40S and H100 GPUs](https://www.scaleway.com/en/h100-pcie-try-it-now/) that support FP8 (8-bit floating point), a revolutionary datatype introduced by NVIDIA. It enables higher throughput of matrix multipliers and convolutions.
+
+FP8 is an 8-bit floating point standard which was jointly developed by NVIDIA, ARM, and Intel to speed up AI development by improving memory efficiency during AI training and inference processes.
+
+The ongoing industry evolution is evident in the shift from 32-bit to 16-bit, and currently, to 8-bit precision formats. This change is especially advantageous for transformer networks, crucial AI breakthroughs, as they perform better with the detailed precision provided by 8-bit floating point formats.
+
+This uniform standard ensures compatibility across diverse hardware and software environments, thus driving computing capabilities to unprecedented levels.
+
+FP8 sets forth two distinct eight-bit floating-point formats, E5M2 and E4M3, to facilitate interoperability between different hardware platforms. It aligns closely with the current IEEE 754 standards for floating-point computations, achieving an ideal harmony between hardware efficiency and software performance. This strategy seeks to leverage existing frameworks, speed up uptake, and boost developer efficiency.
+
+The `E5M2` format adapts the IEEE FP16 format, allocating five bits to the exponent and two bits to the mantissa. The `E4M3` format assigns four bits for the exponent and three bits for the mantissa with slight adjustments. These two eight-bit configurations are designed to optimize both training and inference phases, promising to cut down computational loads in comparison to their more precise counterparts.
+
+The FP8 standard preserves accuracy comparable to 16-bit formats across a wide range of applications, architectures, and networks.
+
+For more information about the FP8 standard, and instructions how to use it with H100 GPU Instances, refer to NVIDIA's [offical FP8 documentation](https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html) and the [code example repository](https://github.com/NVIDIA/TransformerEngine/tree/main/examples).
\ No newline at end of file
diff --git a/pages/gpu/reference-content/understanding-nvidia-nemo.mdx b/pages/gpu/reference-content/understanding-nvidia-nemo.mdx
new file mode 100644
index 0000000000..67083c5526
--- /dev/null
+++ b/pages/gpu/reference-content/understanding-nvidia-nemo.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: Understanding NVIDIA NeMo (Neural Modules)
+ description: This section provides information about NVIDIA NGC (NVIDIA GPU Cloud) on Scaleway
+content:
+ h1: Understanding NVIDIA NeMo (Neural Modules)
+ paragraph: This section provides information about NVIDIA NGC (NVIDIA GPU Cloud) on Scaleway
+tags: NVIDIA NGC NVIDIA GPU cloud
+dates:
+ validation: 2024-10-07
+ posted: 2023-09-24
+categories:
+ - compute
+---
+
+
+NVIDIA NeMo (Neural Modules) is a conversational AI toolkit built by NVIDIA. The toolkit is designed to simplify the process of creating conversational AI models, including Automatic Speech Recognition (ASR), Natural Language Processing (NLP), and Text-to-Speech (TTS) models.
+
+NeMo is built on PyTorch, a popular deep learning framework, and offers a high-level, modular API for building complex conversational AI models using pre-designed "neural modules."
+
+## NeMo features and advantages
+
+* **Modular and reusable:** The modular architecture allows developers to build, share, and reuse components easily, which can speed up the development process.
+* **Flexible and scalable:** The tool supports multi-GPU and multi-node training, which enables the training of large models on large datasets.
+* **End-to-end workflow:** From data processing to model training, optimization, and deployment, NeMo supports the entire conversational AI development workflow.
+* **Diverse models:** NeMo includes a wide range of pre-trained models for various tasks like ASR, NLP, and TTS, which can be fine-tuned or used as they are.
+
+## NeMo components
+
+NeMo is built using the following components:
+
+* **NeMo core:**
+ - Offers foundational elements like the Neural Module Factory which helps in training and inferencing.
+
+* **NeMo collections:**
+ - It consists of different modules and models for ASR, NLP, and TTS.
+ - Provides pre-trained models and training scripts that users can leverage for various tasks.
+
+* **Neural Modules (NMs):**
+ - These are the building blocks of NeMo.
+ - They define trainable components such as encoders, decoders, and other neural network layers.
+ - NMs can be interconnected to construct full models.
+
+* **Application Scripts:**
+ - NeMo provides ready-to-use scripts that allow users to quickly train models on their datasets or fine-tune pre-trained models.
+
+## NeMo use cases
+
+NVIDIA NeMo can be used for various applications such as:
+ - Developing voice assistants.
+ - Creating transcription services.
+ - Building chat bots.
+ - Developing natural language understanding models for various applications.
+
+Developers, researchers, and companies interested in developing conversational AI models can benefit from NVIDIA NeMo to speed up the development process and create high-quality models. For more information, refer to the [official NVIDIA NeMo documentation](https://docs.nvidia.com/deeplearning/nemo/user-guide/docs/en/stable/index.html).
\ No newline at end of file
diff --git a/pages/gpu/reference-content/understanding-nvidia-ngc.mdx b/pages/gpu/reference-content/understanding-nvidia-ngc.mdx
new file mode 100644
index 0000000000..1060ce87f1
--- /dev/null
+++ b/pages/gpu/reference-content/understanding-nvidia-ngc.mdx
@@ -0,0 +1,36 @@
+---
+meta:
+ title: Understanding NVIDIA GPU Cloud (NGC)
+ description: This section provides information about NVIDIA NGC (NVIDIA GPU Cloud) on Scaleway
+content:
+ h1: Understanding NVIDIA GPU Cloud (NGC)
+ paragraph: This section provides information about NVIDIA NGC (NVIDIA GPU Cloud) on Scaleway
+tags: NVIDIA NGC NVIDIA GPU cloud
+dates:
+ validation: 2024-09-10
+ posted: 2023-08-31
+categories:
+ - compute
+---
+
+NVIDIA provides access to NVIDIA GPU Cloud (NGC) through providers including Scaleway. NGC is a cloud-based platform that offers a comprehensive set of GPU-optimized software and tools for various deep learning, machine learning, and AI (Artificial Intelligence) tasks. It is designed to simplify deploying, managing, and utilizing AI and data science frameworks on NVIDIA GPUs.
+
+Unleash the power of your applications' deployment with Scaleway and NGC, where seamless deployment is as effortless as following these three simple steps:
+1. Deploy your Scaleway GPU Instance from the [Scaleway console](https://console.scaleway.com/instance/servers/create?imageKey=7bdc1afb-231f-486a-9b85-1b0478bc0e4a&offerName=RENDER-S&zone=fr-par-2), the [CLI tools](https://github.com/scaleway/scaleway-cli), or the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/).1
+ 1 You need [GPU Instance quotas](/organizations-and-projects/additional-content/organization-quotas/#gpu-instances) to be able to deploy GPU Instances.
+2. Configure your Instance by pulling the required packages from NVIDIA NGC.
+3. Run your application.
+
+Your AI framework is ready to go.
+
+NGC provides a repository of pre-configured containers, models, and software stacks optimized for NVIDIA GPUs. These containers contain popular AI frameworks, libraries, and software applications, allowing data scientists, researchers, and developers to quickly access and deploy these resources without requiring extensive configuration or setup. In detail, NGC provides the following contents in the NGC catalog:
+
+* **Containers:** NGC provides a range of containerized environments that encapsulate AI and deep learning frameworks such as TensorFlow, PyTorch, MXNet, etc. These containers are optimized for NVIDIA GPUs and can easily be deployed on cloud platforms or on-premises hardware.
+* **Pre-trained models:** NGC offers a collection of pre-trained models that cover a wide range of AI tasks, including image and speech recognition, natural language processing, and more. These models can be used as a starting point for building custom solutions.
+* **Software Development Kits (SDKs):** NGC provides SDKs and libraries that enable developers to integrate GPU-accelerated AI capabilities into their applications and workflows.
+* **Frameworks and libraries:** NGC includes popular AI frameworks like TensorFlow, PyTorch, and others, as well as specialized libraries for tasks like computer vision and deep learning.
+* **Data Science tools:** NGC provides tools for data preprocessing, exploration, and analysis. This allows data scientists to work more efficiently with their data.
+
+NVIDIA closely collaborates with software developers to optimize leading AI and machine learning frameworks for peak performance on NVIDIA GPUs. This optimization significantly expedites both training and inference tasks. Software hosted on NGC undergoes scans against an aggregated set of common vulnerabilities and exposures (CVEs), crypto, and private keys.
+
+For more information on NGC, refer to the official [NVIDIA NGC documentation](https://docs.nvidia.com/ngc/index.html).
diff --git a/pages/gpu/reference-content/understanding-nvidia-tao.mdx b/pages/gpu/reference-content/understanding-nvidia-tao.mdx
new file mode 100644
index 0000000000..d44693e1cf
--- /dev/null
+++ b/pages/gpu/reference-content/understanding-nvidia-tao.mdx
@@ -0,0 +1,31 @@
+---
+meta:
+ title: Understanding the NVIDIA TAO (Train, Adapt, Optimize) toolkit
+ description: This section provides information about NVIDIA TAO
+content:
+ h1: Understanding the NVIDIA TAO (Train, Adapt, Optimize) toolkit
+ paragraph: This section provides information about NVIDIA TAO
+tags: NVIDIA TAO
+dates:
+ validation: 2024-09-30
+ posted: 2023-09-22
+categories:
+ - compute
+---
+
+The NVIDIA TAO Toolkit offers an accessible, open-source AI framework designed to accelerate the development of computer vision AI models, catering to individuals with varying skill levels, from novices to seasoned data scientists.
+
+Developers can harness the effectiveness of transfer learning to achieve top-tier accuracy and impressive production throughput in record time through adaptation and optimization.
+
+TAO (Train, Adapt, Optimize) is designed to work with NVIDIA GPUs and is part of NVIDIA's larger ecosystem for AI and deep learning.
+
+The key components and capabilities of NVIDIA TAO include:
+
+* **Transfer Learning Toolkit (TLT):** TLT is a core component of TAO that allows users to take pre-trained deep learning models (often from popular model repositories like NVIDIA NGC or the PyTorch and TensorFlow ecosystems) and fine-tune them on their specific tasks or datasets. This is particularly useful because training large deep learning models from scratch can be computationally expensive and time-consuming. TLT makes it easier to adapt existing models to new tasks.
+* **Model Optimization Tools:** TAO includes tools for optimizing and quantizing deep learning models for deployment on edge devices with limited computational resources. This helps reduce the model's size and ensuring it runs efficiently in real-world scenarios, which is crucial for applications like autonomous vehicles.
+* **Integration with NVIDIA Hardware:** TAO is optimized for use with NVIDIA GPUs and other hardware accelerators, allowing fast training and optimal inference performance.
+* **Pre-trained Models:** NVIDIA provides pre-trained models that can be used as a starting point for various computer vision tasks, such as object detection, segmentation, and classification.
+* **Data Augmentation and Data Processing:** TAO includes tools for data augmentation and preprocessing, which are essential for training robust deep learning models.
+* **Deployment Support:** TAO helps to deploy trained models on NVIDIA platforms, including Jetson edge devices, Drive AGX platforms for autonomous vehicles, and more.
+
+The latest release of the TAO toolkit is version 5, and it introduces groundbreaking features to improve your AI model development. For more information about TAO, refer to the official [NVIDIA TAO Getting Started documentation](https://developer.nvidia.com/tao-toolkit-get-started)
\ No newline at end of file
diff --git a/pages/gpu/troubleshooting/fix-driver-issues.mdx b/pages/gpu/troubleshooting/fix-driver-issues.mdx
new file mode 100644
index 0000000000..ff51b1c5d5
--- /dev/null
+++ b/pages/gpu/troubleshooting/fix-driver-issues.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: Fixing GPU issues after installing nvidia-driver packages
+ description: Resolve GPU issues on Scaleway GPU Instances after installing Nvidia drivers with our troubleshooting guide.
+content:
+ h1: Fixing GPU issues after installing nvidia-driver packages
+ paragraph: Resolve GPU issues on Scaleway GPU Instances after installing Nvidia drivers with our troubleshooting guide.
+tags: gpu issue error driver nvidia-driver sleep gpu-instance
+dates:
+ validation: 2025-01-02
+ posted: 2022-12-01
+categories:
+ - compute
+---
+
+All Scaleway [GPU Instances](/gpu/quickstart/) come with a Nvidia driver preinstalled. This means you do not have to install them by yourself.
+
+The drivers installed on each Instance are from the `nividia-headless-` packages. These are intended for use on Instances without a Windows Desktop or display server.
+
+
+ The manual installation of a `nvidia-driver` package forces the installation of the `xorg` display server and other Gnome packages. As there is no physical display connected to the GPU of your Instance, this may cause side effects such as your Instance entering into sleep mode after a while. The user will get disconnected as a result.
+
+
+If you have `nvidia-driver-*` packages installed on your GPU Instance, remove them from the Instance using the `apt purge` command and make sure to install and use `nvidia-headless-*` packages instead.
+
+
+ If you want to use `ffmpeg` in a Docker container on your GPU-Instance, make sure to install the `libnvidia-encode` library corresponding to the driver version installed on your Instance.
+ For example: `apt install -y libnvidia-encode-525` (with GPU OS12).
+ You also need to specify the driver capabilities to launch your containers (By default graphics and video are not enabled):
+ ```
+ docker run --rm --runtime=nvidia -e NVIDIA_DRIVER_CAPABILITIES=graphics,video
+ ```
+
\ No newline at end of file
diff --git a/pages/gpu/troubleshooting/index.mdx b/pages/gpu/troubleshooting/index.mdx
new file mode 100644
index 0000000000..ec6e33080d
--- /dev/null
+++ b/pages/gpu/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: GPU Instances - Troubleshooting
+ description: GPU Instances Troubleshooting
+content:
+ h1: GPU Instances - Troubleshooting
+ paragraph: GPU Instances Troubleshooting
+---
\ No newline at end of file
diff --git a/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx b/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx
new file mode 100644
index 0000000000..2547739f5c
--- /dev/null
+++ b/pages/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx
@@ -0,0 +1,74 @@
+---
+meta:
+ title: Installing NVIDIA drivers on Ubuntu 22.04
+ description: This section provides information on how to install NVIDIA drivers on Ubuntu 22.04
+content:
+ h1: Installing NVIDIA drivers on Ubuntu 22.04
+ paragraph: This section provides information on how to install NVIDIA Drivers on Ubuntu 22.04
+tags: gpu driver nvidia-driver unbuntu l4 l40s
+dates:
+ validation: 2024-09-30
+ posted: 2024-03-27
+categories:
+ - compute
+---
+
+In this guide, we will walk you through the process of installing NVIDIA drivers for L4/L40S GPU Instances on a customized Ubuntu 22.04 image, adapted from the default OS image.
+
+
+ **This guide is for advanced users.**
+ Scaleway does not provide official support for custom OS images. This documentation aims to offer guidance to expert users interested in creating their own GPU image setups. We encourage users to use our GPU OS 12 images, which are ready to use and maintained by Scaleway.
+
+
+
+ Before installation, it is important to identify the correct NVIDIA driver version for your system. You can check the recommended driver versions from the official [NVIDIA drivers website](https://www.nvidia.com/en-us/drivers/unix/).
+
+
+## Installing NVIDIA drivers
+
+1. Install the NVIDIA repository key. You can follow instructions from the [NVIDIA website](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#prepare-ubuntu) to install the latest version of the key.
+
+2. Update the command line defined in `/etc/default/grub` by adding the parameter `pci=realloc`. This parameter ensures proper GPU detection and allocation.
+
+3. Enable the `scw-set-numa-node` service. This service is installed from the [Scaleway ecosystem](https://launchpad.net/~scaleway/+archive/ubuntu/stable) package.
+
+4. Install the necessary NVIDIA drivers using the package manager (apt-get):
+ ```
+ sudo apt-get install nvidia-docker2 nvidia-headless- nvidia-utils-
+ ```
+ Replace `` with the specific version number of the NVIDIA drivers compatible with your GPU model.
+
+
+ We recommend using Nvidia NGC Docker containers, such as [CUDA](https://catalog.ngc.nvidia.com/orgs/nvidia/containers/cuda) or [PyTorch](https://catalog.ngc.nvidia.com/orgs/nvidia/containers/pytorch).
+ This eliminates the need to install CUDA and cuDNN separately. Only the NVIDIA driver and NVIDIA Docker are required. The NGC Docker images contain the correct versions of CUDA, cuDNN, etc.
+ This approach offers several benefits:
+ - Ability to choose your preferred framework and version.
+ - Ready-to-use setup (CUDA, cuDNN, Python, etc.).
+ - Building your custom Docker image on top of Nvidia images.
+ - Portable code (Local, Instance, K8S/Slurm clusters).
+ - Up-to-date with the latest Nvidia fixes and optimizations.
+
+
+5. After installation, confirm the drivers are working correctly by running:
+ ```
+ sudo nvidia-smi
+ ```
+ This command should display information about the installed NVIDIA GPU(s) and their status.
+
+
+ Depending on your specific requirements, you may need to perform additional configuration steps, such as setting environment variables or adjusting kernel parameters. Refer to the official NVIDIA documentation for guidance on these configurations.
+
+
+## Troubleshooting
+If you encounter errors or issues during the installation process, consider the following troubleshooting steps:
+- Check system logs (`dmesg`, `/var/log/syslog`) for any error messages related to NVIDIA drivers.
+- Ensure the correct driver version is compatible with your GPU model.
+- Verify that the NVIDIA repository is correctly added to your package manager's sources list.
+- Consult relevant documentation or forums for additional troubleshooting steps specific to your setup.
+
+## Additional links
+
+- [NVIDIA NGC Catalog](https://catalog.ngc.nvidia.com/)
+- [Frameworks Support Matrix - NVIDIA Docs](https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html)
+- [How to access the GPU using Docker](/gpu/how-to/use-gpu-with-docker/)
+- [NVIDIA Container Toolkit documentation](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/index.html)
\ No newline at end of file
diff --git a/pages/gpu/troubleshooting/updating-gpu-instance-with-cloud-init.mdx b/pages/gpu/troubleshooting/updating-gpu-instance-with-cloud-init.mdx
new file mode 100644
index 0000000000..1969a58a1a
--- /dev/null
+++ b/pages/gpu/troubleshooting/updating-gpu-instance-with-cloud-init.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: Fixing GPU issues after upgrading GPU Instances with cloud-init
+ description: This section provides information how to fix GPU issues after upgrading Scaleway GPU Instances with cloud-init
+content:
+ h1: Fixing GPU issues after upgrading GPU Instances with cloud-init
+ paragraph: This section provides information how to fix GPU issues after upgrading Scaleway GPU Instances with cloud-init
+tags: gpu issue error upgrade gpu-instance cloud-init
+dates:
+ validation: 2024-10-14
+ posted: 2022-09-19
+categories:
+ - compute
+---
+
+When running the `upgrade_package` command with `cloud-init` the Nvidia drivers may break causing the GPU to become unavailable. This problem persists even after a manual reboot of the Instance and the following error displays:
+
+```
+The GPU is not usable. The driver not loaded, with the following errors in the system journal
+
+[FAILED] Failed to start NVIDIA Persistence Daemon.
+```
+
+This error is caused by the way the `upgrade_package ` command [handles the upgrade](https://cloudinit.readthedocs.io/en/latest/topics/examples.html#additional-apt-configuration-and-repositories) of the packages installed on the system. It runs `apt-get dist-upgrade` instead of `apt upgrade`.
+
+To avoid this issue, use the following `cloud-init` script with your GPU Instances:
+
+```
+#cloud-config
+
+system_info:
+apt_get_upgrade_subcommand: "upgrade"
+
+# Upgrade the instance on first boot and reboot if needed
+package_upgrade: true
+package_reboot_if_required: true
+```
\ No newline at end of file
diff --git a/pages/identity-and-access-management/iam/api-cli/index.mdx b/pages/iam/api-cli/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/api-cli/index.mdx
rename to pages/iam/api-cli/index.mdx
diff --git a/pages/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx b/pages/iam/api-cli/using-api-key-object-storage.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx
rename to pages/iam/api-cli/using-api-key-object-storage.mdx
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-activate.webp b/pages/iam/assets/scaleway-iam-activate.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-activate.webp
rename to pages/iam/assets/scaleway-iam-activate.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-added-user.webp b/pages/iam/assets/scaleway-iam-added-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-added-user.webp
rename to pages/iam/assets/scaleway-iam-added-user.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-api-key.webp b/pages/iam/assets/scaleway-iam-api-key.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-api-key.webp
rename to pages/iam/assets/scaleway-iam-api-key.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-applications.webp b/pages/iam/assets/scaleway-iam-applications.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-applications.webp
rename to pages/iam/assets/scaleway-iam-applications.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-button.webp b/pages/iam/assets/scaleway-iam-button.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-button.webp
rename to pages/iam/assets/scaleway-iam-button.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-concepts.webp b/pages/iam/assets/scaleway-iam-concepts.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-concepts.webp
rename to pages/iam/assets/scaleway-iam-concepts.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-create-app.webp b/pages/iam/assets/scaleway-iam-create-app.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-create-app.webp
rename to pages/iam/assets/scaleway-iam-create-app.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-create-policy-1.webp b/pages/iam/assets/scaleway-iam-create-policy-1.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-create-policy-1.webp
rename to pages/iam/assets/scaleway-iam-create-policy-1.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-create-policy-2.webp b/pages/iam/assets/scaleway-iam-create-policy-2.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-create-policy-2.webp
rename to pages/iam/assets/scaleway-iam-create-policy-2.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-invite-user.webp b/pages/iam/assets/scaleway-iam-invite-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-invite-user.webp
rename to pages/iam/assets/scaleway-iam-invite-user.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-organization.webp b/pages/iam/assets/scaleway-iam-organization.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-organization.webp
rename to pages/iam/assets/scaleway-iam-organization.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-owners-guests.webp b/pages/iam/assets/scaleway-iam-owners-guests.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-owners-guests.webp
rename to pages/iam/assets/scaleway-iam-owners-guests.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-policies.webp b/pages/iam/assets/scaleway-iam-policies.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-policies.webp
rename to pages/iam/assets/scaleway-iam-policies.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-policy-example.webp b/pages/iam/assets/scaleway-iam-policy-example.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-policy-example.webp
rename to pages/iam/assets/scaleway-iam-policy-example.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-policy.webp b/pages/iam/assets/scaleway-iam-policy.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-policy.webp
rename to pages/iam/assets/scaleway-iam-policy.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-splash.webp b/pages/iam/assets/scaleway-iam-splash.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-splash.webp
rename to pages/iam/assets/scaleway-iam-splash.webp
diff --git a/pages/identity-and-access-management/iam/assets/scaleway-iam-users-dashboard.webp b/pages/iam/assets/scaleway-iam-users-dashboard.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/assets/scaleway-iam-users-dashboard.webp
rename to pages/iam/assets/scaleway-iam-users-dashboard.webp
diff --git a/pages/identity-and-access-management/iam/concepts.mdx b/pages/iam/concepts.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/concepts.mdx
rename to pages/iam/concepts.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx b/pages/iam/how-to/accept-invitation-to-orga.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx
rename to pages/iam/how-to/accept-invitation-to-orga.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-accept-orga-invite.webp b/pages/iam/how-to/assets/scaleway-accept-orga-invite.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-accept-orga-invite.webp
rename to pages/iam/how-to/assets/scaleway-accept-orga-invite.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-add-user-to-group.webp b/pages/iam/how-to/assets/scaleway-add-user-to-group.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-add-user-to-group.webp
rename to pages/iam/how-to/assets/scaleway-add-user-to-group.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-api-key.webp b/pages/iam/how-to/assets/scaleway-api-key.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-api-key.webp
rename to pages/iam/how-to/assets/scaleway-api-key.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-create-group.webp b/pages/iam/how-to/assets/scaleway-create-group.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-create-group.webp
rename to pages/iam/how-to/assets/scaleway-create-group.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-create-policy-p1.webp b/pages/iam/how-to/assets/scaleway-create-policy-p1.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-create-policy-p1.webp
rename to pages/iam/how-to/assets/scaleway-create-policy-p1.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-create-policy-p2.webp b/pages/iam/how-to/assets/scaleway-create-policy-p2.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-create-policy-p2.webp
rename to pages/iam/how-to/assets/scaleway-create-policy-p2.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-delete-application-popup.webp b/pages/iam/how-to/assets/scaleway-delete-application-popup.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-delete-application-popup.webp
rename to pages/iam/how-to/assets/scaleway-delete-application-popup.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-delete-group.webp b/pages/iam/how-to/assets/scaleway-delete-group.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-delete-group.webp
rename to pages/iam/how-to/assets/scaleway-delete-group.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-edit-api-key.webp b/pages/iam/how-to/assets/scaleway-edit-api-key.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-edit-api-key.webp
rename to pages/iam/how-to/assets/scaleway-edit-api-key.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-generate-api-key-new.webp b/pages/iam/how-to/assets/scaleway-generate-api-key-new.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-generate-api-key-new.webp
rename to pages/iam/how-to/assets/scaleway-generate-api-key-new.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-generated-api-key-new.webp b/pages/iam/how-to/assets/scaleway-generated-api-key-new.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-generated-api-key-new.webp
rename to pages/iam/how-to/assets/scaleway-generated-api-key-new.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-groups-overview.webp b/pages/iam/how-to/assets/scaleway-groups-overview.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-groups-overview.webp
rename to pages/iam/how-to/assets/scaleway-groups-overview.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-activate.webp b/pages/iam/how-to/assets/scaleway-iam-activate.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-activate.webp
rename to pages/iam/how-to/assets/scaleway-iam-activate.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-added-user.webp b/pages/iam/how-to/assets/scaleway-iam-added-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-added-user.webp
rename to pages/iam/how-to/assets/scaleway-iam-added-user.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-applications.webp b/pages/iam/how-to/assets/scaleway-iam-applications.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-applications.webp
rename to pages/iam/how-to/assets/scaleway-iam-applications.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-button.webp b/pages/iam/how-to/assets/scaleway-iam-button.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-button.webp
rename to pages/iam/how-to/assets/scaleway-iam-button.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-concepts.webp b/pages/iam/how-to/assets/scaleway-iam-concepts.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-concepts.webp
rename to pages/iam/how-to/assets/scaleway-iam-concepts.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-create-app.webp b/pages/iam/how-to/assets/scaleway-iam-create-app.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-create-app.webp
rename to pages/iam/how-to/assets/scaleway-iam-create-app.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-invite-user.webp b/pages/iam/how-to/assets/scaleway-iam-invite-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-invite-user.webp
rename to pages/iam/how-to/assets/scaleway-iam-invite-user.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-owners-guests.webp b/pages/iam/how-to/assets/scaleway-iam-owners-guests.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-owners-guests.webp
rename to pages/iam/how-to/assets/scaleway-iam-owners-guests.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-policies.webp b/pages/iam/how-to/assets/scaleway-iam-policies.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-policies.webp
rename to pages/iam/how-to/assets/scaleway-iam-policies.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-policy.webp b/pages/iam/how-to/assets/scaleway-iam-policy.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-policy.webp
rename to pages/iam/how-to/assets/scaleway-iam-policy.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-splash.webp b/pages/iam/how-to/assets/scaleway-iam-splash.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-splash.webp
rename to pages/iam/how-to/assets/scaleway-iam-splash.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-users-dashboard.webp b/pages/iam/how-to/assets/scaleway-iam-users-dashboard.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-iam-users-dashboard.webp
rename to pages/iam/how-to/assets/scaleway-iam-users-dashboard.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-invite-user.webp b/pages/iam/how-to/assets/scaleway-invite-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-invite-user.webp
rename to pages/iam/how-to/assets/scaleway-invite-user.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-orga-dropdown.webp b/pages/iam/how-to/assets/scaleway-orga-dropdown.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-orga-dropdown.webp
rename to pages/iam/how-to/assets/scaleway-orga-dropdown.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-policy-overview.webp b/pages/iam/how-to/assets/scaleway-policy-overview.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-policy-overview.webp
rename to pages/iam/how-to/assets/scaleway-policy-overview.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-policy-rule.webp b/pages/iam/how-to/assets/scaleway-policy-rule.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-policy-rule.webp
rename to pages/iam/how-to/assets/scaleway-policy-rule.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-remove-user-popup.webp b/pages/iam/how-to/assets/scaleway-remove-user-popup.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-remove-user-popup.webp
rename to pages/iam/how-to/assets/scaleway-remove-user-popup.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-remove-user.webp b/pages/iam/how-to/assets/scaleway-remove-user.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-remove-user.webp
rename to pages/iam/how-to/assets/scaleway-remove-user.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-user-credentials.webp b/pages/iam/how-to/assets/scaleway-user-credentials.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-user-credentials.webp
rename to pages/iam/how-to/assets/scaleway-user-credentials.webp
diff --git a/pages/identity-and-access-management/iam/how-to/assets/scaleway-user-info.webp b/pages/iam/how-to/assets/scaleway-user-info.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/assets/scaleway-user-info.webp
rename to pages/iam/how-to/assets/scaleway-user-info.webp
diff --git a/pages/identity-and-access-management/iam/how-to/create-api-keys.mdx b/pages/iam/how-to/create-api-keys.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/create-api-keys.mdx
rename to pages/iam/how-to/create-api-keys.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/create-application.mdx b/pages/iam/how-to/create-application.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/create-application.mdx
rename to pages/iam/how-to/create-application.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/create-group.mdx b/pages/iam/how-to/create-group.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/create-group.mdx
rename to pages/iam/how-to/create-group.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/create-policy.mdx b/pages/iam/how-to/create-policy.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/create-policy.mdx
rename to pages/iam/how-to/create-policy.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/index.mdx b/pages/iam/how-to/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/index.mdx
rename to pages/iam/how-to/index.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx b/pages/iam/how-to/invite-user-to-orga.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx
rename to pages/iam/how-to/invite-user-to-orga.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/manage-api-keys.mdx b/pages/iam/how-to/manage-api-keys.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/manage-api-keys.mdx
rename to pages/iam/how-to/manage-api-keys.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/manage-applications.mdx b/pages/iam/how-to/manage-applications.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/manage-applications.mdx
rename to pages/iam/how-to/manage-applications.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/manage-groups.mdx b/pages/iam/how-to/manage-groups.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/manage-groups.mdx
rename to pages/iam/how-to/manage-groups.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/manage-policies.mdx b/pages/iam/how-to/manage-policies.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/manage-policies.mdx
rename to pages/iam/how-to/manage-policies.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/manage-users.mdx b/pages/iam/how-to/manage-users.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/manage-users.mdx
rename to pages/iam/how-to/manage-users.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/view-logs.mdx b/pages/iam/how-to/view-logs.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/view-logs.mdx
rename to pages/iam/how-to/view-logs.mdx
diff --git a/pages/identity-and-access-management/iam/how-to/view-permission-sets.mdx b/pages/iam/how-to/view-permission-sets.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/how-to/view-permission-sets.mdx
rename to pages/iam/how-to/view-permission-sets.mdx
diff --git a/pages/identity-and-access-management/iam/index.mdx b/pages/iam/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/index.mdx
rename to pages/iam/index.mdx
diff --git a/pages/identity-and-access-management/iam/quickstart.mdx b/pages/iam/quickstart.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/quickstart.mdx
rename to pages/iam/quickstart.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-api-key-test.webp b/pages/iam/reference-content/assets/scaleway-api-key-test.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-api-key-test.webp
rename to pages/iam/reference-content/assets/scaleway-api-key-test.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-api-key.webp b/pages/iam/reference-content/assets/scaleway-api-key.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-api-key.webp
rename to pages/iam/reference-content/assets/scaleway-api-key.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-bucket.webp b/pages/iam/reference-content/assets/scaleway-bucket.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-bucket.webp
rename to pages/iam/reference-content/assets/scaleway-bucket.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-appli.webp b/pages/iam/reference-content/assets/scaleway-create-appli.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-appli.webp
rename to pages/iam/reference-content/assets/scaleway-create-appli.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-policy.webp b/pages/iam/reference-content/assets/scaleway-create-policy.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-policy.webp
rename to pages/iam/reference-content/assets/scaleway-create-policy.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-rule.webp b/pages/iam/reference-content/assets/scaleway-create-rule.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-create-rule.webp
rename to pages/iam/reference-content/assets/scaleway-create-rule.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-groups.webp b/pages/iam/reference-content/assets/scaleway-groups.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-groups.webp
rename to pages/iam/reference-content/assets/scaleway-groups.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-api-key-change.webp b/pages/iam/reference-content/assets/scaleway-iam-api-key-change.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-api-key-change.webp
rename to pages/iam/reference-content/assets/scaleway-iam-api-key-change.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-app.webp b/pages/iam/reference-content/assets/scaleway-iam-app.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-app.webp
rename to pages/iam/reference-content/assets/scaleway-iam-app.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-concepts.webp b/pages/iam/reference-content/assets/scaleway-iam-concepts.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-concepts.webp
rename to pages/iam/reference-content/assets/scaleway-iam-concepts.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-invitation-groups.webp b/pages/iam/reference-content/assets/scaleway-iam-invitation-groups.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-invitation-groups.webp
rename to pages/iam/reference-content/assets/scaleway-iam-invitation-groups.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-orga.webp b/pages/iam/reference-content/assets/scaleway-iam-orga.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-orga.webp
rename to pages/iam/reference-content/assets/scaleway-iam-orga.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-organization.webp b/pages/iam/reference-content/assets/scaleway-iam-organization.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-organization.webp
rename to pages/iam/reference-content/assets/scaleway-iam-organization.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-owners-guests.webp b/pages/iam/reference-content/assets/scaleway-iam-owners-guests.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-owners-guests.webp
rename to pages/iam/reference-content/assets/scaleway-iam-owners-guests.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-policy-example.webp b/pages/iam/reference-content/assets/scaleway-iam-policy-example.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-policy-example.webp
rename to pages/iam/reference-content/assets/scaleway-iam-policy-example.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-policy.webp b/pages/iam/reference-content/assets/scaleway-iam-policy.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-policy.webp
rename to pages/iam/reference-content/assets/scaleway-iam-policy.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-roles-change.webp b/pages/iam/reference-content/assets/scaleway-iam-roles-change.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-iam-roles-change.webp
rename to pages/iam/reference-content/assets/scaleway-iam-roles-change.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-invite-users.webp b/pages/iam/reference-content/assets/scaleway-invite-users.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-invite-users.webp
rename to pages/iam/reference-content/assets/scaleway-invite-users.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-policy-rules.webp b/pages/iam/reference-content/assets/scaleway-policy-rules.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-policy-rules.webp
rename to pages/iam/reference-content/assets/scaleway-policy-rules.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-preferred-project.webp b/pages/iam/reference-content/assets/scaleway-preferred-project.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-preferred-project.webp
rename to pages/iam/reference-content/assets/scaleway-preferred-project.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-roles-hierarchy.webp b/pages/iam/reference-content/assets/scaleway-roles-hierarchy.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-roles-hierarchy.webp
rename to pages/iam/reference-content/assets/scaleway-roles-hierarchy.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-second-bucket.webp b/pages/iam/reference-content/assets/scaleway-second-bucket.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-second-bucket.webp
rename to pages/iam/reference-content/assets/scaleway-second-bucket.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/assets/scaleway-test-project.webp b/pages/iam/reference-content/assets/scaleway-test-project.webp
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/assets/scaleway-test-project.webp
rename to pages/iam/reference-content/assets/scaleway-test-project.webp
diff --git a/pages/identity-and-access-management/iam/reference-content/index.mdx b/pages/iam/reference-content/index.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/index.mdx
rename to pages/iam/reference-content/index.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/overview.mdx b/pages/iam/reference-content/overview.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/overview.mdx
rename to pages/iam/reference-content/overview.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/permission-sets.mdx b/pages/iam/reference-content/permission-sets.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/permission-sets.mdx
rename to pages/iam/reference-content/permission-sets.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/policy.mdx b/pages/iam/reference-content/policy.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/policy.mdx
rename to pages/iam/reference-content/policy.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx b/pages/iam/reference-content/reproduce-roles-project-api-keys.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx
rename to pages/iam/reference-content/reproduce-roles-project-api-keys.mdx
diff --git a/pages/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx b/pages/iam/reference-content/users-groups-and-applications.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx
rename to pages/iam/reference-content/users-groups-and-applications.mdx
diff --git a/pages/identity-and-access-management/iam/videos.mdx b/pages/iam/videos.mdx
similarity index 100%
rename from pages/identity-and-access-management/iam/videos.mdx
rename to pages/iam/videos.mdx
diff --git a/pages/identity-and-access-management/index.mdx b/pages/identity-and-access-management/index.mdx
deleted file mode 100644
index 13d4f6554f..0000000000
--- a/pages/identity-and-access-management/index.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-meta:
- title: Discover Security & Identity
- description: Discover Security & Identity
-content:
- h1: Discover Security & Identity
- paragraph: Discover Security & Identity
----
diff --git a/pages/instances/api-cli/assets/Scaleway-Instances-CLI-Cheatsheet.pdf b/pages/instances/api-cli/assets/Scaleway-Instances-CLI-Cheatsheet.pdf
new file mode 100644
index 0000000000..7faccb8fe9
Binary files /dev/null and b/pages/instances/api-cli/assets/Scaleway-Instances-CLI-Cheatsheet.pdf differ
diff --git a/pages/instances/api-cli/assets/scaleway-instances-cli-cheatsheet.webp b/pages/instances/api-cli/assets/scaleway-instances-cli-cheatsheet.webp
new file mode 100644
index 0000000000..0e689087eb
Binary files /dev/null and b/pages/instances/api-cli/assets/scaleway-instances-cli-cheatsheet.webp differ
diff --git a/pages/instances/api-cli/assets/scaleway-snapshot-imported.webp b/pages/instances/api-cli/assets/scaleway-snapshot-imported.webp
new file mode 100644
index 0000000000..f21e8d50b5
Binary files /dev/null and b/pages/instances/api-cli/assets/scaleway-snapshot-imported.webp differ
diff --git a/pages/instances/api-cli/attaching-a-volume.mdx b/pages/instances/api-cli/attaching-a-volume.mdx
new file mode 100644
index 0000000000..4ecb76b2e9
--- /dev/null
+++ b/pages/instances/api-cli/attaching-a-volume.mdx
@@ -0,0 +1,147 @@
+---
+meta:
+ title: Attaching a Block Storage volume via the Instance API
+ description: This page explains how to attach a Block Storage volume using the Scaleway API.
+content:
+ h1: Attaching a Block Storage volume via the Instance API
+ paragraph: This page explains how to attach a Block Storage volume using the Scaleway API.
+tags: attach-storage storage volume block api
+categories:
+ - block-storage
+ - storage
+dates:
+ validation: 2025-01-02
+ posted: 2020-01-10
+---
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+- A [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+
+1. Query the current volumes of the Instance.
+ ```
+ curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/servers/be3c50af-e8f3-4ff4-90fe-66972f06670d
+ {
+ "server": {
+ "allowed_actions": [
+ ...
+ "volumes": {
+ "0": {
+ ...
+ "id": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b",
+ "volume_type": "l_ssd",
+ ...
+ }
+ },
+ ...
+ }
+ ```
+
+ As displayed, our current volumes are only constituted of the root volume.
+2. Hot-plug the volume created earlier:
+ ```bash
+ curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X PATCH \
+ -d '{
+ "volumes": {
+ "0": {
+ "id": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b",
+ "volume_type": "l_ssd"
+ },
+ "1": {
+ "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295",
+ "volume_type": "sbs_volume"
+ }
+ }
+ }' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/servers/be3c50af-e8f3-4ff4-90fe-66972f06670d
+ {
+ "server": {
+ ...
+ "id": "be3c50af-e8f3-4ff4-90fe-66972f06670d",
+ ...
+ "name": "scw-blissful-engelbart",
+ "protected": false,
+ "volumes": {
+ "0": {
+ "size": 20000000000,
+ "state": "available",
+ ...
+ "id": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b",
+ "volume_type": "l_ssd",
+ "server": {
+ "id": "be3c50af-e8f3-4ff4-90fe-66972f06670d",
+ "name": "scw-blissful-engelbart"
+ }
+ },
+ "1": {
+ "size": 10000000000,
+ "state": "available",
+ "name": "block-volume101",
+ "modification_date": "2019-09-03T10:17:40.800839+00:00",
+ ...
+ "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295",
+ "volume_type": "sbs_volume",
+ "server": {
+ "id": "be3c50af-e8f3-4ff4-90fe-66972f06670d",
+ "name": "scw-blissful-engelbart"
+ }
+ }
+ },
+ ...
+ }
+ }
+ ```
+3. Use [SSH](/instances/how-to/connect-to-instance/) to log into your server and verify that the new disk exists:
+ ```bash
+ lsblk
+ NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
+ sda 8:0 0 953.7M 0 disk
+ vda 252:0 0 18.6G 0 disk
+ ├─vda1 252:1 0 18.5G 0 part /
+ └─vda15 252:15 0 100M 0 part /boot/efi
+ ```
+
+ The block volume is presented inside your Instance as `/dev/sdX`, to help you
+ automate things, a symlink is also present in `/dev/disk/by-id/` with the `id`
+ of the volume in it:
+
+ ```
+ ls /dev/disk/by-id/
+ scsi-0SCW_b_ssd_volume-b3a42fb1-e85c-46e9-b0a6-9adb62278295
+ ```
+
+ If you query information about the block volume from the API, the `server_id`
+ on which it is plugged in is displayed:
+
+ ```
+ curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes/b3a42fb1-e85c-46e9-b0a6-9adb62278295
+ {
+ "volume": {
+ "size": 10000000000,
+ "state": "available",
+ "name": "block-volume101",
+ ...
+ "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295",
+ "volume_type": "b_ssd",
+ "server": {
+ "id": "be3c50af-e8f3-4ff4-90fe-66972f06670d",
+ "name": "scw-blissful-engelbart"
+ }
+ }
+ }
+ ```
+
+
diff --git a/pages/instances/api-cli/cli-cheatsheet.mdx b/pages/instances/api-cli/cli-cheatsheet.mdx
new file mode 100644
index 0000000000..d602ef845e
--- /dev/null
+++ b/pages/instances/api-cli/cli-cheatsheet.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: Scaleway Instances CLI Cheatsheet
+ description: This page shows the most common Scaleway CLI commands for creating and managing Scaleway Instances.
+content:
+ h1: Scaleway Instances CLI Cheatsheet
+ paragraph: This page shows the most common Scaleway CLI commands for creating and managing Scaleway Instances.
+tags: instance cli cheatsheet scw
+dates:
+ validation: 2024-08-05
+categories:
+ - compute
+---
+
+This page shows the most common Scaleway CLI commands for creating and managing Scaleway Instances.
+
+
+
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+
+
+
+
+ This content is also available as a printable PDF file:
+
+ [Download Instances CLI Cheatsheet - Printable](Scaleway-Instances-CLI-Cheatsheet.pdf)
+
+
+
diff --git a/pages/instances/api-cli/creating-a-volume.mdx b/pages/instances/api-cli/creating-a-volume.mdx
new file mode 100644
index 0000000000..a8a1c5f601
--- /dev/null
+++ b/pages/instances/api-cli/creating-a-volume.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: Creating a Block Storage volume via the Instance API
+ description: This page explains how to create a Block Storage volume using the Scaleway API.
+content:
+ h1: Creating a Block Storage volume via the Instance API
+ paragraph: This page explains how to create a Block Storage volume using the Scaleway API.
+tags: block-storage block volume create storage
+dates:
+ validation: 2025-01-02
+ posted: 2020-01-10
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+
+
+1. Create a block volume from the API by launching the following command:
+ ```
+ curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X POST \
+ -d '{"name": "block-volume-101", "organization": "'$SCW_ORGANIZATION'", "size": 10000000000, "volume_type": "b_ssd"}' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes
+ ```
+2. To retrieve the current status of the block volume, query the volume endpoint.
+ ```
+ curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/volumes/b3a42fb1-e85c-46e9-b0a6-9adb62278295
+ {
+ "volume": {
+ "size": 10000000000,
+ "state": "available",
+ "name": "block-volume101",
+ "modification_date": "2019-09-03T09:57:53.742130+00:00",
+ ...
+ "id": "b3a42fb1-e85c-46e9-b0a6-9adb62278295",
+ "volume_type": "b_ssd",
+ "server": null
+ }
+ }
+ ```
+
diff --git a/pages/instances/api-cli/creating-backups.mdx b/pages/instances/api-cli/creating-backups.mdx
new file mode 100644
index 0000000000..6fcb40254b
--- /dev/null
+++ b/pages/instances/api-cli/creating-backups.mdx
@@ -0,0 +1,100 @@
+---
+meta:
+ title: Creating backups of Instances via the Scaleway API
+ description: This page explains how to create backups of your Instances using the Scaleway API
+content:
+ h1: Creating backups of Instances via the Scaleway API
+ paragraph: This page explains how to create backups of your Instaces using the Scaleway API
+tags: instance create backup scaleway-api
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+The Backup feature is used to back up your Instance data. It creates an image of a snapshot that contains all your volumes. You can create backups of your Instances using either the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/).
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+- A running Instance
+
+## Creating a backup
+
+
+
+
+ Use the following commands to create a backup of your Instance using the [Scaleway CLI](/scaleway-cli/quickstart/).
+ ```sh
+ scw instance server backup server-id zone=fr-par-1
+ ```
+
+ * Replace `server-id` with the unique identifier of the Instance.
+ * Replace `fr-par-1` with the Availability Zone your Instance is deployed in.
+
+
+ By default, the name of the image is built according to the name of the server and the date. You can specify a name for the image in the request:
+ ```sh
+ scw instance server backp server-id zone=fr-par-1 name=myimagename
+ ```
+
+ A backup request will create an image object. You can view it using:
+ ```sh
+ scw instance image get image-uid zone=fr-par-1
+ ```
+ An image contains one snapshot for each volume of the Instance. These snapshots are visible within the image response as `root_volume` and `extra_volumes` fields.
+
+
+
+ A backup is created using the [Instances API](https://www.scaleway.com/en/developers/api/instance/) with the following command:
+ ```
+ POST https://api.scaleway.com/instance/v1/zones//servers//action
+ {"action":"backup"}
+ ```
+ Replace `` with the geographical region of the Instance. For Instances located in Paris, for example, this value would be `fr-par-1`. Replace `` with the unique identifier of the Instance.
+ By default, the name of the image is built according to the name of the server and the date:
+ ```
+ image__YYYY-MM-DD_hh-mm.
+ ```
+ Alternatively, you can specify a name for the image in the request:
+ ```
+ POST https://api.scaleway.com/instance/v1/zones//servers//action
+ { "action":"backup", "name":"myimagename" }
+ ```
+ A backup request will create an image object (visible in the `href_result`: `/images/`)
+ ```
+ GET https://api.scaleway.com/instance/v1/zones//images/
+ ```
+ An image contains one snapshot for each volume of the Instance. These snapshots are visible within the image response, as `root_volume` and `extra_volumes` fields.
+
+
+
+## Deleting a Backup
+
+
+
+ To delete a backup, run the following command:
+ ```sh
+ scw instance image delete image-uid zone=fr-par1
+ ```
+ It is also recommended to remove every snapshot related to the image by running the following command for each snapshot that is no longer needed:
+ ```sh
+ scw instance snapshot delete snapshot-uid zone=fr-par-1
+ ```
+
+
+
+ Run the following call to delete the image that contains a backup:
+ ```
+ DELETE https://api.scaleway.com/instance/v1/zones//images/
+ ```
+ It is also recommended to remove every snapshot related to the image by running the following API call for each snapshot that is no longer needed:
+ ```
+ DELETE https://api.scaleway.com/instance/v1/zones//snapshots/
+ ```
+
+
+
diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx
new file mode 100644
index 0000000000..7b8649517b
--- /dev/null
+++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx
@@ -0,0 +1,292 @@
+---
+meta:
+ title: Creating and managing an Instance with CLI (v2)
+ description: This page explains how to create and manage a Scaleway Instance with CLI (v2)
+content:
+ h1: Creating and managing an Instance with CLI (v2)
+ paragraph: This page explains how to create and manage a Scaleway Instance with CLI (v2)
+tags: instance create manage cli cli-v2 scw
+dates:
+ validation: 2024-08-26
+ posted: 2021-08-05
+categories:
+ - compute
+---
+
+Scaleway Instances provide you with resources to develop, test code and deploy your applications in no time. Instances are designed for modern workflows. They are with you from prototyping to large-scale deployment. You can [create](/instances/how-to/create-an-instance/) and manage your Instances from the [console](https://console.scaleway.com/login), via the [API](https://www.scaleway.com/en/developers/api/instance/) or the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli).
+
+## Scaleway Command Line Interface (CLI) overview
+
+[The Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway-cli) allows you to pilot your Scaleway infrastructure directly from your terminal, providing a faster way to administer and monitor your resources. Scaleway CLI is easy to set up and use, and an essential tool for operating efficiently in your cloud environment. The CLI provides many functionalities, including the ability to create and manage Instances.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+- Downloaded and installed the [Scaleway CLI v2](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2)
+
+## Configuring the CLI
+
+1. Open a terminal and type the following command to configure the Scaleway CLI on your machine:
+
+ `scw init`
+
+ If you have already configured the CLI, you will see a message similar to the following:
+
+ ```
+ Current config is located at /path/to/config.yaml
+ access_key:
+ secret_key:
+ default_organization_id:
+ default_project_id:
+ default_region:
+ default_zone:
+
+ Do you want to override the current config? (Y/n):
+ ```
+2. Unless you want to change your configuration, you can type `n` and go directly to the [Creating an Instance](#creating-an-instance) step of this tutorial.
+
+ If you have not yet configured the CLI, you will be guided through the configuration process via a series of questions:
+
+ ```
+ Enter a valid secret-key or an email
+ ```
+3. Enter either the email address for your account (you will then be asked for your password), or your [API secret key](/organizations-and-projects/how-to/create-ssh-key/):
+ ```
+ To improve this tool we rely on diagnostic and usage data.
+ Sending such data is optional and can be disabled at any time by running "scw config set send-telemetry=false".
+ Do you want to send usage statistics and diagnostics? (Y/n):
+ ```
+
+ Type `y` or `n` and hit enter.
+
+ ```
+ To fully enjoy Scaleway CLI we recommend you install autocomplete support in your shell.
+ Do you want to install autocomplete? (Y/n):
+ ```
+ Type `y` or `n` and hit enter.
+
+ ```
+ To enable autocomplete, scw needs to update your shell configuration.
+ What type of shell are you using (default: zsh):
+ ```
+4. Hit enter if the default shell type is already correct for you. Otherwise, enter your shell type and hit enter.
+ ```
+ To enable autocomplete we need to append to /Users/yourusername/.zshrc the following lines:
+ # Scaleway CLI autocomplete initialization.
+ eval "$(scw autocomplete script shell=zsh)"
+ Do you want to proceed with these changes? (Y/n):
+ ```
+
+ Type `y` or `n` and hit enter. This should complete the configuration process:
+
+ ```
+ Initialization completed with success.
+ ```
+
+## Creating an Instance
+
+1. Type the following command in your terminal to obtain a local-image UUID:
+
+ `scw marketplace image get label=ubuntu_focal`
+
+ A list of local-images UUIDs from marketplace images displays:
+
+ ```
+ Image:
+ Label ubuntu_focal
+ Name Ubuntu 20.04 Focal Fossa
+ ModificationDate 3 months ago
+ CreationDate 2 years ago
+ Description Ubuntu is the ideal distribution for scale-out computing, Ubuntu Server helps you make the most of your infrastructure.
+
+ Local Images:
+ ID ZONE ARCH
+ 401a8e7b-f215-49b5-af8d-e39d9efff24c fr-par-2 x86_64
+ 42e3c57b-f907-4685-8a6a-f016445d867a pl-waw-1 x86_64
+ 9a40a4cd-87bb-410a-86a2-39af87d12667 fr-par-2 x86_64
+ 91edfd06-3eb7-44ad-a903-be54363135a7 pl-waw-1 x86_64
+ 70c3e86b-918d-42bd-af7d-e6be485d3f8b fr-par-1 x86_64
+ 223b6d78-1aa4-4234-b8ce-e5d39e762ef3 nl-ams-1 x86_64
+ 87b79530-0bf4-46da-beeb-f6dc950ab225 fr-par-3 x86_64
+ dcd8d994-b859-4e9e-aa91-2ceca41663fb nl-ams-1 x86_64
+ ff48b73a-097d-4685-b996-d3ebe50636ea fr-par-1 x86_64
+ ```
+2. Run the following command to create an Instance:
+
+ `scw instance server create zone=xx-xxx-x image=ubuntu_focal`
+
+
+ Replace `xx-xxx-x` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/instances/concepts/#availability-zone) for more information about Availability Zones.
+
+
+ You will see an output like the following:
+
+ ```
+ ID 12345678-1234-1234-4321-123456789123
+ Name cli-srv-naughty-stonebraker
+ Organization 12345678-1234-1234-4321-123456789123
+ Project 12345678-1234-1234-4321-123456789123
+ AllowedActions.0 poweron
+ AllowedActions.1 backup
+ CommercialType DEV1-S
+ CreationDate now
+ DynamicIPRequired false
+ EnableIPv6 false
+ Hostname cli-srv-naughty-stonebraker
+ Image.ID 12345678-1234-1234-4321-123456789123
+ Image.Name Ubuntu 20.04 Focal Fossa
+ Image.Arch x86_64
+ Image.CreationDate 4 months ago
+ Image.ModificationDate 4 months ago
+ Image.ExtraVolumes 0
+ Image.FromServer -
+ Image.Organization 12345678-1234-1234-4321-123456789123
+ Image.Public true
+ Image.RootVolume 12345678-1234-1234-4321-123456789123
+ Image.State available
+ Image.Project 12345678-1234-1234-4321-123456789123
+ Image.Zone fr-par-2
+ Protected false
+ PublicIP.ID 12345678-1234-1234-4321-123456789123
+ PublicIP.Address 51.159.163.11
+ PublicIP.Dynamic false
+ ModificationDate now
+ State archived
+ Bootscript x86_64 mainline 4.4.230 rev1
+ BootType local
+ Volumes 1
+ SecurityGroup.ID 12345678-1234-1234-4321-123456789123
+ SecurityGroup.Name Default security group
+ StateDetail -
+ Arch x86_64
+ Zone fr-par-2
+ ```
+
+## Creating an Instance local volume
+
+1. Run the following command to create an Instance volume with a size of 50 GB:
+
+ `scw instance volume create size=50GB name=my-volume`
+
+ You will see an output like the following:
+
+ ```
+ ID 12345678-1234-1234-4321-123456789123
+ Name my-volume
+ ExportURI -
+ Size 50 GB
+ VolumeType l_ssd
+ CreationDate now
+ ModificationDate now
+ Organization 12345678-1234-1234-4321-123456789123
+ Project 12345678-1234-1234-4321-123456789123
+ State available
+ Zone fr-par-1
+ ```
+2. Write down the ID of your Instance. You will need it in the next steps.
+
+## Creating and attaching a block volume to an Instance
+
+
+1. Run the following command to create a [block volume](/instances/concepts/#block-volumes):
+
+ `scw instance volume create size=10GB volume-type=b_ssd`
+
+ Your block volume has been created:
+ ```
+ ID 12345678-1234-1234-4321-123456789123
+ Name cli-vol-albattani
+ ExportURI -
+ Size 10 GB
+ VolumeType b_ssd
+ CreationDate 1 second from now
+ ModificationDate 1 second from now
+ Organization 12345678-1234-1234-4321-123456789123
+ Project 12345678-1234-1234-4321-123456789123
+ State available
+ ```
+2. Write down your block volume's ID. You will need it in the next steps.
+3. Type the following command in your terminal to attach your block volume to your Instance. Make sure you replace `n4m3-0f-y0Ur-s3rv3r-id` by your server ID and `n4m3-0f-y0Ur-volume-id` by your volume ID.
+
+ `scw instance server attach-volume server-id=n4m3-0f-y0Ur-s3rv3r-id volume-id=n4m3-0f-y0Ur-volume-id`
+
+ You will see an output similar to the following:
+
+ ```
+ Server.ID 12345678-1234-1234-4321-123456789123
+ Server.Name scw-sleepy-mestorf
+ Server.Organization 12345678-1234-1234-4321-123456789123
+ Server.Project 12345678-1234-1234-4321-123456789123
+ Server.CommercialType GP1-S
+ Server.CreationDate 4 days ago
+ Server.DynamicIPRequired false
+ Server.EnableIPv6 true
+ Server.Hostname scw-sleepy-mestorf
+ Server.Image.ID 12345678-1234-1234-4321-123456789123
+ Server.Image.Name Ubuntu 20.04 Focal Fossa
+ Server.Image.Arch x86_64
+ Server.Image.CreationDate 4 months ago
+ Server.Image.ModificationDate 4 months ago
+ Server.Image.ExtraVolumes 0
+ Server.Image.FromServer -
+ Server.Image.Organization 12345678-1234-1234-4321-123456789123
+ Server.Image.Public true
+ Server.Image.RootVolume 12345678-1234-1234-4321-123456789123
+ Server.Image.State available
+ Server.Image.Project 12345678-1234-1234-4321-123456789123
+ Server.Image.Zone fr-par-1
+ Server.Protected false
+ Server.PrivateIP 10.194.79.129
+ Server.PublicIP.ID 12345678-1234-1234-4321-123456789123
+ Server.PublicIP.Address 12.345.678.123
+ Server.PublicIP.Dynamic false
+ Server.ModificationDate 4 days ago
+ Server.State running
+ Server.Location fr-par-1
+ Server.IPv6.Address 2001:bc8:610:6300::1
+ Server.IPv6.Gateway 2001:bc8:610:6300::
+ Server.IPv6.Netmask 64
+ Server.Bootscript x86_64 mainline 4.4.230 rev1
+ Server.BootType local
+ Server.Volumes 2
+ Server.SecurityGroup.ID 12345678-1234-1234-4321-123456789123
+ Server.SecurityGroup.Name Default security group
+ Server.StateDetail booted
+ Server.Arch x86_64
+ Server.Zone fr-par-1
+ ```
+
+## Powering off an Instance
+
+Type the following command in your terminal and replace "your-server" with the ID of your server.
+
+`scw instance server stop your-server`
+
+You will see the following output:
+
+```
+Poweroff successful for the server.
+```
+
+Your Instance has been powered off.
+
+## Deleting an Instance
+
+
+ This action will delete all your volumes and data located on your storage server. To avoid losing data, it is recommended to perform regular snapshots.
+
+
+Ensure your Instance is powered off and then run the following command, replacing "your-server" with the ID of your server.
+
+`scw instance server delete your-server`
+
+You will see the following output:
+
+```
+successfully deleted volume ubuntu_20.04_focal_fossa:volume-0 (20 GB l_ssd)
+```
+
+
diff --git a/pages/instances/api-cli/detaching-a-volume.mdx b/pages/instances/api-cli/detaching-a-volume.mdx
new file mode 100644
index 0000000000..4b7ed98055
--- /dev/null
+++ b/pages/instances/api-cli/detaching-a-volume.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: Detaching a Block Storage volume via the Instance API
+ description: This page explains how to detach a Block Storage volume from an Instance using the Scaleway API.
+content:
+ h1: Detaching a Block Storage volume via the Instance API
+ paragraph: This page explains how to detach a Block Storage volume from an Instance using the Scaleway API.
+tags: detach volume block storage unlink unplug api
+dates:
+ validation: 2025-01-02
+ posted: 2020-01-10
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+
+To detach a block volume from a running Instance, relaunch the API call and omit the volume you want to hot unplug. Like so:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X PATCH \
+ -d '{
+ "volumes": {
+ "0": "7fe25caf-0a68-46a7-aeb9-63a278d33e2b",
+ }
+ }' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/servers/be3c50af-e8f3-4ff4-90fe-66972f06670d
+```
+
+
diff --git a/pages/instances/api-cli/increasing-volume-size.mdx b/pages/instances/api-cli/increasing-volume-size.mdx
new file mode 100644
index 0000000000..10516d807e
--- /dev/null
+++ b/pages/instances/api-cli/increasing-volume-size.mdx
@@ -0,0 +1,54 @@
+---
+meta:
+ title: Increasing Block Storage volumes via the Instance API
+ description: This page explains how to increase a Block Storage volume using the Scaleway API.
+content:
+ h1: Increasing Block Storage volumes via the Instance API
+ paragraph: This page explains how to increase a Block Storage volume
+tags: increase expland increment raise storage volume block
+dates:
+ validation: 2024-08-26
+ posted: 2020-01-10
+categories:
+ - block-storage
+ - storage
+---
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+- A [Block Storage volume](/instances/api-cli/creating-a-volume/)
+
+
+1. Inspect the volume and verify its name, size, and if the type is `b_ssd` by running the following request.
+ ```
+ curl -q -H "X-Auth-Token: $SECRET_KEY" -X GET https://api.scaleway.com/instance/v1/zones//volumes/
+ ```
+
+
+ Replace `REGION` with the geographical region of the Instance. This value can either be `fr-par-1`, `fr-par-2`, or `fr-par-3` for Instances located in Paris, `nl-ams-1`, `nl-ams-2` or `nl-ams-3` for Instances located in Amsterdam, or `pl-waw-1`, `pl-waw-2`, or `pl-waw-3` for Instances located in Warsaw. Replace `VOLUME_ID` with the unique identifier of the volume, which can be found on the Scaleway console under **Instances** > **Volumes** > **More info** (for the selected volume).
+
+
+ The following response should appear as an output:
+
+ ```
+ {"volume": {"creation_date": "2020-06-02T08:04:50.094118+00:00", "server": null, "id": "", "size": 25000000000, "name": "myAwesomeVolume", "zone": "", "export_uri": null, "volume_type": "b_ssd", "modification_date": "2020-06-02T08:04:50.094118+00:00", "state": "available", "organization": ""}}
+ ```
+2. To modify the volume size, run the request below:
+ ```
+ curl https://api.scaleway.com/instance/v1/zones/REGION/volumes/VOLUME_ID -H "X-Auth-Token: $SECRET_KEY" -X PATCH -H 'Content-Type: application/json;charset=utf-8' --data '{ "name":"new_name", "size":26000000000 }'
+ ```
+ Replace `REGION` and `VOLUME_ID` following the guidelines mentioned previously and replace the existing size value with the new one.
+
+
+ You can use the same request to change the name of your volume by replacing `new_name` with another of your choice. If you do not wish to change the volume name, erase `"name":"new_name",` from the request before running it.
+
+
+ A response appears confirming the changes:
+ ```
+ {"volume": {"creation_date": "2020-06-02T08:04:50.094118+00:00", "server": null, "id": "VOLUME_ID", "size": 26000000000, "name": "new_name", "zone": "REGION", "export_uri": null, "volume_type": "b_ssd", "modification_date": "2020-06-02T08:08:27.385208+00:00", "state": "resizing", "organization": "ORGANIZATION_ID"}}
+ ```
+
+
diff --git a/pages/instances/api-cli/index.mdx b/pages/instances/api-cli/index.mdx
new file mode 100644
index 0000000000..4f16f93480
--- /dev/null
+++ b/pages/instances/api-cli/index.mdx
@@ -0,0 +1,9 @@
+---
+meta:
+ title: Instances - API/CLI Documentation
+ description: Instances API/CLI Documentation
+content:
+ h1: Instances - API/CLI Documentation
+ paragraph: Instances API/CLI Documentation
+---
+
diff --git a/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx b/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx
new file mode 100644
index 0000000000..b6961d6051
--- /dev/null
+++ b/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx
@@ -0,0 +1,92 @@
+---
+meta:
+ title: Managing Instance snapshots with the CLI (v2)
+ description: This page explains how to manage Scaleway Instance snapshots with the CLI (v2)
+content:
+ h1: Managing Instance snapshots with the CLI (v2)
+ paragraph: This page explains how to manage Scaleway Instance snapshots with the CLI (v2)
+tags: manage instance snapshot cli cli-v2
+dates:
+ validation: 2024-10-14
+ posted: 2022-09-24
+categories:
+ - compute
+---
+
+You can use the Scaleway CLI to create, export, and import snapshots of your Instances. A snapshot is a [QCOW2 image](https://en.wikipedia.org/wiki/Qcow) of your Instance's volumes, stored in a Scaleway Object Storage bucket. It can be imported into any Availability Zone, as long as it is in the same region as the bucket in which it is hosted.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+- Downloaded and installed the [Scaleway CLI v2](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2)
+
+## Creating a snapshot using the CLI
+
+To create a snapshot from a volume using the CLI, run the following command:
+```
+scw instance snapshot create [arg=value ...]
+```
+
+The following arguments and flags are available to customize your command:
+
+```sh
+ARGS:
+ [name=] Name of the snapshot
+ [volume-id] UUID of the volume
+ [tags.{index}] The tags of the snapshot
+ [project-id] Project ID to use. If none is passed the default project ID will be used
+ [bucket] Bucket name for snapshot imports
+ [key] Object key for snapshot imports
+ [size] Imported snapshot size, must be a multiple of 512
+ [organization-id] Organization ID to use. If none is passed the default organization ID will be used
+ [zone=fr-par-1] Zone to target. If none is passed will use the default zone from the config (fr-par-1 | fr-par-2 | fr-par-3 | nl-ams-1 | nl-ams-2 | pl-waw-1)
+
+FLAGS:
+ -h, --help help for create
+ -w, --wait wait until the snapshot is ready
+
+GLOBAL FLAGS:
+ -c, --config string The path to the config file
+ -D, --debug Enable debug mode
+ -o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
+ -p, --profile string The config profile to use
+```
+
+## Creating a snapshot in the default zone from the given volume ID
+
+To create a snapshot in the default zone from the given volume ID, run the following command. Remember to replace `11111111-1111-1111-1111-111111111111` with the actual ID of your volume.
+
+```
+scw instance snapshot create volume-id=11111111-1111-1111-1111-111111111111
+```
+
+## Creating a snapshot in a specific zone from the given volume ID
+
+To create a snapshot in a specific zone (e.g. `fr-par-1`) from the given volume ID, run the following command. Remember to replace `11111111-1111-1111-1111-111111111111` with the actual ID of your volume.
+```
+scw instance snapshot create zone=fr-par-1 volume-id=11111111-1111-1111-1111-111111111111
+```
+
+## Creating a named snapshot in the default zone from a given volume ID
+
+Run the following command to create a named snapshot from the given volume ID. Remember to replace `11111111-1111-1111-1111-111111111111` with the actual ID of your volume.
+
+```
+scw instance snapshot create name=foobar volume-id=11111111-1111-1111-1111-111111111111
+```
+
+## Importing a QCOW file from an Object Storage bucket as Instance snapshot
+
+Run the following command to import a QCOW file as an Instance snapshot. Replace the bucket name `my-bucket` with the name of your Object Storage bucket and the file name `qcow2-file-name.qcow2` with the name of your QCOW file.
+```
+scw instance snapshot create zone=fr-par-1 name=my-imported-snapshot volume-type=b_ssd bucket=my-bucket key=my-qcow2-file-name.qcow
+```
+
+
+ When importing existing QCOW / QCOW2 files from Object Storage as Instance snapshots, make sure that the file has the suffix `.qcow` or `.qcow2`.
+
+
+
diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx
new file mode 100644
index 0000000000..aa8367d26f
--- /dev/null
+++ b/pages/instances/api-cli/migrating-instances.mdx
@@ -0,0 +1,138 @@
+---
+meta:
+ title: Changing the commercial type of an Instance with the API or CLI
+ description: This page explains how to change the commercial type of a Scaleway Instance with the API or CLI
+content:
+ h1: Changing the commercial type of an Instance with the API or CLI
+ paragraph: This page explains how to change the commercial type of a Scaleway Instance with the API or CLI
+tags: upgrade instance api
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+It is possible to change the commercial type of an Instance by using the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/).
+To do so, you need the Instance’s ID and a valid API key.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/), which must be stopped and not be in a placement group
+
+
+
+
+ 1. Stop the Instance.
+ ```
+ scw instance server stop zone=
+ ```
+ Replace `` with the Availability Zone of your Instance. For example, if your Instance is located in Paris-1, the zone would be `fr-par-1`. Replace `` with the ID of your Instance.
+
+ You can find the ID of your Instance on it's overview page in the Scaleway console or using the CLI by running the following command: `scw instance server list`.
+
+
+ 2. Update the commercial type of the Instance
+ ```
+ scw instance server update commercial-type= zone=
+ ```
+ Replace `` with the desired new commercial type.
+
+ You can retrieve a list of all available Instance types using the command `scw instance server-type list`.
+
+
+ Ensure that Local Storage constraints are respected. For example, downgrading from a larger Instance type to a smaller one may not be possible if the smaller Instance type cannot support the existing Local Storage. Check the Scaleway documentation for specific constraints.
+
+
+ 3. Power on the Instance.
+ ```
+ scw instance server start zone=
+ ```
+ You have successfully changed the commercial type of your Scaleway Instance using the Scaleway CLI. For further information, refer to the [Instance CLI documentation](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/instance.md).
+
+
+ 1. Stop the Instance. Replace `{zone}` with the Availability Zone of your Instance. This value can be `fr-par-1` for Instances located in Paris, for example. Replace `{server_id}` with the ID of your Instance.
+
+ Request:
+ ```
+ curl -X POST -H "X-Auth-Token: $SCW_SECRET_KEY" -H "Content-Type: application/json" -d '{"action" : "poweroff"}' "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}/action"
+ ```
+
+ Output:
+ ```
+ {
+ "task":{
+ "id":"cd1cf3da-6dee-4c96-bc86-f4fe848f36d4",
+ "description":"server_poweroff",
+ "status":"pending",
+ "href_from":"/servers/85bde2188-1657-11ee-be56-0242ac120002/action",
+ "href_result":"/servers/85bde2188-1657-11ee-be56-0242ac120002",
+ "started_at":"2023-06-29T08:20:36.927830+00:00",
+ "terminated_at":null
+ }
+ }
+ ```
+
+ 2. Update the `commercial_type` of your Instance.
+
+ Request:
+ ```
+ curl -X PATCH -H "X-Auth-Token: $SCW_SECRET_KEY" -H "Content-Type: application/json" -d '{"commercial_type" : ""}' "https://api.scaleway.com/instance/v1/zones/{zone}/servers/{server_id}"
+ ```
+
+ Local Storage constraints must be respected. For example, downgrading a DEV1-L Instance with 80 GB of local SSD storage to a DEV1-S Instance is not possible because the DEV1-S offer only supports a maximum of 20 GB. However, if the DEV1-L Instance is only using Block Storage (`b_ssd`) without relying on local SSD storage, the downgrade can be performed without any issues.
+
+
+ Output:
+ ```
+ {
+ "server":{
+ "id":"85bde2188-1657-11ee-be56-0242ac120002",
+ "name":"scw-agitated-banach",
+ "arch":"x86_64",
+ "commercial_type":"PLAY2-MICRO", # New commercial type of the Instance
+ "boot_type":"local",
+ "organization":"a6a05c73-fa53-46a4-9ea1-e53b4f625527",
+ "project":"a6a05c73-fa53-46a4-9ea1-e53b4f625527",
+ "hostname":"scw-agitated-banach",
+ "image":{
+ "id":"ce453858-557c-4f1c-a7a9-70026e67d054",
+ "name":"Ubuntu 22.04 Jammy Jellyfish",
+ "organization":"4ce7eb1c-1659-11ee-be56-0242ac120002",
+ "project":"4ce7eb1c-1659-11ee-be56-0242ac120002",
+ "root_volume":{
+ "id":"30e9c843-1cdb-4bd4-96f7-cac26051eeaf",
+ "name":"Ubuntu 22.04 Jammy Jellyfish",
+ "volume_type":"b_ssd",
+ "size":10000000000
+ },
+ [...]
+ ```
+
+ 3. Power on the Instance.
+
+ Request:
+ ```
+ curl -X POST -H "X-Auth-Token: $SCW_SECRET_KEY" -H "Content-Type: application/json" -d '{"action" : "poweron"}' "https://api.scaleway.com/instance/v1/{zone}/servers/{server_id}/action"
+ ```
+
+ Output:
+ ```
+ {
+ "task":{
+ "id":"aca94c37-86b0-4c9a-8df0-3bc13cd568ac",
+ "description":"server_batch_poweron",
+ "status":"pending",
+ "href_from":"/servers/85bde2188-1657-11ee-be56-0242ac120002/action",
+ "href_result":"/servers/85bde2188-1657-11ee-be56-0242ac120002",
+ "started_at":"2023-06-29T08:27:49.409220+00:00",
+ "terminated_at":null
+ }
+ }
+ ```
+
+ For more information on using the API, refer to the complete [API documentation](https://www.scaleway.com/en/developers/api/instance/).
+
+
\ No newline at end of file
diff --git a/pages/instances/api-cli/snapshot-import-export-feature.mdx b/pages/instances/api-cli/snapshot-import-export-feature.mdx
new file mode 100644
index 0000000000..e4fa056e20
--- /dev/null
+++ b/pages/instances/api-cli/snapshot-import-export-feature.mdx
@@ -0,0 +1,180 @@
+---
+meta:
+ title: Using the snapshot import/export feature with the API
+ description: This page explains how to import/export Instance snapshots using the Scaleway API
+content:
+ h1: Using the snapshot import/export feature with the API
+ paragraph: This page explains how to import/export Instance snapshots using the Scaleway API
+tags: snapshot import export api instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-07-25
+categories:
+ - compute
+---
+
+The snapshot transfer feature allows you to export or import Instances snapshots.
+Snapshots are created using the QCOW2 format and their data is stored in a Scaleway Object Storage Bucket. These images can then be used to create a copy of an Instance in a different AZ.
+
+More information on the QCOW2 file format, and how to use it can be found in the [QEMU documentation](https://www.qemu.org/docs/master/system/images.html#cmdoption-image-formats-arg-qcow2).
+
+
+ This page shows you how to use the snapshot import/export feature with the Scaleway API. The import/export feature is also available in the console, CLI, and SDK.
+
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/) with [Block Storage volumes](/block-storage/how-to/create-a-volume/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+- A [snapshot](/instances/how-to/create-a-snapshot/)
+- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/)
+
+## Exporting snapshots
+
+1. Create a Scaleway Object Storage bucket.
+
+ You need an Object Storage bucket to export your QCOW2 file into. Any bucket that belongs to the same project as the snapshot can be used. However, if you do not have one already, you can [create it](/object-storage/how-to/create-a-bucket/) in the console.
+2. Create a snapshot from a volume.
+
+ To use this functionality, you must [create a snapshot](/instances/how-to/create-a-snapshot/#how-to-create-a-snapshot) from the volume you want to export.
+3. Call the `export` snapshot API endpoint to initiate the snapshot export.
+
+ For example, using curl:
+ ```sh
+ curl -X POST https://api.scaleway.com/instance/v1/zones/fr-par-1/snapshots//export \
+ -H "X-Auth-Token: " \
+ -H "Content-Type: application/json" \
+ --data '{"bucket": "my-bucket", "key": "my-exported-snapshot.qcow2"}'
+ ```
+ The following information is required to run the command above:
+ - The Availability Zone of the snapshot (here: `fr-par-1`)
+ - The secret key of your API key pair (``)
+ - The snapshot ID (``)
+ - The name of the Object Storage bucket to store the snapshot (which has to exist in the same Scaleway region as the snapshot)
+ - A key (can be any acceptable key/object name for Scaleway Object Storage (suffixing qcow2 images with `.qcow2`))
+
+ The API returns an output as in the following example:
+ ```json
+ {
+ "task": {
+ "id": "",
+ "description": "export_snapshot",
+ "status": "pending",
+ "href_from": "/snapshots//export",
+ "href_result": "https://s3.fr-par.scw.cloud/my-bucket/my-exported-snapshot.qcow2",
+ "started_at": "2022-07-25T15:23:49.278630+00:00",
+ "terminated_at": null
+ }
+ }
+ ```
+
+
+ Snapshots should have a volume size between one gigabyte (GB) and one terabyte (TB).
+
+
+## Importing snapshots
+
+Any snapshot (a valid QCOW2 image) imported to a Scaleway Object Storage bucket can be imported into Instances in the same region as the snapshot. This allows you to create Instances in other Availability Zones within the same region, for example, you can deploy Instances in `fr-par-2` based on the snapshot exported from an Instance in `fr-par-1`.
+
+Call the `import` snapshot API endpoint to initiate the snapshot import.
+
+For example, using curl:
+
+```sh
+curl -X POST https://api.scaleway.com/instance/v1/zones/fr-par-2/snapshots/ \
+-H "X-Auth-Token: " -H "Content-Type: application/json" \
+--data '{"bucket": "my-bucket", "key": "my-exported-snapshot.qcow2", "volume_type": "b_ssd", "project": "", "name": "my-imported-snapshot"}'
+```
+
+The following information is required to run the command above:
+ - The Availability Zone of the snapshot (here: `fr-par-2`)
+ - The secret key of your API key pair (``)
+ - The name of the Object Storage bucket holding the snapshot (which has to exist in the same Scaleway region as the snapshot)
+ - The object name of the QCOW2 image
+
+ - The snapshot's volume type (It can be `l_ssd` or `b_ssd`.)
+ - A Scaleway Project UUID
+ - The name of the newly created snapshot (used to identify the snapshot in the Console)
+ - **Optional**: A size parameter. If missing, the size of the created snapshot is defaulted to the QCOW2's volume size.
+
+The API returns an output as in the following example:
+
+```json
+{
+"snapshot": {
+ "id": "",
+ "name": "my-imported-snapshot",
+ "volume_type": "b_ssd",
+ "creation_date": "2022-07-25T15:27:48.654782+00:00",
+ "modification_date": "2022-07-25T15:27:48.654782+00:00",
+ "organization": "",
+ "project": "",
+ "size": 10737418240,
+ "state": "importing",
+ "base_volume": null,
+ "tags": [],
+ "zone": "fr-par-2",
+ "error_details": null
+},
+"task": {
+ "id": "",
+ "description": "import_snapshot",
+ "status": "pending",
+ "href_from": "/snapshots/",
+ "href_result": "snapshots/",
+ "started_at": "2022-07-25T15:27:48.797883+00:00",
+ "terminated_at": null
+}
+}
+```
+
+Once the snapshot has been imported, it becomes available in the list of snapshots in the `fr-par-2` AZ:
+
+
+ The Instance snapshot will be created as soon as the API call returns, but the import action will take several minutes to complete. In the meantime, the snapshot will be in the `importing` state, before becoming `available` once the import is successful.
+
+ ```sh
+ curl -X GET https://api.scaleway.com/instance/v1/zones/fr-par-2/snapshots/ \
+ -H "X-Auth-Token: " | jq ".snapshot.state" "importing"
+ ```
+
+
+
+## Import constraints and error handling
+
+Currently, some features of the QCOW2 format are not handled; the import request will not accept images using these features.
+
+These features are:
+
+- Encryption
+ API response sample:
+ ```json
+ {
+ "message": "The provided QCOW2 file is encrypted",
+ "type": "invalid_request_error"
+ }
+ ```
+- ZSTD compression
+ API response sample:
+ ```json
+ {
+ "message": "The provided QCOW2 has an unsupported compression type",
+ "type": "invalid_request_error"
+ }
+ ```
+- Backing files
+ API response sample:
+ ```json
+ {
+ "message": "The provided QCOW2 file has a backing chain",
+ "type": "invalid_request_error"
+ }
+ ```
+
+
+ The API might raise other errors if it cannot find the provided object, if the object is not a valid QCOW2 image, if the volume is bigger than one terabyte, etc.
+
+
+
diff --git a/pages/instances/api-cli/using-cloud-init.mdx b/pages/instances/api-cli/using-cloud-init.mdx
new file mode 100644
index 0000000000..ce7a736947
--- /dev/null
+++ b/pages/instances/api-cli/using-cloud-init.mdx
@@ -0,0 +1,93 @@
+---
+meta:
+ title: Using cloud-init with Scaleway API and CLI
+ description: Learn how to effectively use cloud-init with Scaleway API and CLI for seamless cloud infrastructure deployment.
+content:
+ h1: Using cloud-init with Scaleway API and CLI
+ paragraph: Learn how to effectively use cloud-init with Scaleway API and CLI for seamless cloud infrastructure deployment.
+tags: cloud-init cloud init scaleway-api cli
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+Cloud-init is a package that contains utilities for early initialization of cloud Instances. It enables automatic configuration of cloud Instances as it boots into the cloud, turning it from a generic Ubuntu image into a configured server in a few seconds, quickly and easily.
+
+The cloud-init program is available on recent distributions (Ubuntu, Fedora, Debian) and can consume and execute data from the `user-data` field of the Scaleway service. This process behaves differently depending on the format of the information it finds. One of the most popular formats for scripts within `user-data` is the cloud-config file format.
+
+Cloud-config files are special scripts designed to be run by the cloud-init process. These are generally used for initial configuration on the very first boot of a server.
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+- Downloaded the [latest version of the Scaleway CLI](https://github.com/scaleway/scaleway-cli)
+
+## Provisioning your Instance with Cloud-Init
+
+You can give provisioning instructions to cloud-init using the `cloud-init` key of the `user_data` facility.
+
+For `user_data` to be effective, it has to be added prior to the creation of the instance since `cloud-init` gets activated early in the first phases of the boot process.
+
+* **Server ID** refers to the unique identification string of your server. It will be displayed when you create your server. You can also recover it from the list of your servers, by typing `scw instance server list`.
+
+1. Create your Instance by specifying the path to your cloud-init configuration file.
+ ```
+ scw instance server create image=ubuntu_focal name=myinstance cloud-init=@/path/to/cloud-config-file
+ ```
+
+ `@/path/to/cloud-config-file` is the path of your [Cloud-Init](/instances/how-to/use-boot-modes/#how-to-use-cloud-init) configuration file. Edit it as you wish.
+
+2. Start your Instance
+ ```
+ scw start {server Id}
+ ```
+
+ Since [version 2.3.1](https://github.com/scaleway/scaleway-cli/releases/tag/v2.3.1) of the Scaleway CLI a shorter command is available:
+
+ ```
+ scw instance server create image=ubuntu_focal name=myinstance cloud-init=@/path/to/cloud-config-file
+ ```
+
+## Cloud-Init CLI (Command Line Interface)
+
+The command line documentation is accessible on any cloud-init installed system.
+
+````
+% cloud-init --help
+usage: cloud-init [-h] [--version] [--file FILES]
+
+ [--debug] [--force]
+ {init,modules,single,dhclient-hook,features,analyze,devel,collect-logs,clean,status}
+ ...
+
+optional arguments:
+ -h, --help show this help message and exit
+ --version, -v show program's version number and exit
+ --file FILES, -f FILES
+ additional yaml configuration files to use
+ --debug, -d show additional pre-action logging (default: False)
+ --force force running even if no datasource is found (use at
+ your own risk)
+
+Subcommands:
+ {init,modules,single,dhclient-hook,features,analyze,devel,collect-logs,clean,status}
+ init initializes cloud-init and performs initial modules
+ modules activates modules using a given configuration key
+ single run a single module
+ dhclient-hook run the dhclient hookto record network info
+ features list defined features
+ analyze Devel tool: Analyze cloud-init logs and data
+ devel Run development tools
+ collect-logs Collect and tar all cloud-init debug info
+ clean Remove logs and artifacts so cloud-init can re-run.
+ status Report cloud-init status or wait on completion.
+
+````
+
+For detailed information on cloud-init, refer to the official cloud-init [documentation](http://cloudinit.readthedocs.io/en/latest/index.html).
+
+
diff --git a/pages/instances/api-cli/using-placement-groups.mdx b/pages/instances/api-cli/using-placement-groups.mdx
new file mode 100644
index 0000000000..ce7cf7db47
--- /dev/null
+++ b/pages/instances/api-cli/using-placement-groups.mdx
@@ -0,0 +1,213 @@
+---
+meta:
+ title: Using placement groups with the API
+ description: This page shows you how to use placement groups on Instances using the Scaleway API
+content:
+ h1: Using placement groups with the API
+ paragraph: This page shows you how to use placement groups on Instances using the Scaleway API
+categories:
+ - compute
+tags: compute placement-group server api instance
+dates:
+ validation: 2024-08-05
+---
+
+Placement groups allow you to group your Instances.
+
+You can choose between two operating modes: `max_availability`, which ensures that Instances of a group do not run on the same underlying hardware, and `low_latency`, which brings Instances closer together to achieve higher network throughput.
+
+If you prefer a visual environment, discover [how to manage placement groups from the Scaleway console](/instances/how-to/use-placement-groups/).
+
+
+
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+## Understanding placement groups
+
+Placement groups work for all Instance ranges in the same Availability Zone without any architecture or type distinction. It means that GP1, DEV1, ARM64, or all the future virtualized ranges can be part of the same placement group. However, they are not compatible with Elastic Metal servers.
+
+A placement group is composed of three mandatory fields:
+- Name,
+- Policy type,
+- Policy mode.
+
+**Name** is a free text field.
+
+### Policy types
+
+The policy type enables the choice of placement behavior for underlying Instances. It can be set to either `low_latency` or `max_availability`.
+
+The low latency policy groups your Instances on the nearest hardware and limits network latency, allowing the highest network throughput between servers. At best, Instances will be placed on the same hypervisor.
+
+The maximum availability policy spreads the Instances on far-away hypervisors as much as possible. It will limit the impact in case of hardware failure. For this policy, the Instances may be placed anywhere in the same Availability Zone.
+
+### Policy modes
+
+The policy mode selects the Instance's allocation behavior if the placement constraint cannot be respected. Policy mode can be set to either `optional` or `enforced`.
+
+When the policy mode is set to optional then failing to respect the placement policy still allocates the server. When the policy mode is set to enforced then failing to respect the placement policy results in not allocating the server.
+
+## Checking a group status
+
+When several Instances are part of the same placement group, it is possible to query the full group status and then check the field `policy_respected`. This field indicates if the selected policy is respected or not. It returns `true` if the policy is respected, and `false` otherwise.
+
+To get the placement information for a single server, query its server object. In the result, check the field `placement_group`. Likewise, it will be true if the placement is respected or false if it is not.
+
+## Creating a placement group
+
+As a practical application, we will see how to set up two Instances that should never run on the same hardware. To do so, we will create a `max_availability`type placement group with the `enforced` policy.
+
+First, let us create the placement group with the appropriate `policy_type` and `policy_mode` fields:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X POST \
+ -d '{"name": "cc-test", "policy_mode": "optional", "policy_type": "max_availability", "organization": "c2d2fe22-6b5a-4f09-abae-cb1d633f1533"}' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/
+```
+
+A query to the placement group prints the current operation mode of the group:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/ae5c1189-f421-4285-988b-80d29267ddc4
+{
+ "placement_group": {
+ "name": "cc-test",
+ "policy_mode": "enforced",
+ "policy_type": "max_availability",
+ "organization": "c2d2fe22-6b5a-4f09-abae-cb1d633f1533",
+ "policy_respected": true,
+ "id": "ae5c1189-f421-4285-988b-80d29267ddc4"
+ }
+```
+
+The `policy_respected` field is set to `true` as there is no server in the group at the moment.
+
+To list Instances that belong to the group, use the `/placement_groups/*/servers` API endpoint:
+
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/ae5c1189-f421-4285-988b-80d29267ddc4/servers
+{
+ "servers": []
+}
+```
+
+Our group is empty at the moment, so this is perfectly normal.
+
+## Adding multiple existing Instances to a placement group
+
+Once a placement group is created, you can add existing Instances in it. To do so, just call a PUT method on the `/placement_groups/*/servers` endpoint.
+
+Before adding Instances to a group, ensure that they are all powered off. The placement procedure cannot work with a running server.
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X PUT \
+ -d '{"servers": ["a3505194-b875-4bda-87c0-058466a6ea6d", "dab279bc-aa4d-4ba1-841c-ba04cc23eb00"]}' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/ae5c1189-f421-4285-988b-80d29267ddc4
+{
+ "servers": [
+ {
+ "policy_respected": true,
+ "id": "a3505194-b875-4bda-87c0-058466a6ea6d",
+ "name": "elated-lamport"
+ },
+ {
+ "policy_respected": true,
+ "id": "dab279bc-aa4d-4ba1-841c-ba04cc23eb00",
+ "name": "elegant-brown"
+ }
+ ]
+}
+```
+
+The group now contains the two servers. If one of the servers was running, the API would have returned the error:
+
+```
+{
+ "message": "One or more servers are invalid",
+ "type": "invalid_request_error"
+}
+```
+
+## Adding a single Instance to a placement group
+
+A single Instance can also be directly added to a placement group. Again, the server must be off before doing so:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X PATCH -d '{"placement_group": "ae5c1189-f421-4285-988b-80d29267ddc4"}'
+ \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/servers/a3505194-b875-4bda-87c0-058466a6ea6d
+```
+
+In addition, an Instance can be created directly into a placement group by filing the `placement_group` field in the server creation API call.
+
+## Removing an Instance from a placement group
+
+An Instance, running or stopped, can be removed at any time from a placement group by setting its `placement_group` property to `null`:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X PATCH -d '{"placement_group": null}' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/servers/dab279bc-aa4d-4ba1-841c-ba04cc23eb00
+```
+
+Remember that the Instance must be archived to be made part of a group so be
+careful.
+
+
+After that call, we only have one server left in our group:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/ae5c1189-f421-4285-988b-80d29267ddc4/servers
+{
+ "servers": [
+ {
+ "policy_respected": true,
+ "id": "a3505194-b875-4bda-87c0-058466a6ea6d",
+ "name": "elated-lamport"
+ }
+ ]
+}
+```
+
+It is also possible to remove all Instances from a placement group with a DELETE call on the API endpoint `/placement_groups/*/servers`:
+
+```
+curl -q \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H 'Content-Type: application/json' \
+ -X DELETE \
+ https://api.scaleway.com/instance/v1/zones/fr-par-1/placement_groups/ae5c1189-f421-4285-988b-80d29267ddc4/servers
+
+```
+
+We hope that placement groups will help you build more performant and more reliable systems with Scaleway's products.
+
+For more information and to see the full capabilities of placement groups, refer to the [full API documentation](https://www.scaleway.com/en/developers/api/instance/#path-placement-groups).
+
+Remember that a placement group will work only according to the following rules:
+- Instances must be in the same Availability Zone,
+- An Instance can be in only one group at a time,
+- A running Instance cannot be modified and should be archived.
+
+
diff --git a/pages/instances/api-cli/using-routed-ips.mdx b/pages/instances/api-cli/using-routed-ips.mdx
new file mode 100644
index 0000000000..d8f61c7b83
--- /dev/null
+++ b/pages/instances/api-cli/using-routed-ips.mdx
@@ -0,0 +1,1006 @@
+---
+meta:
+ title: Routing public IPs to Instances using the Scaleway CLI/API
+ description: This page explains how to route public IPs to Instances using the Scaleway CLI/API
+content:
+ h1: Routing public IPs to Instances using the Scaleway CLI/API
+ paragraph: This page explains how to route public IPs to Instances using the Scaleway CLI/API
+tags: routed ip cloud scaleway-api transition
+dates:
+ validation: 2025-01-02
+ posted: 2023-05-17
+categories:
+ - compute
+---
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+
+
+ * The routed IP feature **is not compatible** with legacy Instance types using the bootscript feature.
+ * If you are using a manual DHCP configuration on the public NIC, ensure that it is compatible with a routed IP setup.
+ * You must update the `scw` and `cloud-init` packages before starting the transition.
+
+
+
+ This guide is part of Scaleway's [IP Mobility project](https://www.scaleway.com/en/blog/ip-mobility-removing-nat/) and will evolve over time.
+
+
+During the deployment of an Instance, a private IP address linked to the underlying node hosting the Instance is assigned to it. If the underlying physical node changes, the private IP address will also change accordingly.
+
+This change can occur when you stop and restart your Instance. This private network enables communication between Instances without the need for a public IP address.
+In addition, the public network is provided by a network component that manages a carrier-grade NAT (Network Address Translation), establishing a one-to-one mapping between the flexible IP and the private IP assigned to the Instance during provisioning.
+
+When routing a public IP directly to an Instance, private IPs are no longer in use. Instead, traffic is routed directly to the flexible IP of the Instance. The main advantage of this approach is that your underlying IP remains unchanged when you stop and start the Instance or when it gets provisioned on another hypervisor. However, it also means that it will not have network access if you do not attach any flexible IP to your Instance.
+Another feature of routed IP is the ability to assign multiple flexible IP addresses to your Instance, allowing you to use both IPv4 and IPv6 protocols.
+
+
+ * The routed IP feature is available in all Availability Zones.
+ * [Dynamic IPs](/instances/concepts/#dynamic-ip) continue to be supported after the transition to routed IPs.
+ * The field `enable_ipv6` is being deprecated and has no meaning for routed IP enabled Instances.
+
+
+## How to use routed IPs with the Scaleway CLI
+
+Since version 2.20.0, the [Scaleway CLI tool](https://github.com/scaleway/scaleway-cli) has native support for the routed IP feature.
+
+### Creating a routed IP Instance via CLI
+
+You can create a new routed IP-enabled Instance using the following command:
+```
+❯ scw instance server create routed-ip-enabled=true zone=pl-waw-1
+```
+
+### Moving an existing Instance to routed IP via CLI
+
+To activate the routed IP feature on an existing Instance, you can move it with the command shown below.
+Any attached IPv4 will be transferred. However, the current IPv6 will be substituted with a new one. Once assigned, this new IPv6 will remain assigned to the Instance even through stop/start cycles.
+
+
+ Be aware that the Instance will reboot during this process.
+
+```
+❯ scw instance server enable-routed-ip 01e75c58-db6a-432c-914c-1e281a57d31e zone=pl-waw-1
+✅ Enable_routed_ip successfully started for the server.
+```
+
+### Creating a new routed IP (IPv4/IPv6) via CLI
+
+By using the `type=` field, you can create routed IPs, either as `routed_ipv4` or `routed_ipv6`. You can then assign the newly-created IP to your Instance.
+
+```
+❯ scw instance ip create type=routed_ipv6 zone=pl-waw-1
+```
+
+## How to use routed IPs with the API
+
+
+ Currently, routed IP is disabled by default. If you are interested in exploring its functionality, you need to explicitly enable it.
+
+
+In this section, we will guide you through the process of creating a new Instance with a routed IP. We will also provide instructions on moving your existing legacy Instances.
+
+ * The following examples rely on [httpie](https://httpie.io/cli), you can easily adapt them with curl if you prefer.
+ * The `API_URL` variable contains the following value: `https://api.scaleway.com/instance/v1/zones/`
+ * The `HEADERS` variable contains: `X-Auth-Token:`
+
+
+ Keep in mind that once the transition to routed IPs is complete, there is **no way to revert it**.
+
+
+### Creating a routed IP via the API
+
+You can request routed IPs using the Scaleway API. Available IP types are IPv4 and IPv6.
+
+
+
+ ```json
+ ❯ cat payloads/ip-data.json
+ {
+ "type": "routed_ipv6",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1"
+ }
+
+ ❯ http post $API_URL/ips $HEADERS
+ If you want an IPv4 address instead, replace the type `routed_ipv6` with `routed_ipv4`.
+
+
+
+ ```json
+ {
+ "ip": {
+ "address": null,
+ "id": "01ac2664-699e-46b5-80be-9d43d477857f",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "prefix": "2001:bc8:4e10:6::/64",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "reverse": null,
+ "server": null,
+ "state": "detached",
+ "tags": [],
+ "type": "routed_ipv6",
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+
+ Note that the field `address` will always be `null` with `"type": "routed_ipv6"` because in practice you get assigned a complete /64 prefix and not a single IP address. You will then find the prefix information within the `prefix` key.
+
+
+### Create a new Instance with a routed IP via the API
+
+Run the following command to create an Instance with the previously created IP address.
+
+
+
+ ```json
+ ❯ cat payloads/server-data.json
+ {
+ "name": "my-publicip-instance",
+ "commercial_type": "GP1-S",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "routed_ip_enabled": true,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public_ip": "01ac2664-699e-46b5-80be-9d43d477857f",
+ "image": "62f9eea9-61dc-4944-b420-069687a3238a"
+ }
+
+ ❯ http post $API_URL/servers $HEADERS
+ In order to create an Instance with a routed IP, you have to add `"routed_ip_enabled": true` to your payload.
+
+
+
+ ```json
+ {
+ "server": {
+ "allowed_actions": [
+ "poweron",
+ "backup"
+ ],
+ "arch": "x86_64",
+ "boot_type": "local",
+ "bootscript": {
+ "architecture": "x86_64",
+ "bootcmdargs": "LINUX_COMMON scaleway boot=local nbd.max_part=16",
+ "default": true,
+ "dtb": "",
+ "id": "9246a9bb-896c-464c-b6bd-b7443cd72c23",
+ "initrd": "http://10.195.3.9/initrd/initrd-Linux-x86_64-v3.14.6.gz",
+ "kernel": "http://10.195.3.9/kernel/x86_64-mainline-lts-4.4-4.4.182-rev1/vmlinuz-4.4.182",
+ "organization": "11111111-1111-4111-8111-111111111111",
+ "project": "11111111-1111-4111-8111-111111111111",
+ "public": true,
+ "title": "x86_64 mainline 4.4.182 rev1",
+ "zone": "pl-waw-2"
+ },
+ "commercial_type": "GP1-S",
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "extra_networks": [],
+ "hostname": "my-publicip-instance",
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb4",
+ "image": {
+ "arch": "x86_64",
+ "creation_date": "2022-11-17T16:50:34.380145+00:00",
+ "default_bootscript": null,
+ "extra_volumes": {},
+ "from_server": null,
+ "id": "eb40f656-1923-49b6-bb1d-53fe3a7329a0",
+ "modification_date": "2022-11-17T16:50:34.380145+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public": true,
+ "root_volume": {
+ "id": "ccc917ca-8250-4b7b-89a9-614f08b17826",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "size": 10000000000,
+ "volume_type": "b_ssd"
+ },
+ "state": "available",
+ "tags": [],
+ "zone": "pl-waw-2"
+ },
+ "ipv6": null,
+ "location": null,
+ "mac_address": "de:00:00:01:c2:37",
+ "maintenances": [],
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "my-publicip-instance",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "placement_group": null,
+ "private_ip": null,
+ "private_nics": [],
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "protected": false,
+ "public_ip": {
+ "address": "2001:bc8:4e10:6:dc00:00ff:fe01:c4b7",
+ "dynamic": false,
+ "family": "inet6",
+ "gateway": "fe80::dc00:00ff:fe01:c4b8",
+ "id": "92873598-d8e6-4d98-9254-697b3e56ff6b",
+ "netmask": "64",
+ "provisioning_mode": "slaac"
+ },
+ "public_ips": [
+ {
+ "address": "2001:bc8:4e10:6:dc00:00ff:fe01:c4b7",
+ "dynamic": false,
+ "family": "inet6",
+ "gateway": "fe80::dc00:00ff:fe01:c4b8",
+ "id": "92873598-d8e6-4d98-9254-697b3e56ff6b",
+ "netmask": "64",
+ "provisioning_mode": "slaac"
+ }
+ ],
+ "routed_ip_enabled": true,
+ "security_group": {
+ "id": "f4627d3b-d6f7-499d-924d-9bee71d191fa",
+ "name": "Default security group"
+ },
+ "state": "stopped",
+ "state_detail": "",
+ "tags": [],
+ "volumes": {
+ "0": {
+ "boot": false,
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "export_uri": null,
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb4",
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "server": {
+ "id": "c7f2eb0f-7537-43b1-be95-736087f81b54",
+ "name": "my-publicip-instance"
+ },
+ "size": 300000000000,
+ "state": "available",
+ "tags": [],
+ "volume_type": "l_ssd",
+ "zone": "pl-waw-2"
+ }
+ },
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+### Create a new Instance with one IPv4 only via the API
+
+First you need to create an IPv4 reservation, then create a new Instance with this public IP attached.
+
+
+
+ ```json
+ ❯ cat payloads/ip-data.json
+ {
+ "type": "routed_ipv4",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1"
+ }
+
+ ❯ http post $API_URL/ips $HEADERS
+
+ ```json
+ {
+ "ip": {
+ "address": "51.159.123.86",
+ "id": "01ac2664-699e-46b5-80be-9d43d477858f",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "prefix": null,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "reverse": null,
+ "server": null,
+ "state": "detached",
+ "tags": [],
+ "type": "routed_ipv4",
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+And now we create the Instance.
+
+
+
+ ```json
+ ❯ cat payloads/server-data.json
+ {
+ "name": "my-publicipv4-instance",
+ "commercial_type": "GP1-S",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "routed_ip_enabled": true,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public_ip": "01ac2664-699e-46b5-80be-9d43d477858f",
+ "image": "62f9eea9-61dc-4944-b420-069687a3238a"
+ }
+
+ ❯ http post $API_URL/servers $HEADERS
+ In order to create an Instance with a routed IP, you have to add `"routed_ip_enabled": true` to your payload.
+
+
+
+ ```json
+ {
+ "server": {
+ "allowed_actions": [
+ "poweron",
+ "backup"
+ ],
+ "arch": "x86_64",
+ "boot_type": "local",
+ "bootscript": {
+ "architecture": "x86_64",
+ "bootcmdargs": "",
+ "default": true,
+ "dtb": "",
+ "id": "9246a9bb-896c-464c-b6bd-b7443cd72c23",
+ "initrd": "",
+ "kernel": "",
+ "organization": "11111111-1111-4111-8111-111111111111",
+ "project": "11111111-1111-4111-8111-111111111111",
+ "public": true,
+ "title": "Default",
+ "zone": "pl-waw-2"
+ },
+ "commercial_type": "GP1-S",
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "extra_networks": [],
+ "hostname": "my-publicipv6-instance",
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb5",
+ "image": {
+ "arch": "x86_64",
+ "creation_date": "2022-11-17T16:50:34.380145+00:00",
+ "default_bootscript": null,
+ "extra_volumes": {},
+ "from_server": null,
+ "id": "62f9eea9-61dc-4944-b420-069687a3238a",
+ "modification_date": "2022-11-17T16:50:34.380145+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public": true,
+ "root_volume": {
+ "id": "ccc917ca-8250-4b7b-89a9-614f08b17826",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "size": 10000000000,
+ "volume_type": "b_ssd"
+ },
+ "state": "available",
+ "tags": [],
+ "zone": "pl-waw-2"
+ },
+ "ipv6": null,
+ "location": null,
+ "mac_address": "de:00:00:05:29:93",
+ "maintenances": [],
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "my-publicipv6-instance",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "placement_group": null,
+ "private_ip": null,
+ "private_nics": [],
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "protected": false,
+ "public_ip": {
+ "address": "51.159.123.86",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "fe80::dc00:00ff:fe05:2994",
+ "id": "01ac2664-699e-46b5-80be-9d43d477858f",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ },
+ "public_ips": [
+ {
+ "address": "51.159.123.86",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "62.210.0.1",
+ "id": "01ac2664-699e-46b5-80be-9d43d477858f",
+ "netmask": "32",
+ "provisioning_mode": "slaac"
+ }
+ ],
+ "routed_ip_enabled": true,
+ "security_group": {
+ "id": "f4627d3b-d6f7-499d-924d-9bee71d191fa",
+ "name": "Default security group"
+ },
+ "state": "stopped",
+ "state_detail": "",
+ "tags": [],
+ "volumes": {
+ "0": {
+ "boot": false,
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "export_uri": null,
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb4",
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "server": {
+ "id": "c7f2eb0f-7537-43b1-be95-736087f81b54",
+ "name": "my-publicip-instance"
+ },
+ "size": 300000000000,
+ "state": "available",
+ "tags": [],
+ "volume_type": "l_ssd",
+ "zone": "pl-waw-2"
+ }
+ },
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+### Create a dual stack IPv4/IPv6 Instance
+
+You can now attach several IPs to one public IP enabled Instance and you can mix up both IPv4 and IPv6 addresses.
+We assume you create multiple IPs as described in the [example](#creating-a-routed-ip-via-the-api).
+
+Then you can create a new Instance using those IPs through the `public_ips` field.
+
+
+ Not to be confused with the `public_ip` field that only accepts *one* IP.
+
+
+
+
+ ```json
+ ❯ cat payloads/server-data.json
+ {
+ "name": "my-publicip-instance-multi",
+ "commercial_type": "GP1-S",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "routed_ip_enabled": true,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public_ips": ["01ac2664-699e-46b5-80be-9d43d477868f", "487e556c-0351-4a12-9762-4f33bc2c2379", "92873598-d8e6-4d98-9254-697b3e56ff6b"],
+ "image": "62f9eea9-61dc-4944-b420-069687a3238a"
+ }
+
+ ❯ http post $API_URL/servers $HEADERS
+ In order to create Instance you have to add `"routed_ip_enabled": true` to your payload.
+
+
+
+ ```json
+ {
+ "server": {
+ "allowed_actions": [
+ "poweron",
+ "backup"
+ ],
+ "arch": "x86_64",
+ "boot_type": "local",
+ "bootscript": {
+ "architecture": "x86_64",
+ "bootcmdargs": "",
+ "default": true,
+ "dtb": "",
+ "id": "9246a9bb-896c-464c-b6bd-b7443cd72c23",
+ "initrd": "",
+ "kernel": "",
+ "organization": "11111111-1111-4111-8111-111111111111",
+ "project": "11111111-1111-4111-8111-111111111111",
+ "public": true,
+ "title": "Default",
+ "zone": "pl-waw-2"
+ },
+ "commercial_type": "GP1-S",
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "extra_networks": [],
+ "hostname": "my-publicip-instance-multi",
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb5",
+ "image": {
+ "arch": "x86_64",
+ "creation_date": "2022-11-17T16:50:34.380145+00:00",
+ "default_bootscript": null,
+ "extra_volumes": {},
+ "from_server": null,
+ "id": "62f9eea9-61dc-4944-b420-069687a3238a",
+ "modification_date": "2022-11-17T16:50:34.380145+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public": true,
+ "root_volume": {
+ "id": "ccc917ca-8250-4b7b-89a9-614f08b17826",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "size": 10000000000,
+ "volume_type": "b_ssd"
+ },
+ "state": "available",
+ "tags": [],
+ "zone": "pl-waw-2"
+ },
+ "ipv6": null,
+ "location": null,
+ "mac_address": "de:00:00:05:29:93",
+ "maintenances": [],
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "my-publicip-instance-multi",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "placement_group": null,
+ "private_ip": null,
+ "private_nics": [],
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "protected": false,
+ "public_ip": {
+ "address": "151.115.74.36",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "62.210.0.1",
+ "id": "01ac2664-699e-46b5-80be-9d43d477868f",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ },
+ "public_ips": [
+ {
+ "address": "151.115.74.36",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "62.210.0.1",
+ "id": "01ac2664-699e-46b5-80be-9d43d477868f",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ },
+ {
+ "address": "151.115.78.170",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "62.210.0.1",
+ "id": "487e556c-0351-4a12-9762-4f33bc2c2379",
+ "netmask": "32",
+ "provisioning_mode": "manual"
+ },
+ {
+ "address": "2001:bc8:4e10:6:dc00:00ff:fe01:c4b7",
+ "dynamic": false,
+ "family": "inet6",
+ "gateway": "fe80::dc00:00ff:fe01:c4b8",
+ "id": "92873598-d8e6-4d98-9254-697b3e56ff6b",
+ "netmask": "64",
+ "provisioning_mode": "slaac"
+ }
+ ],
+ "routed_ip_enabled": true,
+ "security_group": {
+ "id": "f4627d3b-d6f7-499d-924d-9bee71d191fa",
+ "name": "Default security group"
+ },
+ "state": "stopped",
+ "state_detail": "",
+ "tags": [],
+ "volumes": {
+ "0": {
+ "boot": false,
+ "creation_date": "2023-02-05T21:30:31.779606+00:00",
+ "export_uri": null,
+ "id": "7981f24a-1760-41b4-81ba-ec5d3868ccb4",
+ "modification_date": "2023-02-05T21:30:31.779606+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "server": {
+ "id": "c7f2eb0f-7537-43b1-be95-736087f81b54",
+ "name": "my-publicip-instance"
+ },
+ "size": 300000000000,
+ "state": "available",
+ "tags": [],
+ "volume_type": "l_ssd",
+ "zone": "pl-waw-2"
+ }
+ },
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+ You will find the configuration of your IPs within the `public_ips` key. Note that IPs with a `provisioning_mode` in `DHCP` or `SLAAC`
+ are automatically configured, whereas `manual` might need manual configuration unless you are using one of our supported OS Images
+ in which case `cloud-init` should take care of any extra IPs at boot time.
+
+
+
+
+### Moving existing Instances to routed IPs via the API
+
+You can use a specific server action to move an existing (legacy network) Instance to routed IPs.
+
+
+
+ ```json
+ ❯ http post $API_URL/servers/$SERVER_ID/action $HEADERS action=enable_routed_ip
+ ```
+
+ Your instance *will* reboot during this action.
+
+
+
+ ```json
+ {
+ "task": {
+ "description": "server_enable_routed_ip",
+ "href_from": "/servers/534c2d3c-5ce2-49dd-b82e-77f6e4eb0587/action",
+ "href_result": "/servers/534c2d3c-5ce2-49dd-b82e-77f6e4eb0587",
+ "id": "879f8362-2ee7-4aac-8df4-9a6cd9fdf7c5",
+ "started_at": "2023-05-16T15:57:39.793534+00:00",
+ "status": "pending",
+ "terminated_at": null
+ }
+ }
+ ```
+
+
+
+### Verifying if an IP is routed or NAT type via the API
+
+You can verify if your IP is a routed IP or a NAT IP through the `/ips` endpoint:
+
+
+
+ ```json
+ ❯ http $API_URL/ips/201f52df-3c83-4eeb-aff4-038bb15f918d $HEADERS
+ ```
+
+
+ Response for an Instance with IP type **NAT**:
+ ```json
+ {
+ "ip": {
+ "address": "51.159.123.5",
+ "id": "201f52df-3c83-4eeb-aff4-038bb15f918d",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "prefix": null,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "reverse": null,
+ "server": {
+ "id": "9515993f-f596-4b51-84e8-9e48f2d49eb8",
+ "name": "cli-srv-youthful-cerf"
+ },
+ "state": "attached",
+ "tags": [],
+ "type": "nat",
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+ Compared to the previous response, an Instance with routed IP would have a different `type`:
+ ```json
+ {
+ "ip": {
+ "address": "51.158.38.9",
+ "id": "7a3f042d-6da4-42cd-b618-fae08348c8fe",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "prefix": null,
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "reverse": null,
+ "server": null,
+ "state": "detached",
+ "tags": [],
+ "type": "routed_ipv4",
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+### Verifying routed IPs are enabled for your Instance via the API
+
+You can verify if your Instance is enabled for routed IPs through the `/servers` endpoint:
+
+
+
+ ```json
+ ❯ http $API_URL/servers/9515993f-f596-4b51-84e8-9e48f2d49eb8 $HEADERS
+ ```
+
+
+ Response for an Instance with IP type **NAT**:
+ ```json
+ {
+ "server": {
+ "allowed_actions": [
+ "poweroff",
+ "terminate",
+ "reboot",
+ "stop_in_place",
+ "backup",
+ "enable_routed_ip"
+ ],
+ "arch": "x86_64",
+ "boot_type": "local",
+ "bootscript": {
+ "architecture": "x86_64",
+ "bootcmdargs": "LINUX_COMMON scaleway boot=local nbd.max_part=16",
+ "default": true,
+ "dtb": "",
+ "id": "9246a9bb-896c-464c-b6bd-b7443cd72c23",
+ "initrd": "http://10.195.3.9/initrd/initrd-Linux-x86_64-v3.14.6.gz",
+ "kernel": "http://10.195.3.9/kernel/x86_64-mainline-lts-4.4-4.4.182-rev1/vmlinuz-4.4.182",
+ "organization": "11111111-1111-4111-8111-111111111111",
+ "project": "11111111-1111-4111-8111-111111111111",
+ "public": true,
+ "title": "x86_64 mainline 4.4.182 rev1",
+ "zone": "pl-waw-2"
+ },
+ "commercial_type": "POP2-2C-8G",
+ "creation_date": "2023-05-11T12:54:57.008745+00:00",
+ "dynamic_ip_required": true,
+ "enable_ipv6": false,
+ "extra_networks": [],
+ "hostname": "cli-srv-youthful-cerf",
+ "id": "9515993f-f596-4b51-84e8-9e48f2d49eb8",
+ "image": {
+ "arch": "x86_64",
+ "creation_date": "2023-04-25T12:13:53.502807+00:00",
+ "default_bootscript": null,
+ "extra_volumes": {},
+ "from_server": null,
+ "id": "182b1177-7828-46db-a688-55e2e2dfac8f",
+ "modification_date": "2023-04-25T12:13:53.502807+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public": true,
+ "root_volume": {
+ "id": "72d9e5b6-60c6-499b-be03-03c9fb07daa3",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "size": 10000000000,
+ "volume_type": "b_ssd"
+ },
+ "state": "available",
+ "tags": [],
+ "zone": "pl-waw-2"
+ },
+ "ipv6": null,
+ "location": {
+ "cluster_id": "97",
+ "hypervisor_id": "301",
+ "node_id": "1",
+ "platform_id": "50",
+ "zone_id": "pl-waw-2"
+ },
+ "mac_address": "de:00:00:04:b8:89",
+ "maintenances": [],
+ "modification_date": "2023-05-11T13:57:30.645561+00:00",
+ "name": "cli-srv-youthful-cerf",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "placement_group": null,
+ "private_ip": "10.195.16.1",
+ "private_nics": [],
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "protected": false,
+ "public_ip": {
+ "address": "51.159.123.5",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": null,
+ "id": "201f52df-3c83-4eeb-aff4-038bb15f918d",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ },
+ "public_ips": [
+ {
+ "address": "51.159.123.5",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": null,
+ "id": "201f52df-3c83-4eeb-aff4-038bb15f918d",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ }
+ ],
+ "routed_ip_enabled": false,
+ "security_group": {
+ "id": "4867a63e-0021-42d0-8d31-b3c853f91c37",
+ "name": "Default security group"
+ },
+ "state": "running",
+ "state_detail": "booted",
+ "tags": [],
+ "volumes": {
+ "0": {
+ "boot": false,
+ "creation_date": "2023-05-11T12:54:57.008745+00:00",
+ "export_uri": null,
+ "id": "0afc1da9-d331-40b6-a7af-55af4cab1e22",
+ "modification_date": "2023-05-11T12:54:57.008745+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "server": {
+ "id": "9515993f-f596-4b51-84e8-9e48f2d49eb8",
+ "name": "cli-srv-youthful-cerf"
+ },
+ "size": 10000000000,
+ "state": "available",
+ "tags": [],
+ "volume_type": "b_ssd",
+ "zone": "pl-waw-2"
+ }
+ },
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+ Compared to the previous response, an Instance with routed IP would have the `routed_ip_enabled` flag set to `true`:
+ ```json
+ {
+ "server": {
+ "allowed_actions": [
+ "poweroff",
+ "terminate",
+ "reboot",
+ "stop_in_place",
+ "backup"
+ ],
+ "arch": "x86_64",
+ "boot_type": "local",
+ "bootscript": {
+ "architecture": "x86_64",
+ "bootcmdargs": "LINUX_COMMON scaleway boot=local nbd.max_part=16",
+ "default": true,
+ "dtb": "",
+ "id": "9246a9bb-896c-464c-b6bd-b7443cd72c23",
+ "initrd": "http://10.195.3.9/initrd/initrd-Linux-x86_64-v3.14.6.gz",
+ "kernel": "http://10.195.3.9/kernel/x86_64-mainline-lts-4.4-4.4.182-rev1/vmlinuz-4.4.182",
+ "organization": "11111111-1111-4111-8111-111111111111",
+ "project": "11111111-1111-4111-8111-111111111111",
+ "public": true,
+ "title": "x86_64 mainline 4.4.182 rev1",
+ "zone": "pl-waw-2"
+ },
+ "commercial_type": "GP1-S",
+ "creation_date": "2023-02-06T09:50:57.923789+00:00",
+ "dynamic_ip_required": false,
+ "enable_ipv6": false,
+ "extra_networks": [],
+ "hostname": "scw-ipmob-demo2",
+ "id": "aab4f033-2219-4937-b0e1-5b78c17f97bf",
+ "image": {
+ "arch": "x86_64",
+ "creation_date": "2022-11-17T16:50:34.380145+00:00",
+ "default_bootscript": null,
+ "extra_volumes": {},
+ "from_server": null,
+ "id": "eb40f656-1923-49b6-bb1d-53fe3a7329a0",
+ "modification_date": "2022-11-17T16:50:34.380145+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "public": true,
+ "root_volume": {
+ "id": "93dbf1e9-cd13-4f60-b427-6fa6b2ad5f99",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "size": 10000000000,
+ "volume_type": "b_ssd"
+ },
+ "state": "available",
+ "tags": [],
+ "zone": "pl-waw-2"
+ },
+ "ipv6": null,
+ "location": {
+ "cluster_id": "1",
+ "hypervisor_id": "201",
+ "node_id": "5",
+ "platform_id": "50",
+ "zone_id": "pl-waw-2"
+ },
+ "mac_address": "de:00:00:01:c4:b7",
+ "maintenances": [],
+ "modification_date": "2023-02-24T14:12:38.456780+00:00",
+ "name": "scw-ipmob-demo2",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "placement_group": null,
+ "private_ip": null,
+ "private_nics": [],
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "protected": false,
+ "public_ip": {
+ "address": "2001:bc8:4e10:6:dc00:00ff:dc00:1234",
+ "dynamic": false,
+ "family": "inet6",
+ "gateway": "fe80::dc00:00ff:fe01:c4b8",
+ "id": "e73c1b43-cd4b-4892-bd6f-fbd84a432a7b",
+ "netmask": "64",
+ "provisioning_mode": "slaac"
+ },
+ "public_ips": [
+ {
+ "address": "2001:bc8:4e10:6:dc00:00ff:dc00:1234",
+ "dynamic": false,
+ "family": "inet6",
+ "gateway": "fe80::dc00:00ff:fe01:c4b8",
+ "id": "e73c1b43-cd4b-4892-bd6f-fbd84a432a7b",
+ "netmask": "64",
+ "provisioning_mode": "slaac"
+ },
+ {
+ "address": "51.159.123.86",
+ "dynamic": false,
+ "family": "inet",
+ "gateway": "62.210.0.1",
+ "id": "dd2ea413-d12b-44da-b3c8-2f0f4c4db242",
+ "netmask": "32",
+ "provisioning_mode": "dhcp"
+ }
+ ],
+ "routed_ip_enabled": true,
+ "security_group": {
+ "id": "4867a63e-0021-42d0-8d31-b3c853f91c37",
+ "name": "Default security group"
+ },
+ "state": "running",
+ "state_detail": "booted",
+ "tags": [],
+ "volumes": {
+ "0": {
+ "boot": false,
+ "creation_date": "2023-02-06T09:50:57.923789+00:00",
+ "export_uri": null,
+ "id": "bc44ee3a-dd25-459a-bbd5-b7e604e8f9cf",
+ "modification_date": "2023-02-06T09:50:57.923789+00:00",
+ "name": "Ubuntu 22.04 Jammy Jellyfish",
+ "organization": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "project": "7ddae24a-ad61-4744-830c-079d1c66abe1",
+ "server": {
+ "id": "aab4f033-2219-4937-b0e1-5b78c17f97bf",
+ "name": "scw-ipmob-demo2"
+ },
+ "size": 300000000000,
+ "state": "available",
+ "tags": [],
+ "volume_type": "l_ssd",
+ "zone": "pl-waw-2"
+ }
+ },
+ "zone": "pl-waw-2"
+ }
+ }
+ ```
+
+
+
+
diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx
new file mode 100644
index 0000000000..064e517f0e
--- /dev/null
+++ b/pages/instances/concepts.mdx
@@ -0,0 +1,184 @@
+---
+meta:
+ title: Instances - Concepts
+ description: This page explains all the concepts related to Scaleway Instances
+content:
+ h1: Instances - Concepts
+ paragraph: This page explains all the concepts related to Scaleway Instances
+tags: region traffic availability-zone block-volume boot-on-block cloud-init dynamic-ip flexible-ip reverse-dns stardust
+dates:
+ validation: 2024-08-12
+categories:
+ - compute
+---
+
+## Availability Zone
+
+An Availability Zone refers to an isolated location within a specific region. Each Availability Zone provides its own services and infrastructure. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region.
+
+For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/)
+
+## Block volumes
+
+Block volumes provide network-attached storage you can plug in/out of Instances like a virtual hard drive. From a user's point of view, block volumes behave like regular disks and can be used to increase the storage of an Instance.
+
+## Boot-on-block
+
+
+
+## Carrier-grade NAT (CGNAT)
+
+Scaleway uses a 1:1 carrier-grade (CGNAT) setup for legacy Instance types. With this architecture, each Instance is assigned a unique NAT IP that directly maps to a unique public IP, unlike standard CGNAT, where multiple users share a single public IP.
+This setup ensures that all outbound and inbound traffic for an Instance is translated between these two addresses, preserving the exclusivity of IP addresses and avoiding certain connectivity issues related to a shared IP setup.
+
+## Cloud-init
+
+Cloud-init is a multi-distribution package that [provides boot time customization for cloud servers](/instances/how-to/use-boot-modes/#how-to-use-cloud-init). It enables an automatic Instance configuration as it boots into the cloud, turning a generic Ubuntu image into a configured server in a few seconds.
+
+## Cost-Optimized Instances
+
+[Cost-Optimized Instances](https://www.scaleway.com/en/cost-optimized-instances/) are production-grade [Instances](#instance) designed for scalable infrastructures. Cost-Optimized Instances support the boot-on-block feature and allow you to launch high-performance services with high-end CPUs.
+
+## Development Instance
+
+[Development Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and flexible Instances tuned to host your websites, applications, and development environments.
+
+## Dynamic IP
+
+A dynamic IP is an alternative type of public IP address for your Instance. This type of IP address is detached and released back into the general public pool of IP addresses whenever you stop your Instance. This means when you next power on your Instance, it may get a different dynamic IP address. In this respect, dynamic IPs are different from [flexible IPs](#flexible-ip), which remain associated with your Instance even when the Instance is stopped and are held in your account and can be moved between different Instances if you wish.
+
+You can choose to give your Instance a dynamic IP address when creating or updating your Instance via the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/) only. Read our [billing FAQ](/faq/billing/#when-does-the-billing-of-an-instance-start-and-stop) for more information about the billing of dynamic and flexible IPs.
+
+## Flexible IP
+
+Flexible IP addresses are public IP addresses that you can hold independently of any Instance. When you create a Scaleway Instance, by default, its public IP address is also a flexible IP address. Flexible IP addresses can be attached to and detached from any Instances you wish. You can keep a number of flexible IP addresses in your account at any given time. When you delete a flexible IP address, it is disassociated from your account to be used by other users. Find out more with our dedicated documentation on [how to use flexible IP addresses](/instances/how-to/use-flexips/). See also [Dynamic IPs](#dynamic-ip).
+
+## GPU Instance
+
+[GPU Instances](https://www.scaleway.com/en/gpu-instances/) are powerful Instances equipped with dedicated high-end Nvidia graphics processing units. See our [dedicated GPU documentation](/gpu/) for more details.
+
+## Image
+
+An image is a complete backup of your Instance. One image contains all the [volumes](#volumes) of your Instance and can be used to restore your Instance and its data. You can also use it to create a series of Instances with a predefined configuration. If you wish to copy only a specific volume of an Instance, you can use the [snapshot](#snapshot) feature instead.
+
+## Instance
+
+An Instance is a virtual computing unit that offers resources for running applications. It functions as a self-contained entity with its own operating system, RAM, and storage. Each type of Instance has unique specifications. You can choose the type that best meets your requirements. Refer to our [Instance types documentation](/instances/reference-content/choosing-instance-type/) for further details on the various Scaleway Instance options.
+
+## InstantApp
+
+An InstantApp is an image with a preinstalled application. By choosing an InstantApp when prompted to select an image during the [creation of your Instance](/instances/how-to/create-an-instance/), you choose to install the specified application on your Instance. You can then start using the application immediately.
+
+## IP mobility
+
+The legacy public network is provided through carrier-grade NAT infrastructure.
+When an Instance starts, it is assigned a NAT IP address that is associated with the underlying node hosting the Instance.
+The carrier-grade NAT establishes a one-to-one mapping between the public IP and the NAT IP assigned to the Instance during provisioning. Consequently, if the underlying node changes, the NAT IP address will also change.
+
+With IP mobility, there are no NAT IPs anymore. The public IP is entirely routed to the Instance. The main benefit is that your underlying IP no longer changes when you stop and start your Instance or if it gets provisioned on another hypervisor. But this also means that if you do not attach a public IP address to your Instance, then it will not have any network access.
+
+
+ Your IP address will only be retained during stop/start operations if you have linked a flexible public IP address to your Instance. If you use a dynamic IP address, the behavior remains consistent, whether your Instance has a routed IP enabled or is a legacy one.
+
+
+## Learning Instance
+
+[Learning Instances](https://www.scaleway.com/en/stardust-instances/) are the perfect Instances for small workloads and simple applications. You can create up to one Instance per Availability Zone (available in FR-PAR-1 and NL-AMS-1).
+
+## Local volumes
+
+The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block). In any case, it is always possible to increase the storage of an Instance by adding additional block volumes.
+
+## Placement groups
+
+Placement groups allow you to run multiple Compute Instances, each on a different physical hypervisor. Placement groups have two operating modes. The first one is called `max_availability`. It ensures that all the Compute Instances that belong to the same cluster will not run on the same underlying hardware. The second one is called `low_latency` and does the opposite, bringing Compute Instances closer together to achieve higher network throughput. [Learn how to use placement groups](/instances/how-to/use-placement-groups/).
+
+## Production-Optimized Instances
+
+[Production-Optimized Instances](https://www.scaleway.com/en/production-optimized-instances/) (aka POP2) are compute resources with dedicated resources (RAM and vCPUs). Designed for demanding applications, high-traffic databases, and production workloads.
+
+Three variants of POP2 Instances are available:
+* **POP2**: Production-Optimized Instances with Block Storage.
+* **POP2-HC**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:8.
+* **POP2-HM**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:2.
+* **POP2-HN**: Workload-Optimized Instances, providing a ratio of vCPU:RAM of 1:2 and up to 10 Gbps bandwidth.
+
+## Power-off mode
+
+The Power-off mode [shuts down an Instance](/instances/how-to/power-off-instance/) by transferring all data on the local volume of the Instance to a volume store. The physical node is released back to the pool of available machines. The reserved flexible IP of the Instance remains available in the account.
+
+
+ Depending on the amount of data to be archived, this process can take some time.
+
+
+## Private Networks
+
+Private Networks allow your virtual Instances to communicate in an isolated and secure network without requiring a connection to the public internet. Each Instance can be [connected to one or several Private Networks](/instances/how-to/use-private-networks/), letting you build your own network topologies.
+
+Private Networks are LAN-like layer 2 Ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Use this interface to communicate in a secure and isolated network, using private IP addresses of your choice.
+
+## Protected Instance
+
+Protected Instance is a feature that prevents any halt action from being performed on your Instance. This only applies to running Instances. [Enabling the Protected Instance feature](/instances/how-to/use-protected-instance/) means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode.
+
+## Public IP
+
+Public IP addresses are routed on the internet. You can enter the public IP address of your Instance into any browser connected to the internet, and access content being served from that Instance. You can think of public IP addresses like postal addresses for buildings - they are unique and tell the routers directing traffic through the internet where to find a particular server.
+
+## Region
+
+A region is a geographical area such as France (Paris: fr-par), the Netherlands (Amsterdam: nl-ams), or Poland (Warsaw: pl-waw) in which Scaleway products and resources are located. Each region contains multiple Availability Zones.
+
+For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/)
+
+## Rescue mode
+
+Rescue mode restarts your server via the network on a minimal operating system. You can [use rescue mode](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode) to debug your server and recover your system data. Rescue mode creates a ramdisk with the content of a downloaded rootfs. You will have access to all your disks and will be able to perform debug and rescue actions. After disabling rescue mode, you will have to reboot your server. Your server needs to be running to switch to rescue mode.
+
+## Reverse DNS
+
+Reverse DNS is the opposite of classic "forward" DNS, and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your Instance. Find out how to [configure reverse DNS on your Instance](/instances/how-to/configure-reverse-dns/) with our how-to documentation.
+
+## Routed flexible IP
+
+A routed flexible IP means assigning a public IP address to an Instance (virtual machine) that is reachable directly from the internet. This means there's [no address translation](/instances/concepts/#carrier-grade-nat-cgnat), and the Instance uses the public IP as its identity on the internet.
+The Instance can be accessed or can communicate directly using this public IP, which helps to make network configuration straightforward, with unrestricted inbound and outbound connections, crucial for services like web hosting or email servers.
+
+## Security group
+
+Security groups allow you to [create rules to drop or allow public traffic coming to and from your Instances](/instances/how-to/use-security-groups/). You can set default policies for inbound and outbound traffic, and/or define rules to deal with traffic differently depending on its source. Security groups can be [stateful](#stateful-security-groups) or [stateless](#stateless-security-groups). Note that security groups for Elastic Metal servers cannot be stateful.
+
+ Security Groups only allow the filtering of **public** traffic to and from your Instances. To filter traffic within a Private Network, you can [configure a firewall](/tutorials/installation-uncomplicated-firewall/) directly on your Instance, or use `iptables` or `nftables` from the command line interface of your Instance.
+
+
+## Snapshot
+
+A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/instances/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance.
+
+## Snapshot type
+
+An image is composed of snapshots of volumes. Snapshots can only be restored to a volume of the original type.
+
+## Standby mode
+
+Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the Local Storage of the Instance.
+
+## Stateful security groups
+
+Stateful security groups disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. Traffic will always be permitted on connections that you initiated. This is useful for example if you want to initiate connections on many and various ports for messaging, video streaming, or other purposes. In this case, the traffic from/to that connection will not be blocked, even if you have defined a rule that would otherwise do so. [Learn how to use security groups](/instances/how-to/use-security-groups/).
+
+## Stateless security groups
+
+Stateless security groups strictly apply the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance or not. This is useful if you know exactly which ports you will always require for your Instance, e.g. port `22` for SSH. You can make your security group stateless, define a rule to allow traffic on port `22` and block incoming traffic on other ports regardless of whether a connection is initiated from your Instance on this port. [Learn how to use security groups](/instances/how-to/use-security-groups/).
+
+## Tags
+
+Tags allow you to organize, sort, filter, and monitor your cloud resources using any pattern you wish. You can assign as many tags as you want to each Scaleway product.
+
+## Volumes
+
+Volumes are the storage space of your Instances. Two types of volumes exist:
+
+* **Local volumes**: The local volume of an Instance is an all-SSD-based storage solution, using a RAID array for redundancy and performance, hosted on the local hypervisor. On Scaleway Instances, the size of the local volume is fixed and depends on the Instance type. Some Instance types do not use local volumes and [boot directly on block volumes](#boot-on-block).
+
+* **Block volumes**: Block volumes provide network-attached storage you can plug in and out of Instances like a virtual hard drive. Block volumes behave like regular disks and can be used to increase the storage of an Instance.
\ No newline at end of file
diff --git a/pages/instances/how-to/assets/scaleway-attach-resource-instance.webp b/pages/instances/how-to/assets/scaleway-attach-resource-instance.webp
new file mode 100644
index 0000000000..7731ddd01f
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-attach-resource-instance.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-connect-tty.webp b/pages/instances/how-to/assets/scaleway-connect-tty.webp
new file mode 100644
index 0000000000..91ed6c4fec
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-connect-tty.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-create-a-snapshot.webp b/pages/instances/how-to/assets/scaleway-create-a-snapshot.webp
new file mode 100644
index 0000000000..01119632f6
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-create-a-snapshot.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-create-backup.webp b/pages/instances/how-to/assets/scaleway-create-backup.webp
new file mode 100644
index 0000000000..b16b9adefc
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-create-backup.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-create-from-snapshot.webp b/pages/instances/how-to/assets/scaleway-create-from-snapshot.webp
new file mode 100644
index 0000000000..d970315f8b
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-create-from-snapshot.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-image-from-multiple-snapshots.webp b/pages/instances/how-to/assets/scaleway-image-from-multiple-snapshots.webp
new file mode 100644
index 0000000000..7c59684480
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-image-from-multiple-snapshots.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-image-from-snapshot.webp b/pages/instances/how-to/assets/scaleway-image-from-snapshot.webp
new file mode 100644
index 0000000000..ba413dd03a
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-image-from-snapshot.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-instance-routedip-transition.webp b/pages/instances/how-to/assets/scaleway-instance-routedip-transition.webp
new file mode 100644
index 0000000000..fc1eb09ae4
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-instance-routedip-transition.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-instances-flexip-tab.webp b/pages/instances/how-to/assets/scaleway-instances-flexip-tab.webp
new file mode 100644
index 0000000000..5de472e2b1
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-instances-flexip-tab.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-list-attached-resources-pn.webp b/pages/instances/how-to/assets/scaleway-list-attached-resources-pn.webp
new file mode 100644
index 0000000000..199b2090d7
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-list-attached-resources-pn.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-private-networks-instances.webp b/pages/instances/how-to/assets/scaleway-private-networks-instances.webp
new file mode 100644
index 0000000000..e16364ddad
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-private-networks-instances.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-private-networks.webp b/pages/instances/how-to/assets/scaleway-private-networks.webp
new file mode 100644
index 0000000000..1c20e125da
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-private-networks.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-putty-logged.webp b/pages/instances/how-to/assets/scaleway-putty-logged.webp
new file mode 100644
index 0000000000..8ec0ac647d
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-putty-logged.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-putty-main.webp b/pages/instances/how-to/assets/scaleway-putty-main.webp
new file mode 100644
index 0000000000..46d9f9630f
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-putty-main.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-putty-security.webp b/pages/instances/how-to/assets/scaleway-putty-security.webp
new file mode 100644
index 0000000000..d1c3b0f6ac
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-putty-security.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-putty-ssh.webp b/pages/instances/how-to/assets/scaleway-putty-ssh.webp
new file mode 100644
index 0000000000..8b0ac2219a
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-putty-ssh.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-snapshot-import.webp b/pages/instances/how-to/assets/scaleway-snapshot-import.webp
new file mode 100644
index 0000000000..bbd2001ff8
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-snapshot-import.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-standby-mode.webp b/pages/instances/how-to/assets/scaleway-standby-mode.webp
new file mode 100644
index 0000000000..de01e1b861
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-standby-mode.webp differ
diff --git a/pages/instances/how-to/assets/scaleway-volume-from-snapshot.webp b/pages/instances/how-to/assets/scaleway-volume-from-snapshot.webp
new file mode 100644
index 0000000000..3f0416c024
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway-volume-from-snapshot.webp differ
diff --git a/pages/instances/how-to/assets/scaleway_instances_overview.webp b/pages/instances/how-to/assets/scaleway_instances_overview.webp
new file mode 100644
index 0000000000..05a1c10d77
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway_instances_overview.webp differ
diff --git a/pages/instances/how-to/assets/scaleway_last_button.webp b/pages/instances/how-to/assets/scaleway_last_button.webp
new file mode 100644
index 0000000000..2ad95e1593
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway_last_button.webp differ
diff --git a/pages/instances/how-to/assets/scaleway_list_snapshots.webp b/pages/instances/how-to/assets/scaleway_list_snapshots.webp
new file mode 100644
index 0000000000..7f85c42a9d
Binary files /dev/null and b/pages/instances/how-to/assets/scaleway_list_snapshots.webp differ
diff --git a/pages/instances/how-to/configure-reverse-dns.mdx b/pages/instances/how-to/configure-reverse-dns.mdx
new file mode 100644
index 0000000000..fab048399c
--- /dev/null
+++ b/pages/instances/how-to/configure-reverse-dns.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to configure reverse DNS of an Instance
+ description: This page explains how to configure the reverse DNS record of a Scaleway Instance.
+content:
+ h1: How to configure reverse DNS of an Instance
+ paragraph: This page explains how to configure the reverse DNS record of a Scaleway Instance.
+tags: configure reverse-dns dns instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+Reverse DNS is the opposite of classic "forward" DNS and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your server.
+
+
+ Using the default reverse DNS (*.pub.instances.scw.cloud) may lead to issues with the deliverability of your emails and subscription to tools like [Junk Mail Reporting Program](https://postmaster.live.com/snds/JMRP.aspx) (JMRP) and [Smart Network Data Services](https://sendersupport.olc.protection.outlook.com/snds/FAQ.aspx#WhatIsSNDS), Microsoft services to whitelist your IP’s on their email servers.
+
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/) with its public (flexible) IP address attached to it
+- Configured a matching `A-record` pointing to your IP address. Note that if you have created the A record recently, it may take up to 24 hours for the operation to be completed.
+
+## How to set up a reverse DNS record
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Flexible IPs** tab.
+3. Click the icon next to the IP address you wish to configure reverse DNS for and select **Edit reverse** from the drop-down menu.
+4. Enter the reverse DNS you want to associate with the IP address. Generally this corresponds to your hostname.
+5. Click **Edit reverse** to finish.
+
+ Once the reverse DNS has been updated, it may take up to 24 hours before it is fully propagated.
+
+
+
diff --git a/pages/instances/how-to/connect-to-instance.mdx b/pages/instances/how-to/connect-to-instance.mdx
new file mode 100644
index 0000000000..986afa6e39
--- /dev/null
+++ b/pages/instances/how-to/connect-to-instance.mdx
@@ -0,0 +1,119 @@
+---
+meta:
+ title: How to connect to your Instance
+ description: This page explains how to connect to your Instance via SSH
+content:
+ h1: How to connect to your Instance
+ paragraph: This page explains how to connect to your Instance via SSH
+tags: instance connection ssh ssh-key
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+This page shows how to connect to your Scaleway Instance via SSH. Thanks to the SSH key that you created and uploaded, you can use a terminal application on your local computer to remotely connect to your Instance as root. This enables you to use your Instance as you wish.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+
+
+
+
+
+ ### How to connect to Linux Instances from OSX (Mac) and Linux
+
+ 1. Open a terminal program.
+ 2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_ed25519`) and `your_instance_ip` with the IP address of your Instance.
+ ```sh
+ ssh -i ~/.ssh/your_private_key root@your_instance_ip
+ ```
+
+ To find the IP address of your Instance, log into the Scaleway console and
+ click **Instances** in the Compute section of the side menu. A list of your
+ Instances and their associated IP addresses will display.
+
+ 3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' can't be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+ You are now connected to your Instance.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+ ### How to connect to Linux Instances from Windows
+
+ To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+ 1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+ 2. Launch PuTTY on your computer. The main screen of the application displays:
+
+ 3. Enter your Instance's IP address in the **Hostname** field.
+
+ To find the IP address of your Instance, log into the Scaleway console and
+ click **Instances** in the Compute section of the side menu. A list of your
+ Instances and their associated IP addresses will display.
+
+ 4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. Do this by expanding **Connection**, then **SSH**, and finally clicking on **Auth**:
+
+ 5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/).
+ 6. Click **Open** at the bottom of the screen to open a connection to the Instance. Upon the first connection, PuTTY asks you to allow the connection to the host.
+ 7. Click **OK** to confirm.
+
+
+ The terminal window displays.
+ 8. Enter the username `root` and press **Enter** to authenticate against the server with your SSH key.
+
+
+ You are now connected to your Instance.
+
+
+ If you are new to using the Linux shell, check out our dedicated tutorial to help you take your [first steps with the Linux command line](/tutorials/first-steps-linux-command-line/).
+
+
+
+ ### How to connect to Windows Instances
+
+ * The steps below are valid only for Instances running Microsoft Windows as operating system.
+ * You must have the [Scaleway CLI](https://github.com/scaleway/scaleway-cli) installed and configured on your local machine to be able to retrieve your Windows administrator password.
+
+ 1. Click **Instances** in the **Compute** section of the left side menu. The Instances dashboard displays.
+ 2. Select the name of the Instance you wish to connect to.
+ 3. Click **Get password** to retrieve the password for your Instance. A popup will display a command for retrieving your initial password using the Scaleway CLI:
+ ```bash
+ scw instance server get-rdp-password zone= key=
+ ```
+ 4. Open a terminal and paste the command. Replace ``, ``, and `` with your Instance ID, the corresponding Availability Zone, and the path to your private RSA SSH key, respectively:
+ ```bash
+ $ scw instance server get-rdp-password e48c5e3e-f3d6-49e5-93be-eacfe4c427fd zone=fr-par-1 key=~/.ssh/id_rsa
+ ```
+ 5. The initial Administrator password will be displayed. Copy and save this password:
+ ```plaintext
+ Username Administrator
+ Password nlW_=v->I"mWuEz
+ SSHKeyID 73f6f13e-0f34-45d0-a61c-463e0289b4a4
+ SSHKeyDescription My RSA SSH key
+ ```
+ 6. Launch your Remote Desktop client and enter your Instance's IP address, the username **Administrator**, and the initial password.
+
+ - On Windows PCs, use the [built-in RDP client](https://support.microsoft.com/en-us/windows/how-to-use-remote-desktop-5fe128d5-8fb1-7a23-3b8a-41e636865e8c).
+ - On Mac OS X, download the [Microsoft RDP client](https://apps.apple.com/en/app/microsoft-remote-desktop/id1295203466).
+ - On Linux, use your preferred remote desktop client, such as [Remmina](https://remmina.org/) (installed by default on Ubuntu-based distributions).
+
+ 7. Enter the username **Administrator** and the password, then click **Login**. The Windows desktop displays.
+
+
+
+## Troubleshooting connection problems
+
+If you have any problems connecting to your Instance via SSH, refer to our [dedicated troubleshooting document](/instances/troubleshooting/cant-connect-ssh/).
diff --git a/pages/instances/how-to/create-a-backup.mdx b/pages/instances/how-to/create-a-backup.mdx
new file mode 100644
index 0000000000..2285ad3522
--- /dev/null
+++ b/pages/instances/how-to/create-a-backup.mdx
@@ -0,0 +1,74 @@
+---
+meta:
+ title: How to create an image
+ description: This page explains how to create an image of your Instance
+content:
+ h1: How to create an image
+ paragraph: This page explains how to create an image of your Instance
+tags: instance image backup
+dates:
+ validation: 2024-09-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+The image feature lets you create an image of your Instance, which contains all its volumes. You can use this image to restore your Instance and its data and create a series of Instances with a predefined configuration.
+
+This feature is available on Instance types. Creating images of your Instance is free. However, keep in mind that as the image feature creates snapshots of your volumes, you will be billed for these snapshots.
+
+
+ This creates an image that is a complete backup of your Instance including **all** of its volumes. The [snapshot](/instances/concepts/#snapshot) feature, on the other hand, creates snapshots of specific volumes. Consider [creating a snapshot](/instances/how-to/create-a-snapshot/) if you want to use different snapshot strategies for different volumes of your Instance, e.g., if it has one volume containing the OS and another containing application data.
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to create an image
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to back up.
+3. Click the **Images** tab.
+4. Click **+ Create image**. A pop-up displays asking you to confirm the action.
+5. Click **Create image from Instance**.
+ You are returned to the **Images** tab, where your new image now displays.
+
+
+ When you create an image, each of the Instance's volumes are snapshotted. You will be able to see the snapshot of each volume via the [**Snapshots**](https://console.scaleway.com/instance/snapshots) tab of your Instance dashboard.
+
+
+
+## How to create or restore an Instance from an image
+
+There are two different ways to create a new Instance from your image:
+
+### Using the Instance creation wizard
+
+Follow the instructions for [creating an Instance](/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My images** tab, and select the desired image.
+
+A new Instance is created from your image.
+
+### Restoring the image
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you created an image of.
+3. Click the **Images** tab.
+4. Click next to the Instance's image.
+5. Select **Create Instance from image** on the drop-down list. You are redirected to the Instance Creation wizard, where the image has been preselected for you at step 2.
+6. Finish configuring the Instance according to your requirements, and click **Create Instance**.
+
+ A new Instance is created from your image.
+
+## How to manage your images
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Images** tab. A list of your images displays.
+3. Click next to the relevant image.
+ - Select **More info** to view more information about the image, including its name, status, location, size, type, ID, and creation date.
+ - Select **Delete** to delete the image if you no longer need it, and confirm via the pop-up window when prompted.
+
+
diff --git a/pages/instances/how-to/create-a-block-volume.mdx b/pages/instances/how-to/create-a-block-volume.mdx
new file mode 100644
index 0000000000..219526bd50
--- /dev/null
+++ b/pages/instances/how-to/create-a-block-volume.mdx
@@ -0,0 +1,43 @@
+---
+meta:
+ title: How to create a Block Storage volume
+ description: This page explains how to create Block Storage volumes in Scaleway
+content:
+ h1: How to create a Block Storage volume
+ paragraph: This page explains how to create Block Storage volumes in Scaleway
+tags: create volume add
+dates:
+ validation: 2024-08-19
+ posted: 2023-11-23
+categories:
+ - instances
+ - compute
+---
+
+
+
+- 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
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Volumes** tab to display a list of all your current volumes.
+3. Click **Create volume** to create a volume that can be attached to any of your Instances.
+4. Choose an Availability Zone for the volume.
+
+ The volume must be in the same Availability Zone as the Instance you want to connect it to.
+
+5. Enter the volume name and select a size.
+6. Configure the volume type. You can either create a **Block Storage** or **Local Storage** volume.
+
+ To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
+
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
+ This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+
+7. Click **Create volume** to confirm.
+
+
+ You can also [create](/block-storage/how-to/create-a-volume/) Block Storage volumes from the [Block Storage console section](https://console.scaleway.com/block-storage/).
+
\ No newline at end of file
diff --git a/pages/instances/how-to/create-a-snapshot.mdx b/pages/instances/how-to/create-a-snapshot.mdx
new file mode 100644
index 0000000000..25f6877098
--- /dev/null
+++ b/pages/instances/how-to/create-a-snapshot.mdx
@@ -0,0 +1,69 @@
+---
+meta:
+ title: How to create a snapshot
+ description: Learn how to create a volume snapshot for a Scaleway Instance with this easy-to-follow guide.
+content:
+ h1: How to create a snapshot
+ paragraph: Learn how to create a volume snapshot for a Scaleway Instance with this easy-to-follow guide.
+tags: snapshot instance
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+The snapshot feature allows you to create an image of a specific [volume](/instances/concepts/#volumes) of your Instance. A snapshot is a full-volume copy stored in our secure data centers. They are usually used to recover volume data or to create a copy of a volume.
+
+Several options are available to create snapshots from your Instance:
+
+* **LSSD (Local Storage):** This snapshot type can be created from local volumes. LSSD snapshots can be converted to local volumes only.
+* **BSSD (Block Storage):** This snapshot type can be created from block volumes. BSSD snapshots can be converted to block volumes only.
+
+
+ The snapshot feature creates backups of specific volumes only. If you wish to create a backup image that is a complete backup of your Instance including **all** of its volumes, check out our documentation on [how to create an image](/instances/how-to/create-a-backup/).
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to create a snapshot
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Snapshots** tab.
+
+3. Click the **+ Create snapshot** button. You are directed to the snapshot creation wizard.
+4. Complete the following steps in the wizard:
+ - Choose a **name** for the snapshot, or use the default suggested name.
+ - Select the **volume** you wish to snapshot. All of your Instances' volumes will be shown on the drop-down list, grouped by Availability Zone.
+ - Select the **snapshot type**. The available types of snapshots depend on your volume type and can either be LSSD or BSSD.
+ - Check the **Estimated cost**.
+5. Click **Create snapshot** to finish. You are redirected to the **Snapshots** tab, where your new snapshot now appears in the list.
+
+## How to create a volume from a snapshot
+
+You can create a [volume](/instances/concepts/#volumes) from a snapshot as follows:
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Snapshots** tab.
+3. Click next to the snapshot you want to create an image from. A drop-down menu displays.
+4. Click **Volume from snapshot**. A pop-up displays.
+
+5. Enter a name for the volume (or use the default suggested name), select the volume type, and click **Create volume from Snapshot**.
+
+ The available volume types may change according to the type of snapshot you select.
+
+
+ The volume is created, and can be viewed in the [Volumes tab](https://console.scaleway.com/instance/volumes). Check out our documentation on [attaching volumes](/block-storage/how-to/attach-a-volume/) and [mounting volumes](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) to learn how to use the volume with your Instances.
+
+## How to create an Instance from a snapshot
+
+Follow the instructions for [creating an Instance](/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My snapshots** tab, and select the desired snapshot.
+
+
+
+You can see the snapshotted volume in the Instance's volumes at **step 4** of the creation wizard.
\ No newline at end of file
diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx
new file mode 100644
index 0000000000..670fba5c00
--- /dev/null
+++ b/pages/instances/how-to/create-an-instance.mdx
@@ -0,0 +1,259 @@
+---
+meta:
+ title: How to create an Instance
+ description: This page explains how to create an Instance
+content:
+ h1: How to create an Instance
+ paragraph: This page explains how to create an Instance
+tags: instance create
+dates:
+ validation: 2024-12-09
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+This page shows how to create your first Scaleway Instance. An [Instance](/instances/concepts/#instance) is a virtual machine in the cloud. Just like a physical machine, it has resources - virtualized CPU, RAM, storage etc. - which vary depending on the [Instance type](/instances/reference-content/choosing-instance-type/) you choose. After you have created your Instance you can [connect](/instances/how-to/connect-to-instance/) to it and use it for a wide range of computing use cases depending on the Instance type you chose, from running small-scale tests and personal projects to hosting applications and development environments to setting up a production environment.
+
+Select a tab below for instructions on how to create an Instance via either our [console](https://console.scaleway.com), our [API](https://www.scaleway.com/en/developers/api/instance/), or our [CLI](https://github.com/scaleway/scaleway-cli).
+
+
+
+
+
+
+
+ - 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
+ - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+ - An [Instance](/instances/how-to/create-an-instance/)
+
+ 1. Click **Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays.
+ 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays.
+ 3. Complete the following steps:
+ - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed.
+ - **Choose an Instance type**.
+ Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/).
+ - **Choose an image** to run on your Instance.
+ This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/).
+ - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance.
+ - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
+
+ - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB.
+ - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
+ - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes.
+
+ - **Configure network** of the Instance.
+ - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4.
+ - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6.
+
+ You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
+
+ - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+ You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
+ - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance.
+ - **Verify the Estimated cost** of your Instance, based on the specifications you chose.
+ 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
+
+ Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance.
+
+
+
+
+
+
+ - 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
+ - An [RSA key pair](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)
+ - An [Instance](/instances/how-to/create-an-instance/)
+
+ 1. Click **Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays.
+ 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays.
+ 3. Complete the following steps:
+ - Choose an **Availability Zone**, which represents the geographical region where your Instance will be deployed.
+ - **Choose a POP2-WIN** Instance type from the **Production-Optimized** range.
+ - **Choose a Windows Server image** to run on your Instance.
+ - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance.
+ - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
+
+ - Ensure that a volume containing a Windows Server image has a minimum capacity of 25 GB.
+ - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
+ - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes.
+
+
+ To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
+
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
+ This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+
+ - **Configure network** of the Instance.
+ - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4.
+ - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6.
+
+ You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
+
+ - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+ You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
+ - **Choose the [RSA SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)** that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated.
+ - Verify the **Estimated cost** of your Instance, based on the specifications you chose.
+ 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
+
+ Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the command to use to [retrieve the password and connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance.
+
+
+
+
+
+
+ - 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
+ - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+ - A valid [API key](/iam/how-to/create-api-keys/)
+ - Installed [curl](https://curl.se/) on your local machine
+
+ 1. Open a terminal and configure your environment variables with the `export` commands shown below.
+
+
+ This is an optional step that seeks to simplify your usage of the API. Ensure that you replace the variables represented by triangle brackets in the example below with your own customized values:
+ - The API [access key and secret key](/iam/concepts/#api-key) that you created.
+ - The Project ID of the [Project](/iam/concepts/#project) you want to create the Instance in. You can find your Project ID in the [**Settings** tab](https://console.scaleway.com/project/settings) of the relevant Project in the Scaleway console.
+ - The [Availability Zone](/instances/concepts/#availability-zone) you want to create the Instance in, e.g. `fr-par-1`.
+
+
+ ```bash
+ export SCW_ACCESS_KEY=""
+ export SCW_SECRET_KEY=""
+ export SCW_PROJECT_ID=""
+ export SCW_DEFAULT_ZONE=""
+ ```
+ 2. Get the label of your OS of choice.
+
+ ```
+ curl --location "https://api.scaleway.com/marketplace/v2/images" \
+ --header "X-Auth-Token: $SCW_SECRET_KEY"
+
+ {
+ "images": [
+ {
+ "id": "607b12c2-685d-45f7-905f-57bc23863834",
+ "name": "Ubuntu 24.04 Noble Numbat",
+ "label": "ubuntu_noble",
+ "description": "Ubuntu is the ideal distribution for scale-out computing, Ubuntu Server helps you make the most of your infrastructure.",
+ "logo": "https://scw-marketplace-logos.s3.fr-par.scw.cloud/ubuntu.png",
+ "categories": [
+ "distribution"
+ ],
+ "valid_until": null,
+ "created_at": "2024-04-15T11:39:21.011004Z",
+ "updated_at": "2024-10-09T07:32:04.494117Z"
+ },
+ ],
+ "total_count": 23
+ }
+ ```
+ 3. Customize the **payload** for your API call. This payload specifies the configuration of the Instance you want to create. We provide an example payload below with all the required parameters, and a table of information to help you adapt it to your needs.
+
+ ```
+ {
+ "name": "my-new-instance",
+ "project": "'""$SCW_PROJECT_ID""'",
+ "commercial_type": "GP1-S",
+ "image": "ubuntu_noble",
+ "enable_ipv6": true,
+ "volumes
+ "0": {
+ "name": "my-volume",
+ "size": 300000000000,
+ "volume_type": "l_ssd"
+ }
+ }
+ }
+ ```
+
+ | Parameter | Description | Valid values |
+ |-----------------|-----------------------------------------------------|----------------------------------------|
+ | name | A name of your choice for the Instance (string) | Any string containing only alphanumeric characters, dots, spaces and dashes, e.g. `"my-new-instance"`. |
+ | project | The Project in which the Instance should be created (string)| Any valid Scaleway Project ID (see above), e.g. `"b4bd99e0-b389-11ed-afa1-0242ac120002"` |
+ | commercial-type | The commercial Instance type to create (string) | Any valid ID of a Scaleway commercial Instance type, e.g. `"GP1-S"`, `"PRO2-M"`. Use the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint to get a list of all valid Instance types and their IDs. |
+ | image | The image to install on the Instance, e.g. a particular OS (string) | Any valid Scaleway image label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. |
+ | enable_ipv6 | Whether to enable IPv6 on the Instance (boolean) | `true` or `false` |
+ | volumes | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`b_ssd`), others also support Local Storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd"` or `"b_ssd"`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`.) Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes). |
+
+ 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance.
+
+ ```
+ curl -X POST -H "Content-Type: application/json" \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/instance/v1/zones/{$ZONE}/servers" \
+ -d '{"name": "my-new-instance", "project": "'"$PROJECT_ID"'", "commercial_type": "GP1-S", "image":"ubuntu_noble","enable_ipv6": true, "volumes":{"0":{"name": "my-volume","size": 300000000000,"volume_type": "l_ssd"}}}'
+ ```
+
+ Valid Instance creation results in a `201` response containing a `server` object that confirms the attributes of your Instance.
+
+
+ To make this response more readable, try adding `| jq '.'` to the end of the command shown in step three. This tells your shell to use the [jq](https://stedolan.github.io/jq/) JSON processor to parse the response received from this call and display it in a formatted way.
+
+
+
+ When creating an Instance via the API, it is in a powered off state by default. To power it on, call the [Perform action](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action) endpoint, passing it the ID of your Instance (returned in the 201 response at step 3) and `poweron` as the `action` to perform.
+
+
+ See the [Instance API documentation](https://www.scaleway.com/en/developers/api/instance/) for full details on the Instance API. In particular, see the [Create an Instance](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance) call for more details of configurable parameters when creating an Instance.
+
+
+
+
+
+
+ - A Scaleway account logged into the [console](https://console.scaleway.com)
+ - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+ - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+ - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+ - A valid [API key](/iam/how-to/create-api-keys/)
+ - Installed and configured the [Scaleway CLI](https://github.com/scaleway/scaleway-cli) on your local machine
+
+ 1. Get the label of your OS of choice.
+
+ ```bash
+ scw marketplace image list
+
+ ID LABEL NAME CATEGORIES VALID UNTIL
+ 607b12c2-685d-45f7-905f-57bc23863834 ubuntu_noble Ubuntu 24.04 Noble Numbat [distribution] -
+ ```
+
+ 2. Prepare your command by choosing values for the parameters below to define the Instance you want to create. Use the table to select appropriate values.
+
+ ```bash
+ name=my-new-instance
+ project-id=adcaffc9-38ef-4502-86e1-f70d3c353745
+ zone=fr-par-1
+ type=GP1-S
+ image=ubuntu_noble
+ ip=new
+ root-volume=l:300GB
+ ```
+
+ | Parameter | Description | Valid values |
+ |-----------------|-----------------------------------------------------|-------------------------------|
+ | name | A name of your choice for the Instance | Any string containing only alphanumeric characters, dots, spaces and dashes, e.g. `my-new-instance`. |
+ | project-id | The Project in which the Instance should be created | Any valid Scaleway Project ID, e.g. `b4bd99e0-b389-11ed-afa1-0242ac120002` |
+ | zone | The Availability Zone in which the Instance should be created. Note that some Instance types are only available in certain Availability Zones (see **type`**below) | Any valid Scaleway Availability Zone, e.g. `fr-par-1`, `pl-waw-2` |
+ | type | The type of Instance to create | Any valid ID of a Scaleway Instance type, e.g. `GP1-S`, `PRO2-M`. Use the [server-type](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/instance.md#server-type-management-commands) command to get a list of all valid Instance types and their IDs. The default value is `DEV1-S` |
+ | image | The image to install on the Instance, e.g. a particular OS | Any valid Scaleway image label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. |
+ | ip | The IP address to use for the Instance. | `new` to create a new IP, `dynamic` to create a dynamic IP address, `none` for no public IP address, or an existing IP ID. Default is `new` |
+ | root-volume | The root volume for the Instance (type e.g. `l` (local) or `b` (block) followed by a colon and its required size e.g. `10GB`) | Any valid volume type and size that is coherent with the storage constraints of the Instance **type** (available via `scw instance server-type list`) |
+
+ 3. Open a terminal and run the command below, with the parameters modified according to your needs as defined in step one.
+
+ ```bash
+ scw instance server create name=my-new-instance project-id=2ea18278-847c-4c33-8111-9c2376ed921e zone=fr-par-1 type=GP1-S image=ubuntu_noble ip=new root-volume=l:300GB
+ ```
+
+ Your Instance is created, and its details are returned to you in response.
+
+ Read the [official Scaleway CLI Instance documentation](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/instance.md) for full details on how to create an Instance via the CLI, including all available parameters, and how to take your next steps.
+
+
+
+
diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx
new file mode 100644
index 0000000000..3bbb3dfe9b
--- /dev/null
+++ b/pages/instances/how-to/create-image-from-snapshot.mdx
@@ -0,0 +1,89 @@
+---
+meta:
+ title: How to create an image from a snapshot
+ description: This page explains how to create an image from a snapshot of a Scaleway Instance.
+content:
+ h1: How to create an image from a snapshot
+ paragraph: This page explains how to create an image from a snapshot of a Scaleway Instance.
+tags: image backup snapshot instance
+dates:
+ validation: 2024-11-15
+ posted: 2021-08-05
+categories:
+ - compute
+---
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+- At least one [snapshot](/instances/how-to/create-a-snapshot/)
+
+## Creating an image from a snapshot via the Scaleway console
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Images** tab. A list of your images displays.
+3. Hover over the button to **Create image**. The overview page displays.
+4. Choose the **Availability Zone** in which you want your image to be created.
+5. Enter a **name** for your image.
+
+ Your image's name can only contain alphanumeric characters and dashes.
+
+6. Select the snapshot from which you want to create your image in the drop-down box.
+7. Click **Create image** to create your image.
+
+
+ You can also create an image from the **Snapshots** dashboard by clicking next to the snapshot from which you want to create an image. Click **Image from snapshot**. A new tab opens: enter a name for your image. Then click **Create image from snapshot**.
+
+
+## Creating an image via the Scaleway CLI
+
+You can also create an image using the [Scaleway CLI](/scaleway-cli/quickstart/). Use the following command:
+
+```bash
+scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id="$SCW_VOLUME_ID_2" arch="x86_64"
+```
+
+- Replace `$SCW_VOLUME_ID_1` with the ID of the snapshot or volume you want to use as the root volume.
+- Replace `$SCW_VOLUME_ID_2` with the ID of any additional volume to be included.
+- Ensure the architecture (`arch`) is set to a valid value (e.g., `x86_64`).
+
+
+ Supported volume IDs include:
+ - Local Storage volumes (`l_ssd`)
+ - Block Storage Low Latency volumes (`sbs`)
+ - Block Storage legacy (`b_ssd`) volumes (deprecated).
+
+
+## Creating an image via the Scaleway API
+
+You can also create an image using the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/#path-images-create-an-instance-image). Use the following `curl` command:
+
+```bash
+curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/images" \
+--header "Content-Type: application/json" \
+--header "X-Auth-Token: $SCW_SECRET_KEY" \
+--data '{
+ "root_volume": "'$SCW_VOLUME_ID_1'",
+ "arch": "x86_64",
+ "name": "image_name",
+ "extra_volumes": {
+ "1": {"id":"'$SCW_VOLUME_ID_2'"}
+ },
+ "project": "'$SCW_PROJECT_ID'"
+}'
+```
+
+- Replace `$SCW_VOLUME_ID_1` with the ID of the snapshot or volume to use as the root volume.
+- Replace `$SCW_VOLUME_ID_2` with the ID of any additional volume.
+- Use `$SCW_PROJECT_ID` for the ID of your project.
+- Ensure the architecture (`arch`) is set to a valid value (e.g., `x86_64`).
+
+
+ Supported volume IDs include:
+ - Local Storage volumes (`l_ssd`)
+ - Block Storage Low Latency volumes (`sbs`)
+ - Block Storage legacy (`b_ssd`) volumes (deprecated).
+
+
diff --git a/pages/instances/how-to/delete-instance.mdx b/pages/instances/how-to/delete-instance.mdx
new file mode 100644
index 0000000000..03257c6b98
--- /dev/null
+++ b/pages/instances/how-to/delete-instance.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: How to delete an Instance
+ description: This page explains how to delete a Scaleway Instance.
+content:
+ h1: How to delete an Instance
+ paragraph: This page explains how to delete a Scaleway Instance.
+tags: delete instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+This page shows you how to delete an Instance.
+
+
+ Deleting an Instance is an **irreversible action**. Any data stored on your Instance will be lost.
+
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to delete an Instance
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the icon next to the Instance you want to delete, and select **Delete** from the drop-down menu.
+ A pop-up asks you to confirm the action.
+3. Type **DELETE** to confirm your choice.
+4. If your Instance has associated IPs or Block Storage volumes, you will be asked whether you want to delete them as well. Check the corresponding box to delete them along with your Instance.
+5. Click **Delete Instance**.
+
+ You are returned to the list of your Instances, where the Instance you deleted no longer appears.
+
+
diff --git a/pages/instances/how-to/index.mdx b/pages/instances/how-to/index.mdx
new file mode 100644
index 0000000000..5b6f5f4feb
--- /dev/null
+++ b/pages/instances/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Instances - How Tos
+ description: Instances How Tos
+content:
+ h1: Instances - How Tos
+ paragraph: Instances How Tos
+---
diff --git a/pages/instances/how-to/manage-volumes.mdx b/pages/instances/how-to/manage-volumes.mdx
new file mode 100644
index 0000000000..240fb4cf1d
--- /dev/null
+++ b/pages/instances/how-to/manage-volumes.mdx
@@ -0,0 +1,90 @@
+---
+meta:
+ title: How to manage Block Storage volumes
+ description: This page explains how to manage Block Storage volumes
+content:
+ h1: How to manage Block Storage volumes
+ paragraph: This page explains how to manage Block Storage volumes
+tags: attach link connect block volume block-storage
+dates:
+ validation: 2024-12-09
+ posted: 2023-11-23
+categories:
+ - compute
+---
+
+
+
+- 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
+- A [Block Storage volume](/block-storage/how-to/create-a-volume/)
+
+## How to attach a volume
+
+
+ You must have created a [volume](/instances/how-to/create-a-block-volume/) that is not attached to any of your Instances before proceeding with the steps below.
+
+
+1. Click **Instances** from the left side menu. The Instances section displays.
+2. Click the **Volumes** tab to display a list of all your current volumes.
+3. Click **Attach to Instance** under the **Linked Instance** section.
+4. Select the Instance to which you want to attach your volume from the drop-down.
+5. Click **Attach volume to Instance**.
+
+
+ Find out [how to mount a Block Storage volume to your Instance](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume).
+
+
+ To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**.
+ You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation.
+
+ Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`.
+ This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage.
+
+## How to increase the volume size
+
+1. Click the [Volumes tab](https://console.scaleway.com/instance/volumes) on the Instance information page of the Scaleway console. A list of your volumes displays.
+2. Click next to the volume you want to increase and then click **Increase Volume**.
+3. Increase the size according to your preference with the button.
+4. Click **Increase volume** to confirm.
+
+ Currently, only the **increase** of a Block Storage volume is supported. The maximum size of a Block Storage volume is 10 TB.
+
+
+
+ Refer to our [dedicated documentation](/block-storage/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase the partition size of your volume.
+
+
+## How to detach a volume
+
+You can detach a Block Storage volume from your Instance at any time. It is important to [unmount (detach) the device](/block-storage/api-cli/unmounting-a-volume/) from the operating system before detaching the Block Storage volume to avoid data loss.
+
+
+
+- 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
+- A [Block Storage volume](/block-storage/concepts/#block-device) attached to a Scaleway Instance
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance with the volume you want to detach. The Instance information page displays.
+3. Click the **Attached volumes** tab. A list of all volumes attached to the Instance displays.
+4. Click next to the volume you want to detach, then click **Detach**. A pop-up displays.
+5. Click **Detach volume from Instance** to confirm.
+
+## How to delete a volume
+
+
+ You must detach a Block Storage volume from an Instance to delete it. Refer to our [documentation](/block-storage/how-to/detach-a-volume/) to find out how to do so.
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Volumes** tab to view a list of your volumes.
+3. Click next to the volume that you want to delete.
+4. Click **Delete**. A pop-up displays.
+5. Type `DELETE` to confirm.
+6. Click **Delete volume** to remove the volume from your account.
+
+ All data on the volume will be removed when you delete it. Make sure you have a backup of your data before removing the volume.
+
+
+
diff --git a/pages/instances/how-to/migrate-instances.mdx b/pages/instances/how-to/migrate-instances.mdx
new file mode 100644
index 0000000000..0016de79df
--- /dev/null
+++ b/pages/instances/how-to/migrate-instances.mdx
@@ -0,0 +1,58 @@
+---
+meta:
+ title: How to migrate Instances
+ description: This page explains how migrate from one Scaleway Instance to another
+content:
+ h1: How to migrate Instances
+ paragraph: This page explains how to migrate from one Scaleway Instance to another
+tags: instance migration migrate
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+The Scaleway platform makes it very easy to migrate your data from one Instance to another or upgrade your Instance to a more powerful one if your requirements grow. In this how-to, we will upgrade an Instance by migrating from a [DEV1-S](/instances/concepts/#development-instance) Instance to a [GP1-XS](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance. The new GP1-XS Instance will have the same [flexible IP](/instances/concepts/#flexible-ip) as the original DEV1-S Instance.
+
+For more information about choosing the best Instance type to migrate to for your use case, see our [dedicated documentation](/instances/reference-content/choosing-instance-type/).
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/) (We are using a DEV1-S Instance)
+
+## How to back up the Instance
+
+Follow the instructions to [create an image](/instances/how-to/create-a-backup/#how-to-create-an-image) of your Instance.
+
+## How to create a new Instance from an image
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you created an image of.
+3. Click the **Images** tab.
+4. Click next to the Instance's image.
+5. Select **Create Instance from image** on the drop-down list. You are redirected to the Instance Creation Wizard, where the image has been preselected for you at step 2.
+6. Finish configuring the Instance according to your requirements. Notably:
+ - You are free to choose your Instance type. We chose to create a [GP1-XS](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance, upgrading from the [DEV1-S](/instances/concepts/#development-instance) on which the image was based.
+ - Click **Advanced options** and use the toggle to deselect **flexible IP**. This creates a the new Instance without a flexible IP, as we are going to attach the one from the existing Instance in the next step.
+7. Click **Create Instance** to finish. The Instance is created and shows in your Instances list.
+
+## How to move a flexible IP to a new Instance
+
+Next, we will move the original DEV1-S Instance's [flexible IP address](/instances/concepts/#flexible-ip) to the new GP1-XS Instance.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Flexible IPs** tab.
+3. Click next to the DEV1-S's flexible IP. In the pop-up menu that then displays, click **Switch Instance**.
+4. Select the GP1-XS Instance from the drop-down list, and click **Attach flexible IP to Instance**.
+
+ The new Instance is now reachable via the old Instance's flexible IP.
+
+## How to delete the old Instance
+
+Presuming that you no longer need the original DEV1-S Instance, you can [delete it](/instances/how-to/delete-instance/).
+
+
diff --git a/pages/instances/how-to/migrate-routed-ips.mdx b/pages/instances/how-to/migrate-routed-ips.mdx
new file mode 100644
index 0000000000..20d9b78cd4
--- /dev/null
+++ b/pages/instances/how-to/migrate-routed-ips.mdx
@@ -0,0 +1,87 @@
+---
+meta:
+ title: How to move an Instance to routed flexible IPs
+ description: This page explains how to move your Instance to routed flexible IPs
+content:
+ h1: How to move an Instance to routed flexible IPs
+ paragraph: This page explains how to move your Instance to routed flexible IPs
+tags: instance flexible ip routed
+dates:
+ validation: 2024-11-14
+ posted: 2023-10-11
+categories:
+ - compute
+---
+
+Prior to April 2024, all Instances got a NAT IP from their hosting node, which was routed to the Instance through a [carrier-grade NAT](/instances/concepts/#carrier-grade-nat-cgnat) solution. This was in addition to the public (flexible) IP. The NAT IP let Instances communicate via an underlying internal network, without public IPs. However, if the underlying hypervisor changed, the NAT IP changed also. This could happen when you restarted your Instance.
+
+Since October 2024 it is no no longer possible to create Instances with NAT IPs. Instead, Instances' public IPs are **routed** IPs. Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported.
+
+In addition to the benefits explained above, routed IPs allow precise control over network configurations, simplify troubleshooting, ensure compatibility with more applications, and allow for enhanced security monitoring. We recommend that users with Instances still using NAT IPs move them to routed IPs by following the instructions below.
+
+
+ * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature.
+ * Ensure no static network configuration is in use for your public network interface (usually `ens2` or `eth0`)
+ * Ensure that you are not using the internal private IP of the Instance for internal communications. Instead, [attach your Instances to a VPC](/vpc/how-to/attach-resources-to-pn/).
+ * You must update the `scaleway-ecosystem` and `cloud-init` packages before starting transition.
+ * Before proceeding with the migration, please review the [FAQ on IP autoconfiguration limitations](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature) and the [guide to fix unreachable Ubuntu Focal Instances with multiple public IPs](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). These resources provide important information to ensure a seamless migration process.
+
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Instance](/instances/how-to/create-an-instance/) that has not been moved to routed IPs
+
+## Updating the required packages
+
+
+ To ensure optimal compatibility and security, especially when working with flexible IPs, we recommend to upgrade your Instance to OS versions that have not reached their end of life.
+
+
+Before proceeding with the migration, consider the following guidelines regarding `scaleway-ecosystem` and `cloud-init`:
+
+- `scaleway-ecosystem` and `cloud-init`: These packages are not strictly required for routed IPs. However, if they are installed, it is recommended to update them to the latest version.
+- Package availability on older Instances:
+ - `scaleway-ecosystem`: Older Instances may not have this package installed. In such cases, no action is required.
+ - `cloud-init`: This package is commonly pre-installed on Instances due to its inclusion in upstream cloud images. For older Instances, a legacy version of `cloud-init` may not impact IPv4 functionality, but IPv6 functionality could be inconsistent with outdated versions.
+
+To check if `scaleway-ecosystem` and `cloud-init` are installed and to update them if needed, [log into your Instance using SSH](/instances/how-to/connect-to-instance/) and run the following commands:
+
+* For **Ubuntu and Debian** Instances:
+ ```bash
+ dpkg-query -W scaleway-ecosystem || echo "scaleway-ecosystem is not installed"
+ apt upgrade scaleway-ecosystem cloud-init -y
+ ```
+
+* For **CentOS and Fedora** Instances:
+ ```bash
+ rpm -q scaleway-ecosystem || echo "scaleway-ecosystem is not installed"
+ dnf update scaleway-ecosystem cloud-init -y
+ ```
+
+If `scaleway-ecosystem` is not installed, no additional steps are needed for this package. However, it is still recommended to ensure that `cloud-init` is up-to-date to support IPv6 functionality.
+
+## Moving the Instance to routed IPs
+
+1. Select **Instances** from the **Compute** category in the sidebar menu. This will show a list of your Instances. Those eligible to transition to routed IPs are identified with an exclamation mark icon.
+
+2. Click **Move IP** next to the Instance you wish to move to routed flexible IPs. A pop-up displays.
+
+ Alternatively, you can initiate the transition from your Instance's overview page by clicking the **Move IP** button.
+
+3. Type **MIGRATE** to confirm your intent and click **Move to routed IP**. This will initiate the transition process, and your Instance will undergo a reboot.
+
+ Post-transition, your Instance will retain its public IP address, but its NAT IP will be removed.
+
+After the transition finishes, the notification icon will no longer be visible in your Instances list.
+
+
+ For detailed guidance on using the routed flexible IP feature via the Scaleway API or CLI tool, refer to our dedicated documentation [Routing public IPs to Instances using the Scaleway API](/instances/api-cli/using-routed-ips/).
+
+
+
+## IPv6 support
+
+Routed IPs provide flexible IPv6 support. This means you can now assign an IPv6 address that will remain the same wherever the Instance is located. Before the advent of routed IPs, IPv6 addresses were assigned per node location, thus whenever an Instance was relocated, its IPv6 address was changed.
+Note that for the best experience with IPv6, your Instance must be supported (we do not provide support for EOL Operating Systems).
+For IPv6 only, you need `cloud-init` version [23.2](https://github.com/canonical/cloud-init/releases/tag/23.2) or later and `scaleway-ecosystem` version 0.6 or later.
diff --git a/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx
new file mode 100644
index 0000000000..5f2318a592
--- /dev/null
+++ b/pages/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx
@@ -0,0 +1,275 @@
+---
+meta:
+ title: How to migrate existing volumes and snapshots to Scaleway's new Block Storage management
+ description: Learn how to migrate your existing Block Storage volumes and snapshots to Scaleway's Block Storage management.
+content:
+ h1: How to migrate existing volumes and snapshots to Scaleway's new Block Storage management
+ paragraph: This guide provides step-by-step instructions to help you migrate your existing Block Storage volumes and snapshots to Scaleway's new Block Storage management system.
+tags: instance snapshot volume b_ssd sbs
+dates:
+ validation: 2025-01-14
+ posted: 2024-08-07
+categories:
+ - compute
+---
+
+To enhance performance and reliability, Scaleway is transitioning the management of Block Storage volumes and snapshots from Compute to Storage.
+
+To facilitate the transition to Scaleway's new Block Storage management, two main approaches for migrating your volumes exist, each with its unique benefits and drawbacks:
+
+- [Using the Instance API/CLI migration endpoint (Plan and Apply)](#migrating-using-the-instance-apicli-migration-endpoint-plan-and-apply):
+ - **Advantage:** Migration can occur without service interruption, as the volume remains attached to the running Instance and fully accessible.
+ - **Drawback:** Only the volume's representation is migrated to the SBS API; the data itself does not move. This means the migrated volume will not benefit from low latency or higher IOPS, as it retains the original `b_ssd` characteristics.
+
+- [Using the snapshot export/import features](#migrating-using-the-snapshot-exportimport-features):
+ - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume.
+ - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which must then be attached to the Instance. This process may require downtime.
+
+Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/block-storage/quickstart/) instead of Compute.
+
+## Comparison of migration methods
+
+| Migration Method | Advantage | Drawback |
+|--------------------------------|-----------------------------------------------|---------------------------------------------|
+| Instance API/CLI migration | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost |
+| Snapshot export/import | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling |
+
+This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage).
+Alternatively, you can use the [snapshot export/import feature](/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes.
+
+
+
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/)
+
+
+ - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool.
+ - If you encounter an error about quota limitations during the migration process, [contact our support team](https://console.scaleway.com/support/tickets/create) for assistance.
+
+
+
+ To ensure continued access to managing your volumes, you must convert your **unified volumes and snapshots** into either **local** or **Block volumes** before the **end-of-life date of June 2nd, 2025**. After this date, unified volumes and snapshots will no longer be supported by any API.
+
+ #### Key migration deadlines:
+ - April 30th, 2025:
+ - Creation of new unified volumes via the Instance API will be disabled.
+ - Unified volumes will no longer be supported by the Instance API.
+ - June 2nd, 2025:
+ - Unified volumes and snapshots can no longer be managed via any API. Existing unified resources must be converted by this date to avoid loss of manageability.
+
+
+## Migrating using the Instance API/CLI migration endpoint (Plan and Apply):
+
+
+ During migration, unified snapshots will be converted into [Block Storage](/block-storage/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot.
+
+
+### Migrating an existing Block Storage volume to Scaleway Block Storage management
+
+
+ This process applies only to Block SSD (`b_ssd`) volumes.
+
+
+
+
+
+ When you migrate a volume, the volume and any snapshots created from it will be migrated as well.
+
+ 1. Use the following command to list your Block Storage volumes and retrieve the ID of the volume you wish to migrate:
+ ```
+ $ scw instance volume list
+ ID STATE SERVER ID SERVER NAME
+ 369feb53-165f-437d-875e-188725df462b available
+ ```
+ 2. Plan the volume migration using the `scw instance volume plan-migration ` command. This command returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration.
+ ```
+ $ scw instance volume plan-migration 369feb53-165f-437d-875e-188725df462b
+ Volume.ID 369feb53-165f-437d-875e-188725df462b
+ Volume.Name vol-peaceful-davinci
+ Volume.Size 25 GB
+ Volume.VolumeType b_ssd
+ Volume.CreationDate 2 weeks ago
+ Volume.ModificationDate 2 weeks ago
+ Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c
+ Volume.Server.Name scw-naughty-robinson
+ Volume.State available
+ Volume.Zone fr-par-1
+ Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f
+ Snapshots.0.Name image-scw-quirky-torvalds_snap_0
+ Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.0.VolumeType b_ssd
+ Snapshots.0.Size 10 GB
+ Snapshots.0.State available
+ Snapshots.0.CreationDate 2 weeks ago
+ Snapshots.0.ModificationDate 5 days ago
+ Snapshots.0.Zone fr-par-1
+ Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c
+ Snapshots.1.Name snap-eloquent-edison
+ Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.1.VolumeType b_ssd
+ Snapshots.1.Size 10 GB
+ Snapshots.1.State available
+ Snapshots.1.CreationDate 2 weeks ago
+ Snapshots.1.ModificationDate 5 days ago
+ Snapshots.1.Zone fr-par-1
+ ValidationKey 30d129ca895c4cd59f4c429e12dab300
+ ```
+ 3. Execute the migration using the `scw instance volume apply-migration validation-key= zone=` command.
+ ```
+ $ scw instance volume apply-migration 369feb53-165f-437d-875e-188725df462b validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1
+ ✅ Success
+ ```
+ The volume migration is complete. You can now manage the migrated volume from the [Block Storage volumes section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console.
+
+
+
+ When you migrate a volume using the API, the volume and any snapshots created from the volume will be migrated.
+
+
+ 1. Plan the migration by sending a `POST` request to the Scaleway API:
+
+ ```bash
+ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \
+ --header "Content-Type: application/json" \
+ --header "X-Auth-Token: $SCW_SECRET_KEY" \
+ --data "{
+ \"volume_id\": \"$SCW_VOLUME_ID\"
+ }"
+ ```
+
+ This request returns the volume and its snapshots that will be migrated, along with a unique `ValidationKey` required to start the migration.
+
+ 2. Confirm and execute the migration by sending another `POST` request:
+
+ ```bash
+ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \
+ --header "Content-Type: application/json" \
+ --header "X-Auth-Token: $SCW_SECRET_KEY" \
+ --data "{
+ \"volume_id\": \"$SCW_VOLUME_ID\",
+ \"validation_key\": \"$SCW_VALIDATION_KEY\"
+ }"
+ ```
+
+
+
+### Migrating an existing Block Storage snapshot to Scaleway Block Storage management
+
+
+ This process applies to Block SSD (`b_ssd`) or Unified (`unified`) snapshots.
+
+
+
+
+
+ When you migrate a snapshot, the source volume of the snapshot and any snapshots created from this volume will also be migrated.
+
+ 1. Use the following command to list your snapshots and retrieve the ID of the snapshot you wish to migrate:
+ ```
+ $ scw instance snapshot list
+ ID NAME
+ a377afe5-a9a3-4706-b8c2-8d1c247a620f snap-eloquent-edison
+ ```
+ 2. Plan the snapshot migration using the `scw instance snapshot plan-migration ` command. This command returns the source volume of the snapshot and any related snapshots that will be migrated, along with a unique `ValidationKey`.
+ ```
+ $ scw instance snapshot plan-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f
+ Volume.ID 369feb53-165f-437d-875e-188725df462b
+ Volume.Name vol-peaceful-davinci
+ Volume.Size 25 GB
+ Volume.VolumeType b_ssd
+ Volume.CreationDate 2 weeks ago
+ Volume.ModificationDate 2 weeks ago
+ Volume.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Volume.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Volume.Server.ID 177c6ed5-e999-4cc7-b152-8ce56217579c
+ Volume.Server.Name scw-naughty-robinson
+ Volume.State available
+ Volume.Zone fr-par-1
+ Snapshots.0.ID a377afe5-a9a3-4706-b8c2-8d1c247a620f
+ Snapshots.0.Name image-scw-quirky-torvalds_snap_0
+ Snapshots.0.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.0.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.0.VolumeType b_ssd
+ Snapshots.0.Size 10 GB
+ Snapshots.0.State available
+ Snapshots.0.CreationDate 2 weeks ago
+ Snapshots.0.ModificationDate 5 days ago
+ Snapshots.0.Zone fr-par-1
+ Snapshots.1.ID 384799c2-c4dd-40ab-bd65-ed95cd7b4d5c
+ Snapshots.1.Name snap-eloquent-edison
+ Snapshots.1.Organization 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.1.Project 4a2e00bf-5126-43ce-9b09-be943c619139
+ Snapshots.1.VolumeType b_ssd
+ Snapshots.1.Size 10 GB
+ Snapshots.1.State available
+ Snapshots.1.CreationDate 2 weeks ago
+ Snapshots.1.ModificationDate 5 days ago
+ Snapshots.1.Zone fr-par-1
+ ValidationKey 30d129ca895c4cd59f4c429e12dab300
+ ```
+ 3. Execute the migration using the `scw instance snapshot apply-migration validation-key= zone=` command.
+ ```
+ $ scw instance snapshot apply-migration a377afe5-a9a3-4706-b8c2-8d1c247a620f validation-key=30d129ca895c4cd59f4c429e12dab300 zone=fr-par-1
+ ✅ Success.
+ ```
+ The snapshot migration is complete. You can now manage the migrated snapshot from the [Block Storage Snapshot section](https://console.scaleway.com/block-storage/volumes) in the Scaleway console.
+
+
+
+ When you migrate a snapshot using the API, the source volume of the snapshot and any snapshots created from this volume will also be migrated.
+
+
+ 1. Plan the migration by sending a `POST` request to the Scaleway API:
+
+ ```bash
+ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/plan" \
+ --header "Content-Type: application/json" \
+ --header "X-Auth-Token: $SCW_SECRET_KEY" \
+ --data "{
+ \"snapshot_id\": \"$SCW_SNAPSHOT_ID\"
+ }"
+ ```
+
+ This request returns the source volume and any related snapshots that will be migrated, along with a unique `ValidationKey`.
+
+ 2. Confirm and execute the migration by sending another `POST` request:
+
+ ```bash
+ curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/block-migration/apply" \
+ --header "Content-Type: application/json" \
+ --header "X-Auth-Token: $SCW_SECRET_KEY" \
+ --data "{
+ \"snapshot_id\": \"$SCW_SNAPSHOT_ID\",
+ \"validation_key\": \"$SCW_VALIDATION_KEY\"
+ }"
+ ```
+
+
+
+## Migrating using the snapshot export/import features
+
+To convert your unified volumes and snapshots, you can use the snapshot export/import features as an alternative solution for transitioning a Block Storage legacy volume into a Block Storage Low Latency volume.
+
+
+ The process below requires manual intervention and **does not preserve the original volume’s ID**. While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround.
+
+
+Follow the procedure below:
+
+1. [Create a snapshot of your Block Storage legacy volume](/instances/how-to/create-a-snapshot/).
+2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots).
+3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket).
+
+
+## Going further
+
+To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/block-storage/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/).
+
+If you encounter any issues during migration, contact [Scaleway's support team](https://console.scaleway.com/support/tickets) for assistance.
diff --git a/pages/instances/how-to/power-off-instance.mdx b/pages/instances/how-to/power-off-instance.mdx
new file mode 100644
index 0000000000..8eccdff210
--- /dev/null
+++ b/pages/instances/how-to/power-off-instance.mdx
@@ -0,0 +1,50 @@
+---
+meta:
+ title: How to power off your Instance
+ description: This page explains how to power off a Scaleway Instance.
+content:
+ h1: How to power off your Instance
+ paragraph: This page explains how to power off a Scaleway Instance.
+tags: power off power-off instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+Powering off your Instance shuts it down by transferring all the data on the Instance's local volume to a volume store. The physical node is released back to the pool of available machines. If the Instance has a flexible IP, it will remain available in your account.
+
+
+ - Before powering off your Instance, shut down the OS by logging into your Instance as root and executing the halt command.
+ - Powering off may take some time, depending on the amount of data in the Instance’s local volume.
+
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to power off an Instance
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to power off. The **Overview** page for that Instance displays.
+3. Use the toggle in the top right corner of the screen to **power off** your Instance.
+
+ A pop-up displays asking you to confirm the action.
+
+4. Click **Power off Instance**.
+
+ When a server is powered off, only its volumes and any reserved flexible IP address are billed.
+
+
+## How to power on an Instance
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to power on again. The **Overview** page for that Instance displays.
+3. Use the toggle in the top right corner of the screen to switch your Instance to **ON**.
+ A pop-up displays asking you to confirm the action.
+4. Click **Power on Instance**.
+
+
diff --git a/pages/instances/how-to/send-emails-from-your-instance.mdx b/pages/instances/how-to/send-emails-from-your-instance.mdx
new file mode 100644
index 0000000000..4b6bdc45c1
--- /dev/null
+++ b/pages/instances/how-to/send-emails-from-your-instance.mdx
@@ -0,0 +1,43 @@
+---
+meta:
+ title: How to send emails from your Instance
+ description: Learn how to configure and send emails directly from your Instance with our comprehensive tutorial.
+content:
+ h1: How to send emails from your Instance
+ paragraph: Learn how to configure and send emails directly from your Instance with our comprehensive tutorial.
+tags: smtp email instance
+dates:
+ validation: 2025-01-06
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+By default, remote SMTP ports (25, 465, and 587) are blocked and cannot be accessed from our infrastructure to prevent spam. To send emails from your Instance, you need to open these ports in the security group configuration.
+
+
+ This document concerns enabling SMTP for Instances. If you want to enable SMTP on other resources, see our documentation on [enabling SMTP on Elastic Metal servers](/elastic-metal/how-to/enable-smtp/) and [enabling SMTP on Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp).
+
+
+
+
+- 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
+- At least one [Instance](/instances/how-to/create-an-instance/)
+- Completed the [identity verification process (KYC)](/account/how-to/verify-identity/)
+
+
+1. Click **Instances** on the side menu of the [Scaleway console](https://console.scaleway.com).
+2. Click the **Security groups** tab.
+3. Select the security group for which you want to enable SMTP ports.
+
+
+ If you have not created any security groups, your Instance has been assigned to the default security group, so this will be the one you should modify.
+
+4. Tick the checkbox **Enable SMTP**.
+
+
+ The security group settings will be immediately updated on all your virtual Instances.
+
+
+
diff --git a/pages/instances/how-to/snapshot-import-export-feature.mdx b/pages/instances/how-to/snapshot-import-export-feature.mdx
new file mode 100644
index 0000000000..4bc452ebaf
--- /dev/null
+++ b/pages/instances/how-to/snapshot-import-export-feature.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: Using the snapshot import/export feature from the Scaleway console
+ description: This page explains how to import/export snapshots of Instances using the Scaleway console.
+content:
+ h1: Using the snapshot import/export feature from the Scaleway console
+ paragraph: This page explains how to import/export snapshots of Instances using the Scaleway console.
+tags: snapshot, import, export, instance, availability zone, qcow2
+dates:
+ validation: 2024-08-13
+ posted: 2021-07-27
+categories:
+ - compute
+---
+
+The snapshot transfer feature allows you to export or import Instance snapshots. Snapshots are created using the QCOW2 format and stored in a Scaleway Object Storage Bucket.
+
+A snapshot stored in a Scaleway Object Storage bucket can be imported into any Availability Zone (AZ), as long as it is in the same region as the bucket. This allows you to create Instances in different AZs within the same region. For example, you can deploy Instances in `fr-par-2` based on the snapshot exported from an Instance in `fr-par-1`.
+
+More information on the QCOW2 file format and how to use it can be found in the [QEMU documentation](https://www.qemu.org/docs/master/system/images.html#cmdoption-image-formats-arg-qcow2).
+
+
+
+- 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
+- A valid [API key](/iam/how-to/create-api-keys/)
+- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/)
+- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/)
+
+## Creating a snapshot from your existing Instance
+
+
+For this guide, we assume you have an Instance running in the `fr-par-1` AZ, your Object Storage bucket is located in the region `fr-par`, and you want to create a new Instance in the `fr-par-2` AZ.
+
+
+1. Click the [Instances section](https://console.scaleway.com/instance/servers) of the Scaleway console, then click the **Snapshots** tab.
+2. Click **+ Create snapshot**. The snapshot creation wizard appears. Enter a name and select the volume to snapshot. Then click **Create snapshot**. The snapshot is created, and the list of all your snapshots displays.
+
+3. Click next to the relevant snapshot, and select **Copy to bucket**. A pop-up displays. Enter the file name for your exported snapshot copy and select the destination bucket. Then click **Copy snapshot to bucket**.
+
+## Importing the snapshot into the destination AZ
+
+1. Click the [Object Storage section](https://console.scaleway.com/object-storage/buckets) of the Scaleway console, then click the bucket to which you have exported the snapshot. The snapshot copy should display in the list of your objects.
+
+ Depending on the size of your snapshot, the export to Object Storage may take some time. It is ready once the status indicator changes to green.
+
+2. Click next to the snapshot copy, then click **Import as snapshot**. A pop-up will appear. Enter the name of the snapshot, select the destination AZ, and choose the snapshot type.
+ The type can be either **Local SSD** or **Block SSD**. Click **Import file as snapshot** to import the snapshot into the destination AZ.
+
+ - Ensure that the QCOW / QCOW2 image file you want to import uses the file extension `.qcow` or `.qcow2` to avoid issues during import.
+ - Imported snapshots must have a volume size between 1 GB and 1 TB.
+
+
+## Creating Instances from the imported snapshot
+
+1. Click the [Instances section](https://console.scaleway.com/instance/servers) of the Scaleway console, then click **+Create Instance**.
+2. Select the Availability Zone into which you have imported the snapshot and the desired Instance type. Under **Choose an image**, click **My snapshots** to select the imported snapshot.
+3. Optionally, add additional volumes, enter a name and optional tags. Once your configuration is complete, click **Create Instance** to launch the Instance creation process.
+
+You can now connect to your new Instance using SSH. It will have the same software configuration as the source Instance.
\ No newline at end of file
diff --git a/pages/instances/how-to/use-boot-modes.mdx b/pages/instances/how-to/use-boot-modes.mdx
new file mode 100644
index 0000000000..40993bdbb2
--- /dev/null
+++ b/pages/instances/how-to/use-boot-modes.mdx
@@ -0,0 +1,107 @@
+---
+meta:
+ title: How to use boot modes on Instances
+ description: This page explains how to use boot modes for Scaleway Instances.
+content:
+ h1: How to use boot modes on Instances
+ paragraph: This page explains how to use boot modes for Scaleway Instances.
+tags: boot-mode boot mode boot instance bootscript
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+You can boot your Instances using local boot or a rescue image. This page explains how to use each of these boot modes.
+
+
+ - You can choose to use **cloud-init** when [creating an Instance](/instances/how-to/create-an-instance/) via **Advanced settings**. This enables you to control the mode of the Instance's very first boot.
+ - Your Instance must be [powered off](/instances/how-to/power-off-instance/) in order to change its boot mode.
+
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to use local boot
+
+Local boot allows you to start your Instance with a local configuration and a specific kernel version. This is the default option. You only need to follow these instructions to revert to local boot after using a different boot mode.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you wish to start with a local boot.
+3. Use the toggle in the top right corner of the screen to **power off** your Instance.
+4. Click the **Advanced settings** tab.
+5. In the **Boot mode** section, select **Use local boot**.
+6. Click **Save**.
+7. Use the toggle in the top right corner of the screen to **power on** your Instance.
+
+ Your Instance starts using local boot.
+
+## How to use rescue mode
+
+Rescue mode restarts your Instance via the network on a minimal operating system. You can use rescue mode to debug your Instance and recover your system data.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you wish to boot into Rescue Mode.
+3. Use the toggle in the top right corner of the screen to **power off** your Instance.
+4. Click the **Advanced settings** tab.
+5. In the **Boot mode** section, select **Use rescue image**.
+6. Click **Save**.
+7. Use the toggle in the top right corner of the screen to **power on** your Instance.
+
+ Your Instance starts in Rescue mode.
+
+## How to use cloud-init
+
+[Cloud-init](/instances/concepts/#cloud-init) enables automatic configuration of an Instance as it boots into the cloud, turning it from a generic Ubuntu image into a configured server in a few seconds.
+
+The cloud-init program can consume and execute data from the user-data field of the Scaleway console. The process then behaves differently depending on the format of the information it finds. One of the most popular formats for scripts within user-data is the cloud-config file format. Cloud-config files are special scripts designed to be run by the cloud-init process.
+These are generally used for initial configuration on the very first boot of a server. **Cloud-init is available for all Scaleway Instances OS images.**
+
+Follow the instructions below to reboot an existing Instance using cloud-init.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you wish to use with cloud-init.
+3. Click the **Advanced settings** tab.
+4. In the **Cloud-init** section, use the toggle to activate **Use cloud-init**.
+5. Enter your **user-data**. User data is the mechanism by which a user can pass information contained in a local file to an Instance at launch time. The typical use case is to pass something like a shell script or a configuration file as user data.
+
+ Cloud-init supports different input formats for user-data:
+
+ |Format|Starts with|Description|
+ | ---- | ------------- | --------- |
+ |**Cloud Config File**|`#cloud-config` or `Content-Type: text/cloud-config`| This file contains `cloud-config` data|
+ | **Shell Script**|`#!` or `Content-Type: text/x-shellscript`|A shell script will be executed at `rc.local` like level during first boot.|
+ |**Include File**|`#include` or `Content-Type: text/x-include-url`|An include file contains a list of one or different URLs, one per line. Each of the URLs will be read, and their content will be passed through this same set of rules. The content read from the URL can either be gzipped, mime-multi-part, or plain text.|
+ |**Gzip Compressed Content**||Gzip compressed content will be uncompressed and then be used as if it were not compressed. This is useful as user data is limited to 16384 bytes.|
+ |**MIME multipart archive**||It is possible to specify more than one type of data by using a MIME multipart file. This can be used to specify both, a shell script and a cloud-config task.|
+ |**Upstart Job**| `#upstart-job` or `Content-Type: text/upstart-job`||
+ |**Cloud Boothook**|`#cloud-boothook` or `Content-Type: text/cloud-boothook`||
+ |**Part Handler**|Starts with `#part-handler` or `Content-Type: text/part-handler`||
+6. Click **Save**.
+7. Click **Reboot** in the top right corner of the page, and confirm the reboot of your Instance when prompted.
+
+ Your Instance is rebooted using cloud-init.
+
+## How to change the boot volume
+
+The [boot-on-block](/instances/concepts/#boot-on-block) feature allows Instances to boot from attached [Block Storage](/instances/concepts/#block-volumes) volumes instead of local volumes. When [creating an Instance](/instances/how-to/create-an-instance/), you can select Block Storage as a boot volume.
+
+Once the Instance is created, you can select a different volume to boot from.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you wish to change the boot volume for.
+3. Click the **Advanced settings** tab.
+4. Go to the **Boot volume** section.
+5. Select a volume in the drop-down.
+6. Click **Save and reboot now** to reboot instantly. Alternatively, click **Save and reboot later**.
+
+ If you have two or more volumes with identical operating systems, or a volume with no operating system, choosing one of these as your boot volume may cause unpredictable boot behavior.
+
+
+
diff --git a/pages/instances/how-to/use-flexips.mdx b/pages/instances/how-to/use-flexips.mdx
new file mode 100644
index 0000000000..a3399229a9
--- /dev/null
+++ b/pages/instances/how-to/use-flexips.mdx
@@ -0,0 +1,85 @@
+---
+meta:
+ title: How to use flexible IP addresses with Instances
+ description: This page explains how to use flexible IP addresses with Scaleway Instances.
+content:
+ h1: How to use flexible IP addresses with Instances
+ paragraph: This page explains how to use flexible IP addresses with Scaleway Instances.
+tags: flexible-ip Instance flexible ip detach delete attach
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+This page provides guidance on using [flexible IP addresses](/instances/concepts/#flexible-ip) with your Scaleway Instances.
+
+When creating an Instance, you have options for network connectivity:
+
+- **Flexible Routed IP addresses**: These are public IP addresses routed directly to your Instance. **Recommended.**
+- **Flexible NAT IP addresses (Legacy)**: Comprising a public IP address (also a flexible IP address) and a private IP address routed to your Instance via a [CG-NAT](/instances/concepts/#carrier-grade-nat-cgnat).
+
+Flexible IP addresses can be managed independently of any Instance. You can attach and detach them from any of your Instances and maintain multiple flexible IP addresses in your account simultaneously. They facilitate [live migration of IP addresses between your Instances](/instances/how-to/migrate-instances/).
+
+You can assign up to five (5) flexible routed IP addresses to each Instance or one set of flexible NAT IP addresses.
+
+
+ Instances using routed public IPv4 addresses can also use flexible IPv6 addresses.
+
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+
+
+## How to detach a flexible IP address from an Instance
+
+Detaching your Instance's flexible (public) IP address cuts any ongoing public connection to the Instance. This feature gives you a lot of control if, for example, you want to put your Instances into a Private Network so that they can communicate between themselves without being exposed to the internet. This is particularly useful for Instances hosting databases, backups, or sensitive content. It also allows you to optimize your costs and fight the global IPv4 shortage.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance whose IP address you want to detach. The Overview page for that Instance displays.
+3. Click **Detach** next to **Public IP**.
+4. Click **Detach IP** on the pop-up that asks you to confirm the action.
+
+ You can also detach a flexible IP by following step 1 above, then clicking on the **Flexible IPs** tab. From here, click next to said Instance, and click **Detach flexible IP from Instance**.
+
+
+## How to create a new flexible IP address
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Navigate to the **Flexible IPs** tab.
+3. Click **Create flexible IP**. The flexible IP creation wizard displays.
+4. Complete the following information in the wizard:
+ - Choose an **Availability Zone**, which is the geographical region where your flexible IP will be created.
+ - Optionally, select the **Instance** to which you want to attach this new flexible IP. You can only choose from Instances that do not already have a flexible IP attached to them.
+ - Check the **Estimated cost** for the flexible IP.
+5. Click **Create flexible IP** to finish.
+
+ You are taken to the list of your flexible IPs, where the new flexible IP address you just created now appears.
+
+## How to attach an existing flexible IP address to an Instance
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Navigate to the **Flexible IPs** tab.
+3. Click next to the flexible IP that you want to attach to an Instance. In the drop-down menu that opens, click **Switch Instance**.
+
+ This option will only be clickable if you have existing Instances with no flexible IPs attached to them.
+
+4. Confirm the Instance that you want to attach to this flexible IP in the pop-up window, and click **Attach flexible IP to Instance**.
+
+## How to delete a flexible IP address
+
+When you no longer want one of your existing flexible IP addresses, you can delete it from your account, which releases it to be used by other users.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Navigate to the **Flexible IPs** tab.
+3. Click next to the flexible IP that you want to delete. In the drop-down menu which opens, click **Delete**.
+4. Confirm that you want to delete the flexible IP in the pop-up window which opens, by clicking **Delete flexible IP**.
+
+ The flexible IP is deleted. If it was attached to an Instance, that Instance now has no public IP address.
+
+
diff --git a/pages/instances/how-to/use-placement-groups.mdx b/pages/instances/how-to/use-placement-groups.mdx
new file mode 100644
index 0000000000..2a9c3c9ba8
--- /dev/null
+++ b/pages/instances/how-to/use-placement-groups.mdx
@@ -0,0 +1,134 @@
+---
+meta:
+ title: How to use placement groups
+ description: This page explains how to use placement groups with Scaleway Instances.
+content:
+ h1: How to use placement groups
+ paragraph: This page explains how to use placement groups with Scaleway Instances.
+tags: placement-group instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+[Placement groups](/instances/concepts/#placement-groups) allow you to define if you want certain Instances to run on different physical hypervisors for maximum availability or as physically close together as possible for minimum latency.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to create a placement group
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Placement groups** tab.
+3. Click **Create placement group**. The creation wizard displays.
+4. Complete the following steps in the wizard:
+ - Enter a **name** for your placement group, or leave the randomly-generated name in place.
+ - Choose an **Availability Zone**, which is the geographical region where your placement group will be created. You can only add Instances from this same Availability Zone to the placement group.
+ - Choose the **type** of placement group:
+ - **Low Latency** groups ensure that Instances are located as close as possible to each other
+ - **Maximum Availability** groups ensure that Instances do not run on the same physical hypervisor
+ - Choose the **policy** for your placement group:
+ - **Enforced**: if the group cannot be applied, only Instances on hypervisors matching the group settings will boot.
+ - **Optional**: ensures the application of the placement group's settings wherever possible, but lets Instances boot on hypervisors that do not match the group policy.
+ - Add **Instances** to the placement group.
+
+
+ You can only add powered off Instances to a placement group.
+
+5. Click **Create placement group** to finish. Your placement group is created, and you are returned to the list of your placement groups.
+
+## How to add Instances to a placement group
+
+
+ You must power off your Instance to perform this action.
+
+
+1. Go to the **Placement groups** tab, accessible from the **Instances** page under the **Compute** section of the side menu. A list of your placement groups displays.
+2. Click the placement group you want to add Instances to. You are taken to the **Overview** for that placement group.
+3. Click the **Instances** tab.
+4. Use the drop-down menu to select the Instance you want to add, then click **Add Instance**
+
+ You can add up to 20 Instances to each of your placement groups.
+
+
+You are returned to the list of Instances attached to your placement group, where the Instance you added now displays. If you wish to power the Instance you added back on, you can do so by clicking , and selecting **Power on** from the drop-down menu.
+
+
+ You can also add an Instance to a placement group from the Instances page (accessible by clicking **Instances** in the **Compute** section of the console side menu). From there, click the name of the Instance in question, then scroll down to the **Placement group** section of the Instance Overview tab. Click **Manage placement group** and select the placement group you want to add the Instance to, confirming your choice when prompted.
+
+
+## How to remove Instances from a placement group
+
+1. Go to the **Placement groups** tab, accessible from the **Instances** page under the **Compute** section of the side menu. A list of your placement groups displays.
+2. Click the placement group you wish to remove Instances from. You are taken to the **Overview** for that placement group.
+3. Click the **Instances** tab.
+4. Click next to the Instance you want to remove, then click **Remove**.
+ A pop-up displays.
+5. Confirm that you want to remove the Instance by clicking the **Remove from placement group** button.
+
+ You are returned to the list of Instances attached to your placement group, where the Instance you removed no longer displays.
+
+
+ You can also remove an Instance from a placement group from the Instances page (accessible by clicking **Instances** in the **Compute** section of the console side menu). From there, click the name of the Instance in question, then scroll down to the **Placement group** section of the Instance Overview tab. Click next to the placement group you want to manage, and select **Remove** from the drop-down menu, confirming your choice when prompted.
+
+
+## How to change an Instance's placement group
+
+
+ You must power off your Instance to perform this action.
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the name of the Instance you want to edit. The Instance Overview tab displays.
+3. Scroll down to **Placement groups**.
+4. Click next to the placement group name, and select **Switch** from the drop-down menu. A pop-up displays.
+5. Select another placement group from the drop-down list, then click **Save settings**.
+
+ Your Instance's placement group is changed, and you are returned to the Instance Overview page. If you wish to power the Instance back on, you can do so using the button at the top right of the page.
+
+
+ You can also switch Instances of a placement group from the Instances page (accessible by clicking **Instances** in the **Compute** section of the console side menu). From there, click the name of the Instance in question, then scroll down to the **Placement group** section of the Instance Overview tab. Click next to the placement group you want to switch from, and select **Switch** from the drop-down menu. You are prompted to select a different placement group, and to confirm your choice.
+
+
+## How to modify a placement group's type
+
+
+ You must power off all Instances within a placement group to perform this action.
+
+
+1. Go to the **Placement groups** tab, accessible from the **Instances** page under the **Compute** section of the side menu. A list of your placement groups displays.
+2. Click the placement group in question. You are taken to the placement group's Overview tab.
+3. Scroll down to the **Placement group type** section, and choose the required type for your group.
+
+The new group type will be applied immediately, and Instances of the group will boot according to the new settings once they are powered back on.
+
+## How to modify a placement group's policy
+
+
+ You must power off all Instances within a placement group to perform this action.
+
+
+1. Go to the **Placement groups** tab, accessible from the **Instances** page under the **Compute** section of the side menu. A list of your placement groups displays.
+2. Click the placement group in question. You are taken to the placement group's Overview tab.
+3. Scroll down to the **Placement group policy** section, and choose the required policy for your group.
+
+The new group policy will be applied immediately, and Instances of the group will boot according to the new settings once they are powered back on.
+
+## How to delete a placement group
+
+Deleting a placement group will have no direct impact on the Instances attached to it. They will continue to run on their current hypervisors until you reboot them.
+
+1. Go to the **Placement groups** tab, accessible from the **Instances** page under the **Compute** section of the side menu. A list of your placement groups displays.
+2. Click next to the placement group you want to delete, and select **Delete** from the drop-down menu that displays.
+
+ A pop-up appears asking you to confirm this action.
+3. Click **Delete placement group**.
+
+ You are returned to the list of your placement groups, where the group you deleted no longer displays.
+
+
diff --git a/pages/instances/how-to/use-private-networks.mdx b/pages/instances/how-to/use-private-networks.mdx
new file mode 100644
index 0000000000..a82008f458
--- /dev/null
+++ b/pages/instances/how-to/use-private-networks.mdx
@@ -0,0 +1,78 @@
+---
+meta:
+ title: How to use Private Networks with your Instances
+ description: This page explains how to use Private Networks for Scaleway Instances
+content:
+ h1: How to use Private Networks with your Instances
+ paragraph: This page explains how to use Private Networks for Scaleway Instances
+tags: private-networks private networks instance
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+[Private Networks](/vpc/concepts/#private-networks) allow your Instances to communicate in an isolated and secure network without needing to be connected to the public internet. Each Instance can be connected to one or several Private Networks, letting you build your own network topologies.
+
+Private Networks are LAN-like layer 2 ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Private Networks' built-in DHCP server manages the distribution of private IP addresses for Instances (and other resources) when they are attached to the network.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to create a new Private Network
+
+The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings (created in your [default VPC](/vpc/concepts/#default-vpc) for the region, with an auto-generated [CIDR block](/vpc/concepts/#cidr-block)). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network.
+
+If you want to create a Private Network without immediately attaching any resources or create it in a specific VPC or with a custom CIDR block, follow [this procedure instead](/vpc/how-to/create-private-network/).
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to add a Private Network to.
+3. Click the **Private Networks** tab.
+4. Click the **Attach to a Private Network** button. A pop-up displays.
+5. Select **Attach to a new Private Network**.
+6. Enter a **Name** for your Private Network, or leave the randomly-generated name in place.
+7. Click **Attach to a Private Network** to finish.
+
+ Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block).
+
+ You are taken back to the Private Networks tab, where your new Private Network is now displayed in the list and you can see the IP address for your Instance on the network. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address).
+
+## How to attach Instances to an existing Private Network
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to add a Private Network to.
+3. Click the **Private Networks** tab.
+4. Click the **Attach to a Private Network** button. A pop-up displays.
+5. Select **Attach to an existing Private Network*
+6. Select the Private Network you want to attach the Instance to.
+
+ Only Instances from the same region as your Private Network will be available in the drop-down menu.
+
+7. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Instance will have on this Private Network.
+8. Click **Attach to Private Network**.
+
+ You are taken back to the **Private Networks** tab, where you can see the private IP address for the Instance you just attached. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address).
+
+## How to detach Instances from a Private Network
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to detach from a Private Network.
+3. Click the **Private Networks** tab.
+4. Click the icon next to the resource you want to detach.
+5. Click **Detach resource** when prompted to confirm.
+
+ You are taken back to the **Private Networks** tab, where the Instance you just detached is now removed from the list.
+
+## How to delete a Private Network
+
+
+ Before deleting a Private Network, you must [detach](/instances/how-to/use-private-networks/#how-to-detach-instances-from-a-private-network) all Instances attached to it.
+
+
+This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/).
+
+
diff --git a/pages/instances/how-to/use-protected-instance.mdx b/pages/instances/how-to/use-protected-instance.mdx
new file mode 100644
index 0000000000..6f872d3fcb
--- /dev/null
+++ b/pages/instances/how-to/use-protected-instance.mdx
@@ -0,0 +1,33 @@
+---
+meta:
+ title: How to use the Protected Instance feature
+ description: Learn how to effectively use the Protected Instance feature in this comprehensive guide.
+content:
+ h1: How to use the Protected Instance feature
+ paragraph: Learn how to effectively use the Protected Instance feature in this comprehensive guide.
+tags: protected-instance protected instance
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+The [Protected Instance](/instances/concepts/#protected-instance) feature is used to prevent any `halt` action from being performed on your Instance. This only applies to running Instances. Enabling the Protected Instance feature means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. This feature is useful to avoid hazardous manipulations, such as batch deletion of Instances.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to activate the Protected Instance feature
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to protect. The **Overview** page for that Instance displays.
+3. Click the **Advanced settings** tab.
+4. Scroll down to the **Protected Instance** section, and use the toggle to activate the Protected Instance feature.
+ A pop-up displays asking you to confirm the action.
+5. Click **Enable Protected Instance**.
+
+
diff --git a/pages/instances/how-to/use-security-groups.mdx b/pages/instances/how-to/use-security-groups.mdx
new file mode 100644
index 0000000000..0284b33236
--- /dev/null
+++ b/pages/instances/how-to/use-security-groups.mdx
@@ -0,0 +1,94 @@
+---
+meta:
+ title: How to use security groups
+ description: Learn how to create, edit, and configure security groups on Scaleway Instances to control traffic and enhance security.
+content:
+ h1: How to use security groups
+ paragraph: Learn how to create, edit, and configure security groups on Scaleway Instances to control traffic and enhance security.
+tags: security create instance traffic security-group
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+[Security groups](/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow traffic to and from your Instance. On this page, we show you how to create, edit, and configure a security group via the Scaleway console.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to create a security group
+
+
+ Security Groups only allow the filtering of **public** traffic to and from your Instances. To filter traffic within a Private Network, you can [configure a firewall](/tutorials/installation-uncomplicated-firewall/) directly on your Instance.
+
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Security groups** tab. The Security groups dashboard displays.
+
+ You will see that at least one **Default security group** already exists in your account. A default security group is auto-generated for each [Availability Zone](/instances/concepts/#availability-zone) you have created Instances in. All your Instances within that Availability Zone are automatically added to that default security group unless you specify a different configuration.
+
+3. Click **+ Create security group** to launch the security group creation wizard.
+4. Complete the following steps:
+ - Choose a **Name** for your security group or keep the randomly generated suggestion. Optionally, add a description.
+ - Choose an **Availability Zone**, which is the geographical location in which your security group will be created. Only Instances from the same Availability Zone can be added to this security group.
+ - Define the inbound and outbound **rules** that will be applied to your security group, including whether you wish to enable SMTP ports. [Learn how to choose security group settings](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings).
+ - Select the **Instances** you wish to add to the security group.
+5. Click **Create security group** to finish. Your security group is created, and you are redirected to the **Security groups** tab, where it now appears.
+
+## How to edit a security group
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the **Security groups** tab. The **Security groups** dashboard displays.
+3. Click the security group you want to edit. Alternatively, click the icon to the right of the security group in question, and select **More info**. You are taken to the dashboard for that security group.
+4. Navigate to the required tab depending on the edit you want to make:
+
+ On the **Overview** tab, you can:
+ - Set/unset this security group as the project default,
+ - Enable/disable SMTP for outgoing emails,
+ - Enable/disable stateful group rules,
+ - Delete the security group.
+
+ On the **Instances** tab, you can:
+ - Link Instances to this security group, using the drop-down menu,
+ - Unlink Instances from the security group, using the button.
+
+ On the **Rules** tab, you can:
+ - Set default inbound and outbound policies, by clicking and choosing **drop** or **accept** for inbound and outbound traffic.
+ - Create, edit, or delete rules to drop or incoming traffic from defined sources:
+ - Click ,
+ - Click the **Add inbound rule** or **Add outbound rule** buttons that appear,
+ - Create your rule and click when you have finished confirming the new rule.
+
+ See [How to choose security group settings](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings) for more information on these choices.
+
+## How to choose security group settings
+
+### Enabling SMTP
+By default, SMTP ports are blocked for security reasons to prevent email spam. This means that you cannot send outgoing emails from the Instance. We recommend leaving this default setting unless you specifically need to send emails from your Instance.
+
+To enable or disable SMTP for a security group, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4.
+
+### Enabling stateful groups
+By default, security groups created via the console are stateful. To disable or re-enable stateful groups, follow the [instructions for editing a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4.
+- **Stateless**: These strictly enforce the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance. [Learn more about stateless security groups](/instances/concepts/#stateless-security-groups).
+- **Stateful**: These disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. [Learn more about stateful security groups](/instances/concepts/#stateful-security-groups).
+
+### Setting default inbound and outbound policies
+You can set default policies to drop or accept all inbound traffic, and drop or accept all outbound traffic. We recommend blocking incoming traffic by default to prevent intrusions. To change your default inbound and outbound policies, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group), checking the relevant boxes in the **Rules** tab at step 4.
+
+### Creating inbound and outbound rules
+You can create customized inbound and outbound rules to drop or accept traffic on particular protocols, ports, and IP ranges. To do so, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group), by clicking the edit icon in the **Rules tab** in step 4.
+
+For each rule, choose the following options:
+- **Rule**: The value can either be **Drop** to drop connections that match the rule or **Accept** to accept these connections.
+- **Protocol**: This field specifies the protocol on which the rule applies. The value can either be TCP, UDP, or ICMP.
+- **Port**: This field specifies the port on which the rule applies. If the **All Ports** box is checked, the rule applies to all ports.
+- **IP Range**: The IP range in CIDR notation on which the rule applies.
+
+
diff --git a/pages/instances/how-to/use-serial-console.mdx b/pages/instances/how-to/use-serial-console.mdx
new file mode 100644
index 0000000000..d642a6eb9e
--- /dev/null
+++ b/pages/instances/how-to/use-serial-console.mdx
@@ -0,0 +1,38 @@
+---
+meta:
+ title: How to use the serial console to connect to an Instance
+ description: This page explains how to use the serial console to connect to a Scaleway Instance.
+content:
+ h1: How to use the serial console to connect to an Instance
+ paragraph: This page explains how t use the serial console to connect to a Scaleway Instance.
+tags: serial console serial-console instance connection
+dates:
+ validation: 2024-08-26
+ posted: 2022-02-25
+categories:
+ - compute
+---
+
+This page shows how to connect to your Scaleway Instance from the Scaleway console using the serial console (TTY, from **T**ele**TY**pewriter). It provides a way to connect to your Instance for debugging, or if it loses its network connectivity. The serial console remains available even if you can not reach your Instance over the internet.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+- A password for your Linux user
+
+## How to use the serial console (TTY)
+
+
+ You have to connect to your Instance using [SSH](/instances/how-to/connect-to-instance/) and define a user password before connecting to your Instance using the serial console.
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to connect to.
+3. Click **Console** on the Instance **Overview** page. The serial console (TTY) displays in a pop-up.
+
+4. Login using your Linux user and password. You can now run all Linux commands like in an SSH shell.
+
+
diff --git a/pages/instances/how-to/use-standby-mode.mdx b/pages/instances/how-to/use-standby-mode.mdx
new file mode 100644
index 0000000000..d96455949a
--- /dev/null
+++ b/pages/instances/how-to/use-standby-mode.mdx
@@ -0,0 +1,40 @@
+---
+meta:
+ title: How to use standby mode
+ description: Learn how to use standby mode on Scaleway Instances to save resources and reduce costs without losing data or configurations.
+content:
+ h1: How to use standby mode
+ paragraph: Learn how to use standby mode on Scaleway Instances to save resources and reduce costs without losing data or configurations.
+tags: instance standby standby-mode
+dates:
+ validation: 2024-08-26
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## How to put an Instance into standby mode
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the Instance you want to put into standby mode. The Overview page for that Instance displays.
+3. Scroll down to the **Standby mode** section
+
+4. Click **Switch to standby mode**. A pop-up displays asking you to confirm the action.
+5. Click **Switch Instance to standby mode** to confirm.
+
+ Your Instance is now in standby mode.
+
+
+ You are still billed for an Instance in standby mode, as well as for its storage and any flexible IPs attached to it. To avoid being charged for an unused Instance, you can [power it off](/instances/how-to/power-off-instance/).
+ [Find out when the billing of your Instance starts and stops](/faq/billing/#when-does-the-billing-of-an-instance-start-and-stop).
+
+
+
diff --git a/pages/instances/index.mdx b/pages/instances/index.mdx
new file mode 100644
index 0000000000..356963f3b5
--- /dev/null
+++ b/pages/instances/index.mdx
@@ -0,0 +1,87 @@
+---
+meta:
+ title: Instances Documentation
+ description: Dive into Scaleway Instances with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+## Tutorials
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/instances/quickstart.mdx b/pages/instances/quickstart.mdx
new file mode 100644
index 0000000000..ee0bc57672
--- /dev/null
+++ b/pages/instances/quickstart.mdx
@@ -0,0 +1,100 @@
+---
+meta:
+ title: Instances - Quickstart
+ description: This page shows you how to get started with Scaleway Instances.
+content:
+ h1: Instances - Quickstart
+ paragraph: This page shows you how to get started with Scaleway Instances.
+tags: instance connection delete create
+dates:
+ validation: 2024-12-19
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+Scaleway [Instances](/instances/concepts/#instance) are computing units that provide you with resources to run your applications. After you have created your Instance and installed your image of choice (e.g., an operating system), you can connect to it via SSH to use it as you wish. When you are done using the Instance, you can delete it from your account.
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+
+## How to create an Instance
+
+ 1. Click **Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays.
+ 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays.
+ 3. Complete the following steps:
+ - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed.
+ - **Choose an Instance type**.
+ Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/).
+ - **Choose an image** to run on your Instance.
+ This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/).
+ - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance.
+ - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed.
+
+ - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB.
+ - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume).
+ - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes.
+
+ - **Configure network** of the Instance.
+ - Leave the checkbox ticked to assign a **Public IPv4** to the Instance. You can either allocate a new IPv4 address or select one or multiple existing IPv4s. Alternatively, uncheck the box if you do not want an IPv4.
+ - Leave the checkbox ticked to assign a **Public IPv6** to the Instance. You can either allocate a new IPv6 address or select one or multiple existing IPv6s. Alternatively, uncheck the box if you do not want an IPv6.
+
+ You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance.
+
+ - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values.
+ You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot.
+ - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance.
+ - **Verify the Estimated cost** of your Instance, based on the specifications you chose.
+ 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready.
+ Once the Instance is created, you can connect to it using the SSH keys you have configured, and begin setting up your applications.
+
+## How to connect to an Instance
+
+### How to connect from OSX (Mac) and Linux
+
+1. Open a terminal program.
+2. Enter the command below into the terminal. Make sure you replace `your_private_key` with the filename of your private key (often `id_rsa`) and `your_instance_ip` with the IP address of your Instance.
+ ```sh
+ ssh -i ~/.ssh/your_private_key root@your_instance_ip
+ ```
+3. If / when prompted, allow connection to the host by typing `yes`, then press **Enter**.
+ ```
+ The authenticity of host 'myhost.ext (212.47.226.35)' can't be established.
+ RSA key fingerprint is 4f:ba:65:cf:14:64:a7:1e:b6:07:7c:00:71:95:21:fa.
+ Are you sure you want to continue connecting (yes/no)?
+ ```
+
+You are now connected to your Instance.
+
+
+### How to connect from Windows
+
+To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client.
+
+1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html).
+2. Launch PuTTY on your computer.
+3. Enter your Instance's IP address in the **Hostname** field.
+4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. (**Connection** > **SSH** > **Auth**).
+5. Click the **Browse** button and select the private key file you [created previously](/organizations-and-projects/how-to/create-ssh-key/).
+6. Click **Open** at the bottom of the screen to open a connection to the Instance. PuTTY asks you to allow the connection to the host.
+7. Click **OK** to confirm. The terminal window displays.
+8. Enter the username `root` and press **Enter** to authenticate against the server with your SSH key.
+
+ You are now connected to your Instance.
+
+
+ For instructions on how to connect to Instances running Microsoft Windows Server OS, refer to our dedicated documentation [How to connect to Instances running Microsoft Windows Server OS](/instances/how-to/connect-to-instance/).
+
+
+## How to delete an Instance
+
+
+ Deleting an Instance will destroy all the volumes and data stored on that Instance. Note that your Instance must be powered off or stopped to be deleted.
+
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the icon next to the Instance you want to delete and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action.
+3. Type **DELETE** and then click **Delete Instance**.
\ No newline at end of file
diff --git a/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx b/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx
new file mode 100644
index 0000000000..36c1ac75d7
--- /dev/null
+++ b/pages/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx
@@ -0,0 +1,106 @@
+---
+meta:
+ title: Using tags to add Instance-specific SSH keys
+ description: Find out how to use tags to add Instance-specific SSH keys on Scaleway.
+content:
+ h1: Using tags to add Instance-specific SSH keys
+ paragraph: Find out how to use tags to add Instance-specific SSH keys on Scaleway.
+categories:
+ - compute
+dates:
+ validation: 2024-10-08
+ posted: 2024-10-08
+tags: instance ssh-key ssh tag
+---
+
+In cloud environments, managing SSH keys across multiple Instances is key to keeping your infrastructure secure and easy to access.
+Sometimes, you need to ensure that a specific SSH key grants access to only one Instance and does not automatically apply to others.
+This can simplify key management and improve security, especially when you are running many Instances
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/)
+
+## The authorized_keys file
+
+Your authorized SSH keys are stored in the `/root/.ssh/authorized_keys` file on your Instance.
+
+```bash
+cat /root/.ssh/authorized_keys
+#
+# WARNING: Automatically generated file
+# This file will be erased at every boot
+# This file was generated with '/usr/sbin/scw-fetch-ssh-keys'
+#
+# To ad
+# To add a new key, you can:
+# -- Add keys on your Scaleway account https://cloud.scaleway.com/#/credentials
+# -- Add keys using server tags - https://cloud.scaleway.com/#/servers/
+# - i.e: "AUTHORIZED_KEY=ssh-rsa_XXXXXXXXXXX AUTHORIZED_KEY=ssh-rsa_YYYYYYYYYYYYYYY"
+# - Be sure to replace all spaces with underscores
+# - $> sed 's/ /_/g' ~/.ssh/id_rsa.pub
+# -- Add the keys to '/root/.ssh/Instance_keys' which will be imported
+#
+# And recreate your 'authorized_keys' file with the new keys:
+# -- Run 'scw-fetch-ssh-keys --upgrade'
+[...]
+```
+
+This file lists all the SSH public keys allowed to access the Instance. Our goal is to add an Instance-specific SSH key that will not be automatically applied to other Instances.
+
+
+## How to add Instance-specific SSH keys using tags
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances overview](https://console.scaleway.com/Instance/servers) displays.
+2. Click the Instance you want to add a specific key to.
+3. Navigate to the section where you can add tags to the Instance on the Instances overview page.
+4. Add the public SSH key tag by writing in the **Tags** form. You can add multiple keys by creating separate `AUTHORIZED_KEY` tags for each SSH key.
+ The format for creating SSH key tags is:
+ ```bash
+ AUTHORIZED_KEY=ssh-ed25519_XXXXXXXXXXX AUTHORIZED_KEY=ssh-ed25519_YYYYYYYYYYYYYYY
+ ```
+
+ Remember to replace any spaces with underscores (`_`) in the SSH public key string when entering it as a tag. Your actual SSH public key remains unchanged.
+
+ For example, if your public key looks like this:
+ ```bash
+ ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIG1hT8oQksyU9BLjoTtI93xT9+Ds9YRHTUZXq99c2EC3
+ ```
+ In the tag field, you would enter:
+
+ ```bash
+ AUTHORIZED_KEY=ssh-ed25519_AAAAC3NzaC1lZDI1NTE5AAAAIG1hT8oQksyU9BLjoTtI93xT9+Ds9YRHTUZXq99c2EC3
+ ```
+
+
+4. Once you have added the SSH key tag(s), they will be saved automatically in the Scaleway console.
+
+### Updating the keys on your Instance
+
+1. Run the following command on your Instance to update the list of authorized public keys:
+
+ ```bash
+ scw-fetch-ssh-keys --upgrade
+ ```
+2. Verify the SSH key on the Instance by typing the following command:
+
+ ```bash
+ cat /root/.ssh/authorized_keys
+ ```
+
+The Instance-specific key has been added to the `/root/.ssh/authorized_keys` file on the Instance alongside with your account-wide configured keys.
+The specific tag public key will not propagate to other Instances in your infrastructure.
+
+
+ Another option to update the SSH keys of your Instances is to reboot them.
+
+
+## Conclusion
+
+You now have configured an Instance-specific SSH key through the Scaleway console.
+One of the main advantages of using tags for SSH keys is that they will not apply to other Instances, even after updates or reboots.
+This ensures that only the designated Instance can be accessed with the specified SSH key.
\ No newline at end of file
diff --git a/pages/instances/reference-content/assets/DDoS_Quick_Guide.pdf b/pages/instances/reference-content/assets/DDoS_Quick_Guide.pdf
new file mode 100644
index 0000000000..19fb1ec7d4
Binary files /dev/null and b/pages/instances/reference-content/assets/DDoS_Quick_Guide.pdf differ
diff --git a/pages/instances/reference-content/assets/NP_Guide_DDoS.pdf b/pages/instances/reference-content/assets/NP_Guide_DDoS.pdf
new file mode 100644
index 0000000000..a04bd2b572
Binary files /dev/null and b/pages/instances/reference-content/assets/NP_Guide_DDoS.pdf differ
diff --git a/pages/instances/reference-content/assets/almalinux.webp b/pages/instances/reference-content/assets/almalinux.webp
new file mode 100644
index 0000000000..d41fcc4b17
Binary files /dev/null and b/pages/instances/reference-content/assets/almalinux.webp differ
diff --git a/pages/instances/reference-content/assets/archlinux.webp b/pages/instances/reference-content/assets/archlinux.webp
new file mode 100644
index 0000000000..abbccf40e0
Binary files /dev/null and b/pages/instances/reference-content/assets/archlinux.webp differ
diff --git a/pages/instances/reference-content/assets/centos.webp b/pages/instances/reference-content/assets/centos.webp
new file mode 100644
index 0000000000..b49635aa27
Binary files /dev/null and b/pages/instances/reference-content/assets/centos.webp differ
diff --git a/pages/instances/reference-content/assets/debian.webp b/pages/instances/reference-content/assets/debian.webp
new file mode 100644
index 0000000000..541fba453c
Binary files /dev/null and b/pages/instances/reference-content/assets/debian.webp differ
diff --git a/pages/instances/reference-content/assets/docker.webp b/pages/instances/reference-content/assets/docker.webp
new file mode 100644
index 0000000000..e14bc94321
Binary files /dev/null and b/pages/instances/reference-content/assets/docker.webp differ
diff --git a/pages/instances/reference-content/assets/fedora.webp b/pages/instances/reference-content/assets/fedora.webp
new file mode 100644
index 0000000000..301e8b4429
Binary files /dev/null and b/pages/instances/reference-content/assets/fedora.webp differ
diff --git a/pages/instances/reference-content/assets/gitlab.webp b/pages/instances/reference-content/assets/gitlab.webp
new file mode 100644
index 0000000000..77ba7d608d
Binary files /dev/null and b/pages/instances/reference-content/assets/gitlab.webp differ
diff --git a/pages/instances/reference-content/assets/nextcloud.webp b/pages/instances/reference-content/assets/nextcloud.webp
new file mode 100644
index 0000000000..f79b67b8ad
Binary files /dev/null and b/pages/instances/reference-content/assets/nextcloud.webp differ
diff --git a/pages/instances/reference-content/assets/openvpn.webp b/pages/instances/reference-content/assets/openvpn.webp
new file mode 100644
index 0000000000..01c815b8f0
Binary files /dev/null and b/pages/instances/reference-content/assets/openvpn.webp differ
diff --git a/pages/instances/reference-content/assets/rockylinux.webp b/pages/instances/reference-content/assets/rockylinux.webp
new file mode 100644
index 0000000000..d01e47e148
Binary files /dev/null and b/pages/instances/reference-content/assets/rockylinux.webp differ
diff --git a/pages/instances/reference-content/assets/scaleway-current-consumption.webp b/pages/instances/reference-content/assets/scaleway-current-consumption.webp
new file mode 100644
index 0000000000..3fa4fd71d5
Binary files /dev/null and b/pages/instances/reference-content/assets/scaleway-current-consumption.webp differ
diff --git a/pages/instances/reference-content/assets/scw-estimated-cost.webp b/pages/instances/reference-content/assets/scw-estimated-cost.webp
new file mode 100644
index 0000000000..b37516f801
Binary files /dev/null and b/pages/instances/reference-content/assets/scw-estimated-cost.webp differ
diff --git a/pages/instances/reference-content/assets/ubuntu.webp b/pages/instances/reference-content/assets/ubuntu.webp
new file mode 100644
index 0000000000..7a852f647b
Binary files /dev/null and b/pages/instances/reference-content/assets/ubuntu.webp differ
diff --git a/pages/instances/reference-content/assets/wordpress.webp b/pages/instances/reference-content/assets/wordpress.webp
new file mode 100644
index 0000000000..9bb9fc58a9
Binary files /dev/null and b/pages/instances/reference-content/assets/wordpress.webp differ
diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx
new file mode 100644
index 0000000000..ecfaed8d8b
--- /dev/null
+++ b/pages/instances/reference-content/choosing-instance-type.mdx
@@ -0,0 +1,76 @@
+---
+meta:
+ title: Choosing the best Scaleway Instance type for your workload
+ description: Find out how to select the ideal Scaleway Instance type for your specific needs, whether it is for learning, testing, production, or workload optimization.
+content:
+ h1: Choosing the best Scaleway Instance type for your workload
+ paragraph: Find out how to select the ideal Scaleway Instance type for your specific needs, whether it is for learning, testing, production, or workload optimization.
+categories:
+ - compute
+dates:
+ validation: 2024-08-12
+tags: instance, type, stardust, range, vcpu, hyperthread, core, ram, bandwidth, dedicated, shared, memory, hypervisor, vm, storage, dev1, play2, gp1, pro2, ent1, gpu, arm, learning, development, production, production-optimized, cost-optimized, memory-optimized, storage-optimized
+---
+
+Scaleway Instances are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs.
+
+## Different Instances for different use cases
+
+Different Instance types have different prices and are designed for different use cases. They offer different levels of power and performance, based on their **vCPU** (cores), **memory**, **storage**, and **bandwidth**.
+
+You may not need a super powerful Instance if you just want to play around and do some experiments for personal projects, so a **Learning** Instance could be perfect for you in this case. But if you want to use your Instance to host a business-critical application in production, you need the power and reliability of a **Production-Optimized** Instance, precisely designed to reliably handle this type of demanding workload.
+
+## Instance technical specifications
+
+Instances are virtual machines: multiple Instances can run on one "real" physical host machine in a data center. The physical host has a **hypervisor**, which **virtualizes** the real physical resources of the host (CPU, memory, storage, etc.) and ensures that each Instance receives its share of those resources. The different types of resources that go into specifying an Instance type are:
+
+* **vCPU**: A **v**irtual **C**entralized **P**rocessing **U**nit represents a part of the underlying physical CPU that is assigned to a particular Instance.
+
+ vCPU may be **shared** or **dedicated**.
+ - **Shared**: A [context-switching mechanism](https://en.wikipedia.org/wiki/Context_switch) allows a physical core to be shared between multiple vCPUs for multitasking. Instances with shared vCPU can be more cost-effective for running small, non-resource-intensive applications than dedicated vCPU Instances. Our different types of shared vCPU Instances offer a variety of options to balance price and performance depending on your use case.
+ - **Dedicated**: Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
+
+
+ Scaleway provides Instances equipped with either x86 or ARM CPUs. ARM Instances generally offer higher energy and cost efficiency, while x86 cloud instances provide wider software compatibility and stronger single-thread performance. [Learn more about the differences between ARM and x86-based Instances](/instances/reference-content/understanding-differences-x86-arm/).
+
+
+* **Core**: A core is a physical unit of vCPU. More cores give an Instance more computing power. A description of an Instance's cores may look something like `4 x86 64bit`, where **4** refers to the number of cores, **x86** refers to the microprocessor family, and **64bit** refers to the chunk size used by the microprocessor for processing data.
+
+* **Memory** (aka **R**andom **A**ccess **M**emory): RAM is like an Instance's short-term memory. Data that is currently being used by the vPCU is stored in RAM. More RAM enables faster computing.
+
+* **Bandwidth**: Bandwidth refers to the volume of data that can be sent to/from an Instance in a given amount of time (usually **p**er **s**econd).
+
+* **Storage**: Different Instance types may support **Local** and/or **Block** Storage:
+ - **Local** storage is an all-SSD-based storage solution, hosted on the local hypervisor.
+ - **Block** storage is more flexible, network-attached storage that can be plugged in and out of Instances like virtual hard drives. Some Instances only support Block Storage, and boot themselves from their Block Storage.
+
+ Depending on the Instance type, you can attach additional storage volumes and increase their size according to your needs.
+
+## Instance ranges
+
+The table below shows the different ranges of Instances at Scaleway and their specifications. Within each range, there are different types of Instances.
+
+Use this table to help identify the right Instance range for your use case and computing needs.
+
+| **Instance range** | [Learning](/instances/reference-content/learning/) | [Cost-Optimized](/instances/reference-content/cost-optimized/) | [Production-Optimized](/instances/reference-content/production-optimized/) | [Workload-Optimized](/instances/reference-content/workload-optimized/) |
+|-----------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Use cases** | Discovering the Scaleway ecosystem
Hosting personal projects | Scaling your development and testing environment
Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications
Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases
Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD |
+| **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage or Local Storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage |
+| **vCPU** | 1 core | From 1 to 32 cores | From 2 to 96 cores | From 2 to 64 cores |
+| **Shared/Dedicated** | Shared vCPU | Shared vCPU | Dedicated vCPU | Dedicated vCPU |
+| **RAM** | 1 GiB | From 2 GiB to 128 GiB | From 8 GiB to 384 GiB | From 4 GiB to 512 GiB |
+| **Maximum Bandwidth** | 100 Mbit/s | From 100 Mbps to 6 Gbps | From 400 Mbps to 20 Gbps | From 400 Mbps to 12.8 Gbps |
+
+For more information about each range, refer to our dedicated documentation pages:
+- [Learning](/instances/reference-content/learning/)
+- [Cost-Optimized](/instances/reference-content/cost-optimized/)
+- [Production-Optimized](/instances/reference-content/production-optimized/)
+- [Workload-Optimized](/instances/reference-content/workload-optimized/)
+
+## Instance types
+
+Check out the [Instances page](https://www.scaleway.com/en/virtual-instances/) of our website for full details on each Instance type. Alternatively, head over to the [Instances datasheet](/instances/reference-content/instances-datasheet/) to see all our available Instance types within each range.
+
+## Instance pricing
+
+Instances are priced by the hour, with different Instance types having different hourly pricing. You can check out the current prices for Instances either on the [Instance creation page of the Scaleway console](https://console.scaleway.com/instance/servers/create) or on the [dedicated pricing page of our website](https://www.scaleway.com/en/pricing/?tags=available).
\ No newline at end of file
diff --git a/pages/instances/reference-content/comaptibility-scw-os-images-flexible-ip.mdx b/pages/instances/reference-content/comaptibility-scw-os-images-flexible-ip.mdx
new file mode 100644
index 0000000000..3da50913e8
--- /dev/null
+++ b/pages/instances/reference-content/comaptibility-scw-os-images-flexible-ip.mdx
@@ -0,0 +1,56 @@
+---
+meta:
+ title: Compatibility between OS Images and different Flexible IP type combinations
+ description: This page shows the currently known state of compatibility between Scaleway Instance OS Images and the different combinations of Flexible IPs types.
+content:
+ h1: Compatibility between OS Images and different Flexible IP type combinations
+ paragraph: This page shows the currently known state of compatibility between Scaleway Instance OS Images and the different combinations of Flexible IPs types.
+tags: instances flexible ip compatibility routed-ip network configuration
+dates:
+ validation: 2024-09-09
+ posted: 2024-09-09
+categories:
+ - compute
+---
+
+This page presents the currently known state of compatibility between Scaleway Instance OS Images and the different combinations of Flexible IPs types.
+
+## Configuration
+
+| ✅ | **routed_ipv4** | **routed_ipv6** |
+| ------------- | ------------- | ------------- |
+| **1v4-0v6** | 1 | 0 |
+| **Nv4-0v6** | 2+ | 0 |
+| **0v4-1v6** | 0 | 1 |
+| **0v4-Nv6** | 0 | 2+ |
+| **1v4-1v6** | 1 | 1 |
+| **Nv4-Nv6** | 2+ | 2+ |
+
+
+## Matrix
+
+| Image label1 | **build_date2** | **build_tag3** | **1v4-0v6** | **Nv4-0v6** | **0v4-1v6** | **0v4-Nv6** | **1v4-1v6** | **Nv4-Nv6** |
+| ----------------------- | ------------------------ | ----------------------- | ------------- | ------------- | ------------- | ------------- | ------------- | ------------- |
+| **almalinux_8** | `202407031540` | `90041a7b` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅ | ✅ |
+| **almalinux_9** | `202407041520` | `a0e9a547` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅ | ✅ |
+| **centos_stream_9** | `202407090704` | `9d844f31` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅ | ✅ |
+| **rockylinux_8** | `202407031543` | `e583b9f3` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅ | ✅ |
+| **rockylinux_9** | `202407031500` | `8e17111b` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅ 6 | ✅6 |
+| **fedora_39** | `202408261203` | `db379337` | ✅ | ✅ | ⚠️4 | ⚠️4 | ❌7 | ❌7 |
+| **fedora_40** | `202408231529` | `2e2324a6` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅6 | ✅6 |
+| **fedora_41** | `202410311306` | `67e3f2fd` | ✅ | ✅ | ⚠️4 | ⚠️4 | ✅6 | ✅6 |
+| **debian_bullseye** | `202408231510` | `20ada37d` | ✅ | ✅ | ⚠️4 | ⚠️5 | ✅ | ✅ |
+| **debian_bookworm** | `202408231520` | `ff285693` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **ubuntu_focal** | `202409021112` | `b2eb59c9` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **ubuntu_jammy** | `202407031538` | `1afe725f` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+| **ubuntu_noble** | `202407031541` | `a6b4f635` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
+
+## Callouts
+
+- **1** - Image label as presented be the Marketplace API
+- **2** - The value of the `build_date` field in the `/etc/cloud/scw-build.info` file
+- **3** - The value of the `build_tag` field in the `/etc/cloud/scw-build.info` file
+- **4** - Instance is reachable but the DNS resolution is not working
+- **5** - Same as 4 + only the first IPv6 gets configured automatically
+- **6** - The Flexible IP attachment order matters: this only works if at least one routed_ipv6 is attached to the Instance after at least one `routed_ipv4` has been attached
+- **7** - The version of cloud-init is too old to support such a configuration
\ No newline at end of file
diff --git a/pages/instances/reference-content/cost-optimized.mdx b/pages/instances/reference-content/cost-optimized.mdx
new file mode 100644
index 0000000000..3bdde00911
--- /dev/null
+++ b/pages/instances/reference-content/cost-optimized.mdx
@@ -0,0 +1,89 @@
+---
+meta:
+ title: The right Instance for development purposes
+ description: Find out more about Instances from Scaleway's Cost-Optimized range, such as Development and General Purpose Instances.
+content:
+ h1: The right Instance for development purposes
+ paragraph: Find out more about Instances from Scaleway's Cost-Optimized range, such as Development and General Purpose Instances.
+dates:
+ validation: 2024-09-10
+ posted: 2023-02-22
+categories:
+ - compute
+tags: instance type development DEV range cost-optimized general-purpose general purpose GP PLAY2 PRO2 play pro
+---
+
+An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/instances/concepts/#instantapp).
+
+## Development Instances and General Purpose Instances
+
+Scaleway's **Cost-Optimized** range includes Development Instances and General Purpose Instances. These Instances provide a balance of compute, memory, and networking resources, and can be used for a wide range of workloads. For example, they are ideally suited for scaling a development and testing environment, but also Content Management Systems (CMS) or microservices. They are also a good default choice if you are not sure which Instance type is best for your application.
+
+See below the technical specifications of Development Instances or General Purposes Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | DEV1
GP1 |
+| Availability Zone | PAR1, PAR2, PAR3 (excl. DEV1), AMS1, AMS2, WAW1, WAW2 |
+| Storage | Local or Block |
+| Max. Bandwidth | From 200 to 500 Mbps |
+| CPU Type | DEV1: AMD EPYC 7281 (2,1 GHz) or equivalent
GP1: AMD EPYC 7410P (2 GHz) or equivalent|
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 4 vCPUs
From 2 to 12 GiB RAM |
+| vCPU:RAM ratio | Various
(1:1, 1:2, 1:3) |
+
+## PLAY2 Instances and PRO2 Instances
+
+In the same **Cost-Optimized** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of Development and General Purpose Instances. They present the best price-performance ratio with the most flexible vCPU to RAM ratio, and provide features that target most standard and cloud-native workloads. In other words, these Instances keep costs down while still supporting a wide variety of cloud applications, such as medium-to-high-traffic web servers, medium-sized databases and e-commerce websites.
+
+See below the technical specifications of PLAY2 and PRO2 Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | PLAY2
PRO2 |
+| Availability Zone | PAR1, PAR2, PAR3 (excl PLAY2), AMS1, AMS2, AMS3, WAW1, WAW2, WAW3 |
+| Storage | Block |
+| Max. Bandwidth | From 100 Mbps to 6 Gbps |
+| CPU Type | AMD EPYC 7543 (2,8 GHz) |
+| Resources | Shared vCPUs |
+| Sizing | From 1 to 32 vCPUs
From 2 to 128 GiB RAM |
+| vCPU:RAM ratio | Various
(1:2, 1:4) |
+
+## COP-ARM Instances
+
+An innovative option in the **Cost-Optimized** range are COP-ARM Instances, which are powered by ARM CPUs. These Instances mark a significant step in the world of development and general purpose computing. Their ARM architecture is a key feature, offering an excellent price-performance ratio while maintaining various vCPU to RAM configurations. This ARM CPU design is especially efficient for various standard and cloud-native workloads, ensuring cost-effective operations. Ideal for a wide range of cloud applications, COP-ARM Instances are well-suited for managing medium-to-high-traffic web servers, medium-sized databases, and e-commerce platforms, all the while leveraging the unique advantages of the ARM architecture.
+
+The table below displays the technical specifications of COP-ARM Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | COPARM1 |
+| Availability Zone | PAR2 |
+| Storage | Block |
+| Max. Bandwidth | From 200 Mbps to 3.2 Gbps |
+| CPU Type | ARM (Ampere Altra Max M128-30) |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 128 vCPUs
From 8 to 128 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+## Complementary services
+
+To help build and manage your applications, consider complementing your Instance with the following compatible services:
+- [Learn how to back up your Instance](/instances/how-to/create-a-backup/)
+- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/)
+- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/)
+
+## Matching use cases
+
+Try Scaleway Development Instances or General Purpose Instances with the following tutorials:
+
+- [Hosting your own GitHub runner on an Instance](/tutorials/host-github-runner/)
+- [Deploying WordPress with LEMP on Ubuntu Jammy Jellyfish (22.04 LTS)](/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/)
+- [Creating your own Minecraft server](/tutorials/setup-minecraft/)
+
+Try Scaleway PLAY2 Instances or PRO2 Instances with the following tutorials:
+
+- [Configuring a Prometheus monitoring server with a Grafana dashboard](/tutorials/prometheus-monitoring-grafana-dashboard/)
+- [Setting up GitLab with a Managed Database for PostgreSQL](/tutorials/configuring-gitlab-scaleway-elements-database/)
+- [Deploying AWStats](/tutorials/deploy-awstats/)
+- [Running web analytics with Plausible on Ubuntu Linux](/tutorials/plausible-analytics-ubuntu/)
diff --git a/pages/instances/reference-content/identify-devices.mdx b/pages/instances/reference-content/identify-devices.mdx
new file mode 100644
index 0000000000..57c589ba7d
--- /dev/null
+++ b/pages/instances/reference-content/identify-devices.mdx
@@ -0,0 +1,213 @@
+---
+meta:
+ title: Identifiying devices of a Scaleway Instance
+ description: This page explains how to identify devices on a Scaleway Instance
+content:
+ h1: Identifying devices of a Scaleway Instance
+ paragraph: This page explains how to identify devices on a Scaleway Instance
+tags: instance
+dates:
+ validation: 2024-09-16
+ posted: 2024-03-15
+categories:
+ - compute
+---
+
+An Instance is composed of a multitude of devices. Some of them can be configured, such as network interfaces and block devices, for example by attaching an SBS volume to the Instance or attaching the Instance to a Private Network.
+
+On a Linux host, devices are named by the kernel in the order they are discovered. The order in which devices are discovered is dependent on things such as the topology of the PCI hierarchy which are *not* guaranteed to be stable across power off/power on/reboot actions.
+
+This guide aims to provide tips to help you stably identify devices on a Linux host.
+
+## Identifying Instance Block Storage volumes (b_ssd)
+
+Instance Block Storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, i.e. as `/dev/sd{a,b,c...}` devices.
+
+SCSI disks have multiple attributes, such as vendor and product/model. They also have a serial. Instance Block Storage (`b_ssd`) volumes have the vendor name `SCW`, the model/product name `b_ssd`, and a serial set to `volume-` where `` is the ID of the volume.
+
+The `lsblk` can be used to list SCSI devices and will show these attributes:
+
+```sh
+root@test-instance:~# lsblk --scsi
+NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN
+sda 2:0:0:0 disk SCW b_ssd v42 volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478
+```
+
+Through `udev` and the sets of configured `udev` rules, these attributes will be retrieved and symlinks will be automatically created for the `/dev/sdX` devices. As the attributes are stable, these symlinks provide a stable path to the devices, as long as the udev rule does not change.
+
+For example, at the time of writing, the `60-persistent-storage.rules` ruleset shipped with systemd on most distributions contains rules which will create symlinks under `/dev/disk/by-id/`. Specifically of interest are the following rules:
+
+```
+# SCSI devices
+KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="scsi"
+KERNEL=="cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="cciss"
+KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
+KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n"
+```
+
+In the first rule, the `sdX` kernel name is matched, and the `scsi_id` command is executed. Its output will be imported into the `udev` environment for the following rules. Let's see what the command outputs:
+
+```sh
+root@test-instance:~# /lib/udev/scsi_id --export --whitelisted -d /dev/sda
+ID_SCSI=1
+ID_VENDOR=SCW
+ID_VENDOR_ENC=SCW\x20\x20\x20\x20\x20
+ID_MODEL=b_ssd
+ID_MODEL_ENC=b_ssd\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
+ID_REVISION=v42
+ID_TYPE=disk
+ID_SERIAL=0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478
+ID_SERIAL_SHORT=volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478
+```
+
+The third and fourth rules create the symlinks properly, using these attributes. This will result in the following symlinks being created:
+
+```sh
+root@test-instance:~# ls -l /dev/disk/by-id/
+total 0
+lrwxrwxrwx 1 root root 9 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 -> ../../sda
+lrwxrwxrwx 1 root root 10 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part1 -> ../../sda1
+lrwxrwxrwx 1 root root 11 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part14 -> ../../sda14
+lrwxrwxrwx 1 root root 11 Mar 7 16:13 scsi-0SCW_b_ssd_volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478-part15 -> ../../sda15
+```
+
+In this setup, we can see an entry named after the `f7a6f113-aaf6-4540-ac5a-9e18d7f61478` volume, pointing to the `/dev/sda` device node, along with three entries also created automatically which point to the individual partitions on the volume.
+
+Note that these rulesets are shipped by the distributions and are out of the control of Scaleway. Their stability is not guaranteed.
+
+Though symlinks are created based on rules which are packaged by distributions, it is also possible to create your own rules to fit your preferred naming. For example, if we create a rule such as:
+
+```
+/etc/udev/rules.d/99-scw-volumes.rules
+
+# Create custom symlink for Scaleway volumes
+KERNEL=="sd*", ENV{ID_VENDOR}=="SCW", SYMLINK+="disk/scw/$env{ID_SERIAL_SHORT}"
+```
+
+This rule will create a symlink `/dev/disk/scw/volume-` (where `uuid` is the ID of the volume) for each volume:
+
+```sh
+root@test-instance:~# ls -l /dev/disk/scw/
+total 0
+lrwxrwxrwx 1 root root 9 Mar 7 16:18 volume-f7a6f113-aaf6-4540-ac5a-9e18d7f61478 -> ../../sda
+```
+
+Note that this rule relies on `ID_VENDOR` and `ID_SERIAL_SHORT` being in the environment, and thus relies on the execution of `scsi_id` and the importing of its output.
+
+For more details on writing `udev` rules, please see `man 7 udev`.
+
+## Identifying Block Storage volumes (SBS)
+
+Block Storage devices are similar to Instance Block Storage devices. They are also connected to the Instance as SCSI devices and thus all explanations from the above section are also valid.
+
+The only difference is the SCSI model attribute. Instead of being fixed to the value `b_ssd`, its value depends on the class of the Block Storage volume.
+
+Two Block Storage volume classes currently exist: `bssd`, and `sbs`. Block Storage volumes migrated from Instance Block Storage (`b_ssd`) volumes have class `bssd`.
+
+Block Storage volumes with class `bssd` have a SCSI model of `b_ssd`, so migrated volumes won't change characteristics. Otherwise, Block Storage volumes have a SCSI model equal to the volume's class.
+
+For example:
+
+```sh
+root@test-instance:~# lsblk --scsi
+NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN
+sda 0:0:0:0 disk SCW sbs v42 volume-7831d52c-758f-4a94-a074-39bfa14b66d8
+sdb 0:0:1:0 disk SCW b_ssd v42 volume-03e206f6-2a3b-4223-bb56-3d7f1495903f
+```
+
+Here, the first volume has been created through the Block Storage API with class `sbs`. The second volume is an Instance Block Storage (`b_ssd`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`.
+
+## Identifying VPC Private Network interfaces
+
+VPC Private Networks to which the Instance is connected will appear as virtio PCI network devices, handled by the `virtio-net` driver.
+
+As all PCI devices, they can be listed with the `lspci` command:
+
+```sh
+
+root@test-instance:~# lspci -d '::0200'
+00:02.0 Ethernet controller: Red Hat, Inc. Virtio network device
+00:05.0 Ethernet controller: Red Hat, Inc. Virtio network device
+00:06.0 Ethernet controller: Red Hat, Inc. Virtio network device
+```
+
+The filter selects the Network controller device class/Ethernet controller device subclass. Three PCI devices are visible, which correspond to the public network device, and two VPC Private Network devices.
+By itself, the output of this command is not enough to distinguish between public and private networks, and can not distinguish between multiple private networks either: this simply confirms their existence in the PCI hierarchy of the Instance.
+
+More interestingly, network interfaces can be listed generically using the `ip link show` command:
+
+```sh
+root@test-instance:~# ip link show
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: ens2: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+ link/ether de:00:00:e1:7e:f2 brd ff:ff:ff:ff:ff:ff
+ altname enp0s2
+3: ens5: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+ link/ether 02:00:00:b7:c8:a5 brd ff:ff:ff:ff:ff:ff
+ altname enp0s5
+4: ens6: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+ link/ether 02:00:00:c1:72:51 brd ff:ff:ff:ff:ff:ff
+ altname enp0s6
+```
+
+Here, four interfaces are listed, one of which (`lo`) is the virtual loopback interface and can be disregarded. The three others correspond to the aforementioned public network interface and VPC Private Network interfaces.
+
+A simple and effective way to distinguish the public network interface from the VPC Private Network interfaces is the MAC address prefix. VPC Private Network interfaces always have a MAC address starting with `02:00:00`.
+
+Using the JSON output mode of the `ip` command and filtering with the `jq` JSON parser, we can thus list VPC Private Network interfaces:
+
+```sh
+root@test-instance:~# ip -j link | jq -r '.[] | select(.address | test("02:00:00:.*")) | .ifname'
+ens5
+ens6
+```
+
+Using the MAC address of the interfaces, it is also possible to distinguish between the different VPC Private Network interfaces. The MAC address of each interface is available through the API.
+For example, querying `/instances/v1//servers//private_nics`, where `` is the zone of the server and `` is the ID of the Instance gives:
+
+```sh
+{
+ "private_nics": [
+ {
+ "id": "d950f973-8b36-4e96-8b86-d8130f9bab36",
+ "private_network_id": "b3ae4ae0-dbbc-45cc-be9d-f2d37afbf8a2",
+ "server_id": "02f28852-b7b3-4cfc-9682-c7d14a044f29",
+ "mac_address": "02:00:00:b7:c8:a5",
+ "state": "available",
+ "creation_date": "2024-03-13T14:42:55.822512+00:00",
+ "modification_date": "2024-03-13T14:42:57.401901+00:00",
+ "zone": "fr-par-1",
+ "tags": []
+ },
+ {
+ "id": "733af716-75bc-4da6-9097-d75a5973f569",
+ "private_network_id": "4fa5577d-ef7a-4235-b642-c5f8cfaa8aba",
+ "server_id": "02f28852-b7b3-4cfc-9682-c7d14a044f29",
+ "mac_address": "02:00:00:c1:72:51",
+ "state": "available",
+ "creation_date": "2024-03-13T15:24:07.686223+00:00",
+ "modification_date": "2024-03-13T15:24:08.647484+00:00",
+ "zone": "fr-par-1",
+ "tags": []
+ }
+ ]
+}
+```
+
+Two entries are listed, which correspond to the interfaces given by the output of `ip link show` above. The output contains the ID of the VPC Private Network, which helps distinguish between the two.
+
+Through the use of `udev` rules, it is possible to rename the interfaces if desired. For example, the following rule would assign the static name `priv0` to the interface with MAC address `02:00:00:b7:c8:a5`:
+
+```
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:00:00:b7:c8:a5", NAME="priv0"
+```
+
+If a more complex scheme is desired, such as including part of the name of the corresponding VPC Private Network, the rule could instead be:
+
+```
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:00:00:*", ENV{SYSTEMD_WANTS}="my-vpc-script@$env{ID_NET_NAME}.service"
+```
+
+This rule would start the systemd service `my-vpc-service@` when a new interface with the name `` is added and has a MAC address matching the VPC Private Network prefix.
+The systemd service can then execute complex operations (retrieving the server's `private_nics` information, the VPC Private Network information through the VPC API, applying custom logic, etc.).
\ No newline at end of file
diff --git a/pages/instances/reference-content/images-and-instantapps.mdx b/pages/instances/reference-content/images-and-instantapps.mdx
new file mode 100644
index 0000000000..97c1e05eeb
--- /dev/null
+++ b/pages/instances/reference-content/images-and-instantapps.mdx
@@ -0,0 +1,42 @@
+---
+meta:
+ title: Scaleway Instance OS images and InstantApps
+ description: Discover a complete list of OS images and InstantApps available for Scaleway Instances. Choose the perfect setup for your needs and optimize your virtual environment.
+content:
+ h1: Scaleway Instance OS images and InstantApps
+ paragraph: Discover a complete list of OS images and InstantApps available for Scaleway Instances. Choose the perfect setup for your needs and optimize your virtual environment.
+tags: instance
+dates:
+ validation: 2024-12-23
+ posted: 2024-06-17
+categories:
+ - compute
+---
+
+## OS images
+
+An OS image for Instances refers to a pre-configured operating system installation that you can select when creating an Instance on the Scaleway cloud platform. We offer a variety of OS images that cater to different needs and preferences.
+Scaleway manages the deployment and maintenance of these OS images, ensuring they are up-to-date and secure.
+
+| Distribution | Description |
+|---|---|
+| | **Ubuntu 24.04** the latest long-term support (LTS) version of the world's most popular Linux operating system, offers reliability and stability with five years of guaranteed free updates.
[Deploy Ubuntu](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=607b12c2-685d-45f7-905f-57bc23863834&offerName=PRO2-S&zone=fr-par-1) |
+| | **Ubuntu ML**, Scaleway’s [optimized version](/gpu/reference-content/docker-images/) of Ubuntu is tailored for machine learning, featuring essential frameworks, tools, and packages. This includes the NVIDIA Container Toolkit (Docker), PyTorch, TensorFlow 2, NVIDIA RAPIDS, and JAX, ensuring a comprehensive and efficient ML environment.
[Deploy Ubuntu ML](https://console.scaleway.com/instance/servers/create/?area=fr-par-2&imageKey=a6c68db3-5613-4b08-acaa-2c92d8baf26c&offerName=L40S-1-48G&zone=fr-par-2) |
+| | **Debian**, the world-renowned free open-source operating system, featuring over 59,000 packages. Celebrated for its reliability, it is available in its stable branch, Debian 12 (Bookworm).
[Deploy Debian](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=fd6931c1-5326-4f8d-8fdf-57867b2830e3&offerName=PRO2-S&zone=fr-par-1) |
+| | **CentOS**, developed using Red Hat® Enterprise Linux®, is characterized by increased stability. It works on computers with both 64-bit and 32-bit architectures and is available as a free distribution. You can choose the version you need directly from the console.
[Deploy CentOS](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=cfb3fa01-6406-4be8-9e9d-29daee2582fa&offerName=PRO2-S) |
+| | **Fedora** is a modern Linux distribution with a focus on free software. It features a constantly evolving system supported by a large community and adheres to a regular release schedule. You can select the version you need directly from the console.
[Deploy Fedora](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=186859f6-0152-45dd-9eb8-21fc5e8d774e&offerName=PRO2-S) |
+| | **Rocky Linux** is an open-source enterprise operating system designed to be 100% compatible with Red Hat Enterprise Linux®. It is intensively developed and maintained by a dedicated community.
[Deploy Rocky Linux](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=1576bf6b-f640-47f2-9117-968419d0546e&offerName=PRO2-S) |
+| | **Alma Linux** is fully binary compatible with Red Hat Enterprise Linux® (RHEL), making it a seamless replacement for CentOS 8.
[Deploy Alma Linux](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=0d3a22da-c634-45d6-a7dd-aff402f88b0c&offerName=PRO2-S) |
+
+## InstantApps
+
+An InstantApp allows you to deploy pre-configured applications quickly.
+InstantApps simplify the process of deploying and managing applications in the cloud, making it accessible even for users without extensive infrastructure management experience.
+
+| InstantApp | Description |
+|---|---|
+| | **Nextcloud** is the self-hosted productivity platform that keeps you in control. It allows you to store your files, folders, contacts, photo galleries, calendars, and more, and access them from your mobile device, desktop, or web browser.
[Learn more](/tutorials/nextcloud-instantapp/) - [Deploy Nextcloud](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=7d4a7cb1-1fd5-4a64-920b-c79f47367254&offerName=PRO2-S&zone=fr-par-1) |
+| | **GitLab** is the most complete DevOps platform, offering a comprehensive CI/CD toolchain within a single application. It serves as a Git repository manager with integrated wiki, issue-tracking, and continuous integration/deployment pipeline features.
[Learn more](/tutorials/gitlab-instant-app/) - [Deploy GitLab](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=233074b9-e2ba-4e78-818e-dd4930ce6bee&offerName=PRO2-S) |
+| | **OpenVPN** is the fastest and simplest way to protect your online privacy and surf anonymously. It is easy to deploy and ready to use after your first SSH connection, ensuring quick setup for enhanced security.
[Learn more](/tutorials/openvpn-instant-app/) - [Deploy OpenVPN](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=b6f4edc8-21e6-4aa2-8f52-1030cf6d4dd8&offerName=PRO2-S) |
+| | **WordPress**, the most famous blog tool, publishing platform, and content management system (CMS), is an open-source software that enables you to create stunning websites, blogs, or applications effortlessly.
[Learn more](/tutorials/wordpress-instantapp/) - [Deploy WordPress](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=215a50f9-0ba8-4e9c-a4e7-10caf50e3586&offerName=PRO2-S) |
+| | **Docker**, the famous container manager encapsulated in a Scaleway image, allows you to deploy your applications within seconds, eliminating concerns about compatibility and dependencies.
[Learn more](/tutorials/docker-instantapp/) - [Deploy Docker](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=c1b530d8-0ca0-45c4-80db-ba06608287b2&offerName=PRO2-S) |
diff --git a/pages/instances/reference-content/index.mdx b/pages/instances/reference-content/index.mdx
new file mode 100644
index 0000000000..bcc3a68100
--- /dev/null
+++ b/pages/instances/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Instances - Additional content
+ description: Instances additional content
+content:
+ h1: Instances - Additional content
+ paragraph: Instances additional content
+---
diff --git a/pages/instances/reference-content/instances-bandwidth-overview.mdx b/pages/instances/reference-content/instances-bandwidth-overview.mdx
new file mode 100644
index 0000000000..5daf58fde3
--- /dev/null
+++ b/pages/instances/reference-content/instances-bandwidth-overview.mdx
@@ -0,0 +1,130 @@
+---
+meta:
+ title: Scaleway Instances internet and Block Storage bandwidth overview
+ description: Find detailed information about the internet and Block Storage bandwidth for each Instance type at Scaleway.
+content:
+ h1: Scaleway Instances internet and Block Storage bandwidth overview
+ paragraph: Find detailed information about the internet and Block Storage bandwidth for each Instance type at Scaleway.
+tags: instance
+dates:
+ validation: 2025-01-07
+ posted: 2024-11-19
+categories:
+ - compute
+---
+
+This guide provides a complete overview of internet and Block Storage bandwidth for Scaleway Instances.
+Understanding these specifications is crucial for optimizing your infrastructure for performance and compatibility.
+
+### Why bandwidth matters
+
+Bandwidth impacts how your applications perform and interact with other systems.
+- **Internet bandwidth**: Affects how fast your Instance can send or receive data over the internet.
+- **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics.
+
+
+ Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications.
+
+
+
+ To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth.
+
+
+## COPARM Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| COPARM1-2C-8G | 200 Mbit/s | 80 MiB/s |
+| COPARM1-4C-16G | 400 Mbit/s | 160 MiB/s |
+| COPARM1-8C-32G | 800 Mbit/s | 320 MiB/s |
+| COPARM1-16C-64G | 1.6 Gbit/s | 640 MiB/s |
+| COPARM1-32C-128G | 3.2 Gbit/s | 1.25 MiB/s |
+
+## DEV Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| DEV1-S | 200 Mbit/s | 100 MiB/s |
+| DEV1-M | 300 Mbit/s | 150 MiB/s |
+| DEV1-L | 400 Mbit/s | 200 MiB/s |
+| DEV1-XL | 500 Mbit/s | 250 MiB/s |
+
+## ENT Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| ENT1-XXS | 400 Mbit/s | 400 MiB/s |
+| ENT1-XS | 800 Mbit/s | 800 MiB/s |
+| ENT1-S | 1.6 Gbit/s | 1.56 GiB/s |
+| ENT1-M | 3.2 Gbit/s | 3.12 GiB/s |
+| ENT1-L | 6.4 Gbit/s | 6.25 GiB/s |
+| ENT1-XL | 12.8 Gbit/s | 12.5 GiB/s |
+
+## GP Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| GP1-XS | 500 Mbit/s | 300 MiB/s |
+| GP1-S | 800 Mbit/s | 500 MiB/s |
+| GP1-M | 1.5 Gbit/s | 800 MiB/s |
+| GP1-L | 5 Gbit/s | 1 GiB/s |
+| GP1-XL | 10 Gbit/s | 2 GiB/s |
+
+## PLAY Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| PLAY2-PICO | 100 Mbit/s | 40 MiB/s |
+| PLAY2-NANO | 200 Mbit/s | 80 MiB/s |
+| PLAY2-MICRO | 400 Mbit/s | 160 MiB/s |
+
+## PRO2 Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| PRO2-XXS | 350 Mbit/s | 125 MiB/s |
+| PRO2-XS | 700 Mbit/s | 250 MiB/s |
+| PRO2-S | 1.5 Gbit/s | 500 MiB/s |
+| PRO2-M | 3 Gbit/s | 1 GiB/s |
+| PRO2-L | 6 Gbit/s | 2 GiB/s |
+
+## POP Range
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| POP2-2C-8G | 400 Mbit/s | 400 MiB/s |
+| POP2-4C-16G | 800 Mbit/s | 800 MiB/s |
+| POP2-8C-32G | 1.6 Gbit/s | 1.56 GiB/s |
+| POP2-16C-64G | 3.2 Gbit/s | 3.12 GiB/s |
+| POP2-32C-128G | 6.4 Gbit/s | 6.25 GiB/s |
+| POP2-64C-256G | 12.8 Gbit/s | 12.5 GiB/s |
+
+## POP-HC Range (High Compute)
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| POP2-HC-2C-4G | 400 Mbit/s | 400 MiB/s |
+| POP2-HC-4C-8G | 800 Mbit/s | 800 MiB/s |
+| POP2-HC-8C-16G | 1.6 Gbit/s | 1.56 GiB/s |
+| POP2-HC-16C-32G | 3.2 Gbit/s | 3.12 GiB/s |
+| POP2-HC-32C-64G | 6.4 Gbit/s | 6.25 GiB/s |
+| POP2-HC-64C-128G | 12.8 Gbit/s | 12.5 GiB/s |
+
+## POP-HM Range (High Memory)
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| POP2-HM-2C-16G | 400 Mbit/s | 400 MiB/s |
+| POP2-HM-4C-32G | 800 Mbit/s | 800 MiB/s |
+| POP2-HM-8C-64G | 1.6 Gbit/s | 1.56 GiB/s |
+| POP2-HM-16C-128G | 3.2 Gbit/s | 3.12 GiB/s |
+| POP2-HM-32C-256G | 6.4 Gbit/s | 6.25 GiB/s |
+| POP2-HM-64C-512G | 12.8 Gbit/s | 12.5 GiB/s |
+
+## POP-HN Range (High Network)
+
+| Instance Type | Internet Bandwidth | Block Bandwidth |
+|-----------------------|-------------------------|---------------------|
+| POP2-HN-3 | 3 Gbit/s | 400 MiB/s |
+| POP2-HN-5 | 5 Gbit/s | 800 MiB/s |
+| POP2-HN-10 | 10 Gbit/s | 800 MiB/s |
diff --git a/pages/instances/reference-content/instances-datasheet.mdx b/pages/instances/reference-content/instances-datasheet.mdx
new file mode 100644
index 0000000000..36e4357a8f
--- /dev/null
+++ b/pages/instances/reference-content/instances-datasheet.mdx
@@ -0,0 +1,144 @@
+---
+meta:
+ title: Scaleway Instances datasheet
+ description: This page shows the technical characteristics of the different Scaleway Instance offers.
+content:
+ h1: Scaleway Instances datasheet
+ paragraph: This page shows the technical characteristics of the different Scaleway Instance offers.
+tags: dedibox server
+dates:
+ validation: 2024-08-26
+ posted: 2023-12-18
+categories:
+ - compute
+---
+
+This datasheet provides a concise overview of the performance, technical features, components, materials, and associated documentation for different Instance offers.
+
+
+ Note that the **Max. NIC bandwidth** specifies the maximum available bandwidth for this Instance type. Bandwidth is shared between public internet and Private Network traffic.
+
+
+## STARDUST1 Instances
+
+ See below the technical specifications of Stardust Instances:
+
+| Range | Learning |
+|:--------------------|:---------------------------------------------|
+| Instance type | STARDUST1-S |
+| Availability Zone | PAR1, AMS1 and WAW2 |
+| Storage | Local (10 GB) or Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | 100 Mbit/s |
+| CPU type | AMD EPYC 7282 (2,8 GHz) or 7281 (2,1 GHz) |
+| CPU architecture | `amd64` |
+| Resources | Shared vCPUs |
+| Sizing | 1 vCPU, 1 GiB RAM |
+| vCPU:RAM ratio | 1:1 |
+| SLA | None |
+
+## Development and General Purpose Instances
+
+See below the technical specifications of Development and General Purpose Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:-------------------------------------------------------------------------------------------|
+| Instance type | DEV1
GP1 |
+| Availability Zone | PAR1, PAR2, PAR3 (excl. DEV1), AMS1, AMS2, WAW1, WAW2 |
+| Storage | Local (up to 150 GB) or Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 200 to 500 Mbps |
+| CPU type | DEV1: AMD EPYC 7281 (2,1 GHz) or equivalent
GP1: AMD EPYC 7410P (2 GHz) or equivalent |
+| CPU architecture | `amd64` |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 4 vCPUs
From 2 to 12 GiB RAM |
+| vCPU:RAM ratio | Various
(1:1, 1:2, 1:3) |
+
+## PLAY2 and PRO2 Instances
+
+See below the technical specifications of PLAY2 and PRO2 Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | PLAY2
PRO2 |
+| Availability Zone | PAR1, PAR2, PAR3 (excl PLAY2), AMS1, AMS2, AMS3, WAW1, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 100 Mbps to 6 Gbps |
+| CPU type | AMD EPYC 7543 (2,8 GHz) |
+| CPU architecture | `amd64` |
+| Resources | Shared vCPUs |
+| Sizing | From 1 to 32 vCPUs
From 2 to 128 GiB RAM |
+| vCPU:RAM ratio | Various
(1:2, 1:4) |
+
+## COP-ARM Instances
+
+The table below displays the technical specifications of COP-ARM Instances:
+
+| Range | Cost-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | COPARM1 |
+| Availability Zone | PAR2 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 200 Mbps to 3.2 Gbps |
+| CPU type | ARM (Ampere Altra Max M128-30) |
+| CPU architecture | `arm64` |
+| Resources | Shared vCPUs |
+| Sizing | From 2 to 128 vCPUs
From 8 to 128 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+## Enterprise Instances
+
+See below the technical specifications of Enterprise Instances:
+
+| Range | Production-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | ENT1 |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, AMS3, WAW1, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 400 Mbps to 20 Gbps |
+| CPU type | AMD EPYC 7543 (2,8 GHz) |
+| CPU architecture | `amd64` |
+| Resources | Dedicated vCPUs* |
+| Security feature | Secure Encrypted Virtualization |
+| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
+
+## Production-Optimized Instances
+
+See below the technical specifications of Production-Optimized Instances:
+
+| Range | Production-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | POP2 |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, AMS3, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 400 Mbps to 20 Gbps |
+| CPU type | AMD EPYC 7543 (2,8 GHz) |
+| CPU architecture | `amd64` |
+| Resources | Dedicated vCPUs* |
+| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
+
+## Workload-Optimized Instances
+
+See below the technical specifications of Workload-Optimized Instances:
+
+* High-Memory: Designed for RAM-intensive usages, and high memory production applications, these machines provide more RAM than vCPU.
+* High-CPU: Made for high computing workloads and compute-bound applications, this machine provides more vCPU than RAM.
+
+| Range | Workload-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance type | POP2-HM, POP2-HC, POP2-HN |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW2, WAW3 |
+| Storage | Block (from 10 GB to 10 TB) |
+| Max. NIC bandwidth | From 400 Mbps to 12.8 Gbps |
+| CPU type | AMD EPYC 7543 (2,8 GHz) |
+| CPU architecture | `amd64` |
+| Resources | Dedicated vCPUs* |
+| Security feature | Secure Encrypted Virtualization |
+| Sizing | From 2 to 64 dedicated vCPUs
From 4 GiB to 512 GiB RAM |
+| vCPU:RAM ratio | 1:8 (POP2-HM), 1:2 (POP2-HC and POP2-HN) |
+
+\* Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications.
\ No newline at end of file
diff --git a/pages/instances/reference-content/learning.mdx b/pages/instances/reference-content/learning.mdx
new file mode 100644
index 0000000000..d63ce85a32
--- /dev/null
+++ b/pages/instances/reference-content/learning.mdx
@@ -0,0 +1,52 @@
+---
+meta:
+ title: The right Instance for learning purposes
+ description: Discover Scaleway's learning range of Instances, including options like the Stardust Instance, ideal for educational purposes.
+content:
+ h1: The right Instance for learning purposes
+ paragraph: Discover Scaleway's learning range of Instances, including options like the Stardust Instance, ideal for educational purposes.
+dates:
+ validation: 2025-01-06
+ posted: 2023-02-22
+categories:
+ - compute
+tags: instance type stardust range learning use-case
+---
+
+An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Learning Instance supports the essential operating systems and distributions.
+
+## Learning range: Stardust Instances
+
+Scaleway's **Learning** range includes our Stardust Instances. Stardust Instances are the perfect Instances for small workloads and simple applications. They are built to host small internal applications, staging environments or low-traffic web servers.
+
+ See below the technical specifications of Stardust Instances:
+
+| **Range** | Learning |
+|:------------------------|:------------------------------------------|
+| **Instance Type** | STARDUST1-S |
+| **Availability Zone** | PAR1, AMS1 and WAW2 |
+| **Storage** | Local or Block |
+| **Max. Bandwidth** | 100 Mbit/s |
+| **CPU Type** | AMD EPYC 7282 (2,8 GHz) or 7281 (2,1 GHz) |
+| **Resources** | Shared vCPUs |
+| **Sizing** | 1 vCPU, 1 GiB RAM |
+| **vCPU:RAM ratio** | 1:1 |
+| **SLA** | None |
+
+
+## Complementary services
+
+To help build and manage your applications, consider complementing your Stardust Instance with the following compatible services:
+
+- [Learn how to back up your Instance](/instances/how-to/create-a-backup/)
+- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/)
+- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/)
+
+## Matching use cases
+
+Try Scaleway Stardust Instances with the following tutorials:
+
+- [Deploying Strapi with a click on Stardust](/tutorials/strapi/)
+- [Using Bash to display a Christmas tree](/tutorials/bash-christmas-tree/)
+- [Setting a Private mesh VPN with WireGuard](/tutorials/wireguard-mesh-vpn/)
+- [First steps with the Linux command line](/tutorials/first-steps-linux-command-line/)
\ No newline at end of file
diff --git a/pages/instances/reference-content/manual-configuration-private-ips.mdx b/pages/instances/reference-content/manual-configuration-private-ips.mdx
new file mode 100644
index 0000000000..45c1e1043b
--- /dev/null
+++ b/pages/instances/reference-content/manual-configuration-private-ips.mdx
@@ -0,0 +1,239 @@
+---
+meta:
+ title: Configuring Instances manually on a Private Network
+ description: Learn how to manually configure Scaleway Instances on a Private Network.
+content:
+ h1: Configuring Instances manually on a Private Network
+ paragraph: Learn how to manually configure Scaleway Instances on a Private Network.
+tags: instance private-ip-address ip address private dhcp
+categories:
+ - compute
+dates:
+ validation: 2024-08-12
+---
+
+
+ - DHCP is activated by default on all newly-created Private Networks, and cannot be deactivated.
+ - If you have a Private Network created before July 12 2023, [check our migration documentation](/vpc/reference-content/vpc-migration/) to find out if DHCP has been automatically activated on your network.
+ - We recommend activating DHCP and letting us take care of the automatic IP address management of all resources on your Private Networks, including Instances, to ensure they are fully compatible with managed products and integrated with our [internal IPAM](/vpc/concepts/#ipam).
+
+ The steps outlined in this document are intended for advanced users only and are not supported by Scaleway.
+
+
+## How to configure the Private Network interface on your Instances
+
+Once you have [added your Instances to a Private Network](/instances/how-to/use-private-networks/), you can manually configure the virtual network interface on each one. You will also need to turn off the automatic DHCP scripts found on the Instance for Private Network, so that they do not conflict with the manual configuration you are creating. These steps are explained below.
+
+
+ - We recommend not using publicly routed IP subnets within your Private Network.
+ While the configuration may work for your Instances to communicate with each other, it could lead to connectivity issues to machines on the public internet within these ranges.
+
+ - We advise you to configure your Private Network using IPs from the following private IP ranges:
+ * `192.168.0.0` - `192.168.255.255` (65,536 IP addresses) and
+ * `172.16.0.0` - `172.31.255.255` (1,048,576 IP addresses).
+
+ - You can use any [subnet mask](https://en.wikipedia.org/wiki/Subnetwork) allowed by these ranges. The only constraint is that all interfaces in the same Private Network must be configured with the same subnet mask. If you are not sure, use `/24` for your Private Network.
+
+ - Using the `10.0.0.0/8` private IP range is **not recommended**, as this block is used for the Instances' own private IPs and infrastructure services.
+
+ - This is only recommended for expert users.
+
+
+1. Connect to the Instance using [SSH](/instances/how-to/connect-to-instance/).
+2. Delete the file `/lib/udev/rules.d/72-scw-vpc-iface.rules` to disable the automatic DHCP scripts:
+ ```bash
+ rm /lib/udev/rules.d/72-scw-vpc-iface.rules
+ ```
+
+
+ If a Private Network was previously plugged into this Instance, you also need to delete the following files, according to your distribution:
+
+
+
+ `/etc/netplan/60-*-vpc.yaml`
+
+
+
+
+ `/etc/network/interfaces.d/60-*-vpc`
+
+
+
+
+ `/etc/sysconfig/network-scripts/ifcfg-*` (excluding any for `ens2` or `eth0`)
+
+
+
+
+3. Find the virtual interface corresponding to the Private Network using the `ip link show` command:
+ ```sh
+ root@virtual-instance:~# ip link show
+ 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 2: ens2: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+ link/ether de:1c:94:64:20:44 brd ff:ff:ff:ff:ff:ff
+ 3: ens5: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
+ link/ether 02:00:00:00:1a:ae brd ff:ff:ff:ff:ff:ff
+ ```
+ The Private Network interface can be identified by its associated MAC address, which always begins with `02:00:00:xx:yy:zz`.
+
+
+ The network interface names may be different, depending on the operating system and the release you use.
+
+
+
+ The network interface name is not guaranteed to be stable and may change across reboot or poweroff and poweron actions, similarily to the rest of the PCI hierarchy.
+
+4. For convenience, you can give a more significant name (e.g. `priv0`) to the Private Network interface. Configure the new interface name as follows:
+ ```sh
+ root@virtual-instance:~# ip link set down dev ens5
+ root@virtual-instance:~# ip link set name priv0 dev ens5
+ root@virtual-instance:~# ip link set up dev priv0
+ ```
+
+
+ This renaming action will not persist across reboots. See below for a solution.
+
+5. Make these changes persistent at reboot to ensure the Private Networks interface always gets the same name based on its MAC address. This is done by adding the following rule to the `/etc/udev/rules.d/75-persistent-net-generator.rules` file. Make sure that you replace the address with the correct MAC address for your case:
+ ```sh
+ SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:00:00:00:1a:ae", NAME="priv0"
+ ```
+
+ If you want to attach a server to multiple Private Networks, create a rule for each network by replacing the MAC address and the interface name `priv0` by `priv1`, `priv2` and so on.
+
+
+## How to configure the Private Network's IP address
+
+Once you have brought up the Private Network via the previous steps, you can configure its IP address. The steps required to configure the IP address change depending on your Linux distribution:
+
+
+
+
+ 1. To configure a static IP address on the Private Network interface (previously named `priv0`), open the Netplan configuration file and configure the interface as follows:
+
+ The location of the Netplan configuration file varies depending on the Ubuntu release:
+ - Ubuntu 20.04: `/etc/netplan/00-installer-config.yaml`
+ - Ubuntu 18.04: `/etc/netplan/01-netcfg.yaml`
+
+
+
+ ```
+ network:
+ version: 2
+ renderer: networkd
+ ethernets:
+ priv0:
+ addresses: [192.168.42.2/24]
+ ```
+
+ In this example, the IP subnet `192.168.42.0/24` is being used.
+
+ Once the interface is configured, save the file and exit the editor.
+ 2. Bring the interface up using the command `netplan apply`.
+ 3. Repeat these steps on the other Instances that will communicate within the Private Network.
+
+
+
+ 1. Open the file `/etc/sysconfig/network-scripts/ifcfg-priv0` (replace `priv0` with the name of the private interface) and configure the virtual network interface as follows:
+ ```
+ DEVICE=priv0
+ BOOTPROTO=none
+ ONBOOT=yes
+ USERCTL=no
+ IPV6INIT=no
+ TYPE=Ethernet
+ # configure the IPADDR and NETMASK towards the parameters of your Private Network
+ NETMASK=255.255.255.0
+ IPADDR=192.168.43.4
+ ARP=yes
+ # replace HWADDR with the MAC address assoicated to the interface
+ HWADDR=02:00:00:00:1a:ae
+ ```
+
+ In this example the IP subnet `192.168.42.0/24` is being used. The interface uses the MAC address (`02:00:00:00:1a:b0`) assigned to the Instance as it was attached to the Private Network.
+
+ Once the interface is configured, save the file and exit the text editor.
+ 2. Restart the network service to bring the configured interface up:
+ - On **CentOS 7** use the following command:
+
+ ```sh
+ root@virtual-instance:~# systemctl restart network.service
+ ```
+
+ - On **CentOS 8** use the following command:
+
+ ```sh
+ root@virtual-instance:~# systemctl restart NetworkManager.service
+ ```
+ 3. Repeat these steps on the other Instances that will communicate within the Private Network.
+
+
+
+## How to test your Private Network configuration
+
+After you followed the steps above, you can test the connection between the Instances.
+
+Enter the `ping` command, pinging the relevant IP address for your Instances/Private Network.
+
+```sh
+root@virtual-instance:~# ping 192.168.42.3
+PING 192.168.42.3 (192.168.42.3): 56 data bytes
+64 bytes from 192.168.42.3: icmp_seq=0 ttl=64 time=0.824 ms
+64 bytes from 192.168.42.3: icmp_seq=1 ttl=64 time=1.180 ms
+64 bytes from 192.168.42.3: icmp_seq=2 ttl=64 time=0.852 ms
+64 bytes from 192.168.42.3: icmp_seq=3 ttl=64 time=0.871 ms
+--- 192.168.42.3 ping statistics ---
+4 packets transmitted, 4 packets received, 0% packet loss
+round-trip min/avg/max/stddev = 0.824/0.932/1.180/0.144 ms
+```
+
+When configured properly, the Instance should reply to the `ping` command. The Private Network is working and you can start to configure your services.
+
+## How to carry out manual configuration of the default route (if Private Network is attached to a Public Gateway)
+
+By default, Instances are configured with a default route on their public interface that allows them to reach the Scaleway Metadata API. When an Instance is on a Private Network attached to a Public Gateway, it ends up with two default routes: one towards the gateway on the Private Network and the other towards the Scaleway Metadata API on the public interface. It is necessary to adjust the metric of the default route through the gateway to make it the preferred one, and to configure the route to the Scaleway Metadata API manually.
+
+
+ If your Instance supports autoconfiguration, and you want to configure manually, make sure that you disable autoconfiguration as follows:
+ ```
+ # mv /lib/udev/rules.d/72-scw-vpc-iface.rules /lib/udev/rules.d/.72-scw-vpc-iface.rules
+ # reboot
+ ```
+
+
+1. Update the route to the Scaleway Metadata API.
+
+ The endpoint for the Scaleway Metadata API is `169.254.42.42/32`, and the gateway depends on your Instance. You can retrieve it with the following command:
+
+ ```
+ # ip route show
+ default via 10.68.2.114 dev eth0 proto dhcp metric 100
+ 10.68.2.114/31 dev eth0 proto kernel scope link src 10.68.2.115 metric 100
+ ```
+
+ The address of the gateway to the Scaleway Metadata API is `10.68.2.114`. Now, add a specific route to the API as follows:
+
+ ```
+ # ip route add 169.254.42.42/32 via 10.68.2.114
+ ```
+2. Configure DHCP on the Instance, adjusting the metric of the default route.
+
+ Example using netplan:
+
+ ```
+ network:
+ version: 2
+ ethernets:
+ ens4:
+ dhcp4: true
+ dhcp4-overrides:
+ route-metric: 50
+ ```
+
+ and using ifupdown:
+
+ ```
+ auto ens4
+ iface ens4 inet dhcp
+ metric 50
+ ```
diff --git a/pages/instances/reference-content/preventing-outgoing-ddos.mdx b/pages/instances/reference-content/preventing-outgoing-ddos.mdx
new file mode 100644
index 0000000000..73965dbe54
--- /dev/null
+++ b/pages/instances/reference-content/preventing-outgoing-ddos.mdx
@@ -0,0 +1,114 @@
+---
+meta:
+ title: Preventing outgoing DDoS
+ description: Learn how to prevent outgoing DDoS from happening on your Scaleway Instance
+content:
+ h1: Preventing outgoing DDoS
+ paragraph: Learn how to prevent outgoing DDoS from happening on your Scaleway Instance
+tags: instance ddos outgoing attack prevention
+dates:
+ validation: 2024-08-12
+categories:
+ - compute
+---
+
+
+ The explanations given below are known best practices. They do not guarantee that your resources will not be locked if we detect that they are part of a DDoS attack.
+
+
+## DoS Overview
+
+A Denial of Service (DoS) attack is an attack through which a person can render a system unusable, or significantly slow it down for legitimate users, by overloading its resources.
+
+[A Distributed Denial of Service (DDoS) attack](DDoS_Quick_Guide.pdf) is a DoS attack that is performed at the same time by a multitude of compromised systems.
+
+The goal of a DoS is not to gain unauthorized access to machines or data, but to prevent legitimate users of a service from using it.
+
+You are responsible for your resources.
+If a resource you control takes part in a DDoS, you will be considered responsible for attacking the target of this DDoS.
+
+Scaleway will lock any resources (e.g. Instances, Kubernetes clusters, Elastic Metal servers) that are identified as a contributor to a DDoS.
+This lock can be done without prior notice to protect our network and the target network; this is written in our Terms and Conditions ([Scaleway](https://www.scaleway.com/en/terms/), [Scaleway Dedibox](https://www-uploads.scaleway.com/cgv_en_36883f3024.pdf)).
+
+## Preventing Memcache from being used in a DDoS attack
+
+[Memcached](https://memcached.org/) is a free & open-source, high-performance, distributed memory object caching system.
+It is used as a key-value store in memory.
+
+[Memcached can be used in DDoS](https://github.com/memcached/memcached/wiki/DDOS) because of its large amplification factor.
+
+**Recommendations**
+
+To configure securely your memcache, proceed as follows:
+
+Ensure that in your `/etc/memcached.conf` you have both settings defined:
+
+```conf
+# Disable UDP listening
+-U 0`
+
+# Listen only on localhost
+-l 127.0.0.1
+```
+
+## Preventing NTP to be used in a DDoS attack
+
+[Network time protocol](https://en.wikipedia.org/wiki/Network_Time_Protocol) (NTP) servers are regularly being used to reflect and amplify spoofed UDP packets towards the target of a DDoS attack.
+
+NTP servers where the `monlist` command can be run by any unauthorized users are particularly troublesome.
+These commands provide a huge amplification effect to the attacker.
+
+**Recommendations**
+
+To configure securely your NTP server, proceed as follows:
+
+- If you need to have an NTP server running, upgrade your NTP server as much as possible.
+- Use a [secure configuration](https://github.com/team-cymru/network-security-templates/tree/master/Secure-NTP-Templates) as much as possible
+- Avoid having an NTP server open on the internet. Try to restrict access to localhost only.
+- If you need to have an NTP server open, be sure to specify which range of IPs can access your NTP server.
+
+## Preventing DNS from being used in a DDoS attack
+
+Domain Name System (DNS) is a commonly used protocol to perform DDoS attacks because of its UDP-based protocol and lack of security features by default.
+DNS amplification attacks almost always take advantage of open resolvers.
+An open resolver is a DNS server that answers queries for a domain name without restrictions: anybody on the internet can query it and it will answer.
+This makes it particularly troublesome as a spoofed IP address that will generate a reflection attack.
+
+In addition to that, a DNS reply is usually larger than its corresponding query.
+Therefore, DNS can be used to have an amplification effect.
+
+**Recommendations**
+
+To configure securely your DNS server, proceed as follows:
+
+- Do not run an open DNS resolver on the internet. Restrict your DNS server to answer only requests coming from your IP range.
+- Do not enable recursion on your DNS server
+- If you need recursion, limit the authorized range of IPs that can perform those requests.
+ - [BIND](https://kb.isc.org/docs/aa-01316)
+ - [unbound](https://nlnetlabs.nl/documentation/unbound/unbound.conf/)
+ - If you use PowerDNS, you can also use [dnsdist](https://dnsdist.org/index.html).
+- Enable RateLimiting of queries and answers from your authoritative DNS
+ - [BIND](https://kb.isc.org/docs/aa-00994)
+ - [unbound](https://nlnetlabs.nl/documentation/unbound/unbound.conf/)
+ - If you use PowerDNS, you can also use [dnsdist](https://dnsdist.org/index.html).
+- Set ACL on your remote control if used and limit it to localhost if possible
+ - [rndc for BIND](https://mirror.apps.cam.ac.uk/pub/doc/redhat/redhat7.3/rhl-rg-en-7.3/s1-bind-rndc.html)
+ - [dnsdist for PowerDNS](https://dnsdist.org/index.html)
+ - [unbound-control for unbound](https://nlnetlabs.nl/documentation/unbound/unbound-control/)
+
+## Preventing HTTP(s) proxy from being used in a DDoS attack
+
+HTTP(s) proxies are software that will perform an HTTP(s) request in place of a client and forward the response to the client.
+This can be used in the case of a DDoS attack to perform amplification (a small request can generate a large answer) and reflection (IP address can be spoofed).
+
+**Recommendations**
+
+To configure securely your HTTP proxy, proceed as follows:
+
+- Do not run HTTP proxies that are open on the internet.
+- Limit as much as possible the range of IPs of machines that can connect to your HTTP(s) proxy.
+
+## External References
+
+- (In English) [Denial of Service (DoS) guidance](https://www.ncsc.gov.uk/collection/denial-service-dos-guidance-collection)
+- (In French) [Comprendre et anticiper les attaques DDoS](NP_Guide_DDoS.pdf)
\ No newline at end of file
diff --git a/pages/instances/reference-content/production-optimized.mdx b/pages/instances/reference-content/production-optimized.mdx
new file mode 100644
index 0000000000..c8c1570778
--- /dev/null
+++ b/pages/instances/reference-content/production-optimized.mdx
@@ -0,0 +1,75 @@
+---
+meta:
+ title: The right Instance for production purposes
+ description: Find out more about Instances from Scaleway's Production-Optimized range, such as ENT1 and POP2 Instances.
+content:
+ h1: The right Instance for production purposes
+ paragraph: Find out more about Instances from Scaleway's Production-Optimized range, such as ENT1 and POP2 Instances.
+dates:
+ validation: 2024-08-26
+ posted: 2023-02-22
+categories:
+ - compute
+tags: instance type production production-optimized range POP2 ENT1
+---
+
+An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/instances/concepts/#instantapp).
+
+
+ Both ENT1 and POP2 Instance types have identical hardware specifications, dedicated vCPU allocation, the same pricing structure, and an accelerated booting process.
+ However, POP2 Instances offer CPU- and memory-optimized variants for better workload customization. The main difference is that AMD Secure Encrypted Virtualization (SEV) is disabled for POP2 Instances.
+ Opting for **POP2 gives access to the latest features** like potential future live migration of instances, keeping your infrastructure updated with evolving demands and technology.
+ POP2 Instances are recommended for general workloads, unless your workload specifically needs features unique to ENT1 Instances.
+
+
+## Production-Optimized range: ENT1 Instances
+
+Scaleway's **Production-Optimized** range includes Enterprise Instances (ENT1). ENT1 Instances are high-end, dedicated cloud Instances for demanding workloads. They offer the highest consistent performance per core to support real-time applications. In addition, their computing power makes them generally more robust for compute-intensive workloads.
+
+They are best suited for production websites, enterprise applications, high-traffic databases, and any application that requires 100% sustained CPU usage such as monitoring and analytics software. This includes Prometheus and Grafana, gaming sessions, and ad serving.
+
+See below the technical specifications of Enterprise Instances:
+
+| Range | Production-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | ENT1 |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, AMS3, WAW1, WAW2, WAW3 |
+| Storage | Block |
+| Max. Bandwidth | From 400 Mbps to 20 Gbps |
+| CPU Type | AMD EPYC 7543 (2,8 GHz) |
+| Resources | Dedicated vCPUs |
+| Security feature | Secure Encrypted Virtualization |
+| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+## Production-Optimized range: POP2 Instances
+
+Scaleway's **Production-Optimized** range includes POP2 Instances. POP2 Instances are high-end, dedicated cloud Instances for demanding workloads. They offer the highest consistent performance per core to support real-time applications. In addition, their computing power makes them generally more robust for compute-intensive workloads.
+
+They are best suited for production websites, demanding applications, high-traffic databases, and any application that requires 100% sustained CPU usage such as monitoring and analytics software. This includes Prometheus and Grafana, gaming sessions, and ad serving.
+
+See below the technical specifications of Production-Optimized Instances:
+
+| Range | Production-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | POP2 |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, AMS3, WAW2, WAW3 |
+| Storage | Block |
+| Max. Bandwidth | From 400 Mbps to 20 Gbps |
+| CPU Type | AMD EPYC 7543 (2,8 GHz) |
+| Resources | Dedicated vCPUs |
+| Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM |
+| vCPU:RAM ratio | 1:4 |
+
+## Complementary services
+To help build and manage your applications, consider complementing your Production-Optimized Instances with the following compatible services:
+- [Learn how to back up your Instance](/instances/how-to/create-a-backup/)
+- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/)
+- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/)
+
+## Matching use cases
+Try Scaleway Production-Optimized Instances with the following tutorials:
+- [Setting up a Kubernetes cluster using Rancher on Ubuntu Bionic Beaver](/tutorials/setup-k8s-cluster-rancher/)
+- [Deploying a RTMP Streaming Server](/tutorials/rtmp-self-hosted-streaming/)
+- [Configuring a Nagios Monitoring System](/tutorials/configure-nagios-monitoring/)
+- [Configuring Sentry error tracking](/tutorials/sentry-error-tracking/)
\ No newline at end of file
diff --git a/pages/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx b/pages/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx
new file mode 100644
index 0000000000..2a22622c68
--- /dev/null
+++ b/pages/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx
@@ -0,0 +1,82 @@
+---
+meta:
+ title: Understanding automatic network hot-reconfiguration for Scaleway Instances
+ description: Find out how to configure automatic network hot-reconfiguration for Scaleway Instances.
+content:
+ h1: Understanding automatic network hot-reconfiguration for Scaleway Instances
+ paragraph: Find out how to configure automatic network hot-reconfiguration for Scaleway Instances.
+categories:
+ - compute
+dates:
+ validation: 2024-10-29
+ posted: 2024-10-29
+tags: instance network hot-reconfiguration
+---
+
+The Scaleway Instances product includes a feature called **automatic network hot-reconfiguration**.
+
+This mechanism automatically configures or deconfigures a [flexible IP address](/instances/concepts/#flexible-ip) in the guest operating system when it is attached to or detached from an Instance.
+
+This guide explains how to enable or disable the automatic network hot-reconfiguration mechanism on your Instance.
+
+
+ This documentation page does not apply to Instances running the Microsoft Windows operating system.
+
+
+## Supported configurations
+
+Before proceeding, ensure that your operating system supports the target network configuration: refer to Scaleway’s compatibility guidelines on [OS images and flexible IP type combinations](/instances/reference-content/comaptibility-scw-os-images-flexible-ip/).
+
+Starting from **October 10th, 2024**, all GNU/Linux-based operating systems and InstantApp images for Scaleway Instances have automatic network hot-reconfiguration enabled by default.
+
+To verify that the feature is active on your Instance, use the following command:
+
+```bash
+# systemctl is-active scw-net-reconfig.path
+```
+
+If the output is `active`, the feature is enabled and ready to use. If the output is `inactive`, you have to enable it first.
+
+
+### Enabling network hot-reconfiguration
+
+Follow these steps to enable automatic network hot-reconfiguration on a Scaleway Instance where the feature is currently inactive.
+
+1. Enable the QEMU Guest Agent. Refer to Scaleway’s documentation on [enabling the QEMU Guest Agent (GQA)](/instances/reference-content/understanding-qemu-guest-agent/#opting-in) for further details.
+
+2. Install the latest Scaleway ecosystem package.
+
+ - **Fedora / AlmaLinux / RockyLinux / CentOS**
+ ```bash
+ # yum -y --best install scaleway-ecosystem
+ ```
+
+ - **Debian / Ubuntu**
+ ```bash
+ # apt-get update
+ # apt-get -y install scaleway-ecosystem
+ ```
+
+
+ Ensure you install version `0.0.7-1` or higher of the `scaleway-ecosystem` package.
+
+
+3. Enable the automatic network reconfiguration mechanism.
+
+ On Debian and Ubuntu systems, the mechanism typically activates automatically after installing or upgrading the `scaleway-ecosystem` package. However, RedHat-based distributions may require a manual start:
+
+ ```bash
+ # systemctl enable --now scw-net-reconfig.path
+ ```
+
+
+ Rebooting your Instance will also activate network hot-reconfiguration.
+
+
+### Disabling network hot-reconfiguration
+
+If you prefer to prevent automatic network reconfiguration when a flexible IP is attached or detached, run the following command:
+
+ ```bash
+ # systemctl disable --now scw-net-reconfig.path
+ ```
\ No newline at end of file
diff --git a/pages/instances/reference-content/understanding-differences-x86-arm.mdx b/pages/instances/reference-content/understanding-differences-x86-arm.mdx
new file mode 100644
index 0000000000..ca3a6afbe3
--- /dev/null
+++ b/pages/instances/reference-content/understanding-differences-x86-arm.mdx
@@ -0,0 +1,81 @@
+---
+meta:
+ title: Understanding the differences between ARM and x86 Instances
+ description: Discover the differences between ARM and x86 architectures in cloud computing, and learn which is best suited for your needs.
+content:
+ h1: Understanding the differences between ARM and x86 Instances
+ paragraph: Discover the differences between ARM and x86 architectures in cloud computing, and learn which is best suited for your needs.
+tags: instance x86 arm
+dates:
+ validation: 2024-08-12
+categories:
+ - compute
+---
+
+In cloud computing and data centers, the dominance of x86 architecture has been unchallenged for decades.
+However, with the rise of ARM processors, a new type of Instance is emerging, promising efficiency and performance.
+This page helps you understand the technical differences between Scaleway's ARM and x86 Instances, highlighting their advantages and disadvantages.
+
+## Understanding the architectural differences between x86 and ARM
+
+## x86 Instances
+
+x86 Instances are provided with processors from Intel Xeon or AMD EPYC families being common choices.
+
+**x86 Architecture:**
+- Developed by Intel, x86 architecture is a family of instruction set architectures (ISAs) for computer processors.
+- It is a complex instruction set computing (CISC) architecture, which means it has a rich set of instructions, some of which execute complex tasks.
+- x86 processors are known for their high performance and are widely used in desktops, laptops, and servers.
+
+
+
+
+ - **Raw Performance:** x86 CPUs generally provide superior single-threaded performance, necessary for legacy applications and specific high-performance computing tasks.
+ - **Software Ecosystem:** The x86 architecture has a vast software ecosystem, including operating systems, development tools, and enterprise applications.
+ - **Virtualization:** x86 processors have advanced virtualization features essential for efficient cloud operations and running multiple containers in a VM.
+
+
+ - **Power Consumption:** x86 processors typically consume more power than ARM processors, leading to a larger ecological footprint.
+ - **Heat Output:** Higher power consumption results in more heat, which can increase the complexity of cooling solutions.
+ - **Cost:** x86 processors are often more expensive, especially when power and cooling are factored in - which may result in higher Instance costs.
+
+
+
+
+## ARM Instances
+
+ARM Instances in the cloud are typically powered by for-purpose designed processors such as the Ampere Altra, designed for high efficiency and lower power consumption.
+
+**ARM Architecture:**
+- ARM architecture, initially developed by ARM Holdings, stands for Advanced RISC Machine.
+- It is a reduced instruction set computing (RISC) architecture, which simplifies the processor design and focuses on efficiency.
+- ARM processors are prevalent in mobile devices, embedded systems, and, increasingly, in servers and cloud infrastructure.
+
+
+
+ - **Energy efficiency:** ARM's chip design allows for more efficient processing per watt, leading to significant energy savings, especially at scale.
+ - **Scalability:** ARM's simplicity allows for highly scalable designs suitable for environments with a high density of cores.
+ - **Customization:** ARM licenses its architecture to various manufacturers, enabling customization for specific use cases or optimization for certain workloads.
+
+
+ - **Software Compatibility:** The ARM ecosystem is still catching up with x86 in terms of the breadth of software compatibility, particularly for specialized enterprise applications.
+ - **Performance:** While single-thread performance has improved, ARM may lag behind x86 in specific compute-intensive tasks that benefit from the CISC design.
+ - **Ecosystem maturity:** The x86 ecosystem is more mature, with a vast range of supporting tools and experienced developers, which ARM is still developing.
+
+
+
+## Choosing between ARM and x86 Instances
+
+The decision between ARM and x86 Instances is often not straightforward and depends on various factors, including the specific application workload, energy efficiency objectives, and software ecosystem prerequisites.
+
+- **Workload compatibility:** If your applications are compiled for ARM and can leverage its efficiency, ARM Instances may be the right choice. However, if you rely on legacy software or specific x86 features, x86 Instances might be unavoidable.
+- **Performance needs:** When it comes to raw computational power, particularly in single-threaded applications, x86 Instances frequently surpass their ARM counterparts. However, in scenarios with workloads that can be parallelized, ARM's multi-core efficiency may offer advantages.
+- **Energy efficiency:** Organizations with a strong emphasis on sustainability may lean towards ARM due to its power efficiency.
+
+## Conclusion
+
+The rise of ARM in the cloud computing market is pushing the industry towards more energy-efficient and sustainable solutions, providing a competitive alternative to traditional x86 offerings. ARM Instances are known for their energy efficiency and reduced environmental impact, making them attractive to organizations prioritizing environmental responsibility.
+
+While x86 Instances continue to dominate in terms of raw power and software ecosystem, ARM is carving out a niche in sustainable cloud and server solutions. This shift is influenced by the increasing awareness of ecological considerations in technology choices.
+
+As technology advances, the choice between ARM and x86 may be driven not only by technical specifications but also by their ecological impact. ARM's alignment with green computing principles positions it as a key player in the transition to a more sustainable digital infrastructure.
\ No newline at end of file
diff --git a/pages/instances/reference-content/understanding-instance-pricing.mdx b/pages/instances/reference-content/understanding-instance-pricing.mdx
new file mode 100644
index 0000000000..13e81d160c
--- /dev/null
+++ b/pages/instances/reference-content/understanding-instance-pricing.mdx
@@ -0,0 +1,101 @@
+---
+meta:
+ title: Understanding Scaleway Instance pricing
+ description: Discover how Scaleway Instance pricing works, including hourly rates, billing, and tips to manage costs effectively.
+content:
+ h1: Understanding Scaleway Instance pricing
+ paragraph: Discover how Scaleway Instance pricing works, including hourly rates, billing, and tips to manage costs effectively.
+tags: instance pricing prices billing invoice bill how-much cost charge
+dates:
+ validation: 2024-08-19
+categories:
+ - compute
+---
+
+Scaleway Instances are virtual machines hosted in the cloud. You can create an Instance, pay for it by the hour, and then delete it and stop paying when you no longer need it.
+
+This page gives more information about Instances pricing and helps you understand how you will be billed when using Instances.
+
+## Overview
+
+As a public cloud provider, Scaleway operates on a "pay as you go" model: you only pay for what you use. The flexibility to provision resources when you need them and delete them when you do not is a fundamental tenet of cloud computing and the backbone of our billing model.
+
+Our [console](https://console.scaleway.com/) tries to make it as easy as possible for you to create and delete Instances and their associated resources based on your fluctuating needs, as well as to estimate your spending and keep track of your budget.
+
+## Hourly pricing
+
+Instances are priced by the hour, with different [Instance types](/instances/reference-content/choosing-instance-type/) having different hourly rates. You can check out the current prices for Instances in one of two ways:
+- Go to the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console. Note that you must have [an account](/account/how-to/create-an-account/) to access this page.
+- See the dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available) of our website.
+
+## Instance billing
+
+- Your hourly billing begins when you [create the Instance](/instances/how-to/create-an-instance/).
+- Billing pauses if you [power off](/instances/how-to/power-off-instance/) the Instance, and recommences when you power it back on. Any attached storage or flexible IPs are still billed while the Instance is powered off though - see full details [below](#flexible-ip-addresses-and-storage-volumes).
+- Billing ends when you [delete the Instance](/instances/how-to/create-an-instance/).
+
+You can power off your Instance or delete it at any time: no minimum commitment or notice period is required.
+
+At the end of each calendar month you will be invoiced for your hourly billed usage that month.
+
+## Flexible IP addresses and storage volumes
+
+### Flexible IP address billing
+
+When you create an Instance, by default a [flexible IP](/instances/concepts/#flexible-ip) is created for it at the same time. This gives the Instance a public IP address. A flexible IP address is billed separately to the Instance and has its own hourly rate. You can see the hourly rate for a flexible IP address on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console or on our dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available).
+
+Your hourly billing for a flexible IP address begins when you reserve the IP address (either during the creation of an Instance or by [creating a new flexible IP address)](/instances/how-to/use-flexips/#how-to-create-a-new-flexible-ip-address) and ends when you [delete the address](/instances/how-to/use-flexips/#how-to-delete-a-flexible-ip-address) from your account.
+
+
+ - You can choose to create an Instance without a flexible IP address via the **Advanced settings** option.
+ - Billing of an Instance stops when you power it off, but the Instance's flexible IP remains reserved to your account nonetheless. You will continue to be billed for the flexible IP even if your Instance is powered off, unless you delete the flexible IP.
+ - When you delete an Instance via the console, you are asked whether you want to also delete its flexible IP. If you delete it, billing for this IP will end. If you keep it in your account, billing continues.
+ - See the [Billing FAQ](/faq/billing/) for more information about the billing of [dynamic IP addresses](/instances/concepts/#dynamic-ip) as opposed to flexible IPs.
+
+
+You can detach a flexible IP address from your Instance and delete it at any time: no minimum commitment or notice period is required.
+
+At the end of each calendar month, you will be invoiced for your hourly billed flexible IP usage.
+
+### Storage volume billing
+
+When you create an Instance, you also need to create a certain amount of storage for it, in the form of [local or block volumes](/instances/concepts/#volumes). Volumes are billed separately to Instances and have their own hourly rates. You can see the hourly rate for different types of volume on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console, or on the dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available) of our website.
+
+Your hourly billing for a storage volume begins when you create the volume (either during the creation of an Instance, or by creating a [new volume](/block-storage/how-to/create-a-volume/)), and ends when you [delete](/block-storage/how-to/delete-a-volume/) the volume from your account.
+
+
+ The billing of an Instance stops when it is powered off.
+ However, any volumes attached to it are kept in your account and continue to be billed until you delete them.
+
+
+At the end of each calendar month, you will be invoiced for your hourly billed volume usage.
+
+## Estimating your monthly invoice and avoiding overspending
+
+We provide a number of tools to help you estimate your monthly invoice ahead of time, and stick to any budget you may have:
+
+### Estimated cost calculator
+
+When you [create an Instance in the Scaleway console](https://console.scaleway.com/instance/servers/create/), we provide you with an estimated cost calculator to help you visualize the potential charges for the Instance, including its storage and flexible IP, based on your projected usage in hours, days, or months. Feel free to experiment with this calculator to find your optimal configuration before finalizing your Instance creation.
+
+
+ The estimated cost calculator is simply a tool to help you predict your costs. It represents an approximate sum and you are in no way committed to spending that amount.
+
+
+
+
+### Current consumption
+
+The **Current consumption** panel on the main dashboard of your Scaleway console shows you an estimation of your charges so far for the current calendar month. It is broken down by category: Instances, flexible IPs, and storage volumes all come under the **Compute** category. This helps you keep track of how much you're spending each month.
+
+
+
+### Billing alerts
+
+The Scaleway console **Billing Alerts** feature allows you to set up alerts if your monthly consumption reaches a given budget threshold. An alert can be sent to you by SMS, email, or API webhook. Receiving alerts like this can remind you to delete your Instances or other resources to avoid going over your budget. Read our [dedicated documentation](/billing/how-to/use-billing-alerts/) on billing alerts to find out more about setting up this feature.
+
+## Paying your invoice
+
+We initiate automatic payment of your monthly invoice via the [preferred payment method](/billing/how-to/add-payment-method/) you configured.
+
+For more information about invoices and payments, check out our dedicated [Billing FAQ page](/faq/billing/).
\ No newline at end of file
diff --git a/pages/instances/reference-content/understanding-qemu-guest-agent.mdx b/pages/instances/reference-content/understanding-qemu-guest-agent.mdx
new file mode 100644
index 0000000000..ffa3fecd10
--- /dev/null
+++ b/pages/instances/reference-content/understanding-qemu-guest-agent.mdx
@@ -0,0 +1,113 @@
+---
+meta:
+ title: Understanding the QEMU Guest Agent in Scaleway Instances
+ description: Discover how the QEMU Guest Agent works with Scaleway Instances.
+content:
+ h1: Understanding the QEMU Guest Agent in Scaleway Instances
+ paragraph: Discover how the QEMU Guest Agent works with Scaleway Instances.
+tags: instance qga guemu guest agent
+dates:
+ validation: 2024-10-28
+ posted: 2024-10-28
+categories:
+ - compute
+---
+
+Some features of the Instances product require Scaleway's infrastructure to query or exchange information with your Instance. To enable this communication, a software component must run on the guest operating system: the QEMU Guest Agent (QGA).
+
+This page provides essential insights into this mechanism.
+
+
+ This documentation page does not apply to Instances running the Microsoft Windows operating system.
+
+
+## What are the features provided by QGA?
+
+Running the QEMU Guest Agent (QGA) on your Instance currently enables the following feature:
+
+- **Automatic network reconfiguration** upon flexible IP attachment or detachment [Learn how to enable/disable this feature](/instances/reference-content/understanding-automatic-network-hot-reconfiguration/).
+
+Additional features may be added in the future.
+
+## Checking QGA's status
+
+Since March 1st, 2024, all Scaleway-provided GNU/Linux and InstantApp images for Instances come with QGA pre-installed and enabled by default.
+
+To verify that QGA is running on your Instance, use the following command:
+
+```bash
+# systemctl is-active qemu-guest-agent.service
+```
+
+If the output is `active`, QGA is running, and you are ready to benefit from the associated features. If the output is `inactive`, you may need to install and/or activate QGA.
+
+## Opting in
+
+Follow these steps to enable QGA on an Instance where it is currently inactive.
+
+### Installation
+
+Instances created from images older than March 1st, 2024 may require manual installation of the `qemu-guest-agent` package:
+
+- **Fedora / AlmaLinux / RockyLinux / CentOS**
+
+ ```bash
+ # yum -y --best install qemu-guest-agent
+ ```
+
+- **Debian / Ubuntu**
+
+ ```bash
+ # apt-get update
+ # apt-get -y install qemu-guest-agent
+ ```
+
+### Activation
+
+After installing the package, start the `qemu-guest-agent.service` by either:
+
+- Rebooting your Instance, or
+- Running the following command:
+
+ ```bash
+ # systemctl start qemu-guest-agent.service
+ ```
+
+## Opting Out
+
+Follow these steps to disable QGA and the associated Scaleway features.
+
+### Deactivation
+
+
+ Disabling QGA is not recommended, as doing so also disables all the [Scaleway features](#what-are-the-features-provided-by-qga) it provides.
+
+
+To stop and disable QGA, run:
+
+```bash
+# systemctl stop qemu-guest-agent.service
+# systemctl mask qemu-guest-agent.service
+```
+
+This stops the service and prevents it from starting on subsequent reboots.
+
+### Deinstallation (Optional)
+
+
+ You do not necessarily need to deinstall QGA to opt out. [Deactivating the service](#deactivation) is sufficient.
+
+
+If you prefer to completely remove QGA, ensure the service is stopped first, then run:
+
+- **Fedora / AlmaLinux / RockyLinux / CentOS**
+
+ ```bash
+ # yum -y remove qemu-guest-agent
+ ```
+
+- **Debian / Ubuntu**
+
+ ```bash
+ # apt-get -y purge qemu-guest-agent
+ ```
\ No newline at end of file
diff --git a/pages/instances/reference-content/workload-optimized.mdx b/pages/instances/reference-content/workload-optimized.mdx
new file mode 100644
index 0000000000..1f7a22c69d
--- /dev/null
+++ b/pages/instances/reference-content/workload-optimized.mdx
@@ -0,0 +1,51 @@
+---
+meta:
+ title: The right Instance for workload purposes
+ description: Find out more about Instances from Scaleway's Workload-Optimized range, such as POP2-HC, POP2-HN, and POP2-HM.
+content:
+ h1: The right Instance for workload purposes
+ paragraph: Find out more about Instances from Scaleway's Workload-Optimized range.
+dates:
+ validation: 2024-11-18
+ posted: 2023-05-11
+categories:
+ - compute
+tags: instance type workload workload-optimized range POP2-HM POP2-HC POP2-HN
+---
+
+An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [InstantApps](/instances/concepts/#instantapp).
+
+## Workload-Optimized range: POP2-HM and POP2-HC Instances
+
+Scaleway's **Workload-Optimized** range includes POP2-HM (High Memory), POP2-HN (High Network) and POP2-HC (High CPU). Equipped with dedicated vCPUs, these Instances are optimized for workload-intensive applications.
+
+* **High-Memory**: Designed for RAM-intensive usages, and high memory production applications, these machines provide more RAM than vCPU. These Instances are designed for high-demanding analysis, in-memory calculation, big-data processing, high-performance, or cache databases.
+
+* **High-CPU**: Made for high computing workloads and compute-bound applications, this machine provides more vCPU than RAM. Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD.
+
+See below the technical specifications of Workload-Optimized Instances:
+
+| Range | Workload-Optimized |
+|:--------------------------------|:------------------------------------------------------------------------------|
+| Instance Type | POP2-HM, POP2-HC, POP2-HN |
+| Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW2, WAW3 |
+| Storage | Block |
+| Max. Bandwidth | From 400 Mbps to 12.8 Gbps |
+| CPU Type | AMD EPYC 7543 (2,8 GHz) |
+| Resources | Dedicated vCPUs |
+| Security feature | Secure Encrypted Virtualization |
+| Sizing | From 2 to 64 dedicated vCPUs
From 4 GiB to 512 GiB RAM |
+| vCPU:RAM ratio | 1:8 (POP2-HM), 1:2 (POP2-HC and POP2-HN) |
+
+## Complementary services
+To help build and manage your applications, consider complementing your Workload-Optimized Instance with the following compatible services:
+- [Learn how to back up your Instance](/instances/how-to/create-a-backup/)
+- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/)
+- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/)
+
+## Matching use cases
+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/)
+- [Visualizing time-Series data with TimescaleDB and Grafana](/tutorials/visualize-timeseries-data-timescaledb-grafana/)
+- [Installing a multi-node Cockroach database with HA Proxy](/tutorials/setup-cockroachdb-cluster/)
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/assets/scaleway-boot-modes.webp b/pages/instances/troubleshooting/assets/scaleway-boot-modes.webp
new file mode 100644
index 0000000000..a2c3358242
Binary files /dev/null and b/pages/instances/troubleshooting/assets/scaleway-boot-modes.webp differ
diff --git a/pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-credentials-nav.webp b/pages/instances/troubleshooting/assets/scaleway-credentials-nav.webp
similarity index 100%
rename from pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-credentials-nav.webp
rename to pages/instances/troubleshooting/assets/scaleway-credentials-nav.webp
diff --git a/pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-ssh-keys.webp b/pages/instances/troubleshooting/assets/scaleway-ssh-keys.webp
similarity index 100%
rename from pages/identity-and-access-management/organizations-and-projects/how-to/assets/scaleway-ssh-keys.webp
rename to pages/instances/troubleshooting/assets/scaleway-ssh-keys.webp
diff --git a/pages/instances/troubleshooting/bootscript-eol.mdx b/pages/instances/troubleshooting/bootscript-eol.mdx
new file mode 100644
index 0000000000..681177db7c
--- /dev/null
+++ b/pages/instances/troubleshooting/bootscript-eol.mdx
@@ -0,0 +1,107 @@
+---
+meta:
+ title: Dealing with the end of life of the bootscript feature
+ description: This page helps you migrating your Scaleway Instance following the EOL of the bootscript feature
+content:
+ h1: Dealing with the end of life of the bootscript feature
+ paragraph: This page helps you migrating your Scaleway Instance following the EOL of the bootscript feature
+tags: bootscript boot-script instance boot script
+dates:
+ validation: 2024-08-26
+ posted: 2023-02-20
+categories:
+ - compute
+---
+
+Some legacy Instance types (e.g. **VC1-x**, **X64-x**, **Start1-x**) supported the option to use a bootscript (a preconfigured boot configuration) to start your Instance. This boot method was also available on **DEV1-x**, **GP1-x**, and **STARDUST1** Instances. This feature is now deprecated and will no longer be supported.
+
+If you are still using one of these Instance types with a bootscript, you have to change your boot configuration in order to keep your Instance operational.
+
+You can find information about the Instances quotas allocated to your account at the following link: [Understanding Organization quotas](/organizations-and-projects/additional-content/organization-quotas/).
+
+
+
+ If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the [Scaleway CLI](/instances/api-cli/creating-managing-instances-with-cliv2/) as you normally would or through the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance), as long as you stay within your allocated quotas. [Check your Organization's quota usage in the Scaleway console](https://console.scaleway.com/organization/settings).
+
+
+
+ To ensure the continued stability of your service, it is crucial to follow the procedures outlined below, as the bootscript feature enters the decommissioning phase. Failure to do so may result in service instability for your Instances.
+
+
+
+
+- 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
+- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
+- An [Instance](/instances/how-to/create-an-instance/) using a bootscript
+
+## How do I know if I am impacted?
+
+If your Instance is using the bootscript option to boot in normal mode you are impacted. You can check which boot mode is used by your Instance directly in the Scaleway console.
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the name of the Instance you want to check. The Instance overview displays.
+3. Click the **Advanced Settings** tab.
+4. Check the **Boot Mode** of your Instance. If it uses **local boot** you are not concerned by the migration. If you are using a **bootscript** your intervention is required.
+
+## Migration options for Instances using bootscripts
+
+
+ Local volume(s) that do not support UEFI cannot be used to boot any other type of Instance. You must retrieve and migrate manually your data to an Instance that supports UEFI boot.
+ Unfortunately, Scaleway cannot access your data to identify if you are using an OS image with or without UEFI partitions.
+ To do so, [connect to your Instance](/instances/how-to/connect-to-instance/) using SSH and run the following command to list the EFI directories:
+ ```
+ ls -ld /sys/firmware/efi
+ ```
+ If you can see the following output, your Instance uses UEFI boot:
+ ```
+ root@my-virtual-instance:~# ls -ld /sys/firmware/efi
+ drwxr-xr-x 6 root root 0 Feb 20 11:16 /sys/firmware/EFI
+ ```
+ In this case, use **option 1** to migrate your Instance.
+ If you see `ls: cannot access /sys/firmware/efi: No such file or directory`, the UEFI directories are not present on your Instance. Migrate your data using options **2**, **3**, or **4**.
+
+
+
+
+
+ #### Change the boot type of the Instance to local boot
+
+
+ This option is the **recommended** procedure for most Instance types.
+
+
+ **This section applies if your Instance supports UEFI boot.** To continue using your current Instance, [change the boot type](/instances/how-to/use-boot-modes/#how-to-use-local-boot) of the Instance to **Local boot**:
+
+ 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+ 2. Click the Instance you wish to start with a local boot.
+ 3. Use the toggle icon in the top right corner of the screen to **power off** your Instance.
+ 4. Click the **Advanced settings** tab.
+ 5. In the **Boot mode** section, select **Use local boot**.
+ 6. Click **Save**.
+ 7. Use the toggle icon in the top right corner of the screen to **power on** your Instance.
+ Your Instance starts using local boot.
+ 8. Check that the Instance is booting correctly with the local boot method and that its services are behaving correctly.
+
+
+ * If changing the boot type from bootscript to local boot is not successfully achieved via option 1, you can always use option 2 or 3 to migrate your Instance data to a new one.
+ * If you are a **STARDUST1** user, we recommend that you put your VM into [standby mode](/instances/how-to/use-standby-mode/). This ensures your Instance will not lose its slot in the case of availability shortages.
+
+
+
+
+ #### Create a snapshot of the volume(s) and export it to Object Storage to retrieve the data
+
+ 1. [Create a snapshot](/instances/how-to/create-a-snapshot/) of the volume using the **l_ssd** type of snapshot.
+ 2. [Export](/instances/how-to/snapshot-import-export-feature/) the snapshot to an Object Storage bucket in the same region as the Instance.
+ 3. Retrieve your data from the Object Storage bucket and reuse it at your convenience.
+ 4. Delete the old Instance that was using a bootscript once you have recovered your data.
+
+
+
+
+ #### Create a new Instance using the local boot method and manually copy data from the old Instance to the new one.
+
+ Migrate the data of your old Instance manually. For example, you can do this by using FTP, SCP, or Rsync.
+
+
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/cant-connect-ssh.mdx b/pages/instances/troubleshooting/cant-connect-ssh.mdx
new file mode 100644
index 0000000000..c2df88545d
--- /dev/null
+++ b/pages/instances/troubleshooting/cant-connect-ssh.mdx
@@ -0,0 +1,140 @@
+---
+meta:
+ title: Troubleshooting SSH connection issues to Instances
+ description: This page helps you troubleshoot problems when you cannot connect to your Scaleway Instance via SSH
+content:
+ h1: Troubleshooting SSH connection issues to Instances
+ paragraph: This page helps you troubleshoot problems when you cannot connect to your Scaleway Instance via SSH
+tags: connection instance ssh ssh-key error publickey public-key
+dates:
+ validation: 2024-08-01
+ posted: 2021-10-19
+categories:
+ - compute
+---
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+Discover how to resolve common SSH connection problems with your Scaleway Instance. Learn to fix errors like "Permission denied (publickey)" and "Remote host identification has changed" with our step-by-step troubleshooting guides.
+
+## Permission denied (publickey)
+
+You may try to connect to your Instance and see a message like the following:
+
+```
+marie-curie:/# ssh root@51.15.40.150
+Permission denied (publickey)
+```
+
+In this case, the Instance rejected your attempt to connect. There is most probably a problem with the SSH key pair - either the public key on the Instance or the private key on your local machine, or both.
+
+### Check that the Instance has the correct public key
+
+When you create your Instance, check step 6 of the creation wizard and make sure you are uploading a public key to which you have the corresponding private key on your local machine.
+
+- You can view and manage your public SSH keys from the [credentials section of the console](https://console.scaleway.com/project/credentials).
+- Credentials are specific to each [Project](/organizations-and-projects/concepts/#project) of your Organization.
+- If you [add a new public key to your Project credentials](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) **after** creating a new Instance, it will not automatically be uploaded to the existing Instance. Scaleway only uploads the public SSH keys specified at the time of the Instance's creation. To add a new public SSH key after that point, you will need to connect to your Instance and add the additional public key yourself. Public keys are stored by default in `~/.ssh` with a filename similar to `id_rsa.pub`.
+
+### Check that you have the correct private key on your local machine
+
+To connect to your remote Instance from your local machine, your local machine must have the corresponding private key to the Instance's public key.
+
+#### On Linux / Mac
+
+By default, your SSH keys are stored on your local machine in the hidden `.ssh` folder of the home or root directory.
+
+1. Navigate to the directory on your local machine as follows:
+ ```
+ cd ~/.ssh
+ ```
+2. List all the keys in the directory as follows:
+ ```
+ ls
+ ```
+
+ You should now see a list of all your keys. Public keys should have the `.pub` suffix, private keys do not have this suffix.
+3. Use `cat ` to view the contents of a public key file. Alternatively use your favorite text editor, e.g., `nano `.
+
+ Check that you have the corresponding private key to the public key you uploaded to your Instance.
+
+#### On Windows
+
+Check that you uploaded the correct public key to PuTTY:
+
+1. Open PuTTY.
+2. Navigate to **Connection**>**SSH**>**Auth** in the side menu.
+3. Check the file and path for the **Private key file for authentication**, using **Browse** to replace it if necessary.
+
+## Warning: Remote host identification has changed
+
+You may try to connect to your Instance and see a message like the following:
+
+```
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that a host key has just been changed.
+The fingerprint for the ECDSA key sent by the remote host is
+SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
+Please contact your system administrator.
+Add correct host key in /home/marie-curie/.ssh/known_hosts to get rid of this message.
+Offending ECDSA key in /home/marie-curie/.ssh/known_hosts:24
+ remove with:
+ ssh-keygen -f "/home/marie-curie/.ssh/known_hosts" -R "51.15.40.150"
+ECDSA host key for 51.15.40.150 has changed and you have requested strict checking.
+Host key verification failed.
+```
+
+This may happen if you are connecting to a newly created Instance that has a flexible IP address you previously used to connect to a different Instance.
+
+The warning message itself tells you how to solve this problem, in the following extract:
+
+```
+Add correct host key in /home/marie-curie/.ssh/known_hosts to get rid of this message.
+Offending ECDSA key in /home/marie-curie/.ssh/known_hosts:24
+ remove with:
+ ssh-keygen -f "/home/marie-curie/.ssh/known_hosts" -R "51.15.40.150"
+```
+
+1. Execute the following command in the terminal of your local machine, replacing the path and IP address with those shown in your own error message:
+ ```
+ ssh-keygen -f "/home/marie-curie/.ssh/known_hosts" -R "51.15.40.150"
+ ```
+ This deletes the key fingerprint from your `known_hosts` file. You should see a message similar to:
+
+ ```
+ # Host 51.15.40.150 found: line 24
+ /home/marie-curie/.ssh/known_hosts updated.
+ Original contents retained as /home/marie-curie/.ssh/known_hosts.old
+ ```
+2. Try to connect to your Instance via SSH again. This time, the connection should be successful.
+
+### Check that the correct public key is installed on your Instance
+
+You must upload the content of the public part of the SSH key pair to the Scaleway console. The public key information is transferred to your Instance during the boot process. You can then connect and authenticate from your local machine (where the private key is) to the remote Instance (where the public key is).
+
+1. Log into the [Scaleway console](https://console.scaleway.com), and navigate to the [SSH keys](https://console.scaleway.com/project/ssh-keys) of your Project dashboard.
+2. Click the **Add SSH key** button.
+3. Paste the content of the public key (which you copied in the previous step) into the pop-up box, and optionally add a description. Then click **Add SSH key**.
+4. [Reboot your Instance](/instances/how-to/use-boot-modes/#how-to-use-local-boot) or run `scw-fetch-ssh-keys --upgrade` to download the new key onto the Instance. You will now be able to [connect to your Instances via SSH](/instances/how-to/connect-to-instance/)
+
+
+ Do not edit the `authorized_keys` file on your Instance manually. All content in this file is overwritten during the boot process of the Instance. If you want to add SSH keys to it, upload them to the Scaleway console.
+
+
+
+ If you have any difficulties connecting to an Instance after uploading a new public SSH key to your Project, try the following:
+ - If you cannot connect to your Instance at all via SSH, reboot your Instance from the console and try again.
+ - If you can connect to your Instance using a previously uploaded SSH key but not the new one, go ahead and connect to your Instance with the old key. Once connected, run the `scw-fetch-ssh-keys --upgrade` command, which launches a script on your Instance to update your SSH keys. You can then check that the new key has been added to the `authorized_keys` file (`~/.ssh/authorized_keys`). Note that this command works only for Instances.
+
+
+## Timeout when trying to connect
+
+You may find the SSH connection attempt times out without connecting. This may be expected behavior if the Instance is attached to a Private Network on which there is also a Public Gateway advertising the default route. See our [dedicated troubleshooting](/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/) page for more help with this issue.
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx
new file mode 100644
index 0000000000..42859c5bf0
--- /dev/null
+++ b/pages/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx
@@ -0,0 +1,25 @@
+---
+meta:
+ title: I cannot connect to my Instance using SSH after attaching it to a Private Network
+ description: This page explains how to troubleshoot connection problems after attaching a Scaleway Instance to a Private Network
+content:
+ h1: I cannot connect to my Instance using SSH after attaching it to a Private Network
+ paragraph: This page explains how to troubleshoot connection problems after attaching a Scaleway Instance to a Private Network
+tags: troubleshoot error private-network private network vpc dhcp
+dates:
+ validation: 2025-01-02
+ posted: 2021-05-26
+categories:
+ - compute
+---
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+
+The action to take depends on whether DHCP is [activated](/vpc/reference-content/vpc-migration/) on your Private Network.
+
+If it is not, disconnect the Instance from the Private Network, as there may be other factors impacting your Instance, like one of your Instances running a DHCP server.
+
+If it is, this is expected behavior as all the traffic towards your Instance now goes through the Public Gateway. To access your Instance using SSH, first create a static NAT association between a port of your Public Gateway (eg 2222) and the private IP assigned to your Instance, on the SSH port (22 by default). Then, SSH to the Public Gateway's IP on port 2222.
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/change-rescue-mode.mdx b/pages/instances/troubleshooting/change-rescue-mode.mdx
new file mode 100644
index 0000000000..cbfc4946ff
--- /dev/null
+++ b/pages/instances/troubleshooting/change-rescue-mode.mdx
@@ -0,0 +1,46 @@
+---
+meta:
+ title: Changing the rescue mode of your Instance
+ description: This page helps you switch your Scaleway Instance to the new rescue mode
+content:
+ h1: Changing the rescue mode of your Instance
+ paragraph: This page helps you switch your Scaleway Instance to the new rescue mode
+tags: rescue rescuemode bootscript boot-script instance boot script
+dates:
+ validation: 2024-08-26
+ posted: 2023-05-04
+categories:
+ - compute
+---
+
+The previous Instances rescue mode, which relied on bootscripts, was discontinued on **May 31, 2023**.
+
+
+
+- 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
+- An [Instance](/instances/how-to/create-an-instance/)
+- A valid [API key](/iam/how-to/create-api-keys/)
+
+## Updating rescue mode from the Scaleway console
+
+1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays.
+2. Click the name of the Instance that is using the previous rescue mode. The Instance overview displays.
+3. Stop the Instance if it is currently running by using the top right toggle of the Instances overview page.
+4. Click the **Advanced settings** tab.
+5. Scroll to the **Boot mode** section and change the boot mode of your Instance to **local boot**.
+6. Power the Instance on again by using the toggle.
+
+ If you want to use rescue mode again, change the boot type back to **rescue mode** to reboot the Instance using the latest rescue mode.
+
+
+## Updating rescue mode using the Scaleway API
+
+1. [List the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-list-all-instances) of your Project(s).
+2. Filter the returned Instances to keep only the ones with `boot_type: "rescue"`.
+3. [Stop the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action)
+4. [Update the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-update-an-instance) and set `boot_type: "local"`
+
+ If you still want to use rescue mode for your Instance(s), update these Instances again and switch back the `boot_type` to “rescue”. They will then use the updated rescue system.
+
+5. [Start the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action).
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx b/pages/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx
new file mode 100644
index 0000000000..92af19f825
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx
@@ -0,0 +1,62 @@
+---
+meta:
+ title: Fix broken VPN when switching OpenVPN Instance to routed IP
+ description: This page helps you recover VPN functionality when switching your OpenVPN Instance to routed IP
+content:
+ h1: Fix broken VPN when switching OpenVPN Instance to routed IP
+ paragraph: This page helps you recover VPN functionality when switching your OpenVPN Instance to routed IP
+tags: openvpn instance routed ip
+dates:
+ validation: 2024-10-11
+ posted: 2024-10-11
+categories:
+ - compute
+---
+
+When switching an Instance created with the OpenVPN InstantApp to routed IP, the configured VPN will fail to work after the reboot. This is caused by a bug in a script that has been fixed on newer versions of the OpenVPN image.
+
+This can now be fixed by installing a new version of the OpenVPN scripts, which has been packaged in Scaleway's stable PPA and contains the fixed script.
+
+You can also avoid this situation altogether by installing the package prior to moving to a routed IP.
+
+
+ This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+
+
+
+## Your Instance has not been rebooted
+
+1. Add Scaleway's stable PPA
+
+```sh
+add-apt-repository ppa:scaleway/stable
+```
+2. Add the scaleway-ovpn-scripts package containing the new scripts
+
+```sh
+apt -y install scaleway-ovpn-scripts
+```
+
+From this point on, your Instance may be safely rebooted and you will no longer lose VPN functionality.
+
+## Your Instance has rebooted and the VPN service no longer works.
+
+1. Add Scaleway's stable PPA
+
+```sh
+add-apt-repository ppa:scaleway/stable
+```
+2. Add the scaleway-ovpn-scripts package containing the new scripts
+
+```sh
+apt -y install scaleway-ovpn-scripts
+```
+
+3. Reboot your Instance.
+
+Once rebooted, your VPN service will be available.
+
+
+ OpenVPN images published after November 9th 2023 already contain the fixed script and do not need to be modified.
+
+
diff --git a/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx b/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx
new file mode 100644
index 0000000000..6102203c2e
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-cloud-init-debian12.mdx
@@ -0,0 +1,30 @@
+---
+meta:
+ title: Fix the wrong user configuration of cloud-init on Debian 12 (Bookworm)
+ description: This page helps you fix the wrong user configuration of cloud-init on Debian 12 (Bookworm)
+content:
+ h1: Fix the wrong user configuration of cloud-init on Debian 12 (Bookworm)
+ paragraph: This page helps you fix the wrong user configuration of cloud-init on Debian 12 (Bookworm)
+tags: debian12 debian bookworm cloud-init
+dates:
+ validation: 2025-01-02
+ posted: 2023-05-04
+categories:
+ - compute
+---
+
+Debian 12 (Bookworm) Instances created before June 2nd, 2023 were delivered with a preinstalled version of `cloud-init` that came with a wrong user configuration made by the custom-built upstream `cloud-init 23.2`.
+
+The issue has been fixed for Instances created after June 2nd, 2023. The Debian 12 image now uses the official Debian Unstable `cloud-init` package.
+
+Run the following commands to fix the issue on an Instance affected by this bug:
+```
+wget http://ftp.fr.debian.org/debian/pool/main/c/cloud-init/cloud-init_23.2-1_all.deb -O /tmp/cloud-init_23.2-1_all.deb
+
+dpkg -i /tmp/cloud-init_23.2-1_all.deb
+
+for FILE in /etc/group /etc/gshadow /etc/passwd /etc/shadow /etc/subgid /etc/subuid /etc/sudoers.d/90-cloud-init-users;
+do
+sed -i -e 's/Ubuntu/Debian/g' -e 's/ubuntu/debian/g' $FILE
+done
+```
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx b/pages/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx
new file mode 100644
index 0000000000..6ee524c8bd
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx
@@ -0,0 +1,147 @@
+---
+meta:
+ title: Fixing DNS resolution with a routed IPv6-only setup on Debian Bullseye
+ description: This page helps you to fix DNS resolution with a routed IPv6-only setup on Debian Bullseye
+content:
+ h1: Fixing DNS resolution with a routed IPv6-only setup on Debian Bullseye
+ paragraph: This page helps you to fix DNS resolution with a routed IPv6-only setup on Debian Bullseye
+tags: dns ipv6 Instance debian bullseye
+dates:
+ validation: 2024-08-05
+ posted: 2024-01-23
+categories:
+ - compute
+---
+
+This guide outlines the steps to enable DNS resolution on a Scaleway Instance that uses the Debian Bullseye image, configured with one or more routed IPv6 addresses and without any IPv4 addresses.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Instance](/instances/how-to/create-an-instance/) running Debian Bullseye (11) with an IPv6-only setup
+
+
+ This guide explains how to switch from the traditional `ifupdown` toolset to the more modern `netplan` solution, which is used in recent Debian releases. The process is straightforward if your Instance is using the default network configuration provided by Scaleway metadata.
+ However, if your Instance has a customized network setup, ensure you are comfortable with both `ifupdown` and `netplan` before proceeding. You can safely apply this procedure to a newly created Instance.
+
+
+## Technical explanation
+
+When a Scaleway Instance uses routed IP addresses, the IPv6 stack is automatically configured using [`SLAAC`](https://datatracker.ietf.org/doc/html/rfc4862). With this method, the Instance is periodically advertised with various network configuration details, including the DNS server addresses it should use. The Instance is then free to consume these advertisements or not. By default, the operating system images provided by Scaleway are configured to leverage these advertisements to configure the IPv6 networking and the related DNS servers. The Debian Bullseye image is no exception.
+
+When configuring the network at boot time, the `cloud-init` software detects the appropriate network configuration method used by the system at hand and writes and/or applies the necessary configuration files/parameters. On Debian Bullseye, and because of [`cloud-init`'s built-in order of detection](https://cloudinit.readthedocs.io/en/latest/reference/network-config.html#network-output-policy), the primary detected method is [ENI](https://cloudinit.readthedocs.io/en/latest/reference/network-config.html#eni), which configures the network through Debian's well known `/etc/network/interfaces` set of files, along with the `ifupdown` toolset.
+
+This configuration method does not interact well with SLAAC's DNS advertisements. This results in an absence of DNS resolver configuration, thus breaking most of the network activities.
+
+Due to its modern nature and active maintenance, [`netplan` is a favorable option for configuring cloud systems](https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_modern_network_configuration_for_cloud) and conveniently addresses the current issue. However, in alignment with our image building policy, which aims to minimize alterations to the official upstream cloud image, `netplan` is intentionally not enabled by default in Scaleway's Debian Bullseye image.
+
+## Checking if your Instance is concerned
+
+You can check whether your Debian Bullseye Instance is concerned by running the following command, where `UUID` is the identifier of your Instance:
+
+```sh
+scw -o json instance server get UUID | jq '.routed_ip_enabled and ([.public_ips[] | select(.family != "inet6")] == [])'
+```
+
+
+ Make sure you have installed the [Scaleway CLI tools](/scaleway-cli/quickstart/) on your local machine before running the command above.
+
+
+The command will output:
+
+* `true` if the Instance is concerned by the present procedure.
+* `false` otherwise.
+
+
+ The above command must only be run against a Debian Bullseye Instance. It does not check for this condition itself.
+
+
+## Installing netplan
+
+The `netplan` package must be installed **before** you apply this procedure, or it will fail.
+
+
+ Latest Debian Bullseye images from Scaleway ship with `netplan` pre-installed.
+
+
+### Checking for netplan
+
+To check whether your Instance has `netplan` installed, run the following command:
+ ```sh
+ dpkg-query -W netplan.io
+ ````
+The command should return an output like this, where `` is the currently installed version of the package, meaning you can skip directly to the first step of the procedure:
+ ```sh
+ netplan.io
+ ```
+If the tool is not installed, the command will print the following:
+ ```sh
+ dpkg-query: no packages found matching netplan.io
+ ````
+In this situation, proceed with the next section to install `netplan` before applying the procedure.
+
+### Installing the tool
+
+
+ All steps below require super-user (`root`) privileges.
+
+
+1. *(optional)* If, **and only if**, your Instance is already booted using a routed IPv6-only setup, you need to temporarily configure your DNS resolver so that it can reach the Debian repositories, in order to install `netplan`. The following uses Google's DNS server:
+ ```sh
+ > /etc/resolv.conf cat <
+ All steps below require super-user (`root`) privileges.
+
+
+1. Force `cloud-init` to set up the network configuration using `netplan`.
+ ```sh
+ > /etc/cloud/cloud.cfg.d/99_scw_ip6dns.cfg cat <
+ Refer to the [Debian NetworkConfiguration wiki](https://wiki.debian.org/NetworkConfiguration) and the [`netplan` documentation](https://netplan.readthedocs.io/en/stable/) if required.
+
+4. Enable the necessary `systemd` units:
+ ```sh
+ systemctl enable systemd-networkd-wait-online.service systemd-resolved.service
+ ```
+5. Reboot the Instance:
+ ```
+ reboot
+ ```
+6. Reconnect to the Instance and ensure DNS resolution is working:
+ ```
+ host -W3 google.com
+ ```
+7. Optionally, it is strongly recommended that you upgrade the `scaleway-ecosystem` package to at least version `0.0.6-10`.
+ ```
+ apt-get update
+ apt-get -y upgrade scaleway-ecosystem
+ reboot
+ ```
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx b/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx
new file mode 100644
index 0000000000..2f2514f63e
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx
@@ -0,0 +1,37 @@
+---
+meta:
+ title: Fix long delays when booting without a public IP
+ description: This page explains how to avoid long delays when booting a Scaleway Instance without a public IP
+content:
+ h1: Fix long delays when booting without a public IP
+ paragraph: This page explains how to avoid long delays when booting a Scaleway Instance without a public IP
+tags: centos-stream rockylinux almalinux network-manager ipv6 routed ip
+dates:
+ validation: 2024-10-21
+ posted: 2024-04-17
+categories:
+ - compute
+---
+
+When booting an Instance lacking a public IP address and connected to a Private Network, users may encounter significant delays during the boot process.
+This delay is particularly noticeable in Ubuntu Jammy, where it can extend up to 5 minutes. Other distributions may experience delays of approximately 2 minutes during boot.
+The cause of this delay stems from systemd's failure to configure the public network interface, waiting for a timeout before further boot operations proceed.
+
+To minimize boot delays, you can manually implement a bypass in the `systemd-networkd-wait-online.service`:
+
+1. Create a directory for additional systemd service configurations:
+
+ ```bash
+ mkdir /etc/systemd/system/systemd-networkd-wait-online.service.d
+ ```
+
+2. Create a configuration file within the directory to adjust the timeout:
+
+ ```bash
+ cat >/etc/systemd/system/systemd-networkd-wait-online.service.d/wait-for-5-seconds.conf<
+ This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+
+
+1. Install the new `debian-stable` PPA.
+ The URL of the PPA may be configured to use the `noble` series. Replace `noble` with `bionic` in the URL.
+ ```bash
+ rm -f /etc/apt/sources.list.d/scaleway-ubuntu-stable-bionic.list
+ add-apt-repository ppa:scaleway/debian-staging
+ nano /etc/apt/sources.list.d/scaleway-ubuntu-debian-staging-noble.list
+ ```
+ In the file opened with `nano`, replace `noble` with `bionic`.
+2. Install the new version of `scaleway-ecosystem` and `cloud-init`. It is important to clean the previous `cloud-init` data as the new version has a structure that may cause a failure at the next boot.
+ ```bash
+ apt update
+ apt -y install scaleway-ecosystem cloud-init
+ cloud-init clean
+ ```
+3. Reboot the Instance to apply the changes.
+ ```bash
+ reboot
+ ```
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-noble-wrong-ppa-configuration.mdx b/pages/instances/troubleshooting/fix-noble-wrong-ppa-configuration.mdx
new file mode 100644
index 0000000000..bc5c7eb4d2
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-noble-wrong-ppa-configuration.mdx
@@ -0,0 +1,29 @@
+---
+meta:
+ title: Fixing wrong PPA configuration on Ubuntu Noble Instances
+ description: This page helps you to fix the PPA configuration on Ubuntu 24.04 Noble
+content:
+ h1: Fixing wrong PPA configuration on Ubuntu Noble Instances
+ paragraph: This page helps you to fix the PPA configuration on Ubuntu 24.04 Noble
+tags: ubuntu-noble noble 24.04 ppa staging
+dates:
+ validation: 2024-12-23
+ posted: 2024-06-20
+categories:
+ - compute
+---
+
+The newest Ubuntu 24.04 Noble Numbat Instances created before June 19, 2024, may have their Scaleway PPA pointing to the staging PPA.
+
+
+ Instances created on or after June 19, 2024, do not encounter this issue.
+
+
+## Fixing the PPA configuration
+
+To resolve this issue, execute the following commands:
+```
+rm -f /etc/apt/sources.list.d/scaleway-ubuntu-staging-noble.sources
+add-apt-repository ppa:scaleway/stable
+```
+Press `` when prompted.
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx
new file mode 100644
index 0000000000..7d5dc1be36
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx
@@ -0,0 +1,124 @@
+---
+meta:
+ title: Fix unreachable Ubuntu Focal Instance when it has two public IP adresses
+ description: This page helps you recover or avoid unreachable Ubuntu 20.04 Focal Instance when it has two public IP addresses.
+content:
+ h1: Fix unreachable Ubuntu Focal Instance when it has two public IP adresses
+ paragraph: This page helps you recover or avoid unreachable Ubuntu 20.04 Focal Instance when it has two public IP addresses.
+tags: ubuntu-focal focal 20.04 multiple ipv4 ip
+dates:
+ validation: 2024-07-23
+ posted: 2024-07-23
+categories:
+ - compute
+---
+
+When using an Ubuntu 20.04 Focal Instance with more than one routed IP address, the Instance will become unreachable after a reboot. This may happen when you attach a second routed IPv4 or IPv6 IP address to the Instance.
+
+The version of `systemd-networkd` used in Ubuntu Focal does not support the definition of a default route which is not part of the subnet of the network interface. The `on-link: true` option must be added to the netplan profile.
+
+A modified `cloud-init` package named `cloud-init_24.2-0ubuntu1~20.04.1+scaleway` has been added to Scaleway's stable PPA to work around this situation.
+
+
+ This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+
+
+## Your Instance has not been rebooted
+
+1. Add Scaleway's stable PPA
+
+```sh
+add-apt-repository ppa:scaleway/stable
+```
+2. Add the modified cloud-init package
+
+```sh
+apt -y install cloud-init
+```
+3. Re-initialize cloud-init to fix the netplan profile
+```sh
+cloud-init clean
+cloud-init init --local
+cloud-init init
+```
+From this point on, your Instance may be safely rebooted and you will no longer lose connectivity.
+
+## Your Instance has rebooted and is no longer reachable
+
+[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more.
+
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/scaleway-cli/quickstart/):
+```
+scw instance server stop
+# Wait for the instance to be stopped.
+scw instance server update boot-type=rescue
+scw instance server start
+```
+
+ Replace `` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`.
+
+
+2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it:
+```sh
+cat /proc/partitions
+major minor #blocks name
+
+7 0 65480 loop0
+7 1 89120 loop1
+7 2 39760 loop2
+252 0 19531250 vda
+252 1 19417569 vda1
+252 14 4096 vda14
+252 15 108544 vda15
+8 0 9765625 sda
+8 1 3240943 sda1
+8 14 4096 sda14
+8 15 108544 sda15
+
+```
+Then mount the partitions and get into the `chroot`:
+
+```sh
+mount /dev/vda1 /mnt
+mount -o bind /sys /mnt/sys
+mount -o bind /proc /mnt/proc
+mount -o bind /dev /mnt/dev
+mount -o bind /run /mnt/run
+chroot /mnt
+```
+3. Fix the DNS resolution file in the chroot
+```sh
+rm -f /etc/resolv.conf
+ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
+```
+4. Once in the `chroot` install the modified cloud-init package:
+```
+add-apt-repository ppa:scaleway/stable
+apt -y install cloud-init
+```
+5. Re-initialize cloud-init to fix the netplan profile:
+```sh
+cloud-init clean && cloud-init init --local && cloud-init init
+```
+6. Get out of the `chroot` and remove the mounts:
+```sh
+umount /mnt/sys /mnt/proc /mnt/dev /mnt/run /mnt
+```
+7. Stop the Instance, switch back the Instance's `boot_type` to `local`, and reboot the Instance:
+```
+scw instance server stop
+# Wait for the instance to be stopped
+scw instance server update boot-type=local
+scw instance server start
+```
+Once rebooted, your Instance will be reachable again.
+
+
+ This modification will be valid until Ubuntu publishes a new version, i.e. cloud-init 24.3. You can use the following commands to hold the newly installed version so it does not get updated when the new version comes in.
+
+
+8. Put a hold on the newly installed cloud-init:
+```sh
+apt-mark hold cloud-init
+cloud-init set on hold.
+```
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx b/pages/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx
new file mode 100644
index 0000000000..9de26efc4a
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx
@@ -0,0 +1,97 @@
+---
+meta:
+ title: Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP
+ description: This page helps recover or avoid unreachable IPv6 Instances after transitioning to routed IP
+content:
+ h1: Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP
+ paragraph: This page helps recover or avoid unreachable IPv6 Instances after transitioning to routed IP
+tags: centos-stream rockylinux almalinux network-manager ipv6 routed ip
+dates:
+ validation: 2024-09-02
+ posted: 2023-11-16
+categories:
+ - compute
+---
+
+RHEL-based Instances created before November 15 2023 require a NetworkManager configuration that enables correct IPv6 configuration, after a transition to routed IP is performed. If your Instance is configured only with an IPv6 address, it will become unreachable after the migration. It is important to add the NetworkManager configuration so IPv6 configuration remains correct.
+
+The affected O/S distributions are:
+
+- CentOS Stream versions 8 and 9
+- RockyLinux versions 8 and 9
+- AlmaLinux versions 8 and 9
+- Fedora versions 37 and 38
+
+
+ CentOS 7.9 is not concerned by this issue as it does not support routed IP.
+
+
+
+ This guide addresses specific issues related to RHEL-based Instances after transitioning to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature).
+
+
+## Your Instance has not been migrated to routed IP yet
+
+Connect to your Instance and execute the following command as `root` user to add the required NetworkManager option:
+```
+cat << EOF > /etc/NetworkManager/conf.d/00-scaleway.conf
+[connection]
+# The value 0 stands for eui64 -- see nm-settings-nmcli(5)
+ipv6.addr-gen-mode=0
+EOF
+```
+
+## Your Instance has been moved to routed IP
+
+If your Instance has been moved to routed IP and you have IPv4 connectivity, add the NetworkManager configuration as outlined in the previous section. After the next reboot, you will recover IPv6 connectivity while IPv4 configuration will remain untouched
+
+### You only have IPv6 configured so you cannot connect to the Instance anymore
+
+
+ Two reboots of your Instance will be required in order to recover IPv6 connectivity.
+
+
+If you are in this situation, you need to temporarily add an IPv4 address to connect to your Instance in order to add the NetworkManager configuration.
+
+```
+scw instance server list
+ID NAME TYPE STATE ZONE PUBLIC IP PRIVATE IP TAGS IMAGE NAME ROUTED
+{Instance_ID} rocky8 DEV1-S running fr-par-2 2001:bc8:1210:26a:dc00:ff:fe23:ab83 - [] RockyLinux 8 true
+
+scw instance ip create type=routed_ipv4 server={Instance_ID}
+scw instance server reboot {Instance_ID}
+
+```
+Once the reboot is completed, list your IP addresses and identify the IPv4 address attached to your Instance:
+```
+$ scw instance ip list
+ID ADDRESS PREFIX TYPE REVERSE PROJECT SERVER ID SERVER NAME TAGS ZONE
+{IPv6_address_ID} - 2001:bc8:1210:26a::/64 routed_ipv6 - {project id} {project id} rocky8 [] fr-par-2
+{IPv4_address_ID} 51.159.143.128 - routed_ipv4 - {project id} {project id} rocky8 [] fr-par-2
+```
+You can now connect to your Instance with the IPv4 address to make the NetworkManager configuration change:
+```
+ssh root@51.159.143.128
+cat << EOF > /etc/NetworkManager/conf.d/00-scaleway.conf
+[connection]
+ipv6.addr-gen-mode=0
+EOF
+```
+Once modified, reset your Instance to its prior configuration. It is necessary to first detach the IPv4 address before attaching the IPv6 address.
+```
+scw instance server standby {Instance_ID}
+scw instance server update {Instance_ID} ip=none
+scw instance server update {Instance_ID} ip={IPv6_address_ID}
+scw instance server start {Instance_ID}
+scw instance ip delete {IPv4_address_ID}
+```
+
+You can now connect using your IPv6 address:
+```
+ssh root@2001:bc8:1210:26a:dc00:ff:fe23:ab83
+Warning: Permanently added '2001:bc8:1210:26a:dc00:ff:fe23:ab83' (ED25519) to the list of known hosts.
+Activate the web console with: systemctl enable --now cockpit.socket
+
+ Last login: Wed Nov 15 16:53:09 2023 from 51.159.46.153
+ [root@rocky8 ~]#
+```
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx b/pages/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx
new file mode 100644
index 0000000000..82044fb0f1
--- /dev/null
+++ b/pages/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx
@@ -0,0 +1,92 @@
+---
+meta:
+ title: Fix unreachable Ubuntu Noble Instances following a reboot
+ description: This page helps you to recover or avoid unreachable Ubuntu 24.04 Noble Instances after a reboot
+content:
+ h1: Fix unreachable Ubuntu Noble Instances following a reboot
+ paragraph: This page helps you to recover or avoid unreachable Ubuntu 24.04 Noble Instances after a reboot
+tags: ubuntu-noble noble 24.04 reboot
+dates:
+ validation: 2024-12-19
+ posted: 2024-06-11
+categories:
+ - compute
+---
+
+The newest Ubuntu 24.04 Noble Numbat Instances may become unreachable after a reboot. This distribution now uses dhcpcd which may encounter longer delays to reapply its DHCP lease after a reboot.
+
+Instances created after June 11th 2024 will not encounter this problem.
+
+## Your Instance has not been rebooted
+
+You can avoid this situation by increasing the dhcpcd timeout in its configuration file:
+```
+sed -i 's/timeout 5/timeout 10/' /etc/dhcpcd.conf
+
+tail /etc/dhcpcd.conf
+option rapid_commit
+
+# A ServerID is required by RFC2131.
+require dhcp_server_identifier
+
+# Generate SLAAC address using the Hardware Address of the interface
+#slaac hwaddr
+# OR generate Stable Private IPv6 Addresses based from the DUID
+slaac private
+timeout 10
+```
+
+## Your Instance has rebooted and is no longer reachable
+
+[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more.
+
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/scaleway-cli/quickstart/):
+ ```
+ scw instance server stop
+ scw instance server update boot-type=rescue
+ scw instance server start
+ ```
+
+ Replace `` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`.
+
+2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it:
+ ```sh
+ cat /proc/partitions
+ major minor #blocks name
+
+ 8 0 9765625 sda
+ 8 1 9634536 sda1
+ 8 14 3072 sda14
+ 8 15 126976 sda15
+ ```
+ Then mount the partitions:
+ ```
+ mount /dev/sda1 /mnt
+ ```
+3. Once mounted, use the `chroot` command to get into your Instance's root file system. You can then change the timeout value for dhcpcd as shown above:
+ ```
+ chroot /mnt
+ sed -i 's/timeout 5/timeout 10/' /etc/dhcpcd.conf
+
+ tail /etc/dhcpcd.conf
+ option rapid_commit
+
+ # A ServerID is required by RFC2131.
+ require dhcp_server_identifier
+
+ # Generate SLAAC address using the Hardware Address of the interface
+ #slaac hwaddr
+ # OR generate Stable Private IPv6 Addresses based from the DUID
+ slaac private
+ timeout 10
+
+ exit
+ umount /mnt
+ ```
+4. Switch back the Instance's `boot_type` to `local` and reboot the Instance:
+ ```
+ scw instance server stop
+ scw instance server update boot-type=local
+ scw instance server start
+ ```
+ Once rebooted, your Instance will be reachable again.
\ No newline at end of file
diff --git a/pages/instances/troubleshooting/index.mdx b/pages/instances/troubleshooting/index.mdx
new file mode 100644
index 0000000000..ecd9daf1fe
--- /dev/null
+++ b/pages/instances/troubleshooting/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Instances - Troubleshooting
+ description: Instances Troubleshooting
+content:
+ h1: Instances - Troubleshooting
+ paragraph: Instances Troubleshooting
+---
diff --git a/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx b/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx
new file mode 100644
index 0000000000..6bd57a2796
--- /dev/null
+++ b/pages/instances/troubleshooting/reboot-from-faulty-kernel.mdx
@@ -0,0 +1,115 @@
+---
+meta:
+ title: Troubleshooting issues with faulty kernel installations
+ description: Learn how to troubleshoot and resolve issues caused by faulty kernel installations with our comprehensive guide.
+content:
+ h1: Troubleshooting issues with faulty kernel installations
+ paragraph: Learn how to troubleshoot and resolve issues caused by faulty kernel installations with our comprehensive guide.
+tags: kernel faulty-kernel reboot bugfix
+dates:
+ validation: 2025-01-06
+ posted: 2022-11-23
+categories:
+ - compute
+---
+
+[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more.
+
+
+
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Instance](/instances/how-to/create-an-instance/)
+- Installed and configured the Scaleway [CLI](/instances/api-cli/creating-managing-instances-with-cliv2) on your local computer
+
+
+1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the CLI-Tools:
+ ```
+ scw instance server update {Instance_ID} boot-type=rescue
+ scw instance server reboot {Instance_ID}
+ ```
+
+ Replace `{Instance_ID}` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`.
+
+2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it:
+ ```sh
+ cat /proc/partitions
+ major minor #blocks name
+
+ 8 0 9765625 sda
+ 8 1 9634536 sda1
+ 8 14 3072 sda14
+ 8 15 126976 sda15
+ ```
+ Then mount the partitions:
+ ```
+ mount /dev/sda1 /mnt
+ mount /dev/sda15 /mnt/boot/efi
+ mount -o bind /sys /mnt/sys
+ mount -o bind /proc /mnt/proc
+ mount -o bind /dev /mnt/dev
+ ```
+3. Once mounted, use the `chroot` command to get into your Instances' root file system. You can then change the `GRUB_DEFAULT` value to boot using the previous kernel:
+ ```sh
+ chroot /mnt
+ nano /etc/default/grub
+ ```
+
+ In the example above, we use `nano` as text editor. Feel free to use your favorite text editor to edit the file.
+
+ Change the value of `GRUB_DEFAULT` to `"1 > 2":
+ ```sh
+ # head /etc/default/grub
+ # If you change this file, run 'update-grub' afterward to update
+ # /boot/grub/grub.cfg.
+ # For full documentation of the options in this file, see:
+ # info -f grub -n 'Simple configuration'
+
+ GRUB_DEFAULT="1>2"
+ GRUB_TIMEOUT=5
+ GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
+ GRUB_CMDLINE_LINUX_DEFAULT=""
+ GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0"
+ ```
+ Save the file and exit the text editor.
+4. Update the `grub` boatloader` to apply the kernel's update:
+ ```
+ # update-grub
+ Generating grub configuration file ...
+ Found linux image: /boot/vmlinuz-6.0.0-0.deb11.2-cloud-amd64
+ Found initrd image: /boot/initrd.img-6.0.0-0.deb11.2-cloud-amd64
+ Found linux image: /boot/vmlinuz-5.19.0-0.deb11.2-cloud-amd64
+ Found initrd image: /boot/initrd.img-5.19.0-0.deb11.2-cloud-amd64
+ Found linux image: /boot/vmlinuz-5.10.0-19-cloud-amd64
+ Found initrd image: /boot/initrd.img-5.10.0-19-cloud-amd64
+ done
+ ```
+5. Switch back the Instance's `boot_type` to `local` and reboot the Instance:
+ ```
+ scw instance server update {Instance_ID} boot-type=local
+ scw instance server reboot {Instance_ID}
+ ```
+ Your Instance reboots on the previously installed kernel.
+
+ ### Examples of failed boots
+
+* In the following example, the Instance may only boot with the root file system in `read-only` mode:
+ ```sh
+ [ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
+ [ 4.219158] cloud-init[542]: Traceback (most recent call last):
+ [ 4.220328] cloud-init[542]: File "/usr/bin/cloud-init", line 33, in
+ [ 4.221518] cloud-init[542]: sys.exit(load_entry_point('cloud-init==20.4.1', 'console_scripts', 'cloud-init')())
+ [ 4.223064] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 891, in main
+ [ 4.224435] cloud-init[542]: retval = util.log_time(
+ [ 4.225251] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2348, in log_time
+ [ 4.226838] cloud-init[542]: ret = func(*args, **kwargs)
+ [ 4.227743] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 600, in status_wrapper
+ [ 4.229478] cloud-init[542]: util.ensure_dirs((data_d, link_d,))
+ [ 4.230501] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1534, in ensure_dirs
+ [ 4.232014] cloud-init[542]: ensure_dir(d, mode)
+ [ 4.232540] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1591, in ensure_dir
+ [ 4.233980] cloud-init[542]: chmod(path, mode)
+ [ 4.234756] cloud-init[542]: File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1830, in chmod
+ [ 4.235672] cloud-init[542]: os.chmod(path, real_mode)
+ [ 4.236227] cloud-init[542]: OSError: [Errno 30] Read-only file system: '/var/lib/cloud/data'
+ [FAILED] Failed to start Apply the …ngs specified in cloud-config.
+ ```
\ No newline at end of file
diff --git a/pages/interlink/assets/scaleway-interlink-diag-simple.webp b/pages/interlink/assets/scaleway-interlink-diag-simple.webp
new file mode 100644
index 0000000000..ac3bf704c3
Binary files /dev/null and b/pages/interlink/assets/scaleway-interlink-diag-simple.webp differ
diff --git a/pages/interlink/concepts.mdx b/pages/interlink/concepts.mdx
new file mode 100644
index 0000000000..a80940313d
--- /dev/null
+++ b/pages/interlink/concepts.mdx
@@ -0,0 +1,78 @@
+---
+meta:
+ title: InterLink - Concepts
+ description: Understand Scaleway InterLink terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and workflows.
+ noindex: true
+content:
+ h1: InterLink - Concepts
+ paragraph: Understand Scaleway InterLink terminology with our glossary of the core concepts underpinning this product. Learn about key features, architecture, and workflows.
+tags: interlink direct-connect dedicated connection
+dates:
+ creation: 2024-10-31
+ validation: 2024-10-31
+categories:
+ - networks
+---
+
+
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+
+
+## Allowed routes list
+
+The default rule blocks any and all routes from being propagated over InterLink. Attaching an allowed routes list (aka **routing policy**) allows you to define the ranges of routes that should be whitelisted. When creating an allowed routes list, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure.
+
+Each InterLink can have one allowed routes list attached to it, but a single allowed routes list can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the allowed routes list are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
+
+You may also know allowed routes lists under the terms "routing policy", or "route filters".
+
+## Attached VPC
+
+Each InterLink can be attached to one Scaleway VPC. The InterLink and the VPC must be in the same [region](#region). You can detach the InterLink from the VPC at any time, and attach it to a different VPC in the same region, if you wish. When an InterLink is not attached to any VPC, no traffic can flow.
+
+## Bandwidth
+
+Every InterLink has a defined bandwidth, representing the maximum data transfer rate possible over the connection. Measured in megabits per second (Mbps) or gigabits per second (Gbps), it shows how much data can be transmitted over InterLink per second.
+
+## InterLink
+
+InterLink, currently in Private Beta, is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet.
+
+Currently, InterLink is available in **hosted** version only. This means that you must choose a compatible [partner](#partner) to facilitate the physical connection between the external infrastructure and the Scaleway VPC. The physical connection may be shared between several clients, each allocated a specific amount of bandwidth for their InterLink.
+
+
+
+For more information on how InterLink works, see our [detailed overview](/interlink/reference-content/overview/).
+
+## Location
+
+A location, aka a **P**oint **o**f **P**resence (PoP), is a physical location where you can establish an InterLink connection between your on-premises infrastructure and the Scaleway network. Locations are facilitated by partners.
+
+## Pairing key
+
+A pairing key is a unique identifier used to establish and authenticate an InterLink connection. It is provided by Scaleway once an InterLink order is made. You must then share this key with your selected partner to facilitate the setup of the physical link. The pairing key ensures that the correct endpoints are securely connected.
+
+## Partner
+
+A partner is a third party service provider that facilitates a hosted InterLink connection between a client's on-premises infrastructure, and their Scaleway infrastructure. Current partners include [Free Pro](https://pro.free.fr/), with more coming soon.
+
+Partners are generally companies specialized in data transit, with their own fibers at data connection points. To establish an InterLink connection via a partner, generally you must be client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. See our information on [hosted InterLinks](/interlink/reference-content/overview/#hosted-interlinks) for more information.
+
+## PoP
+
+See [Location](#location)
+
+## Region
+
+When creating an InterLink, you must specify a [region](/vpc/concepts/#region-and-availability-zone) for the resource. The region sets the scope for the Scaleway infrastructure that can be connected via the InterLink: it must correspond to the region of the VPC to attach to the InterLink.
+
+## Route propagation
+
+Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must use an [allowed routes list](#allowed-routes-list) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink)
+
+## Routing policy
+
+See [Allowed routes list](#allowed-routes-list).
+
+
+
diff --git a/pages/interlink/index.mdx b/pages/interlink/index.mdx
new file mode 100644
index 0000000000..f9ec0575fe
--- /dev/null
+++ b/pages/interlink/index.mdx
@@ -0,0 +1,55 @@
+---
+meta:
+ title: InterLink Documentation
+ description: Dive into Scaleway InterLink with our quickstart guides, how-tos, tutorials and more.
+ noindex: true
+---
+
+
+ InterLink is currently available in [Private Beta](https://www.scaleway.com/en/betas/) only, for selected testers. Watch this space for more information on public availability.
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-config.webp b/pages/interlink/reference-content/assets/scaleway-interlink-config.webp
new file mode 100644
index 0000000000..e226b9b417
Binary files /dev/null and b/pages/interlink/reference-content/assets/scaleway-interlink-config.webp differ
diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-diag-simple.webp b/pages/interlink/reference-content/assets/scaleway-interlink-diag-simple.webp
new file mode 100644
index 0000000000..ac3bf704c3
Binary files /dev/null and b/pages/interlink/reference-content/assets/scaleway-interlink-diag-simple.webp differ
diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-diag-tech.webp b/pages/interlink/reference-content/assets/scaleway-interlink-diag-tech.webp
new file mode 100644
index 0000000000..5b59f89159
Binary files /dev/null and b/pages/interlink/reference-content/assets/scaleway-interlink-diag-tech.webp differ
diff --git a/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp b/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp
new file mode 100644
index 0000000000..6d06561261
Binary files /dev/null and b/pages/interlink/reference-content/assets/scaleway-interlink-ordering.webp differ
diff --git a/pages/interlink/reference-content/configuring.mdx b/pages/interlink/reference-content/configuring.mdx
new file mode 100644
index 0000000000..74a423e8c9
--- /dev/null
+++ b/pages/interlink/reference-content/configuring.mdx
@@ -0,0 +1,66 @@
+---
+meta:
+ title: Configuring an InterLink
+ description: Find out how to set up your Scaleway InterLink so that traffic can flow between your external infrastructure and your Scaleway resources. Understand how to attach a VPC, create an allowed routes list to whitelist route announcements, and activate route propagation across the connection.
+ noindex: true
+content:
+ h1: Configuring an InterLink
+ paragraph: Find out how to set up your Scaleway InterLink so that traffic can flow between your external infrastructure and your Scaleway resources. Understand how to attach a VPC, create an allowed routes list to whitelist route announcements, and activate route propagation across the connection.
+tags: interlink configuration attach-vpc whitelist route-range ip-prefix route-propagation
+categories:
+ - interlink
+ - network
+dates:
+ validation: 2024-10-24
+ posted: 2024-10-24
+---
+
+
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+
+
+Once your InterLink has been created and the [provisioning process](/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink.
+
+This document explains the process in full, and gives tips for troubleshooting any potential issues.
+
+## Configuration overview
+
+
+
+The diagram above shows the four configuration steps necessary for an InterLink. Only when all steps have been completed can traffic flow across the InterLink, connecting the Scaleway VPC to the external (on-premises) infrastructure.
+
+Read more about each step, and possible errors at each stage, in the following sections.
+
+### 1. Create the InterLink
+
+Creating an InterLink is itself a multi-step process, that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/interlink/reference-content/provisioning/).
+
+You must wait until the InterLink has reached `Active` [status](/interlink/reference-content/statuses/) before you can continue with the following configuration steps.
+
+### 2. Attach VPC
+
+Attaching an InterLink to a VPC allows you to complete the connection from your external infrastructure, across the InterLink, to the Scaleway resources in the selected VPC.
+
+The VPC must be in the same region as the InterLink. An InterLink can only be attached to one VPC at a time, but you are free to detach the VPC and attach a different one whenever you like.
+
+You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-vpc) endpoint to attach a VPC to a given InterLink.
+
+### 3. Attach allowed routes list (routing policy)
+
+InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked** . You must create and attach an [allowed routes list](/interlink/concepts/#allowed-routes-list) aka routing policy, to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink.
+
+You can [create](https://www.scaleway.com/en/developers/api/interlink/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-routing-policy) allowed routes lists via the API.
+
+When setting the route ranges to whitelist, you must separately define the IP prefixes to accept from the external infrastructure (incoming ranges of route announcements to accept), and the IP prefix filters to advertise from the Scaleway VPC to the peer (outgoing ranges of routes to advertise). For example, adding `172.16.4.0/22` whitelists all 1,024 IPs in this block, from `172.16.4.0` to `172.16.7.255`.
+
+Only one allowed routes list (routing policy) can be attached to an InterLink at a given time. However, you can reuse the same list by attaching it to multiple InterLinks, for example if you have a second InterLink attached to the same VPC/external infrastructure for redundance purposes. You can update, delete or reattach a list at any time.
+
+### 4. Activate route propagation.
+
+Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes.
+
+
+Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka [allowed routes list](/interlink/concepts/#allowed-routes-list) to the InterLink to allow traffic to flow.
+
+
+You can deactivate route propagation via the dedicated endpoint at any time. When you do this, all routes are blocked and removed from the VPC's route table. No traffic can flow across the InterLink until route propagation is reactivated.
diff --git a/pages/interlink/reference-content/index.mdx b/pages/interlink/reference-content/index.mdx
new file mode 100644
index 0000000000..121452b0d8
--- /dev/null
+++ b/pages/interlink/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: InterLink - Additional content
+ description: InterLink additional content
+content:
+ h1: InterLink - Additional content
+ paragraph: InterLink additional content
+---
diff --git a/pages/interlink/reference-content/overview.mdx b/pages/interlink/reference-content/overview.mdx
new file mode 100644
index 0000000000..6cfadb998b
--- /dev/null
+++ b/pages/interlink/reference-content/overview.mdx
@@ -0,0 +1,76 @@
+---
+meta:
+ title: InterLink - Technical overview
+ description: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more.
+ noindex: true
+content:
+ h1: InterLink - Technical overview
+ paragraph: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more.
+ noindex: true
+tags: interlink pop infrastructure diagram technical overview
+categories:
+ - interlink
+ - network
+dates:
+ validation: 2024-10-24
+ posted: 2024-10-24
+---
+
+
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+
+
+InterLink is Scaleway's product to let you create a secure, private connection between your external infrastructure, and your Scaleway VPC. This allows you to direct your traffic safely from your Scaleway infrastructure to your on-premises infrastructure, away from the public internet. Compared to a typical internet-based VPN, an InterLink is more reliable, more secure and offers lower latency.
+
+At its simplest level, InterLink can be understood as a configurable connection between your own infrastructure, and your Scaleway VPC. You can configure details such as available bandwidth, and the routes allowed between the two peers:
+
+
+
+## Types of InterLink
+
+Scaleway plans to offer two types of InterLink, though currently only the **hosted** type is available.
+
+### Hosted InterLinks
+
+A hosted InterLink is provisioned via a [partner](/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink.
+
+By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100Mbps - 25Gbps) across the InterLink.
+
+The diagram below shows the architecture of a hosted InterLink. Note that three possibilities are available on the customer side:
+- The partner's router connects to the customer's router (itself connected to the customer's on-premises infrastructure) via a **M**eet **M**e **R**oom at a PoP where both networks are present.
+- The partner's router connects directly to the customer's on-premises infrastructure via a last-mile connection facilitated by the partner.
+- The customer's infrastructure is hosted in the partner's datacenter, and connects to the partner's router directly.
+
+
+
+### Dedicated InterLink
+
+A dedicated InterLink is provisioned, where the customer gets sole use of a single InterLink port on Scaleway's router, with the entire bandwidth of that port. This type of InterLink is not yet available at Scaleway - [contact a sales representative](https://www.scaleway.com/en/contact-sales/) to register your interest.
+
+## Provisioning an InterLink
+
+Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from Scaleway, the customer, and the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/interlink/reference-content/provisioning/) for full details.
+
+## Attaching a VPC
+
+When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/interlink/reference-content/configuring/) page for more information.
+
+While each InterLink can only be attached to a single Scaleway VPC, it is possible to attach two InterLinks to the same VPC to ensure redundancy and high availability. In this case, each InterLink must be provisioned and configured separately, and will be billed separately. Note that you can reuse the same [allowed routes lists](#allowed-routes-list) across multiple InterLinks.
+
+## Routing across an InterLink
+
+InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s network and the Scaleway VPC.
+
+Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes. This facilitates efficient traffic flow across the link towards these destinations, providing that [allowed routes](#allowed-routes-list) and [route propagation](#route-propagation) have been correctly set up.
+
+In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions.
+
+When both BGP sessions are up, the InterLink has `Active` status. If one BGP session is up, and the other down, the status moves to `Limited Connectivity`. If both BGP sessions are down, the status is marked as `Down`. See the page on [InterLink statuses](/interlink/reference-content/statuses) for full information.
+
+### Allowed routes list
+
+By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach an [allowed routes list](/interlink/concepts/#allowed-routes-list) (aka routing policy), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/interlink/reference-content/configuring/) page for more information on allowed routes lists.
+
+### Route propagation
+
+Even after attaching an allowed route list, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation.
diff --git a/pages/interlink/reference-content/provisioning.mdx b/pages/interlink/reference-content/provisioning.mdx
new file mode 100644
index 0000000000..3a3fa23b6f
--- /dev/null
+++ b/pages/interlink/reference-content/provisioning.mdx
@@ -0,0 +1,107 @@
+---
+meta:
+ title: Provisioning an InterLink
+ description: Get help with understanding all the different stages of ordering and provisioning a Scaleway InterLink, from placing the initial order, to dealing with error messages, and deleting the resource if no longer needed.
+ noindex: true
+content:
+ h1: Provisioning an InterLink
+ paragraph: Get help with understanding all the different stages of ordering and provisioning a Scaleway InterLink, from placing the initial order, to dealing with error messages, and deleting the resource if no longer needed.
+tags: interlink provision order steps partner process error
+categories:
+ - interlink
+ - network
+dates:
+ validation: 2024-10-24
+ posted: 2024-10-24
+---
+
+
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+
+
+The process of ordering an InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure.
+
+
+
+This document explains the provisioning process in full, so you know what to expect when ordering an InterLink, what action is required from all parties, and how to deal with any potential errors.
+
+## Provisioning overview
+
+
+
+The diagram above shows the four steps necessary to provision an InterLink. Only when all steps have been completed will the InterLink move to an **Active** status, ready for traffic to flow. Read more about each step, and possible errors at each stage, in the following sections.
+
+For full information about different statuses an InterLink might flow through, see our [dedicated documentation on InterLink statuses](/interlink/reference-content/statuses/).
+
+### 1. User orders InterLink via Scaleway
+
+The order process begins when you order an InterLink via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/) (or, coming soon, via the [Scaleway console](https://console.scaleway.com/) or one of our other [developer tools](https://www.scaleway.com/en/developers/)). To order via the API, use the [Create a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-create-a-link) call. You need to set the following parameters when ordering:
+
+- **Connection type**: In the long term, dedicated, shared and hosted InterLinks will be available. For now, only **hosted** connections (facilitated via a partner) are available.
+- **Partner**: The third-party service provider to facilitate the InterLink. Use the [List available partners](https://www.scaleway.com/en/developers/api/interlink/#path-partners-list-available-partners) call to find available partners.
+- **Region**: The region in which to create the InterLink. It must correspond to the region of the Scaleway VPC you want to later attach to the InterLink.
+- **Location**: The physical **P**oint **o**f **P**resence (PoP) where the connection to Scaleway's network will be established, via the partner.
+- **Bandwidth**: The maximum bandwidth which you want to be available over the InterLink.
+- **Name**: A name (and, optionally, tags) for the InterLink.
+
+
+Scaleway starts charging for the InterLink as soon as your order is placed. You must then wait for the partner to provision the connection, and they may charge you additional fees.
+
+
+After placing the order via the API, the ID of the InterLink is returned in the response. You can use this ID to [check the status of your InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) at any time.
+
+Immediately after ordering, it is expected that your InterLink will briefly be in `Configuring` status, before moving to `Requested` status.
+
+
+If you see a `Failed` status, it means there was a configuration error on the Scaleway side as we attempted to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. When the problem is resolved, the InterLink should automatically move to `Requested` status. If you have any concerns, open a support ticket.
+
+
+### 2. User requests InterLink from partner
+
+After ordering the InterLink from Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you.
+
+Use the [Get a partner](https://www.scaleway.com/en/developers/api/interlink/#path-partners-get-a-partner) endpoint to get information about your selected partner. Each partner provides either a contact email address, and/or the URL of their online portal. You should make contact with your partner via one of these channels.
+
+You should also provide the partner with your unique [pairing key](/interlink/concepts/#pairing-key), which you can get via the [Get an InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) endpoint.
+
+Your InterLink will remain in `Requested` status until the partner responds to your request.
+
+### 3. Partner accepts InterLink request
+
+When the partner approves your request, the InterLink moves to `Provisioning` status. This means that the partner has agreed to facilitate your InterLink, and is now preparing the resources and configuration necessary to establish the physical connection.
+
+Your InterLink will remain in `Provisioning` status until this process has been completed.
+
+
+If your InterLink does not move to `Provisioning` status, you may see one of the following statuses:
+
+- `Refused`: The partner did not agree to provision your InterLink. Delete this InterLink resource, and contact your partner for more information. Consider re-ordering with a different partner.
+- `Expired`: Your InterLink order timed out: after 10 days, no response was received from the selected partner. Delete the InterLink resource, and create a new order if you wish to try again.
+
+
+### 4. Partner provisions InterLink
+
+When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use.
+
+You must still configure your InterLink by attaching it to a VPC, attaching an allowed routes list, and activating route propagation, before traffic can flow over the InterLink. For help with these steps, see our documentation on [configuring your InterLink](/interlink/reference-content/configuring/).
+
+
+If you see a `Limited connectivity` status, this indicates that the partner provisioned your InterLink, but either IPv4 or IPv6 connectivity is down. Similarly, a `Down` status indicates the InterLink is provisioned, but both IPv4 **and** IPv6 connectivity are down. Open a Scaleway support ticket, or contact your partner for assistance.
+
+A `Locked` status indicates, again, that the InterLink was provisioned, but Scaleway Trust and Safety have locked the resource. No actions are possible from you as a user: you should open a support ticket for help and information.
+
+
+## Deprovisioning overview
+
+When you no longer want your InterLink connection, you can delete it. The process is as follows:
+
+1. Deactivate route propagation.
+2. [Delete your InterLink on the Scaleway side](https://www.scaleway.com/en/developers/api/interlink/#path-links-delete-a-link). InterLink status moves to `Deprovisioning`.
+3. Contact your partner to request they deprovision the InterLink resource on their side.
+4. InterLink moves to `Deleted` status once the partner has completed deprovisioning.
+
+Scaleway stops billing you for your InterLink immediately after step 2. Your partner may continue to bill you until they deprovision the resource on their side.
+
+
+If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient.
+
diff --git a/pages/interlink/reference-content/statuses.mdx b/pages/interlink/reference-content/statuses.mdx
new file mode 100644
index 0000000000..19819cca8a
--- /dev/null
+++ b/pages/interlink/reference-content/statuses.mdx
@@ -0,0 +1,39 @@
+---
+meta:
+ title: Understanding InterLink statuses
+ description: Find out what the different possible statuses of your InterLink mean, and how to take action based on these statuses when necessary.
+ noindex: true
+content:
+ h1: Understanding InterLink statuses
+ paragraph: Find out what the different possible statuses of your InterLink mean, and how to take action based on these statuses when necessary.
+tags: interlink status
+categories:
+ - interlink
+ - network
+dates:
+ validation: 2024-10-24
+ posted: 2024-10-24
+---
+
+
+InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
+
+
+An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call.
+
+This document explains the different statuses possible for an InterLink, and how to understand them.
+
+| **Status** | **Description** |
+|-------------------|-----------------------------------------|
+| **Configuring** | InterLink is configuring and is in a transient state. No user actions can be carried out.
This status could occur immediately after creating your InterLink order, while Scaleway processes the order and configures the InterLink, or at any time when a new configuration is being applied. |
+| **Requesting** | InterLink has been created successfully on the Scaleway side, provisioning must now be requested from the chosen partner.
You must contact your partner to request that they provision your InterLink. Either a contact email address, or a link to the partner’s portal is provided via the Scaleway API. Scaleway does not make the request to the partner, this is the responsibility of the user.
The InterLink will remain in `Requesting` status until the partner accepts the request, at which point it moves into `Provisioning` status. Alternatively, the partner may refuse the request, or the request may time out. |
+| **Failed** | Scaleway was unable to create the InterLink.
This usually occurs when there is a configuration error on the Scaleway side while attempting to create the InterLink. Our technical team is automatically made aware of such a problem, and will intervene to resolve it. When the problem is resolved, the InterLink should move to `Requesting` status. Wait for technical intervention, or open a support ticket if you require further help.
+| **Provisioning** | The partner has accepted the InterLink request, and is now provisioning the connection at their end.
The InterLink is not yet operational: traffic cannot yet flow. You must wait for the partner to finish provisioning the connection. When provisioning is complete, the InterLink should move to `Active` status. |
+| **Expired** | No response was received from the selected partner in the 10 days following the creation of the InterLink on the Scaleway side.
If Scaleway does not receive a response from the selected partner after 10 days, the InterLink moves to `Expired` status. It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again. |
+| **Refused** | The partner refused the request to provision the InterLink.
It is not possible to take action to move this InterLink to a different status: you must delete the InterLink, and create a new order if you wish to try again with a different partner or configuration. |
+| **Active** | The InterLink is in a ready state, and traffic can flow.
The InterLink has been provisioned on both the Scaleway side and the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that allowed routes lists, route propagation, and an attached VPC are correctly configured). |
+| **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited.
This may be the case if either, but not both of, the BGP, IPv4, or IPv6 sessions are down. |
+| **Down / All down** | The InterLink is provisioned, but there is no IP connectivity.
The InterLink has been provisioned successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. |
+| **Locked** | The InterLink has been locked by the Trust and Safety team
You cannot carry out any actions on the InterLink. Open a support ticket. |
+| **Deprovisioning** | Deletion of the InterLink has been initiated on either the partner side or the Scaleway side, but has not been finalized.
An InterLink must be deleted by both Scaleway and the partner in order to move to `Deleted` status. If you have deleted an InterLink on the Scaleway side, ensure you contact the partner separately to request that they delete the resource on their side. If you have deleted an InterLink on the partner side, ensure that you delete the resource on the Scaleway side. |
+| **Deleted** | The InterLink has been deprovisioned by both Scaleway and the partner, and is now deleted. |
\ No newline at end of file
diff --git a/pages/ipam/assets/scaleway-ipam-moreinfo.webp b/pages/ipam/assets/scaleway-ipam-moreinfo.webp
new file mode 100644
index 0000000000..2b88ae87f4
Binary files /dev/null and b/pages/ipam/assets/scaleway-ipam-moreinfo.webp differ
diff --git a/pages/ipam/assets/scaleway-reserve-ip.webp b/pages/ipam/assets/scaleway-reserve-ip.webp
new file mode 100644
index 0000000000..c83b443fab
Binary files /dev/null and b/pages/ipam/assets/scaleway-reserve-ip.webp differ
diff --git a/pages/ipam/concepts.mdx b/pages/ipam/concepts.mdx
new file mode 100644
index 0000000000..d4b23e9f9f
--- /dev/null
+++ b/pages/ipam/concepts.mdx
@@ -0,0 +1,60 @@
+---
+meta:
+ title: IPAM - Concepts
+ description: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
+content:
+ h1: IPAM - Concepts
+ paragraph: Learn about IP Address Management (IPAM) concepts with Scaleway. Understand how to organize, allocate, and manage IP resources efficiently in your cloud infrastructure.
+tags: ipam ip-address-management internet-protocol private-ip public-ip flexible-ip list-ips book-ip
+dates:
+ validation: 2024-12-03
+categories:
+ - networks
+---
+
+## CIDR notation
+
+When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses.
+
+## IPAM
+
+**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources.
+
+The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging, and filtering all your [private IP addresses](#private-ip-address). You can also [reserve](/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer, Public Gateway, or Elastic Metal server to the network.
+
+More functionality is planned for the future, including:
+
+- Support for attaching Managed Databases and other resources to a Private Network using a reserved IP address
+- Management of public (flexible) IP addresses
+
+## IPv4
+
+Internet Protocol Version 4 is the standard protocol used for IP addresses, and routes most internet traffic as of today. Each IPv4 address has 32 bits. Written in human-readable form, an IPv4 address is generally shown as four octets separated by periods, e.g. `151.115.59.87`.
+
+Scaleway resources may have a [public](#public-flexible-ip-address) IPv4 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv4 address for each Private Network they are attached to.
+
+## IPv6
+
+Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`.
+
+IPv6-compatible Scaleway resources may have a [public](#public-flexible-ip-address) IPv6 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv6 address for each Private Network they are attached to. [Find out more about IPv6 in the Scaleway ecosystem](/ipam/reference-content/ipv6/).
+
+## Private IP address
+
+Private IP addresses identify devices on Private Networks. They are not routed on the public internet, and can be used to route traffic privately between resources attached to the Private Network, as well as to [other Private Networks in the same VPC](/vpc/concepts/#routing).
+
+When you attach a resource to a Private Network, you can either specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use for the attachment, or let the Private Network's [DHCP](/vpc/concepts/#dhcp) assign it a private [IPv4](#ipv4) address from the Private Network's [CIDR](/vpc/concepts/#cidr-block) block. In both cases, the resource's private IP address will not change unless you detach the resource from the Private Network, or delete the resource. [IPv6](#ipv6) addresses can also be assigned for IPv6-compatible resources.
+
+Four IP addresses from each CIDR block are unavailable for reservation/use: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.256`.
+
+## Public (flexible) IP address
+
+Public IP addresses identify devices on the public internet. You can enter the public IP address of an Instance into any browser connected to the Internet, and access content being served from that Instance.
+
+Depending on the type of resource and its configuration, it may or may not have a public IP address. For example, you can choose to give an [Instance](/instances/) one or more public IP addresses ([IPv4](#ipv4) and/or IPv6), or alternatively, no public IP address at all. Find out more about managing public connectivity in our [best practices guide](/ipam/reference-content/public-connectivity-best-practices/).
+
+Public IP addresses at Scaleway are often called flexible IP addresses, because you can move them between different resources. However, flexible IP addresses are scoped to a single product and to a single Availability Zone. If you create a flexible IP address for an Instance in `PAR-2`, you can move it to a different Instance in `PAR-2`, but not to an Instance in `PAR-1`, nor to an Elastic Metal server in any AZ.
+
+## Reserved IP address
+
+A reserved IP address is a private IP address from the [CIDR block](/vpc/concepts/#cidr-block) of a given Private Network, that you have [reserved via IPAM](/ipam/how-to/reserve-ip/). Reserving an IP means that it can no longer be auto-allocated by DHCP to resources that join the network. You can then use the reserved IP to attach a specified resource of your choice to the Private Network. After you detach the resource, the IP remains reserved, and you can either use it to attach a different resource, or release it back into the pool of generally available IPs.
\ No newline at end of file
diff --git a/pages/ipam/how-to/assets/scaleway-ipam-moreinfo.webp b/pages/ipam/how-to/assets/scaleway-ipam-moreinfo.webp
new file mode 100644
index 0000000000..2b88ae87f4
Binary files /dev/null and b/pages/ipam/how-to/assets/scaleway-ipam-moreinfo.webp differ
diff --git a/pages/ipam/how-to/assets/scaleway-reserve-ip.webp b/pages/ipam/how-to/assets/scaleway-reserve-ip.webp
new file mode 100644
index 0000000000..c83b443fab
Binary files /dev/null and b/pages/ipam/how-to/assets/scaleway-reserve-ip.webp differ
diff --git a/pages/ipam/how-to/index.mdx b/pages/ipam/how-to/index.mdx
new file mode 100644
index 0000000000..2ea19d8f85
--- /dev/null
+++ b/pages/ipam/how-to/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: IPAM - How Tos
+ description: IPAM How Tos
+content:
+ h1: IPAM - How Tos
+ paragraph: IPAM How Tos
+---
diff --git a/pages/ipam/how-to/list-ips.mdx b/pages/ipam/how-to/list-ips.mdx
new file mode 100644
index 0000000000..80f0f01941
--- /dev/null
+++ b/pages/ipam/how-to/list-ips.mdx
@@ -0,0 +1,45 @@
+---
+meta:
+ title: How to list your private IP addresses
+ description: This page explains how to list your private IP addresses with Scaleway's IPAM
+content:
+ h1: How to list your private IP addresses
+ paragraph: This page explains how to list your private IP addresses with Scaleway's IPAM
+tags: ipam ip-address-manager private-ip-address ip-address ip filter reserve-ip-address
+dates:
+ validation: 2024-09-06
+ posted: 2024-05-30
+categories:
+ - network
+---
+
+**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources.
+
+[Read more about IPAM and future planned functionality](/ipam/concepts/#ipam).
+
+You can currently use IPAM in the Scaleway console to manage the IP address space of your Scaleway Private Networks. This document shows you how to list the [private IP addresses](/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks.
+
+
+
+- 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
+- At least one resource [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/).
+
+## How to list and filter your private IP addresses
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+ A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM. This means either:
+
+ - You manually reserved an address via IPAM (currently only possible via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or
+ - You [attached a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network.
+
+ The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/vpc/concepts/#cidr-block) do not display in the list.
+
+
+ When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses.
+
+
+2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/ipam/concepts/#ipv4) or [IPv6](/ipam/concepts/#ipv6) addresses:
+
+3. Click **Apply filters** to activate the filters you chose, or **Reset** to reset all filters.
diff --git a/pages/ipam/how-to/manage-ips.mdx b/pages/ipam/how-to/manage-ips.mdx
new file mode 100644
index 0000000000..85878c4830
--- /dev/null
+++ b/pages/ipam/how-to/manage-ips.mdx
@@ -0,0 +1,63 @@
+---
+meta:
+ title: How to manage your private IP addresses
+ description: This page explains how to manage your private IP addresses with Scaleway's IPAM
+content:
+ h1: How to manage your private IP addresses
+ paragraph: This page explains how to manage your private IP addresses with Scaleway's IPAM
+tags: ipam ip-address-manager private-ip-address ip-address ip tags manage edit
+dates:
+ validation: 2024-09-06
+ posted: 2024-05-30
+categories:
+ - network
+---
+
+IPAM acts as a single source of truth for the IP addresses of your Scaleway resources. You can use IPAM in the console Scaleway console to manage [private IP addresses](/ipam/concepts/#private-ip-address) that are either attached to one of your resources on a Private Network, or [reserved via the IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip).
+
+The management actions currently available include:
+- Viewing the details of a private IP address, including its ID, tags, creation date and to which resource (if any) it is attached
+- Editing the tags of a private IP address
+
+Learn [how to reserve a private IP address](/ipam/how-to/reserve-ip/).
+
+
+
+- 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
+- At least one resource [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/).
+
+## How to view the details of a private IP address
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+ A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/vpc/how-to/attach-resources-to-pn/).
+
+2. Modify the filters of the list using the drop-down menus at the top if necessary to display the required IP address.
+
+3. Click the icon next to the IP address whose details you want to view, then click **More info**.
+
+ A screen similar to the following displays:
+
+
+
+ You can view the following information:
+ - The IP address
+ - The **region** of the IP address
+ - Which **resource** (if any) it is attached to
+ - The **ID** of the IP address
+ - The date on which the IP was **created**. This corresponds to the date it was reserved in IPAM, either via a manual [API reservation](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip) or when it was attached to a resource on a Private Network.
+ - The date on which the IP was last **updated**
+ - The **tags** associated with the IP address.
+
+4. Click **OK** to exit the screen.
+
+## How to edit the tags of a private IP address
+
+Tags help you organize your IPAM IP addresses. You can assign as many tags as you want to each reserved IP, and use them for identification and sorting purposes.
+
+1. Follow steps 1 to 3 [above](#how-to-view-the-details-of-a-private-ip-address).
+
+2. Click into the **Tags** box, and type the tag(s) you want to add. Alternatively, click the **x** symbol to remove any existing tags.
+
+3. Click **OK** to exit the screen.
diff --git a/pages/ipam/how-to/reserve-ip.mdx b/pages/ipam/how-to/reserve-ip.mdx
new file mode 100644
index 0000000000..2a9aeea07f
--- /dev/null
+++ b/pages/ipam/how-to/reserve-ip.mdx
@@ -0,0 +1,111 @@
+---
+meta:
+ title: How to reserve an IP address
+ description: Learn how to reserve IP addresses with Scaleway's IPAM. This step-by-step guide helps you easily manage and allocate IPs for future use when attaching resources to your Private Network, ensuring efficient network configuration.
+content:
+ h1: How to reserve an IP address
+ paragraph: Learn how to reserve IP addresses with Scaleway's IPAM. This step-by-step guide helps you easily manage and allocate IPs for future use when attaching resources to your Private Network, ensuring efficient network configuration.
+tags: ipam ip-address-manager private-ip-address ip-address reserve static
+dates:
+ validation: 2024-09-05
+ posted: 2024-09-05
+categories:
+ - network
+---
+
+**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources.
+
+You can use IPAM to reserve a private IP address from a given Private Network's [CIDR block](/vpc/concepts/#cidr-block). When you reserve an IP in this way, it stops it from being potentially auto-allocated to new resources being attached to the Private Network. You can then use the reserved address to attach the specific resource of your choice to the Private Network. If you later detach the resource from the network, the reserved IP will stay reserved, until you either release it back into the general pool, or use it to attach a different resource.
+
+
+Currently, only **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases will be coming soon.
+
+
+This page sets out the steps necessary to reserve an IP address with IPAM.
+
+
+
+- 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
+- At least one [Private Network](/vpc/how-to/create-private-network/)
+
+## How to reserve a private IP address
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+2. Click **Reserve private IP**. The following screen displays:
+
+
+
+3. Define the parameters for the private IP address you want to reserve:
+ - **IP type**: IPv4 or IPv6
+ - **Tags**: Tags to help you filter and manage your reserved IPs later
+ - **Region**: The region in which you want to reserve a private IP address
+ - **VPC**: The VPC in which you want to reserve a private IP address
+ - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/vpc/concepts/), and available to attach resources to this network.
+
+4. Define whether you want to specify the IP address to reserve, or reserve any available IP on the Private Network (the IP selected will be displayed after reservation). If specifying the IP address yourself, do **not** include the network prefix (e.g. `/22`).
+
+
+ Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.256`.
+
+
+5. Define whether you want to attach a MAC address to the reserved IP. **Only do this for custom resources** e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server.
+
+
+ Do **not** attach a MAC address for reserved IPs you want to use with standard Scaleway resources such as Instances, Load Balancers or Elastic Metal servers themselves.
+
+
+ For more help with attaching MAC addresses, [see below](#how-to-reserve-a-private-ip-address-with-an-attached-mac-address).
+
+6. Click **Reserve** to reserve the IP.
+
+ The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](#how-to-release-a-reserved-private-ip-address) it.
+
+## How to reserve a private IP address with an attached MAC address
+
+When you reserve a private IP, you have the option to attach a MAC address to it. This allows you to use the IP with a custom resource e.g. virtual machines hosted on a Proxmox cluster on an Elastic Metal server. This functionality marks the final stage of replacing the now-deprecated static DHCP reservations via the Public Gateway.
+
+It is only possible to attach a MAC address during the IP reservation. You cannot edit an existing reserved IP to attach a MAC address.
+
+1. Follow the steps above to [reserve a private IP](#how-to-reserve-a-private-ip-address), and at step 5, check the box to attach a MAC address.
+
+2. Enter the MAC address of the custom resource you want to attach, e.g. `00:1B:44:11:3A:B7`.
+
+3. Enter the name of the resource. This will be used for DNS resolution on the Private Network.
+
+4. Click **Reserve**.
+
+ The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays.
+
+ If you later attach this reserved IP address to a standard Scaleway resource e.g. an Instance, the attached MAC address and resource name will be erased.
+
+## How to attach a resource to a Private Network using a reserved IP address
+
+You can currently attach **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** to Private Networks using a reserved IP address. Support for Managed Databases will be coming soon.
+
+The option to use a reserved IP displays when you attach the resource to a Private Network in the console. Follow the instructions below:
+
+- Attach a resource to a Private Network from the [Private Networks](/vpc/how-to/attach-resources-to-pn/) product dashboard
+- Attach an Instance to a Private Network from the [Instances](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) product dashboard
+- Attach an Elastic Metal server to a Private Network from the [Elastic Metal](/elastic-metal/how-to/use-private-networks/) product dashboard
+- Attach a Load Balancer to a Private Network from the [Load Balancer](/load-balancer/how-to/use-with-private-network/) product dashboard
+- Attach a Public Gateway to a Private Network from the [Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) product dashboard
+
+## How to release a reserved private IP address
+
+You can release a reserved IP address, as long as it is not attached to a resource. Releasing the IP means it goes back into the general pool of available IP addresses for that Private Network, and could potentially be auto-allocated to a new resource joining the network.
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+2. Click the three dot menu next to the IP you want to release, and then click **Release IP**.
+
+
+ Only reserved IPs that are not attached to a resource can be released.
+
+
+ A message displays asking you to confirm you want to release the IP address.
+
+3. Click **Confirm**.
+
+ The IP address is released.
\ No newline at end of file
diff --git a/pages/ipam/index.mdx b/pages/ipam/index.mdx
new file mode 100644
index 0000000000..3c57dde83f
--- /dev/null
+++ b/pages/ipam/index.mdx
@@ -0,0 +1,68 @@
+---
+meta:
+ title: IPAM Documentation
+ description: Dive into Scaleway IPAM with our quickstart guides, how-tos, tutorials and more.
+---
+
+
+ Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment, with our [new guide](/ipam/reference-content/public-connectivity-best-practices/). Learn how to enhance performance and ensure robust protection.
+
+
+
+
+## Getting Started
+
+
+
+
+
+
+
+
+
+
+## Changelog
+
+
\ No newline at end of file
diff --git a/pages/ipam/quickstart.mdx b/pages/ipam/quickstart.mdx
new file mode 100644
index 0000000000..a6f26ba56f
--- /dev/null
+++ b/pages/ipam/quickstart.mdx
@@ -0,0 +1,83 @@
+---
+meta:
+ title: IPAM - Quickstart
+ description: This page shows you how to get started with Scaleway IPAM.
+content:
+ h1: IPAM - Quickstart
+ paragraph: This page shows you how to get started with Scaleway IPAM.
+tags: ipam ip-address-management internet-protocol private-ip public-ip flexible-ip list-ips book-ip
+dates:
+ validation: 2024-09-06
+ posted: 2021-05-30
+categories:
+ - network
+---
+
+**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources.
+
+[Read more about IPAM and its current and future planned functionality](/ipam/concepts/#ipam).
+
+You can currently use IPAM in the Scaleway console to list the [private IP addresses](/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks, and view/edit their additional information. You can also [reserve](/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network.
+
+## How to list and filter your private IP addresses
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+ A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM. This means either:
+
+ - You manually reserved an address via IPAM (currently only possible via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or
+ - You [attached a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network.
+
+ The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/vpc/concepts/#cidr-block) do not display in the list.
+
+2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/ipam/concepts/#ipv4) or [IPv6](/ipam/concepts/#ipv6) addresses:
+
+3. Click **Apply filters** to activate the filters you chose, or **Reset** to reset all filters.
+
+## How to view and edit the details of a private IP address
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+ A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/vpc/how-to/attach-resources-to-pn/).
+
+2. Modify the filters of the list using the drop-down menus at the top if necessary to display the required IP address.
+
+3. Click the icon next to the IP address whose details you want to view, then click **More info**.
+
+ A screen similar to the following displays:
+
+
+
+ You can view the following information:
+ - The IP address
+ - The **region** of the IP address
+ - Which **resource** (if any) it is attached to
+ - The **ID** of the IP address
+ - The date on which the IP was **created**. This corresponds to the date it was reserved in IPAM, either via a manual [API reservation](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip) or when it was attached to a resource on a Private Network.
+ - The date on which the IP was last **updated**
+ - The **tags** associated with the IP address. You can edit these tags if you wish.
+
+4. Click **OK** to exit the screen.
+
+## How to reserve a private IP address
+
+1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu.
+
+2. Click **Reserve private IP**. The following screen displays:
+
+
+
+3. Define the parameters for the private IP address you want to reserve:
+ - **IP type**: IPv4 or IPv6
+ - **Tags**: Tags to help you filter and manage your reserved IPs later
+ - **Region**: The region in which you want to reserve a private IP address
+ - **VPC**: The VPC in which you want to reserve a private IP address
+ - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/vpc/concepts/), and available to attach resources to this network.
+
+4. Define whether you want to specify the IP address to reserve, or reserve any available IP on the Private Network (the IP selected will be displayed after reservation). If specifying the IP address yourself, do **not** include the network prefix (e.g. `/22`).
+
+
+ Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.256`.
+
+
+ The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address) it.
\ No newline at end of file
diff --git a/pages/ipam/reference-content/index.mdx b/pages/ipam/reference-content/index.mdx
new file mode 100644
index 0000000000..55c52f78b1
--- /dev/null
+++ b/pages/ipam/reference-content/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: IPAM - Additional content
+ description: IPAM additional content
+content:
+ h1: IPAM - Additional content
+ paragraph: IPAM additional content
+---
diff --git a/pages/ipam/reference-content/ipv6.mdx b/pages/ipam/reference-content/ipv6.mdx
new file mode 100644
index 0000000000..295952d7d9
--- /dev/null
+++ b/pages/ipam/reference-content/ipv6.mdx
@@ -0,0 +1,140 @@
+---
+meta:
+ title: IPv6 and the Scaleway ecosystem
+ description: Learn about IPv6 at Scaleway - configuration, routing, security, and best practices for seamless integration and scalability. Transition smoothly with our step-by-step guide.
+content:
+ h1: IPv6 and the Scaleway ecosystem
+ paragraph: Learn about IPv6 at Scaleway - configuration, routing, security, and best practices for seamless integration and scalability. Transition smoothly with our step-by-step guide.
+tags: ipv6 ipv4 support
+dates:
+ validation: 2024-11-18
+ posted: 2024-11-18
+categories:
+ - network
+---
+
+IPv6 is increasingly important, as the world transitions to a more connected, secure and scalable internet. While IPv4 still reigns supreme in terms of volume of usage, IPv6 adoption is steadily increasing, with tech giants and ISPs in particular pushing for more widespread IPv6 uptake and integration.
+
+Read on to find out more about IPv6, how it is supported at Scaleway, and how you can configure your resources and infrastructure to take full advantage of this modern protocol.
+
+## What is IPv6?
+
+**IP**, or **Internet Protocol** enables machines to locate and communicate with each other on networks like the Internet or private subnets, by assigning each connected machine a unique IP address. An IP address is a set of numbers to identify the machine on the network.
+
+The most commonly recognized and most widely-used IP version is **IPv4**, launched in 1983. Each IPv4 address has 32 bits. Written in human-readable form, an IPv4 address is generally shown as four octets separated by periods, e.g. `151.115.59.87`. However, with the growing number of machines connected to the Internet, the world is literally running out of unique IPv4 addresses - only 4.3 billion unique addresses of this format are possible.
+
+This is where **IPv6** comes in, the most recent version of the IP protocol. Each IPv6 address has 128 bits, meaning a potential pool of 3.4 x 1038 unique IPv6 addresses - you could assign a trillion unique IPv6 addresses to every atom in a human body and still have addresses left over.
+
+Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`.
+
+As well as providing a much bigger address space, IPv6 also includes a built-in network security layer (IPsec), as well as improved features for reliability and efficiency, like autoconfiguration, streamlined headers and improved Quality of Service (QoS). All leading to a more robust and secure protocol, that can potentially offer lower latency and faster data transfer.
+
+## IPv6-compatible products
+
+The following products support IPv6:
+
+### Instances and IPv6
+
+Scaleway Instances are compatible with IPv6, with the caveat that the Instance must be using [routed IPs](/instances/concepts/#routed-flexible-ip).
+
+#### Public IPv6
+
+You can attach one or multiple public (flexible) IPv6 addresses to your Instance, as well as, or instead of, a public IPv4 address. These public addresses are flexible, meaning that you can detach them from an Instance, hold them in your account, and attach them to a different Instance later, if you want. Each flexible IPv6 address is a `/64` IPv6 subnet.
+
+#### Private IPv6
+
+When you attach an Instance to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use.
+
+#### Going further
+
+Go further with Instances and IPv6 in the following documentation:
+
+- [How to use flexible IPs](/instances/how-to/use-flexips/)
+- [Compatibility between OS images and different flexible IP type combinations](/instances/reference-content/comaptibility-scw-os-images-flexible-ip/)
+- [Using routed IPs](/instances/api-cli/using-routed-ips/)
+- Fix lost IPv6 connectivity when migrating to routed IP for old [Debian Buster images](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/) or [RHEL images](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/)
+- [Fix DNS resolution with a routed IPv6-only setup on Debian Bullseye](/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye/)
+
+### Elastic Metal and IPv6
+
+Scaleway Elastic Metal servers are compatible with IPv6.
+
+#### Public IPv6
+
+You can attach one or multiple public (flexible) IPv6 addresses to your Elastic Metal server, as well as, or instead of, a public IPv4 address. These public addresses are flexible, meaning that you can detach them from an Elastic Metal server, hold them in your account, and attach them to a different Elastic Metal server, if you want. Each flexible IPv6 address is a `/64` IPv6 subnet. Flexible IPv6 addresses can also be used as additional IP addresses to create virtual machines on your Elastic Metal server.
+
+
+In addition to the possibility of attaching and detaching flexible IP addresses, note that each Elastic Metal server also comes with a statically routed public IPv4 address, which cannot be detached, other than manually.
+
+
+#### Private IPv6
+
+When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use.
+
+You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses.
+
+#### Going further
+
+Go further with Elastic Metal and IPv6 in the following documentation:
+- [How to order a flexible IP](/elastic-metal/how-to/order-flexible-ip/)
+- [How to attach/detach a flexible IP](/elastic-metal/how-to/attach-detach-flexible-ip/)
+- [How to configure a flexible IPv6 address on your Elastic Metal server](/elastic-metal/how-to/configure-flexible-ipv6/)
+- [How to configure a flexible IPv6 address on a virtual Proxmox machine](/elastic-metal/how-to/configure-ipv6-hypervisor/)
+- [How to configure the network interface on your server for Private Networks](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks)
+
+### Dedibox and IPv6
+
+The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server’s primary IP and also as a failover IP utilizing the concept of a virtual MAC address.
+
+Full information on IPv6 with Dedibox can be found in our [dedicated documentation](/dedibox-ipv6/), or you can read more in our [blog post](https://www.scaleway.com/en/blog/ipv6-the-future-proof-internet-protocol/#ipv6-at-scaleway-dedibox).
+
+### Load Balancer and IPv6
+
+Scaleway Load Balancers are compatible with IPv6.
+
+#### Public IPv6
+
+You can attach a maximum of one (flexible) IPv6 address to your Load Balancer, in addition to a flexible IPv4 address. The Load Balancer cannot have **only** an IPv6 address. Once attached, the IPv6 address cannot be detached or changed for a different one. Each flexible IPv6 address is a `/64` IPv6 subnet.
+
+#### Private IPv6
+
+When you attach a Load Balancer to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use.
+
+#### IPv6 at the backend
+
+Load Balancers can also use IPv6 to communicate with their backend servers. When you attach backend servers to a Load Balancer, you can either specify their public IPv6 address, or their private IPv6 address (if the Load Balancer and the backend servers are attached to the same Private Network).
+
+#### Going further
+
+Go further with IPv6 and Load Balancers with the following documentation:
+- [How to create and manage flexible IPs](/load-balancer/how-to/create-manage-flex-ips/)
+
+### VPC, Private Networks and IPv6
+
+VPC and Private Networks are compatible with IPv6.
+
+- Private Networks are dual-stack, meaning each Private Network necessarily has both an IPv4 and and an IPv6 CIDR blocks.
+- For IPv6, this is a `/64` block, automatically created by Scaleway, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks.
+- All IPv6-compatible resources will automatically receive an IPv6 address when they join a Private Network, in addition to an IPv4 address.
+- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/ipam/how-to/reserve-ip/)
+- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPV4 and IPV6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process.
+
+### Serverless Functions and Containers and IPv6
+
+Serverless Functions and Containers are compatible with public IPv6 traffic. A function or container endpoint resolves to both IPv4 and IPv6 addresses (dual stack), ensuring compatibility for clients using either protocol.
+
+## Other products and IPv6
+
+Products other than those listed here do not officially support IPv6. These non-compatible products include Managed Databases, Kubernetes Kapsule and Public Gateways.
+
+Please open or upvote a [feature request](https://feature-request.scaleway.com/) to register your interest in IPv6 for these resources.
+
+Alternatively, get in touch on the [Scaleway Slack Community](/tutorials/scaleway-slack-community/) to find out more about IPv6 compatibility of these or other products.
+
+## IPv6 best practices
+
+**Only expose a public IPv6 address when necessary**: Adding both IPv4 and IPv6 public addresses to your resource expands the potential attack surface, particularly in terms of the large address space of IPv6. As stated in our [dedicated documentation](/ipam/reference-content/public-connectivity-best-practices/), you should favor connectivity over Private Networks, and detach public IP addresses from resources unless strictly necessary.
+
+**Audit DNS and address exposure**: Regularly audit the DNS records and public IPv6 addresses associated with your resources to minimize exposure.
+
+**Implement IPv6-specific security measures**: Features such as [security groups](/instances/concepts/#security-group) for Instances and [ACLs](/load-balancer/concepts/#acl) for Load Balancers allow you to filter traffic based on both IPv4 and IPv6 addresses. Ensure that such security measures are equally robust for both protocols.
\ No newline at end of file
diff --git a/pages/ipam/reference-content/public-connectivity-best-practices.mdx b/pages/ipam/reference-content/public-connectivity-best-practices.mdx
new file mode 100644
index 0000000000..b15bffe9e3
--- /dev/null
+++ b/pages/ipam/reference-content/public-connectivity-best-practices.mdx
@@ -0,0 +1,117 @@
+---
+meta:
+ title: Public connectivity - best practices
+ description: Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment. Learn how to enhance performance and ensure robust protection.
+content:
+ h1: Public connectivity - best practices
+ paragraph: Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment. Learn how to enhance performance and ensure robust protection.
+tags: flexible-ip public-ip private-network connectivity best-practice
+dates:
+ validation: 2024-09-30
+ posted: 2024-09-30
+categories:
+ - network
+---
+
+This document sets out best practices for securing and optimizing public connectivity for your Scaleway resources.
+
+## Public vs private connectivity
+
+Public vs private connectivity defines how resources are accessed and exposed over networks.
+
+- **Public connectivity**: Your resource has a [public IP address](/ipam/concepts/#public-flexible-ip-address) and is reachable over the public internet. Anyone with the right credentials can access the resource via its public IP address, e.g. over an [SSH connection](/instances/how-to/connect-to-instance/) or simply by directly accessing its IP address in a browser to retrieve and display any content it is serving, e.g. over HTTP.
+- **Private connectivity**: Your resources is reachable over an attached [Private Network](/vpc/concepts/#private-networks). The resource has a [private IP address](/vpc/concepts/#private-ip-address), but it can only be accessed via this address from within the VPC of the Private Network. Such a resource may or may not also have a public IP address.
+
+## Effectively managing IP addresses
+
+### Flexible IP addresses: definition
+
+Public connectivity for **Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/concepts/#public-flexible-ip-address).
+
+- A flexible IP address is a public IP address that you can attach and detach from the resource at will.
+- If you detach it, it returns to the pool of flexible IP addresses kept in your account for that product, and you can attach it to a different resource (or reattach it to the same one as before).
+- Flexible IP addresses are scoped to a single product and a single Availability Zone (AZ). If you create a flexible IP address for an Instance in PAR-2, you can move it to a different Instance in PAR-2, but not to an Instance in PAR-1, nor to an Elastic Metal server in any AZ.
+
+Other resource types generally facilitate public connectivity in other ways, e.g. via public endpoints that cannot be modified by the user. Public connectivity may be mandatory with no option to deactivate (e.g. for Apple Silicon), or optional (e.g. for Managed Database). See the specific documentation for the product in question to find out more.
+
+### Exploiting the benefits of flexible IPs
+
+As flexible IP addresses can be moved between resources, they provide the following advantages:
+
+- **Seamless failover and disaster recovery**: If your Instance, for example, goes down, you can move its public IP to a different Instance in the same AZ to ensure the service remains available.
+- **Zero downtime during maintenance and migration**: When you need to carry out updates, migrations or maintenance on a resource, you can temporarily move its public IP to a backup resource to avoid disruption for users.
+- **IP retention and consistent endpoints**: Maintaining the same IP avoids the need for frequent DNS or firewall rule updates, and makes it easier to manage your dynamic cloud environments.
+
+In the future, look out for even more improvements to our flexible IP offering, such as the ability to move flexible IPs between different types of products, and to manage all your public flexible IPs from your [IPAM](/ipam/) dashboard.
+
+### Limiting public connectivity, prioritizing Private Networks
+
+We strongly recommend that you disable public connectivity on all of your Scaleway resources, unless it is absolutely required. Attaching resources to Private Networks, and limiting their communication to these networks brings the following advantages:
+
+- **Minimized attack surface**: Without a public IP address, the resource is not exposed directly to the internet, decreasing the risk of DDoS or brute force attacks, or unauthorized access.
+- **Reduced cost**: Public (flexible) IP addresses are [billed](https://www.scaleway.com/en/pricing/), whereas Private Networks and the private IP addresses that attach resources to Private Networks are free of charge (except for Elastic Metal servers).
+- **Improved latency**: Communication between resources over a Private Network is generally faster, as it does not need to be routed through the public internet.
+
+Depending on the resource type, public connectivity can be disabled by:
+- Toggling off **Public connectivity** when creating the resource
+- Detaching an existing flexible IP address (after resource creation)
+- Deactivating public connectivity (after resource creation)
+
+
+For some products, e.g. Apple Silicon, public connectivity cannot be disabled at any stage, and for other resources, eg Managed Databases for Redis, public connectivity options cannot be modified after resource creation. Check the documentation for your specific product to learn more.
+
+
+Favor resources such as Public Gateways and Load Balancers to provide access to the public internet over the Private Network. This allows Instances and other attached resources to send and receive packets to the internet through a single, secure point of access. You can use the Public Gateway's SSH bastion feature to [connect to your resource via its private IP address](/public-gateways/how-to/use-ssh-bastion/#how-to-connect-to-a-resource-behind-your-ssh-bastion).
+
+Find out more about how to get the most from Private Network in our [dedicated documentation](/vpc/reference-content/getting-most-private-networks/)
+
+## Implementing security controls
+
+Different products offer different security features and controls to help place limits and restrictions on the traffic arriving over your resource's public interface. We strongly recommend that you implement all available measures to minimize security risk and optimize the security of your resource. Some of the available security controls are listed below.
+
+### Instances: Security groups
+
+[Security groups](/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow public traffic to and from your Instance. [Find out how to create and configure security groups](/instances/how-to/use-security-groups/).
+
+### Load Balancers: ACLs
+
+
+
+Learn how to use the ACL feature in our [dedicated how-to](/load-balancer/how-to/create-manage-acls/) and go deeper with our [reference documentation](/load-balancer/reference-content/acls/).
+
+### Other controls
+
+For resources such as Instances and Elastic Metal servers, you may wish to implement third-party manual solutions in front of your public services to enhance security, for example:
+
+- Deploying a reverse proxy, e.g. Nginx (/tutorials/nginx-reverse-proxy/), and configuring it to enforce rate limits and to throttle traffic. This helps to prevent abuse and DDOS attacks on your public-facing services.
+- Installing a **W**eb **A**pplication **F**irewall that can filter out malicious traffic such as requests containing attack patterns, or requests from blacklisted IPs.
+
+## Handling traffic surges
+
+Exposing your resource to the public internet can present risks of unexpected traffic surges. These may be malicious DDoS attacks, or legitimate surges that are simply the result of high demand. If correct mechanisms are not put in place to deal with high load, you risk facing downtime, service unavailability and performance degradation. A number of possibilities exist to help you handle this scenario:
+
+### Autoscaling
+
+Scaleway currently offers Autoscaling in Public Beta. Autoscaling allows you to dynamically adjust the number of Instances within a given Instance group based on defined scaling policies. Scaling actions (scale up or down) are triggered when the monitored metric exceeds the configured thresholds from your policies. Check out the [API documentation](https://www.scaleway.com/en/developers/api/autoscaling/).
+
+### Load Balancer
+
+Placing a Scaleway Load Balancer in front of your backend servers allows you to expose multiple Instances through a single public IP. The Load Balancer distributes workload across the servers in the backend pool, ensurable scalable and continuously available applications, even during heavy traffic. You can manually add and remove servers from the backend pool as necessary, and configure the best balancing method for your particular needs. Find out more in the [Load Balancer documentation](/load-balancer/).
+
+### Edge Services
+
+Available for Load Balancers and Object Storage buckets, Scaleway Edge Services provides a caching service to reduce load on your origin. This means that content can be served directly to users from Edge Services' servers, instead of from your Load Balancer or Object Storage bucket. [Learn more about Edge Services](/edge-services/).
+
+### Kubernetes Kapsule
+
+Hosting your containerized application in a managed Kubernetes cluster brings many benefits in terms of scaling and managing fluctuating demand. Kubernetes can automatically adjust the number of running resources within defined limits, based on current demand. It also offers self-healing capabilities in the case of node failure. Find out more in the [Scaleway Kubernetes](/kubernetes/) documentation.
+
+## Monitoring and alerting via Scaleway Cockpit
+
+We recommend that you use [Scaleway Cockpit](/cockpit/) to monitor your resources. Cockpit stores metrics, logs and traces and provides a dedicated dashboarding system on Grafana for easy visualisation. Different metrics are available for different resource types, with metrics for network traffic being available for many, enabling you to monitor connections over the public interface. You can also configure managed and pre-configured alerts for your resources, to receive warnings for potentially abnormal behavior or unusual network activity.
+
+Read more about [Scaleway Cockpit](/cockpit/).
+
+
+
+
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_deploy_ingress.webp b/pages/kubernetes/api-cli/assets/scaleway_deploy_ingress.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_deploy_ingress.webp
rename to pages/kubernetes/api-cli/assets/scaleway_deploy_ingress.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_dash_datasource.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_dash_datasource.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_dash_datasource.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_dash_datasource.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_dashboard.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_dashboard.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_dashboard.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_dashboard.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_datasource.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_datasource.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_datasource.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_datasource.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_home.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_home.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_home.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_home.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_import.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_import.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_import.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_import.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_grafana_login.webp b/pages/kubernetes/api-cli/assets/scaleway_grafana_login.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_grafana_login.webp
rename to pages/kubernetes/api-cli/assets/scaleway_grafana_login.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_loki1.webp b/pages/kubernetes/api-cli/assets/scaleway_loki1.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_loki1.webp
rename to pages/kubernetes/api-cli/assets/scaleway_loki1.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_loki2.webp b/pages/kubernetes/api-cli/assets/scaleway_loki2.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_loki2.webp
rename to pages/kubernetes/api-cli/assets/scaleway_loki2.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_loki3.webp b/pages/kubernetes/api-cli/assets/scaleway_loki3.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_loki3.webp
rename to pages/kubernetes/api-cli/assets/scaleway_loki3.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_monito3.webp b/pages/kubernetes/api-cli/assets/scaleway_monito3.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_monito3.webp
rename to pages/kubernetes/api-cli/assets/scaleway_monito3.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_prom2.webp b/pages/kubernetes/api-cli/assets/scaleway_prom2.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_prom2.webp
rename to pages/kubernetes/api-cli/assets/scaleway_prom2.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_prom3.webp b/pages/kubernetes/api-cli/assets/scaleway_prom3.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_prom3.webp
rename to pages/kubernetes/api-cli/assets/scaleway_prom3.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_prom4.webp b/pages/kubernetes/api-cli/assets/scaleway_prom4.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_prom4.webp
rename to pages/kubernetes/api-cli/assets/scaleway_prom4.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_prom5.webp b/pages/kubernetes/api-cli/assets/scaleway_prom5.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_prom5.webp
rename to pages/kubernetes/api-cli/assets/scaleway_prom5.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_prom_dashboard.webp b/pages/kubernetes/api-cli/assets/scaleway_prom_dashboard.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_prom_dashboard.webp
rename to pages/kubernetes/api-cli/assets/scaleway_prom_dashboard.webp
diff --git a/pages/containers/kubernetes/api-cli/assets/scaleway_traefik_wildcard.webp b/pages/kubernetes/api-cli/assets/scaleway_traefik_wildcard.webp
similarity index 100%
rename from pages/containers/kubernetes/api-cli/assets/scaleway_traefik_wildcard.webp
rename to pages/kubernetes/api-cli/assets/scaleway_traefik_wildcard.webp
diff --git a/pages/containers/kubernetes/api-cli/changing-control-plane-offer.mdx b/pages/kubernetes/api-cli/changing-control-plane-offer.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/changing-control-plane-offer.mdx
rename to pages/kubernetes/api-cli/changing-control-plane-offer.mdx
diff --git a/pages/containers/kubernetes/api-cli/cluster-monitoring.mdx b/pages/kubernetes/api-cli/cluster-monitoring.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/cluster-monitoring.mdx
rename to pages/kubernetes/api-cli/cluster-monitoring.mdx
diff --git a/pages/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx b/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx
rename to pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx
diff --git a/pages/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx b/pages/kubernetes/api-cli/external-secrets-kubernetes.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx
rename to pages/kubernetes/api-cli/external-secrets-kubernetes.mdx
diff --git a/pages/containers/kubernetes/api-cli/index.mdx b/pages/kubernetes/api-cli/index.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/index.mdx
rename to pages/kubernetes/api-cli/index.mdx
diff --git a/pages/containers/kubernetes/api-cli/managing-storage.mdx b/pages/kubernetes/api-cli/managing-storage.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/managing-storage.mdx
rename to pages/kubernetes/api-cli/managing-storage.mdx
diff --git a/pages/containers/kubernetes/api-cli/managing-tags.mdx b/pages/kubernetes/api-cli/managing-tags.mdx
similarity index 100%
rename from pages/containers/kubernetes/api-cli/managing-tags.mdx
rename to pages/kubernetes/api-cli/managing-tags.mdx
diff --git a/pages/containers/kubernetes/assets/DecisionTreeKubernetes-DocumentationWebsite.webp b/pages/kubernetes/assets/DecisionTreeKubernetes-DocumentationWebsite.webp
similarity index 100%
rename from pages/containers/kubernetes/assets/DecisionTreeKubernetes-DocumentationWebsite.webp
rename to pages/kubernetes/assets/DecisionTreeKubernetes-DocumentationWebsite.webp
diff --git a/pages/containers/kubernetes/assets/decision-tree-kubernetes.pdf b/pages/kubernetes/assets/decision-tree-kubernetes.pdf
similarity index 100%
rename from pages/containers/kubernetes/assets/decision-tree-kubernetes.pdf
rename to pages/kubernetes/assets/decision-tree-kubernetes.pdf
diff --git a/pages/containers/kubernetes/concepts.mdx b/pages/kubernetes/concepts.mdx
similarity index 100%
rename from pages/containers/kubernetes/concepts.mdx
rename to pages/kubernetes/concepts.mdx
diff --git a/pages/containers/kubernetes/how-to/access-audit-logs.mdx b/pages/kubernetes/how-to/access-audit-logs.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/access-audit-logs.mdx
rename to pages/kubernetes/how-to/access-audit-logs.mdx
diff --git a/pages/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx b/pages/kubernetes/how-to/access-kubernetes-dashboard.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx
rename to pages/kubernetes/how-to/access-kubernetes-dashboard.mdx
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-add-external-node-instr.webp b/pages/kubernetes/how-to/assets/scaleway-add-external-node-instr.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-add-external-node-instr.webp
rename to pages/kubernetes/how-to/assets/scaleway-add-external-node-instr.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-api-key-purpose.webp b/pages/kubernetes/how-to/assets/scaleway-api-key-purpose.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-api-key-purpose.webp
rename to pages/kubernetes/how-to/assets/scaleway-api-key-purpose.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-api-keys.webp b/pages/kubernetes/how-to/assets/scaleway-api-keys.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-api-keys.webp
rename to pages/kubernetes/how-to/assets/scaleway-api-keys.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-choose-cluster-type.webp b/pages/kubernetes/how-to/assets/scaleway-choose-cluster-type.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-choose-cluster-type.webp
rename to pages/kubernetes/how-to/assets/scaleway-choose-cluster-type.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-choose-pool-type.webp b/pages/kubernetes/how-to/assets/scaleway-choose-pool-type.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-choose-pool-type.webp
rename to pages/kubernetes/how-to/assets/scaleway-choose-pool-type.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-cluster-information.webp b/pages/kubernetes/how-to/assets/scaleway-cluster-information.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-cluster-information.webp
rename to pages/kubernetes/how-to/assets/scaleway-cluster-information.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-create-kubernetes-kapsule.webp b/pages/kubernetes/how-to/assets/scaleway-create-kubernetes-kapsule.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-create-kubernetes-kapsule.webp
rename to pages/kubernetes/how-to/assets/scaleway-create-kubernetes-kapsule.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-create-kubernetes-kosmos.webp b/pages/kubernetes/how-to/assets/scaleway-create-kubernetes-kosmos.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-create-kubernetes-kosmos.webp
rename to pages/kubernetes/how-to/assets/scaleway-create-kubernetes-kosmos.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-cron-job.webp b/pages/kubernetes/how-to/assets/scaleway-cron-job.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-cron-job.webp
rename to pages/kubernetes/how-to/assets/scaleway-cron-job.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-estimated-cost-pool.webp b/pages/kubernetes/how-to/assets/scaleway-estimated-cost-pool.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-estimated-cost-pool.webp
rename to pages/kubernetes/how-to/assets/scaleway-estimated-cost-pool.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-generate-api-key.webp b/pages/kubernetes/how-to/assets/scaleway-generate-api-key.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-generate-api-key.webp
rename to pages/kubernetes/how-to/assets/scaleway-generate-api-key.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-k8s-cluster-metrics.webp b/pages/kubernetes/how-to/assets/scaleway-k8s-cluster-metrics.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-k8s-cluster-metrics.webp
rename to pages/kubernetes/how-to/assets/scaleway-k8s-cluster-metrics.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-k8s-cp-logs.webp b/pages/kubernetes/how-to/assets/scaleway-k8s-cp-logs.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-k8s-cp-logs.webp
rename to pages/kubernetes/how-to/assets/scaleway-k8s-cp-logs.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_cluster_list.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_cluster_list.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_cluster_list.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_cluster_list.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_cluster_menu.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_cluster_menu.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_cluster_menu.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_cluster_menu.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_creation.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_creation.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_creation.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_creation.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_ingress.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_ingress.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_ingress.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_ingress.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_kubeconfig.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_kubeconfig.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_kubeconfig.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_kubeconfig.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_nodes.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_nodes.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_nodes.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_nodes.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_pools.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_pools.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_pools.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_pools.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kapsule_splashscreen.webp b/pages/kubernetes/how-to/assets/scaleway-kapsule_splashscreen.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kapsule_splashscreen.webp
rename to pages/kubernetes/how-to/assets/scaleway-kapsule_splashscreen.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kosmos-add-application.webp b/pages/kubernetes/how-to/assets/scaleway-kosmos-add-application.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kosmos-add-application.webp
rename to pages/kubernetes/how-to/assets/scaleway-kosmos-add-application.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kosmos-add-external-node.webp b/pages/kubernetes/how-to/assets/scaleway-kosmos-add-external-node.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kosmos-add-external-node.webp
rename to pages/kubernetes/how-to/assets/scaleway-kosmos-add-external-node.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kosmos-generate-api-key.webp b/pages/kubernetes/how-to/assets/scaleway-kosmos-generate-api-key.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kosmos-generate-api-key.webp
rename to pages/kubernetes/how-to/assets/scaleway-kosmos-generate-api-key.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-application-library.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-application-library.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-application-library.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-application-library.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-cluster-information.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-cluster-information.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-cluster-information.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-cluster-information.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-cluster-upgrade.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-cluster-upgrade.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-cluster-upgrade.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-cluster-upgrade.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-clusters-list.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-clusters-list.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-clusters-list.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-clusters-list.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-dashboard.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-dashboard.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-dashboard.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-dashboard.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-easy-deploy-feature.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-easy-deploy-feature.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-easy-deploy-feature.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-easy-deploy-feature.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-edit-application.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-edit-application.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-edit-application.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-edit-application.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-kubectl-all.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-kubectl-all.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-kubectl-all.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-kubectl-all.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-kubernetesexternalnoderegister.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-kubernetesexternalnoderegister.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-kubernetesexternalnoderegister.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-kubernetesexternalnoderegister.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-version-select.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-version-select.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-version-select.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-version-select.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-wordpress.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-wordpress.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-wordpress.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-wordpress.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-yaml-edit.webp b/pages/kubernetes/how-to/assets/scaleway-kubernetes-yaml-edit.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-kubernetes-yaml-edit.webp
rename to pages/kubernetes/how-to/assets/scaleway-kubernetes-yaml-edit.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-multicloud-pool-name.webp b/pages/kubernetes/how-to/assets/scaleway-multicloud-pool-name.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-multicloud-pool-name.webp
rename to pages/kubernetes/how-to/assets/scaleway-multicloud-pool-name.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-settings-tab.webp b/pages/kubernetes/how-to/assets/scaleway-settings-tab.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-settings-tab.webp
rename to pages/kubernetes/how-to/assets/scaleway-settings-tab.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-update-container.webp b/pages/kubernetes/how-to/assets/scaleway-update-container.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-update-container.webp
rename to pages/kubernetes/how-to/assets/scaleway-update-container.webp
diff --git a/pages/containers/kubernetes/how-to/assets/scaleway-upgrade-cluster-new.webp b/pages/kubernetes/how-to/assets/scaleway-upgrade-cluster-new.webp
similarity index 100%
rename from pages/containers/kubernetes/how-to/assets/scaleway-upgrade-cluster-new.webp
rename to pages/kubernetes/how-to/assets/scaleway-upgrade-cluster-new.webp
diff --git a/pages/containers/kubernetes/how-to/connect-cluster-kubectl.mdx b/pages/kubernetes/how-to/connect-cluster-kubectl.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/connect-cluster-kubectl.mdx
rename to pages/kubernetes/how-to/connect-cluster-kubectl.mdx
diff --git a/pages/containers/kubernetes/how-to/create-cluster.mdx b/pages/kubernetes/how-to/create-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/create-cluster.mdx
rename to pages/kubernetes/how-to/create-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/create-kosmos-cluster.mdx b/pages/kubernetes/how-to/create-kosmos-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/create-kosmos-cluster.mdx
rename to pages/kubernetes/how-to/create-kosmos-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/delete-cluster.mdx b/pages/kubernetes/how-to/delete-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/delete-cluster.mdx
rename to pages/kubernetes/how-to/delete-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx b/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx
rename to pages/kubernetes/how-to/deploy-image-from-container-registry.mdx
diff --git a/pages/containers/kubernetes/how-to/deploy-ingress-controller.mdx b/pages/kubernetes/how-to/deploy-ingress-controller.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/deploy-ingress-controller.mdx
rename to pages/kubernetes/how-to/deploy-ingress-controller.mdx
diff --git a/pages/containers/kubernetes/how-to/deploy-x86-arm-images.mdx b/pages/kubernetes/how-to/deploy-x86-arm-images.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/deploy-x86-arm-images.mdx
rename to pages/kubernetes/how-to/deploy-x86-arm-images.mdx
diff --git a/pages/containers/kubernetes/how-to/edit-cluster.mdx b/pages/kubernetes/how-to/edit-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/edit-cluster.mdx
rename to pages/kubernetes/how-to/edit-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/edit-kosmos-cluster.mdx b/pages/kubernetes/how-to/edit-kosmos-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/edit-kosmos-cluster.mdx
rename to pages/kubernetes/how-to/edit-kosmos-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/enable-disable-ssh.mdx b/pages/kubernetes/how-to/enable-disable-ssh.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/enable-disable-ssh.mdx
rename to pages/kubernetes/how-to/enable-disable-ssh.mdx
diff --git a/pages/containers/kubernetes/how-to/enable-easy-deploy.mdx b/pages/kubernetes/how-to/enable-easy-deploy.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/enable-easy-deploy.mdx
rename to pages/kubernetes/how-to/enable-easy-deploy.mdx
diff --git a/pages/containers/kubernetes/how-to/index.mdx b/pages/kubernetes/how-to/index.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/index.mdx
rename to pages/kubernetes/how-to/index.mdx
diff --git a/pages/containers/kubernetes/how-to/manage-allowed-ips.mdx b/pages/kubernetes/how-to/manage-allowed-ips.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/manage-allowed-ips.mdx
rename to pages/kubernetes/how-to/manage-allowed-ips.mdx
diff --git a/pages/containers/kubernetes/how-to/monitor-cluster.mdx b/pages/kubernetes/how-to/monitor-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/monitor-cluster.mdx
rename to pages/kubernetes/how-to/monitor-cluster.mdx
diff --git a/pages/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx b/pages/kubernetes/how-to/upgrade-kubernetes-version.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx
rename to pages/kubernetes/how-to/upgrade-kubernetes-version.mdx
diff --git a/pages/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx b/pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx
rename to pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx
diff --git a/pages/containers/kubernetes/how-to/use-scratch-storage-h100.mdx b/pages/kubernetes/how-to/use-scratch-storage-h100.mdx
similarity index 100%
rename from pages/containers/kubernetes/how-to/use-scratch-storage-h100.mdx
rename to pages/kubernetes/how-to/use-scratch-storage-h100.mdx
diff --git a/pages/containers/kubernetes/index.mdx b/pages/kubernetes/index.mdx
similarity index 100%
rename from pages/containers/kubernetes/index.mdx
rename to pages/kubernetes/index.mdx
diff --git a/pages/containers/kubernetes/quickstart.mdx b/pages/kubernetes/quickstart.mdx
similarity index 100%
rename from pages/containers/kubernetes/quickstart.mdx
rename to pages/kubernetes/quickstart.mdx
diff --git a/pages/containers/kubernetes/reference-content/assets/kubernetes-kapsule-on-pn-v2.webp b/pages/kubernetes/reference-content/assets/kubernetes-kapsule-on-pn-v2.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/kubernetes-kapsule-on-pn-v2.webp
rename to pages/kubernetes/reference-content/assets/kubernetes-kapsule-on-pn-v2.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-dcp-detailed.webp b/pages/kubernetes/reference-content/assets/scaleway-dcp-detailed.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-dcp-detailed.webp
rename to pages/kubernetes/reference-content/assets/scaleway-dcp-detailed.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-deployment_evo.webp b/pages/kubernetes/reference-content/assets/scaleway-deployment_evo.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-deployment_evo.webp
rename to pages/kubernetes/reference-content/assets/scaleway-deployment_evo.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-ingress-contr-diagram.webp b/pages/kubernetes/reference-content/assets/scaleway-ingress-contr-diagram.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-ingress-contr-diagram.webp
rename to pages/kubernetes/reference-content/assets/scaleway-ingress-contr-diagram.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-2.webp b/pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-2.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-2.webp
rename to pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-2.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-3.webp b/pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-3.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-3.webp
rename to pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-3.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-cluster.webp b/pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-cluster.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-k8s-multi-az-cluster.webp
rename to pages/kubernetes/reference-content/assets/scaleway-k8s-multi-az-cluster.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.pdf b/pages/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.pdf
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.pdf
rename to pages/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.pdf
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.webp b/pages/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.webp
rename to pages/kubernetes/reference-content/assets/scaleway-kubernetes-cheatsheet.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-kapsule-on-pn-v2.webp b/pages/kubernetes/reference-content/assets/scaleway-kubernetes-kapsule-on-pn-v2.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-kubernetes-kapsule-on-pn-v2.webp
rename to pages/kubernetes/reference-content/assets/scaleway-kubernetes-kapsule-on-pn-v2.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-l-b-diagram.webp b/pages/kubernetes/reference-content/assets/scaleway-l-b-diagram.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-l-b-diagram.webp
rename to pages/kubernetes/reference-content/assets/scaleway-l-b-diagram.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-managed-kubernetes-schema.webp b/pages/kubernetes/reference-content/assets/scaleway-managed-kubernetes-schema.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-managed-kubernetes-schema.webp
rename to pages/kubernetes/reference-content/assets/scaleway-managed-kubernetes-schema.webp
diff --git a/pages/containers/kubernetes/reference-content/assets/scaleway-node-port-diagram.webp b/pages/kubernetes/reference-content/assets/scaleway-node-port-diagram.webp
similarity index 100%
rename from pages/containers/kubernetes/reference-content/assets/scaleway-node-port-diagram.webp
rename to pages/kubernetes/reference-content/assets/scaleway-node-port-diagram.webp
diff --git a/pages/containers/kubernetes/reference-content/exposing-services.mdx b/pages/kubernetes/reference-content/exposing-services.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/exposing-services.mdx
rename to pages/kubernetes/reference-content/exposing-services.mdx
diff --git a/pages/containers/kubernetes/reference-content/index.mdx b/pages/kubernetes/reference-content/index.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/index.mdx
rename to pages/kubernetes/reference-content/index.mdx
diff --git a/pages/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx b/pages/kubernetes/reference-content/introduction-to-kubernetes.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx
rename to pages/kubernetes/reference-content/introduction-to-kubernetes.mdx
diff --git a/pages/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx b/pages/kubernetes/reference-content/kubernetes-cheatsheet.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx
rename to pages/kubernetes/reference-content/kubernetes-cheatsheet.mdx
diff --git a/pages/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx b/pages/kubernetes/reference-content/kubernetes-control-plane-offers.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx
rename to pages/kubernetes/reference-content/kubernetes-control-plane-offers.mdx
diff --git a/pages/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx b/pages/kubernetes/reference-content/kubernetes-load-balancer.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx
rename to pages/kubernetes/reference-content/kubernetes-load-balancer.mdx
diff --git a/pages/containers/kubernetes/reference-content/lb-ingress-controller.mdx b/pages/kubernetes/reference-content/lb-ingress-controller.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/lb-ingress-controller.mdx
rename to pages/kubernetes/reference-content/lb-ingress-controller.mdx
diff --git a/pages/containers/kubernetes/reference-content/managed-kubernetes-service-definition.mdx b/pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/managed-kubernetes-service-definition.mdx
rename to pages/kubernetes/reference-content/managed-kubernetes-service-definition.mdx
diff --git a/pages/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx b/pages/kubernetes/reference-content/managing-load-balancer-ips.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx
rename to pages/kubernetes/reference-content/managing-load-balancer-ips.mdx
diff --git a/pages/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx b/pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx
rename to pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx
diff --git a/pages/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx b/pages/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx
rename to pages/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx
diff --git a/pages/containers/kubernetes/reference-content/multi-az-clusters.mdx b/pages/kubernetes/reference-content/multi-az-clusters.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/multi-az-clusters.mdx
rename to pages/kubernetes/reference-content/multi-az-clusters.mdx
diff --git a/pages/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx b/pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx
rename to pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx
diff --git a/pages/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx b/pages/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx
rename to pages/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx
diff --git a/pages/containers/kubernetes/reference-content/using-kapsule-autoheal-feature.mdx b/pages/kubernetes/reference-content/using-kapsule-autoheal-feature.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/using-kapsule-autoheal-feature.mdx
rename to pages/kubernetes/reference-content/using-kapsule-autoheal-feature.mdx
diff --git a/pages/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx b/pages/kubernetes/reference-content/using-load-balancer-annotations.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx
rename to pages/kubernetes/reference-content/using-load-balancer-annotations.mdx
diff --git a/pages/containers/kubernetes/reference-content/version-support-policy.mdx b/pages/kubernetes/reference-content/version-support-policy.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/version-support-policy.mdx
rename to pages/kubernetes/reference-content/version-support-policy.mdx
diff --git a/pages/containers/kubernetes/reference-content/wildcard-dns.mdx b/pages/kubernetes/reference-content/wildcard-dns.mdx
similarity index 100%
rename from pages/containers/kubernetes/reference-content/wildcard-dns.mdx
rename to pages/kubernetes/reference-content/wildcard-dns.mdx
diff --git a/pages/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx b/pages/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx
similarity index 100%
rename from pages/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx
rename to pages/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx
diff --git a/pages/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx b/pages/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx
similarity index 100%
rename from pages/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx
rename to pages/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx
diff --git a/pages/containers/kubernetes/troubleshooting/index.mdx b/pages/kubernetes/troubleshooting/index.mdx
similarity index 100%
rename from pages/containers/kubernetes/troubleshooting/index.mdx
rename to pages/kubernetes/troubleshooting/index.mdx
diff --git a/pages/containers/kubernetes/videos.mdx b/pages/kubernetes/videos.mdx
similarity index 100%
rename from pages/containers/kubernetes/videos.mdx
rename to pages/kubernetes/videos.mdx
diff --git a/pages/load-balancer/api-cli/configuring-balancing-rules.mdx b/pages/load-balancer/api-cli/configuring-balancing-rules.mdx
new file mode 100644
index 0000000000..4ce1f8b2a4
--- /dev/null
+++ b/pages/load-balancer/api-cli/configuring-balancing-rules.mdx
@@ -0,0 +1,97 @@
+---
+meta:
+ title: Configure balancing rules via API
+ description: Explore how to configure balancing rules using Scaleway Load Balancer API and CLI. Enhance your network setup with efficient routing and load distribution strategies.
+content:
+ h1: Configure balancing rules via the API
+ paragraph: Explore how to configure balancing rules using Scaleway Load Balancer API and CLI. Enhance your network setup with efficient routing and load distribution strategies.
+tags: balancing-rule balancing rules api load-balancer
+dates:
+ posted: 2023-11-27
+ validation: 2024-12-23
+categories:
+ - network
+---
+You can configure balancing rules via the [Scaleway API](https://www.scaleway.com/en/developers/api/) when you create a backend. You have access to the following parameters:
+
+- `forward_port` — Load Balancer with forward user sessions to this port. For example, you can use port `8080` on a backend, while your front-end port is `80`.
+- `forward_port_algorithm` — A string value, specifying one of the following options:
+ - `"roundrobin"` — New sessions are balanced equally between the backend servers.
+ - `"leastconn"` — This mode will take into account the number of active sessions, established to each of the servers, and will forward new ones to the server, which has the least.
+ - `"first"` — The first server with available slots will be chosen.
+- `server_ip`- A list of IPv4 or IPv6 address of your servers to redirect the load to.
+
+This page shows you an example of a curl command to create a backend and configure it with your desired balancing rules.
+
+
+
+- A Scaleway [account](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+## Setting up your environment
+
+Before configuring the Load Balancer from the API, prepare your environment to facilitate usage of the API.
+
+- Ensure you have [generated an API key](/iam/how-to/create-api-keys/), and that you have the secret key at hand.
+- Decide the [Availability Zone](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#technical-information) for your Load Balancer.
+- Ensure that you have [created a Load Balancer](/load-balancer/how-to/create-load-balancer/#how-to-create-a-load-balancer) and noted its Load Balancer ID.
+
+Set these elements as environment variables as follows:
+
+```json
+export SCW_SECRET_KEY=""
+export SCW_DEFAULT_ZONE=""
+export LB_ID=""
+```
+
+
+## Creating a backend
+
+Use the following command to create a backend. Modify the parameters as you require. Ensure you replace `` with the IP address of your backend server.
+
+For help on possible parameter values, see the [API documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-backends-create-a-backend-for-a-given-load-balancer). For assistance with configuring backends generally, see our [dedicated documentation]](/load-balancer/reference-content/configuring-backends/).
+
+```json
+
+curl -X POST \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "forward_port": 42,
+ "forward_port_algorithm": "roundrobin",
+ "forward_protocol": "tcp",
+ "health_check": {
+ "check_delay": "3000",
+ "check_max_retries": 42,
+ "check_send_proxy": false,
+ "check_timeout": "1000",
+ "port": 42,
+ "tcp_config": {},
+ "transient_check_delay": "2.5s"
+ },
+ "name": "My New Backend",
+ "server_ip": [
+ ""
+ ],
+ "sticky_sessions": "none"
+ }' \
+ "https://api.scaleway.com/lb/v1/zones/$SCW_DEFAULT_ZONE/lbs/$LB_ID/backends"
+ ```
+
+A JSON object is returned to you as a response, containing the ID of your newly created backend. You may wish to save this for further use:
+
+```json
+export $BACKEND_ID=""
+```
+
+## Deleting a backend
+
+To delete the backend, run the following command:
+
+```json
+
+curl -X DELETE \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/lb/v1/zones/$SCW_DEFAULT_ZONE/backends/$BACKEND_ID"
+
+```
\ No newline at end of file
diff --git a/pages/load-balancer/api-cli/index.mdx b/pages/load-balancer/api-cli/index.mdx
new file mode 100644
index 0000000000..9c2da07dfb
--- /dev/null
+++ b/pages/load-balancer/api-cli/index.mdx
@@ -0,0 +1,8 @@
+---
+meta:
+ title: Load Balancers - API/CLI Documentation
+ description: Load Balancers API/CLI Documentation
+content:
+ h1: Load Balancers - API/CLI Documentation
+ paragraph: Load Balancers API/CLI Documentation
+---
diff --git a/pages/load-balancer/api-cli/setting-up-ssl-offloading.mdx b/pages/load-balancer/api-cli/setting-up-ssl-offloading.mdx
new file mode 100644
index 0000000000..67170332e5
--- /dev/null
+++ b/pages/load-balancer/api-cli/setting-up-ssl-offloading.mdx
@@ -0,0 +1,202 @@
+---
+meta:
+ title: Setting up SSL offloading via API
+ description: Learn how to set up SSL offloading on Scaleway Load Balancer using API and CLI. Enhance security and performance with this comprehensive step-by-step guide.
+content:
+ h1: Setting up SSL Offloading via API
+ paragraph: Learn how to set up SSL offloading on Scaleway Load Balancer using API and CLI. Enhance security and performance with this comprehensive step-by-step guide.
+tags: ssl offloading api ssl-offloading load-balancer
+dates:
+ validation: 2024-11-25
+ posted: 2021-05-26
+categories:
+ - network
+---
+
+SSL offloading describes a pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic), to forward it unencrypted to the backend servers. This effectively “offloads” the work of decrypting traffic from the backend server to the Load Balancer.
+
+You can read more about SSL offloading, compared to SSL bridging or passthrough, in our [dedicated documentation](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/)
+
+This page shows you how to create a Load Balancer configured for SSL offloading using the [Load Balancer API](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/).
+
+
+
+- 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
+
+## Setting up your environment
+
+Before configuring the Load Balancer from the API, prepare your environment to facilitate usage of the API.
+
+- Ensure you have [generated an API key](/iam/how-to/create-api-keys/), and that you have the secret key to hand.
+- Get your [Project](/organizations-and-projects/concepts/#project) ID from the [Scaleway console](https://console.scaleway.com/).
+- Decide the [Availability Zone](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#technical-information) for your Load Balancer.
+
+Set these elements as environment variables as follows:
+
+```json
+export SCW_SECRET_KEY=""
+export SCW_DEFAULT_ZONE=""
+export SCW_PROJECT_ID=""
+```
+
+## Creating the Load Balancer
+
+1. Create a new Load Balancer by running the following API call. Customize the `name`, `description` and `tags`:
+
+ ```
+ curl -X POST \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/lb/v1/zones/$SCW_DEFAULT_ZONE/lbs" \
+ -d '{
+ "name":"API Test LB",
+ "description": "my new Load Balancer",
+ "project_id":"'"$SCW_PROJECT_ID"'",
+ "tags":["test","another tag"]
+ }'
+ ```
+
+ The output of the API call returns a `json` output, similar to the example below where:
+ - The first line starting with `id` displays the ID of the newly-created Load Balancer.
+ - The line starting with `ip_address` displays the Load Balancer's IP address.
+
+ ```json no-copy
+ {
+ "id":"625f3892-13ex-xxxx-xxxx-xxxxxxxxxxxxx",
+ "name":"API Test LB",
+ "description":"my new Load Balancer",
+ "status":"to_create",
+ "instances":[
+
+ ],
+ "organization_id":"2ea18278-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
+ "project_id":"2ea18278-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
+ "ip":[
+ {
+ "id":"8802d6eb-abb6-4f35-a4f7-685182be39ab",
+ "ip_address":"195.154.72.139",
+ "organization_id":"2ea18278-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
+ "project_id":"2ea18278-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx",
+ "lb_id":"625f3892-13ex-xxxx-xxxx-xxxxxxxxxxxxx",
+ "reverse":"195-154-72-139.lb.fr-par.scw.cloud",
+ "tags":[
+
+ ],
+ "region":"fr-par",
+ "zone":"fr-par-1"
+ }
+ ],
+ "tags":[
+ "test",
+ "another tag"
+ ],
+ "frontend_count":0,
+ "backend_count":0,
+ "type":"lb-s",
+ "subscriber":null,
+ "ssl_compatibility_level":"ssl_compatibility_level_intermediate",
+ "created_at":"2024-05-28T08:52:54.473341297Z",
+ "updated_at":"2024-05-28T08:52:54.473341297Z",
+ "private_network_count":0,
+ "route_count":0,
+ "region":"fr-par",
+ "zone":"fr-par-1"
+ }
+ ```
+
+2. Copy the `id` field of the response. Save this ID to a variable to use in the next steps.
+
+ ```json
+ export LOAD_BALANCER_ID=""
+ ```
+
+## Creating a backend
+
+This tutorial supposes that a web application is running on port `80` of the backend machines.
+
+1. Create a new backend for your Load Balancer. Make sure to replace `` and `` with the IPs of your backend servers:
+
+ ```json
+ curl -X POST \
+ -H "Content-Type: application/json" \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ "https://api.scaleway.com/lb/v1/zones/$SCW_DEFAULT_ZONE/lbs/$LOAD_BALANCER_ID/backends" \
+ -d '{
+ "name":"main backend",
+ "forward_port": 80,
+ "forward_port_algorithm": "roundrobin",
+ "forward_protocol": "tcp",
+ "health_check":{
+ "check_delay": 2000,
+ "check_max_retries": 3,
+ "check_timeout": 1000,
+ "port": 80,
+ "tcp_config":{}
+ },
+ "server_ip": ["", ""]
+ }'
+ ```
+
+ A `json` output similar to the first request displays.
+
+2. Copy the value of the first line of the output, starting with `id`. This is the ID of your Load Balancer's backend. Set it as a variable:
+
+ ```json
+ export BACKEND_ID=""
+ ```
+
+## Creating an SSL/TLS certificate
+
+In order to achieve SSL offloading, your Load Balancer needs an [SSL/TLS certificate](/load-balancer/concepts/#certificate). In these steps, we create a Let's Encrypt certificate, which we will then add to the Load Balancer's frontend.
+
+1. Create a new certificate for your Load Balancer. Replace `` with a friendly name for the certificate, and `` with your domain name (this domain must exist and resolve to your Load Balancer IP address).
+
+ ```json
+ curl -X POST \
+ -H "X-Auth-Token: $SCW_SECRET_KEY" \
+ -H "Content-Type: application/json" \
+ "https://api.scaleway.com/lb/v1/zones/$SCW_DEFAULT_ZONE/lbs/$LOAD_BALANCER_ID/certificates" \
+ -d '{
+ "name":"",
+ "letsencrypt":{
+ "common_name":""
+ }
+ }'
+ ```
+
+ The certificate details are returned in the form of a `json` list.
+
+2. Copy the value of the first line of the output, starting with `id`. This is the ID of your Load Balancer's certificate. Set it as a variable:
+
+ ```json
+ export CERTIFICATE_ID="