diff --git a/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx new file mode 100644 index 0000000000..42165d16d8 --- /dev/null +++ b/changelog/august2025/2025-08-25-instances-changed-windows-images-network-configuration-.mdx @@ -0,0 +1,13 @@ +--- +title: Windows Images - Network configuration now uses DHCP. Serial console enabled +status: changed +date: 2025-08-25 +category: compute +product: instances +--- + +Windows Server 2022 and Windows Server 2022 Core images now use DHCP for network configuration by default, consistent with all existing Instance OS images. + +For running Instances, no network configuration changes are needed unless you modify the public IPv4 address. + +If you change the public IPv4 address, the Instance will retain its existing static configuration and continue using the previous address. To enable DHCP for your Instance, follow our [dedicated documentation](/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022/) before updating the public IPv4 address. diff --git a/changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx b/changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx new file mode 100644 index 0000000000..9de1fbfcd0 --- /dev/null +++ b/changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx @@ -0,0 +1,13 @@ +--- +title: DNS Service IP and Pod & Service CIDR are now customizable +status: added +date: 2025-08-27 +category: containers +product: kubernetes +--- + +The following parameters can be set when creating a cluster: +- `service-dns-ip`: IP used for the DNS Service (cannot be changes later) +- `pod-cidr`: Subnet used for the Pod CIDR (cannot be changed later) +- `service-cidr`: Subnet used for the Service CIDR (cannot be changed later) + diff --git a/changelog/august2025/2025-08-28-containers-added-custom-domains-now-supports-websockets.mdx b/changelog/august2025/2025-08-28-containers-added-custom-domains-now-supports-websockets.mdx new file mode 100644 index 0000000000..7aeca385b6 --- /dev/null +++ b/changelog/august2025/2025-08-28-containers-added-custom-domains-now-supports-websockets.mdx @@ -0,0 +1,10 @@ +--- +title: Custom domains now supports WebSockets +status: added +date: 2025-08-28 +category: serverless +product: containers +--- + +Serverless Containers configured with custom domains are now compatible with WebSockets. + diff --git a/changelog/august2025/2025-08-28-functions-added-custom-domains-now-supports-websockets.mdx b/changelog/august2025/2025-08-28-functions-added-custom-domains-now-supports-websockets.mdx new file mode 100644 index 0000000000..4e06690d69 --- /dev/null +++ b/changelog/august2025/2025-08-28-functions-added-custom-domains-now-supports-websockets.mdx @@ -0,0 +1,10 @@ +--- +title: Custom domains now support WebSockets +status: added +date: 2025-08-28 +category: serverless +product: functions +--- + +Serverless Functions configured with custom domains are now compatible with WebSockets. + diff --git a/changelog/august2025/2025-08-29-instances-deprecated-ent1-instances-are-now-deprecated.mdx b/changelog/august2025/2025-08-29-instances-deprecated-ent1-instances-are-now-deprecated.mdx new file mode 100644 index 0000000000..0419343d2e --- /dev/null +++ b/changelog/august2025/2025-08-29-instances-deprecated-ent1-instances-are-now-deprecated.mdx @@ -0,0 +1,11 @@ +--- +title: ENT1 Instances are now deprecated +status: deprecated +date: 2025-08-29 +category: compute +product: instances +--- + +ENT1 Instances are now deprecated and unavailable for new deployments. Existing ENT1 Instances will soon be automatically migrated to their POP2 equivalent, as announced recently through our emails & ticket communication. +[POP2 Instances](/instances/reference-content/general-purpose/#pop2-instances), which share the same hardware specifications as ENT1 Instances, provide access to the latest features, ensuring your infrastructure remains current with evolving technology and demands. + diff --git a/changelog/september2025/2025-09-01-key-manager-changed-key-manager-is-now-in-general-avail.mdx b/changelog/september2025/2025-09-01-key-manager-changed-key-manager-is-now-in-general-avail.mdx new file mode 100644 index 0000000000..1e0c2eeced --- /dev/null +++ b/changelog/september2025/2025-09-01-key-manager-changed-key-manager-is-now-in-general-avail.mdx @@ -0,0 +1,10 @@ +--- +title: Key Manager is now in General Availability +status: changed +date: 2025-09-01 +category: security-identity +product: key-manager +--- + +[Key Manager](/key-manager/) is now in General Availability. Secure your production applications and start managing your keys today. + diff --git a/macros/ai/chat-comp-vs-responses-api.mdx b/macros/ai/chat-comp-vs-responses-api.mdx new file mode 100644 index 0000000000..01c1cd7837 --- /dev/null +++ b/macros/ai/chat-comp-vs-responses-api.mdx @@ -0,0 +1,17 @@ +--- +macro: chat-comp-vs-responses-api +--- + +Both the [Chat Completions API](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion) and the [Responses API](https://www.scaleway.com/en/developers/api/generative-apis/#path-responses-beta-create-a-response) are OpenAI-compatible REST APIs that can be used for generating and manipulating conversations. The Chat Completions API is focused on generating conversational responses, while the Responses API is a more general REST API for chat, structured outputs, tool use, and multimodal inputs. + +The **Chat Completions** API was released in 2023, and is an industry standard for building AI applications, being specifically designed for handling multi-turn conversations. It is stateless, but allows users to manage conversation history by appending each new message to the ongoing conversation. Messages in the conversation can include text, images and audio extracts. The API supports `function` tool-calling, allowing developers to define functions that the model can choose to call. If it does so, it returns the function name and arguments, which the developer's code must execute and feed back into the conversation. + +The **Responses** API was released in 2025, and is designed to combine the simplicity of Chat Completions with the ability to do more agentic tasks and reasoning. It supports statefulness, being able to maintain context without needing to resend the entire conversation history. It offers tool-calling by built-in tools (e.g. web or file search) that the model is able to execute itself while generating a response. + + +Scaleway's support for the Responses API is currently at beta stage. Support of the full feature set will be incremental: currently statefulness and tools other than `function` calling are not supported. + + +Most supported Generative API models can be used with both Chat Completions and Responses API. For the **`gtp-oss-120b` model, use of the Responses API is recommended, as it will allow you to access all of its features, especially tool-calling. + +For full details on the differences between these APIs, see the [official OpenAI documentation](https://platform.openai.com/docs/guides/migrate-to-responses). \ No newline at end of file diff --git a/macros/compute/instances-block-bandwidth-overview.mdx b/macros/compute/instances-block-bandwidth-overview.mdx index 80d3137623..2c9c59fef1 100644 --- a/macros/compute/instances-block-bandwidth-overview.mdx +++ b/macros/compute/instances-block-bandwidth-overview.mdx @@ -38,17 +38,6 @@ Bandwidth impacts how your applications perform and interact with other systems. | DEV1-L | 400 Mbit/s | 200 MiB/s | | DEV1-XL | 500 Mbit/s | 250 MiB/s | -## ENT1 range - -| Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | -|-----------------------|-------------------------|---------------------| -| 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 | - ## GP1 range | Instance Type | Internet Bandwidth (up to) | Block Bandwidth (up to) | diff --git a/macros/compute/instances.mdx b/macros/compute/instances.mdx index 18f165b8a6..7d2bdb7381 100644 --- a/macros/compute/instances.mdx +++ b/macros/compute/instances.mdx @@ -2,4 +2,4 @@ macro: compute-instances --- -An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [Development](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [GPU](/instances/concepts/#gpu-instance), [Stardust](/instances/reference-content/learning/#learning-range-stardust-instances) and [Enterprise](/instances/reference-content/production-optimized/#production-optimized-range-ent1-instances). \ No newline at end of file +An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/instances/reference-content/general-purpose/), [Development](/instances/reference-content/development/), [GPU](/instances/concepts/#gpu-instance), and [Specialized](/instances/reference-content/specialized/). \ No newline at end of file diff --git a/menu/mainLinks.json b/menu/mainLinks.json index 9f18e9b503..bdce4adf76 100644 --- a/menu/mainLinks.json +++ b/menu/mainLinks.json @@ -10,6 +10,11 @@ "label": "Tutorials", "slug": "tutorials" }, + { + "icon": "UseCaseCategoryIcon", + "label": "Use cases", + "slug": "use-cases" + }, { "icon": "BillingCategoryIcon", "label": "Troubleshooting Hub", diff --git a/menu/navigation.json b/menu/navigation.json index 9adb842ca4..5e5f3adb9b 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -308,6 +308,10 @@ { "label": "Block Storage footprint calculation", "slug": "block-storage-env-footprint" + }, + { + "label": "Object Storage footprint calculation", + "slug": "object-storage-env-footprint" } ], "label": "Additional Content", @@ -1171,6 +1175,10 @@ "label": "Activate an IPv6 block ", "slug": "activate-ipv6-block" }, + { + "label": "Configure IPv6", + "slug": "configure-ipv6-dedibox" + }, { "label": "Modify Dedibox options", "slug": "modify-server-options" @@ -1478,6 +1486,10 @@ "label": "Use placement groups", "slug": "use-placement-groups" }, + { + "label": "Create an image", + "slug": "create-a-backup" + }, { "label": "Create an image from a snapshot", "slug": "create-image-from-snapshot" @@ -1602,21 +1614,17 @@ "label": "Instances internet and Block Storage bandwidth overview", "slug": "instances-bandwidth-overview" }, - { - "label": "The right Instance for learning purposes", - "slug": "learning" - }, { "label": "The right Instance for development purposes", - "slug": "cost-optimized" + "slug": "development" }, { "label": "The right Instance for production purposes", - "slug": "production-optimized" + "slug": "general-purpose" }, { - "label": "The right Instance for workload purposes", - "slug": "workload-optimized" + "label": "The right Instance for specialized purposes", + "slug": "specialized" }, { "label": "Instance OS images and InstantApps", @@ -1661,6 +1669,14 @@ { "label": "Compatibility between Scaleway OS Images and Flexible IPs", "slug": "comaptibility-scw-os-images-flexible-ip" + }, + { + "label": "Enabling DHCP network configuration for Windows Server 2022 Instances", + "slug": "enabling-dhcp-network-configuration-windows-server-2022" + }, + { + "label": "Historical Instances offerings", + "slug": "historical-offers" } ], "label": "Additional Content", @@ -4579,6 +4595,10 @@ "label": "Serverless overview", "slug": "serverless-overview" }, + { + "label": "Migrating to Serverless Containers", + "slug": "migrate-to-serverless-containers" + }, { "label": "Containers and Private Networks integration", "slug": "containers-private-networks" @@ -4990,6 +5010,10 @@ "label": "Detach a volume", "slug": "detach-a-volume" }, + { + "label": "Unmount a volume", + "slug": "unmount-a-volume" + }, { "label": "Delete a snapshot", "slug": "delete-a-snapshot" diff --git a/pages/account/concepts.mdx b/pages/account/concepts.mdx index 88b1306773..63eb53f9a9 100644 --- a/pages/account/concepts.mdx +++ b/pages/account/concepts.mdx @@ -40,6 +40,8 @@ A magic link provides quick and secure access to your account without the hassle 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. +Refer to the [How to use MFA](/account/how-to/use-2fa) documentation page for more information. + ## 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. diff --git a/pages/billing/additional-content/understanding-savings-plans.mdx b/pages/billing/additional-content/understanding-savings-plans.mdx index bd307db7fa..8a421f0ddf 100644 --- a/pages/billing/additional-content/understanding-savings-plans.mdx +++ b/pages/billing/additional-content/understanding-savings-plans.mdx @@ -116,10 +116,10 @@ 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, POP2-HM, POP2-HN)  + - Instances + - Development + - Geneal Purpose + - Specialized The following resources are **not** covered by the savings plan discount: diff --git a/pages/billing/concepts.mdx b/pages/billing/concepts.mdx index 0ca06e30c0..2dcf55306f 100644 --- a/pages/billing/concepts.mdx +++ b/pages/billing/concepts.mdx @@ -3,7 +3,7 @@ title: Billing - Concepts description: Understand the key billing concepts in the Scaleway console. tags: billing account pricing payment dates: - validation: 2025-02-17 + validation: 2025-08-25 --- ## Billing alerts @@ -65,10 +65,14 @@ Pay-as-you-go is a billing system in which you only pay for what you consume ins 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. +Refer to the [How to add a payment method](/billing/how-to/add-payment-method) documentation page for more information. + ## 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. +Refer to the [How to create a Project](/organizations-and-projects/how-to/create-a-project) documentation page for more information. + ## 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. diff --git a/pages/classic-hosting/how-to/change-ftp-account-password.mdx b/pages/classic-hosting/how-to/change-ftp-account-password.mdx index 72d0c60cf2..a7c3ea8eb9 100644 --- a/pages/classic-hosting/how-to/change-ftp-account-password.mdx +++ b/pages/classic-hosting/how-to/change-ftp-account-password.mdx @@ -3,7 +3,7 @@ title: How to change the password of an FTP account for Scaleway Web Hosting Cla description: This page shows you how to change the password of an FTP account tags: webhosting ftp-account ftp account password dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/classic-hosting/how-to/configure-outlook.mdx b/pages/classic-hosting/how-to/configure-outlook.mdx index 5122767eef..6c7f168522 100644 --- a/pages/classic-hosting/how-to/configure-outlook.mdx +++ b/pages/classic-hosting/how-to/configure-outlook.mdx @@ -3,7 +3,7 @@ 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 tags: configuration outlook email webhosting dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx b/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx index 897d6c96db..1450553df0 100644 --- a/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx +++ b/pages/classic-hosting/how-to/retrieve-headers-of-email.mdx @@ -3,7 +3,7 @@ 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. tags: webhosting email header thunderbird dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-05-26 --- import WebhostingOnline from '@macros/webhosting/webhosting-online.mdx' diff --git a/pages/cockpit/faq.mdx b/pages/cockpit/faq.mdx index 43ccf915fa..7b4391c738 100644 --- a/pages/cockpit/faq.mdx +++ b/pages/cockpit/faq.mdx @@ -2,13 +2,9 @@ title: Cockpit FAQ description: Discover Scaleway's Cockpit dates: - validation: 2025-08-18 + validation: 2025-08-28 productIcon: CockpitProductIcon --- -import CockpitPlanDeprecation from '@macros/cockpit/plan-deprecation.mdx' - - - ## Overview diff --git a/pages/cockpit/how-to/change-data-retention.mdx b/pages/cockpit/how-to/change-data-retention.mdx index 7321062c45..1ba9599d47 100644 --- a/pages/cockpit/how-to/change-data-retention.mdx +++ b/pages/cockpit/how-to/change-data-retention.mdx @@ -3,26 +3,13 @@ title: How to change your data retention period description: Discover how to adjust data retention settings for metrics, logs, and traces in Cockpit. tags: cockpit data-retention retention-period edit-retention dates: - validation: 2025-04-02 + validation: 2025-08-28 posted: 2024-11-25 --- import Requirements from '@macros/iam/requirements.mdx' -This page shows you how to change the [retention](/cockpit/concepts/#retention) period for your data sources. Refer to the [Cockpit FAQ](/cockpit/faq/) for detailed information on pricing. - - - **Pricing update for Cockpit custom retention**

- - On January 1st, 2025, Cockpit pricing plans were deprecated and replaced by the custom [retention](/cockpit/concepts/#retention) feature, available for free during beta. - On May 1st, 2025, this feature reaches general availability and **becomes billable**.

- - **Logs and traces**: free retention for 7 days, then charged €0.002/GB/day - - **Metrics**: free retention for 31 days, then charged €0.0002/10 million samples/day - - Ingestion of custom data remains billable at [the current pricing](/cockpit/faq/#how-am-i-billed-for-using-cockpit-with-custom-data). - +This page shows you how to change the [retention](/cockpit/concepts/#retention) period for your data sources. Extending your retention above default value is priced based on the volume of data effectively stored. Refer to the [Cockpit FAQ](/cockpit/faq/) for detailed information on pricing. diff --git a/pages/cockpit/reference-content/cockpit-limitations.mdx b/pages/cockpit/reference-content/cockpit-limitations.mdx index ab0e038cbb..3cbcd48fa2 100644 --- a/pages/cockpit/reference-content/cockpit-limitations.mdx +++ b/pages/cockpit/reference-content/cockpit-limitations.mdx @@ -3,7 +3,7 @@ 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. tags: observability cockpit retention metrics logs dates: - validation: 2025-05-13 + validation: 2025-08-28 posted: 2023-09-05 --- @@ -86,7 +86,7 @@ The following table provides details about the products that are integrated into | Database RDB MySQL | **Integrated*** | **Integrated*** | **Integrated** | | Serverless SQL Database | **Integrated*** | **Integrated*** | **Integrated** | | Redis | **Integrated*** | **Integrated*** | **Integrated** | -| MongoDB | Planned | Not integrated | Not integrated | +| MongoDB | **Integrated*** | Not integrated | Not integrated | | Data Lab (Apache Spark) | **Integrated*** | Not integrated | Not integrated | | Clickhouse | Planned | Not integrated | Not integrated | | Private Networks | **Integrated*** | Not integrated | Not integrated | @@ -100,7 +100,7 @@ The following table provides details about the products that are integrated into | Cockpit | **Integrated*** | Not integrated | Not integrated | | Audit Trail | Not integrated | Not integrated | Not integrated | | IAM | Not integrated | Not integrated | Not integrated | -| Secret Manager | **Integrated*** | **Integrated** | Not integrated | +| Secret Manager | **Integrated*** | Not integrated | Not integrated | | Key Manager | Not integrated | Not integrated | Not integrated | *: Including data and dashboards diff --git a/pages/dedibox-account/how-to/create-a-dedibox-account.mdx b/pages/dedibox-account/how-to/create-a-dedibox-account.mdx index 457a97b710..80b1809f80 100644 --- a/pages/dedibox-account/how-to/create-a-dedibox-account.mdx +++ b/pages/dedibox-account/how-to/create-a-dedibox-account.mdx @@ -3,7 +3,7 @@ title: How to create your Scaleway Dedibox account description: Learn how to create a Scaleway Dedibox account. tags: dedibox account create signup dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2020-03-12 --- diff --git a/pages/dedibox-account/how-to/outsource-failover-ip.mdx b/pages/dedibox-account/how-to/outsource-failover-ip.mdx index b42e5e437e..820ce74962 100644 --- a/pages/dedibox-account/how-to/outsource-failover-ip.mdx +++ b/pages/dedibox-account/how-to/outsource-failover-ip.mdx @@ -3,11 +3,11 @@ 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. tags: dedibox-console dedibox outsource failover failover-ip dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2020-03-12 --- -Outsourcing a Dedibox dedicated server and its allocated failover IPs allows another Dedibox user to manage these resources on your behalf. +Outsourcing a Dedibox 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. diff --git a/pages/dedibox-dns/how-to/add-dns-delegation.mdx b/pages/dedibox-dns/how-to/add-dns-delegation.mdx index ac06e0a750..b7978a42c1 100644 --- a/pages/dedibox-dns/how-to/add-dns-delegation.mdx +++ b/pages/dedibox-dns/how-to/add-dns-delegation.mdx @@ -1,9 +1,9 @@ --- -title: How to add a DNS delegation +title: How to add a DNS delegation to a Scaleway Dedibox IP address block description: This page explains how to add a DNS delegation to IPv6 and IPv4 on Scaleway Dedibox. tags: dns dedibox delegation IPv6 IPv4 dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' @@ -11,9 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx' import image from './assets/scaleway-dedibox-server-list.webp' import image2 from './assets/scaleway-edit-delegation.webp' - -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. +You cannot directly edit reverse DNS for IPv4 /27 blocks or IPv6 blocks (/48, /56, /64) in the Dedibox console. +Instead, you must delegate these subnets to your nameservers, which will handle the propagation of reverse DNS records on the internet. For redundancy, you need at least two DNS servers, and you can delegate subnets directly from your account. diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx index 948e039de4..51eece26d2 100644 --- a/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx +++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-p410.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox hp smart array p410 raid kvm dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx index 3af8a3016f..4c843a6f40 100644 --- a/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx +++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-p420.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox hp smart array p420 raid kvm dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx b/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx index dd7479d76f..2925a9d96f 100644 --- a/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx +++ b/pages/dedibox-ip-failover/how-to/configure-multiip-virtualmac.mdx @@ -1,9 +1,9 @@ --- -title: How to configure multi-IP virtual MAC addresses +title: How to configure multi-IP virtual MAC addresses for Scaleway Dedibox description: This page explains how to configure multi-IP virtual MAC addresses on Scaleway Dedibox. tags: dedibox multi-ip virtual mac dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-07-29 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-ipv6/how-to/create-subnet.mdx b/pages/dedibox-ipv6/how-to/create-subnet.mdx index 5c59ea868a..42c304bc88 100644 --- a/pages/dedibox-ipv6/how-to/create-subnet.mdx +++ b/pages/dedibox-ipv6/how-to/create-subnet.mdx @@ -3,7 +3,7 @@ title: How to create an IPv6 subnet for Dedibox servers description: This page explains how to create an IPv6 subnet for Scaleway Dedibox servers. tags: dedibox ipv6 subnet dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-08-03 --- import Requirements from '@macros/iam/requirements.mdx' @@ -11,7 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx' import image from './assets/scaleway_ipv6_list.webp' -You can split your IPv6 prefix into several subnets and use them on your Dedibox servers in all locations. Each subnet has its own [DUID](/dedibox-ipv6/concepts/#duid) and can be configured individually. +Splitting your /48 IPv6 prefix into smaller subnets (e.g., /56 or /64) allows you to assign unique IPv6 address ranges to individual servers or virtual machines (VMs) on your Dedibox infrastructure. +This enables better network organization, improved security through segmentation, and easier management of IP assignments across multiple devices or services. Each subnet has its own [DUID](/dedibox-ipv6/concepts/#duid) (DHCP Unique Identifier) and can be configured individually. * You can create as many /56 subnets as you have servers. @@ -34,5 +35,3 @@ You can split your IPv6 prefix into several subnets and use them on your Dedibox 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-network/how-to/subscribe-to-jmrp.mdx b/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx index 5e2a2c99f6..c4bd4a07f7 100644 --- a/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx +++ b/pages/dedibox-network/how-to/subscribe-to-jmrp.mdx @@ -3,7 +3,7 @@ title: How to subscribe to JMRP description: This page explains how to subscribe to JMRP. tags: dedibox network jmrp dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-08-20 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx b/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx index bc26ece4d8..02b9f0464e 100644 --- a/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx +++ b/pages/dedibox-rpn/how-to/connect-rpn-san-windows.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox windows-server windows server rpn san dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' @@ -54,6 +54,6 @@ import image8 from './assets/scaleway_windows_server_san_08.webp' - For additional information, refer to [Microsoft's Windows storage configuration guide](https://docs.microsoft.com/en-us/windows-server/storage/). + For additional information, refer to [Microsoft's Windows storage configuration guide](https://learn.microsoft.com/en-us/windows-server/storage/storage). diff --git a/pages/dedibox-rpn/how-to/connect-rpn-san.mdx b/pages/dedibox-rpn/how-to/connect-rpn-san.mdx index fa7375c336..ebe761a2bc 100644 --- a/pages/dedibox-rpn/how-to/connect-rpn-san.mdx +++ b/pages/dedibox-rpn/how-to/connect-rpn-san.mdx @@ -1,9 +1,9 @@ --- -title: How to connect a Dedibox to RPN SAN +title: How to connect a Scaleway Dedibox to RPN SAN description: This page explains how to connect a Scaleway Dedibox to RPN SAN tags: dedibox rpn san dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' 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 index 0573450994..be37116b95 100644 --- a/pages/dedibox-rpn/how-to/use-rpn-san-esxi-v7.mdx +++ b/pages/dedibox-rpn/how-to/use-rpn-san-esxi-v7.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox rpn san vmware esxi esxi7 dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-11-10 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx b/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx index e65c039b5e..c951c1ec12 100644 --- a/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx +++ b/pages/dedibox-rpn/how-to/use-rpn-san-esxi.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox rpn san vmware esxi dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-11-10 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx b/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx index 535743b649..cd8af53f50 100644 --- a/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx +++ b/pages/dedibox-rpn/how-to/use-rpn-vpn.mdx @@ -3,7 +3,7 @@ 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 tags: dedibox rpn vpn dedibox-server dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-10-07 --- import Requirements from '@macros/iam/requirements.mdx' @@ -19,7 +19,7 @@ The feature is based on [OpenVPN](/tutorials/install-openvpn/) and you can add t The RPN VPN service allows you to: -* Connect from anywhere in your totally secure and private network. +* Connect from anywhere to your totally secure and private network. * Connect servers which do not have an RPN interface to the RPN. diff --git a/pages/dedibox-scaleway/concepts.mdx b/pages/dedibox-scaleway/concepts.mdx index 05321f955b..b3f08daba8 100644 --- a/pages/dedibox-scaleway/concepts.mdx +++ b/pages/dedibox-scaleway/concepts.mdx @@ -3,7 +3,7 @@ title: Dedibox - Concepts description: This page explains all the concepts related to Scaleway Dedibox servers tags: dedibox concepts hostname dates: - validation: 2025-02-11 + validation: 2025-08-27 --- ## Administrator password diff --git a/pages/dedibox/faq.mdx b/pages/dedibox/faq.mdx index b0b110f3d1..d489703589 100644 --- a/pages/dedibox/faq.mdx +++ b/pages/dedibox/faq.mdx @@ -37,7 +37,7 @@ Your server operates on a monthly contract, with the billing cycle running from A commitment plan allows you to commit to keeping your Dedibox for a period of 12 or 36 months. By choosing a commitment period, you benefit from lower monthly rent for your server and free setup, depending on the plan you choose. ## Can I benefit from a commitment plan on a server I'm already renting? -No, commitment plans are available only for new subscriptions. +Yes, in most cases, you can apply a commitment plan to a server you're already renting. To check your eligibility and choose a plan, go to your server in the Scaleway Dedibox console and click **Commitment** in the left-side menu. ## Will my server options also benefit from the discount? No, the discount applies only to the Dedibox server. diff --git a/pages/dedibox/how-to/manage-packages.mdx b/pages/dedibox/how-to/manage-packages.mdx index 6c1dc010d9..b6c2366ae9 100644 --- a/pages/dedibox/how-to/manage-packages.mdx +++ b/pages/dedibox/how-to/manage-packages.mdx @@ -3,7 +3,7 @@ title: How to manage software packages on Linux description: Learn how to manage software packages on a Scaleway Dedibox server. tags: dedibox package management dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-06-11 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/concepts.mdx b/pages/elastic-metal/concepts.mdx index 29a78bf15a..db164d7fb2 100644 --- a/pages/elastic-metal/concepts.mdx +++ b/pages/elastic-metal/concepts.mdx @@ -3,7 +3,7 @@ title: Elastic Metal - Concepts description: This page explains all the concepts related to Scaleway Elastic Metal servers tags: elastic-metal rescue-mode private-networks remote-access az dates: - validation: 2025-02-17 + validation: 2025-08-27 --- import RegionAndAz from '@macros/console/region-and-az.mdx' diff --git a/pages/elastic-metal/how-to/create-server.mdx b/pages/elastic-metal/how-to/create-server.mdx index d1564bad5c..92e6108cc0 100644 --- a/pages/elastic-metal/how-to/create-server.mdx +++ b/pages/elastic-metal/how-to/create-server.mdx @@ -3,7 +3,7 @@ title: How to Create an Elastic Metal server description: Learn how to create an Elastic Metal server on Scaleway. tags: elastic-metal server dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/how-to/install-server.mdx b/pages/elastic-metal/how-to/install-server.mdx index 3b58a22cb1..aab429c0b6 100644 --- a/pages/elastic-metal/how-to/install-server.mdx +++ b/pages/elastic-metal/how-to/install-server.mdx @@ -3,7 +3,7 @@ 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. tags: elastic-metal server installation dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/how-to/use-rescue-mode.mdx b/pages/elastic-metal/how-to/use-rescue-mode.mdx index c19dff8a14..a0db97c0d3 100644 --- a/pages/elastic-metal/how-to/use-rescue-mode.mdx +++ b/pages/elastic-metal/how-to/use-rescue-mode.mdx @@ -3,7 +3,7 @@ title: How to use rescue mode on Elastic Metal servers description: This page explains how to use rescue mode on Elastic Metal servers tags: elastic-metal rescue-mode dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-05-26 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/elastic-metal/troubleshooting/troubleshoot-remote-access-issues.mdx b/pages/elastic-metal/troubleshooting/troubleshoot-remote-access-issues.mdx index 6fef4fe0cd..663d492dbd 100644 --- a/pages/elastic-metal/troubleshooting/troubleshoot-remote-access-issues.mdx +++ b/pages/elastic-metal/troubleshooting/troubleshoot-remote-access-issues.mdx @@ -35,6 +35,9 @@ You are unable to connect to your Scaleway Elastic Metal server using remote acc - Try using a different network or disable VPNs that may interfere. - Allow the necessary ports for remote access in your firewall settings. +#### Ensure Fail2ban is installed and configured on the machine +- [Fail2ban](/tutorials/protect-server-fail2ban/) is a software that detects potential malicious connection attempts to the server and blocks them. + #### Try a different browser or system - Some remote access solutions require specific browsers or Java versions. - Try launching the KVM session in a different browser (Chrome, Firefox, Safari, Edge). @@ -45,6 +48,9 @@ You are unable to connect to your Scaleway Elastic Metal server using remote acc - Close any existing remote access session and relaunch it from the Scaleway console. - If the session remains unresponsive, try rebooting your server. +#### Ensure web administration panels (e.g. Proxmox) are located within a Private Network +- Create a [Private Network](/vpc/faq/#private-networks) to avoid exposing the server admin interface on the public internet. + #### Check server status - If your server is unresponsive, attempt a soft reboot from the Scaleway console. - If that does not work, use the power cycle option to restart the machine. diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index f26a2021ce..6462c6dbee 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -129,6 +129,7 @@ You can find the calculation specifications for each of the available products i - [Bare Metal](/environmental-footprint/additional-content/bare-metal-env-footprint) - [Instances](/environmental-footprint/additional-content/instances-env-footprint) - [Block Storage](/environmental-footprint/additional-content/block-storage-env-footprint) +- [Object Storage](/environmental-footprint/additional-content/object-storage-env-footprint) ### Cross-IT equipment & stock diff --git a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx index 3178e64522..a88c813b2e 100644 --- a/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx +++ b/pages/environmental-footprint/additional-content/environmental-footprint-integration.mdx @@ -17,13 +17,15 @@ The following tables provide details about the Scaleway products that currently | CPU Instances | **Yes** | | Block Storage | **Yes** | | Elastic Metal | **Yes** | +| Object Storage | **Yes** | ## Planned product integration | **Product Name** | **Environmental Footprint calculator available** | |----------------------------|---------------------------------| | Dedibox | **Integration ongoing** | -| Object Storage | **Integration ongoing** | +| Load Balancers | **Integration ongoing** | +| VPC | **Integration ongoing** | | GPU Instances | **Not integrated yet** | | Kubernetes | **Not integrated yet** | | Container Registry | **Not integrated yet** | @@ -34,9 +36,7 @@ The following tables provide details about the Scaleway products that currently | 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** | diff --git a/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx new file mode 100644 index 0000000000..aa6fa9d4e4 --- /dev/null +++ b/pages/environmental-footprint/additional-content/object-storage-env-footprint.mdx @@ -0,0 +1,75 @@ +--- +title: Object Storage footprint calculation +description: This page explains how Scaleway calculates the environmental footprint of Object Storage in detail. +tags: object storage environmental-footprint impact cloud-computing +dates: + validation: 2025-08-22 + posted: 2025-08-22 +--- + + +This page includes the specificities of the environmental footprint calculation for Object Storage. + +## Calculation aspects + +The total estimated impact of Object Storage volumes is calculated by integrating the: + +- **Dedicated manufacturing impact** - Related to the physical servers hosting the storage volumes. +- **Related manufacturing impact** - The impact of the tools used to manage the Object Storage offers: control plane, monitoring, internal load balancers, and others. +- **Energy usage impact** - The average electricity consumption of storage servers and their energy efficiency and of the tools used to manage the Object Storage offers. + +### Ratio per storage volume + +To allocate the impact of an Object Storage volume, we apply the unit resulting from the RCP allocation rule, the s3_ratio, to all calculation steps: + +``` +s3_ratio = VOLsto/VolstoPool +``` + +- **VOLsto** - represents the **reserved volume** per user. In Object Storage, your data is replicated 1.5 times on multiple nodes to guarantee availability, so the **VOLsto** is applied with factor of 1.5 to account for replication. +- **VolstoPool** - represents the total storage volume reserved for Object Storage. For this product, only 80% of the total storage capacity of the machines is available. The remaining 20% is reserved for performance reasons. + +In the example below we consider a **VOLsto** of 150 GB and a **VolstoPool** of 800 GB. + +``` +s3_ratio = 150/800 = 0.19 +``` + +### Manufacturing impact + +The calculation of the manufacturing impact of Object Storage volumes is based on: + +- The manufacturing impact of servers that host user storage +- The manufacturing impact of servers used by the Scaleway Object Storage team to manage the service - on both the Control and Data planes +- The manufacturing and electricity consumption impact of the remaining product lifecycle aspects: datacenters and technical environment, network and cross-IT equipment & stocks. + +The calculation is the same one used for [measuring the impact of manufacturing for Bare Metal servers](/environmental-footprint/additional-content/environmental-footprint-calculator), which we consider the basis footprint calculation, but for Object Storage we also apply the `s3_ratio` to break the impact down to only the allocated volumes. + +#### Calculation example + +For the example below, we consider a single server with a lifespan of 6 years (52 560 hours) and power of 110w. We measure the impact of 100 hours and consider through [Boavizta estimates](https://www.boavizta.org/) that the impact of the manufacturing of this server is 850 kgCo2e. Also considering a `s3_ratio` of `0.19`, we make the following calculation: + +``` +VolumeManufacturingImpact = (100 / 52560) * 850 * 0.19 = 0.3 kgCO2e +``` + +In the example, the dedicated manufacturing impact of a 150 GB usage for 100 hours is 0.3 kgCo2e. + +### Usage impact + +The calculation of the usage impact of Object Storage volumes is based on: + +- Impact of electricity consumption of servers that host user storage +- Impact of electricity consumption of infrastructure and service management servers by the Scaleway Object Storage team to run the Object Storage service. In this case we consider both the Control and Data planes. +- The electricity consumption impact of the remaining product lifecycle aspects: datacenters and technical environment, network and cross-IT equipment & stocks. + +Since Object Storage is a regional product, we consider the energy mix of the country and the average PUE of data centers in the region to calculate the impact of a kwh. + +In the example below, the energy mix is O,065kgCo2e/kwh and the PUE is 1.16. Considering a server electrical consumption of 600wh, 100 hours of usage, and a `s3_ratio` of `0.19`, the total usage impact comes down to: + +```math +UsageImpact = 0.600 * 100 * 1.16 * 0.065v* 0.19 = 0.74 kgCo2e +``` + +In the example, the usage impact of a 100 GB usage for 100 hours is 0.74 kgCo2e. + diff --git a/pages/environmental-footprint/concepts.mdx b/pages/environmental-footprint/concepts.mdx index 1418e16d85..65a1357374 100644 --- a/pages/environmental-footprint/concepts.mdx +++ b/pages/environmental-footprint/concepts.mdx @@ -35,6 +35,8 @@ In the context of digital services, and more specifically cloud infrastructures 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. +Refer to the [calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page for a detailed description of how the environmental impact is calculated at Scaleway. + ## 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. @@ -77,4 +79,6 @@ The calculation is performed using the following formula: ``` WUE = Total Water Used (liters) ÷ Total IT Energy Consumption (kWh)​ -``` \ No newline at end of file +``` + +Refer to the [calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator/#water-consumption) documentation page for a detailed description of how water consumption is calculated. \ No newline at end of file diff --git a/pages/generative-apis/faq.mdx b/pages/generative-apis/faq.mdx index 99cd33b139..84010a2d6f 100644 --- a/pages/generative-apis/faq.mdx +++ b/pages/generative-apis/faq.mdx @@ -40,7 +40,7 @@ No, you cannot increase maximum output tokens above [limits for each models](/ge These limits are in place to protect you against: - Long generation which may be ended by an HTTP timeout. Limits are designed to ensure a model will send its HTTP response in less than 5 minutes. - Uncontrolled billing, as several models are known to be able to enter infinite generation loops (specific prompts can make the model generate the same sentence over and over, without stopping at all). -If you require higher maximum output tokens, you can use [Managed Inference](https://console.scaleway.com/inference/deployments) where these limts do not apply (as your bill will be limited by the size of your deployment). +If you require higher maximum output tokens, you can use [Managed Inference](https://console.scaleway.com/inference/deployments) where these limits do not apply (as your bill will be limited by the size of your deployment). ### Can I use OpenAI libraries and APIs with Scaleway's Generative APIs? Yes, Scaleway's Generative APIs are designed to be compatible with OpenAI libraries and SDKs, including the OpenAI Python client library and LangChain SDKs. This allows for seamless integration with existing workflows. diff --git a/pages/generative-apis/how-to/query-language-models.mdx b/pages/generative-apis/how-to/query-language-models.mdx index 72c31e7e73..ea5239835e 100644 --- a/pages/generative-apis/how-to/query-language-models.mdx +++ b/pages/generative-apis/how-to/query-language-models.mdx @@ -3,17 +3,17 @@ title: How to query language models description: 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: 2025-05-12 + validation: 2025-08-22 posted: 2024-08-28 --- import Requirements from '@macros/iam/requirements.mdx' - +import ChatCompVsResponsesApi from '@macros/ai/chat-comp-vs-responses-api.mdx' 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) +- Via the [Chat Completions API](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion) or the [Responses API](https://www.scaleway.com/en/developers/api/generative-apis/#path-responses-beta-create-a-response) @@ -39,10 +39,12 @@ The web playground displays. ## 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. +In the example that follows, we will use the OpenAI Python client. + +### Chat Completions API or Responses API? + + ### Installing the OpenAI SDK @@ -68,48 +70,97 @@ client = OpenAI( ### Generating a chat completion -You can now create a chat completion, for example with the `llama-3.1-8b-instruct` model: +You can now create a chat completion using either the Chat Completions or Responses API, as shown in the following examples: -```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) -``` + + + ```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_completion_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_completion_tokens`, and `top_p` parameters control the response's creativity, length, and diversity, respectively. + + + + + + ```python + # Create a chat completion using the 'gpt-oss-120b' model + response = client.responses.create( + model="gpt-oss-120b", + input=[{"role": "user", "content": "Briefly describe a futuristic city with advanced technology and green energy solutions."}], + temperature=0.2, # Adjusts creativity + max_output_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. Here, the last output message will contain the final content. + # Previous outputs will contain reasoning content. + print(response.output[-1].content[0].text) + ``` + + -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?" - } -] -``` + ```python + [ + { + "role": "system", + "content": "You are Xavier Niel." + }, + { + "role": "user", + "content": "Hello, what is your name?" + } + ] + ``` + +Adding such a system prompt can also help resolve issues if you receive responses such as `I'm not sure what tools are available to me. Can you please provide a library of tools that I can use to generate a response?`. ### 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. + + + + + - **`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_completion_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. + + See the [dedicated API documentation](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion) for a full list of all available parameters. + + + + + + - **`input`**: A single text string, or an array of string/multi-modal inputs to provide to the model to generate a response. When using the array option, you can define a `role` and list of `content` inputs of different types (texts, files, images etc.) + - **`max_output_tokens`**: A maximum number of output tokens that can be generated for a completion. Different default maximum values +are enforced for each model, to avoid edge cases where tokens are generated indefinitely. + - **`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. + - **`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`. + + See the [dedicated API documentation](https://www.scaleway.com/en/developers/api/generative-apis/#path-responses-beta-create-a-response) for a full list of all available parameters. + + + If you encounter an error such as "Forbidden 403" refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips. @@ -118,7 +169,8 @@ The following parameters will influence the output of the model: ## 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: + +Following is an example using the Chat Completions API, but the `stream` parameter can be set in the same way with the Responses API. ```python from openai import OpenAI @@ -145,28 +197,62 @@ for chunk in response: 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()) -``` + + + + + ```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 = 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()) + ``` + + + ```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.responses.create( + model="gpt-oss-120b", + input=[{ + "role": "user", + "content": "Sing me a song" + }], + stream=True, + ) + async for event in stream: + if event.type == "response.output_text.delta": + print(event.delta, end="") + elif event.type == "response.completed": + break + + 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 index cc7b1ef08e..1bac3e7330 100644 --- a/pages/generative-apis/how-to/query-vision-models.mdx +++ b/pages/generative-apis/how-to/query-vision-models.mdx @@ -8,7 +8,6 @@ dates: --- import Requirements from '@macros/iam/requirements.mdx' - Scaleway's Generative APIs service allows users to interact with powerful vision models hosted on the platform. @@ -17,7 +16,7 @@ Scaleway's Generative APIs service allows users to interact with powerful vision 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) +- The [Chat Completions API](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion). @@ -43,17 +42,16 @@ The web playground displays. ## 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 vision models programmatically using your favorite tools or languages. -You can query the vision models programmatically using your favorite tools or languages. Vision models take both text and images as inputs. +In the example that follows, we will use the OpenAI Python client. + 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: @@ -78,21 +76,21 @@ client = OpenAI( ### Generating a chat completion -You can now create a chat completion, for example with the `pixtral-12b-2409` model: +You can now create a chat completion: ```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. + {"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 @@ -127,7 +125,7 @@ To encode Base64 images in Python, you first need to install `Pillow` library: pip install pillow ``` -Then, the following Python code sample shows you how to encode an image in Base64 format and pass it to your request payload: +Then, the following Python code sample shows you how to encode an image in Base64 format and pass it to a request payload for the Chat Completions API: ```python import base64 @@ -165,9 +163,9 @@ payload = { ``` -### Model parameters and their effects +### Model parameters and their effects -The following parameters will influence the output of the model: +When using the Chat Completions API, 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. @@ -182,7 +180,8 @@ The following parameters will influence the output of the model: ## 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: + +An example for the Chat Completions API is provided below: ```python from openai import OpenAI @@ -192,15 +191,15 @@ client = OpenAI( 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, +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: @@ -208,9 +207,10 @@ for chunk in response: print(chunk.choices[0].delta.content, end="") ``` + ## Async -The service also supports asynchronous mode for any chat completion. +The service also supports asynchronous mode for any chat completion. An example for the Chat Completions API is provided below: ```python diff --git a/pages/generative-apis/how-to/use-function-calling.mdx b/pages/generative-apis/how-to/use-function-calling.mdx index 2bb3bb6397..f62b7ce712 100644 --- a/pages/generative-apis/how-to/use-function-calling.mdx +++ b/pages/generative-apis/how-to/use-function-calling.mdx @@ -3,13 +3,13 @@ title: How to use function calling description: Learn how to implement function calling capabilities using Scaleway's Chat Completions API service. tags: chat-completions-api dates: - validation: 2025-05-26 + validation: 2025-08-22 posted: 2024-09-24 --- import Requirements from '@macros/iam/requirements.mdx' -Scaleway's Chat Completions API supports function calling as introduced by OpenAI. +Scaleway's Chat Completions API supports function calling as introduced by OpenAI. The Responses API allows not only function calling, but also direct tool-calling by the model, e.g. web and file search. However currently only function calling is supported by Scaleway, as our support of Responses API is at beta stage. [Read more about Chat Completions vs Responses API](/generative-apis/how-to/query-language-models/#chat-completions-api-or-responses-api?). ## What is function calling? @@ -39,7 +39,7 @@ The workflow typically follows these steps: 4. Execute selected functions 5. Return results to model for final response -## Code examples +## Code example for Chat Completions API Before diving into the code examples, ensure you have the necessary libraries installed: @@ -48,7 +48,7 @@ The workflow typically follows these steps: ``` -We will demonstrate function calling using a flight scheduling system that allows users to check available flights between European airports. +We will demonstrate function calling with the Chat Completions API using a flight scheduling system that allows users to check available flights between European airports. ### Basic function definition @@ -152,42 +152,43 @@ As the model detects properly that a tool call is required to answer the questio 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. - + ### Call the tool and provide a final answer To provide the answer, or 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] +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) - # 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) + # 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 @@ -294,6 +295,11 @@ messages = [ ] ``` +## Code example for Responses API + +See the OpenAPI documentation for a fully worked example on [function calling using the Responses API](https://platform.openai.com/docs/guides/function-calling#function-tool-example). Note that Scaleway's support of the Responses API is currently at beta stage - [find out more](/generative-apis/how-to/query-language-models/#chat-completions-api-or-responses-api). + + ## Best practices When implementing function calling, follow these guidelines for optimal results: diff --git a/pages/generative-apis/how-to/use-structured-outputs.mdx b/pages/generative-apis/how-to/use-structured-outputs.mdx index c1c05fd6bf..7868f3d858 100644 --- a/pages/generative-apis/how-to/use-structured-outputs.mdx +++ b/pages/generative-apis/how-to/use-structured-outputs.mdx @@ -3,22 +3,22 @@ title: How to use structured outputs description: Learn how to get consistent JSON format responses using Scaleway's Chat Completions API service. tags: chat-completions-api dates: - validation: 2025-05-12 + validation: 2025-08-22 posted: 2024-09-17 --- import Requirements from '@macros/iam/requirements.mdx' - +import ChatCompVsResponsesApi from '@macros/ai/chat-comp-vs-responses-api.mdx' 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. +By specifying a response format when using the Chat Completions API or Responses 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) +- Via the [Chat Completions API](https://www.scaleway.com/en/developers/api/generative-apis/#path-chat-completions-create-a-chat-completion) or the [Responses API](https://www.scaleway.com/en/developers/api/generative-apis/#path-responses-beta-create-a-response) @@ -41,9 +41,13 @@ There are several ways to interact with language models: - JSON mode is older and has been used by developers since early API implementations, but lacks reliability in response formats. - - All LLMs in the Scaleway library support **Structured outputs** and **JSON mode**. However, a schemaless **JSON mode** will produce lower quality results and is not recommended. + - All LLMs in the Scaleway library support **Structured outputs** and **JSON mode**. However, a schemaless **JSON mode** will produce lower quality results and is not recommended. Note that structured output is more reliably validated and more richly parsed with the Responses API. +## Chat Completions API or Responses API? + + + ## Code examples @@ -55,80 +59,132 @@ There are several ways to interact with language models: The following Python examples demonstrate how to use **Structured outputs** to generate structured responses. -We are using the base code below to send our LLM a voice note transcript to structure: +We using the base code below to send our LLM a voice note transcript to structure: -```python -import json -from openai import OpenAI -from pydantic import BaseModel, Field +### Defining the voice note and transcript -# Set your preferred model -MODEL = "llama-3.1-8b-instruct" + ```python + import json + from openai import OpenAI + from pydantic import BaseModel, Field -# Set your API key -API_KEY = "" + # Set your preferred model + MODEL = "llama-3.1-8b-instruct" ## or "gpt-oss-120b" for the Responses API -client = OpenAI( - base_url="https://api.scaleway.ai/v1", - api_key=API_KEY, -) + # Set your 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." -) -``` + 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 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 using '{' as the first character.", - }, - { - "role": "user", - "content": TRANSCRIPT, + + + + ```python + extract = client.chat.completions.create( + messages=[ + { + "role": "system", + "content": "The following is a voice message transcript. Only answer in JSON using '{' as the first character.", + }, + { + "role": "user", + "content": TRANSCRIPT, + }, + ], + model=MODEL, + response_format={ + "type": "json_schema", + "json_schema": { + "name": "VoiceNote", + "schema": VoiceNote.model_json_schema(), + } }, - ], - 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" + ] + } + ``` + + + ```python + + extract = client.responses.create( + input=[ + { + "role": "system", + "content": "The following is a voice message transcript. Only answer in JSON using '{' as the first character.", + }, + { + "role": "user", + "content": TRANSCRIPT, + } + ], + model=MODEL, + text={ + "format": { + "type": "json_schema", + "name": "VoiceNote", + "schema": VoiceNote.model_json_schema() + } } - }, -) -output = json.loads(extract.choices[0].message.content) -print(json.dumps(output, indent=2)) -``` + ) + + # Print the generated response. Here, the last output message will contain the final content. + # Previous outputs will contain reasoning content. + output = json.loads(extract.output[-1].content[0].text) + print(json.dumps(output, indent=2)) + ``` + + Output example: + + ```json + { + "actionItems": [ + "Water the plants in the garden", + "Prepare a simple pasta dish with garlic bread", + "Catch up on missed phone calls while dinner is cooking" + ], + "summary": "The user plans to water plants, cook dinner, and make phone calls after arriving home at 6:30\u202fPM.", + "title": "Evening Tasks" + } + ``` + + -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" - ] -} -``` Structured outputs accuracy may vary between models. For instance, with Llama models, we suggest adding a description of the field looked for in `response_format` and in `system` or `user` messages. In our example this would mean adding a system prompt similar to: @@ -140,7 +196,7 @@ Output example: ### Using structured outputs with JSON schema (manual definition) -Alternatively, users can manually define the JSON schema inline when calling the model. +Alternatively, users can manually define the JSON schema inline when calling the model. See below an example for doing this with the Chat Completions API: ```python extract = client.chat.completions.create( @@ -182,13 +238,13 @@ print(json.dumps(output, indent=2)) Output example: ```json { - "title": "Evening Routine", - "actionItems": [ +"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" +], +"summary": "Made a list of tasks to accomplish before relaxing tonight" } ``` @@ -199,11 +255,10 @@ Output example: ### Using JSON mode (schemaless, Legacy method) - - When using the OpenAI SDKs as in the examples above, you are expected to set `additionalProperties` to false, and to specify all your properties as required. - - JSON mode: It is important to explicitly ask the model to generate a JSON output either in the system prompt or user prompt. To prevent infinite generations, model providers most often encourage users to ask the model for short JSON objects. Prompt example: `Only answer in JSON using '{' as the first character.`. + JSON mode: It is important to explicitly ask the model to generate a JSON output either in the system prompt or user prompt. To prevent infinite generations, model providers most often encourage users to ask the model for short JSON objects. Prompt example: `Only answer in JSON using '{' as the first character.`. -In JSON mode, you can prompt the model to output a JSON object without enforcing a strict schema. +In JSON mode, you can prompt the model to output a JSON object without enforcing a strict schema. See below an example for the Chat Completions API: ```python extract = client.chat.completions.create( @@ -229,21 +284,21 @@ print(json.dumps(output, indent=2)) Output example: ```json { - "current_time": "6:30 PM", - "tasks": [ +"current_time": "6:30 PM", +"tasks": [ { - "task": "water the plants in the garden", - "priority": "high" + "task": "water the plants in the garden", + "priority": "high" }, { - "task": "prepare dinner (pasta with garlic bread)", - "priority": "high" + "task": "prepare dinner (pasta with garlic bread)", + "priority": "high" }, { - "task": "catch up on phone calls", - "priority": "medium" + "task": "catch up on phone calls", + "priority": "medium" } - ] +] } ``` diff --git a/pages/generative-apis/index.mdx b/pages/generative-apis/index.mdx index 48e9e96d47..a48aad7e31 100644 --- a/pages/generative-apis/index.mdx +++ b/pages/generative-apis/index.mdx @@ -44,6 +44,14 @@ description: Dive into Scaleway Generative APIs with our quickstart guides, how- /> + + ## Changelog - 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) diff --git a/pages/generative-apis/reference-content/integrating-generative-apis-with-popular-tools.mdx b/pages/generative-apis/reference-content/integrating-generative-apis-with-popular-tools.mdx index caab856613..9269a5659e 100644 --- a/pages/generative-apis/reference-content/integrating-generative-apis-with-popular-tools.mdx +++ b/pages/generative-apis/reference-content/integrating-generative-apis-with-popular-tools.mdx @@ -3,7 +3,7 @@ title: Integrating Scaleway Generative APIs with popular AI tools description: Learn how to integrate Scaleway's Generative APIs with popular AI tools to unlock the full potential of your applications. tags: generative-apis ai language-models dates: - validation: 2025-02-18 + validation: 2025-08-26 posted: 2025-02-18 --- @@ -63,6 +63,10 @@ response = client.chat.completions.create( print(response.choices[0].message.content) ``` + +You can also use the [Responses API](https://www.scaleway.com/en/developers/api/generative-apis/#technical-information) as an alternative to Chat Completions, but note that Scaleway's support of this API is currently at beta stage. + + ## LangChain (RAG & LLM applications) LangChain is a popular library for building AI applications. Scaleway's Generative APIs support LangChain for both inference and embeddings. @@ -158,7 +162,7 @@ LlamaIndex is an open-source framework for building Large Language Models (LLMs) Make sure to replace `` with your actual API key. -3. You can then interact with the LLM by sending messages to the model with the following code: +3. Interact with the LLM by sending messages to the model with the following code: ```python response = llm.chat([ChatMessage("Could you tell me about Scaleway please ?")]) print(response) diff --git a/pages/gpu/how-to/use-gpu-with-docker.mdx b/pages/gpu/how-to/use-gpu-with-docker.mdx index 0461eb5ef6..cbcbd50f5a 100644 --- a/pages/gpu/how-to/use-gpu-with-docker.mdx +++ b/pages/gpu/how-to/use-gpu-with-docker.mdx @@ -13,7 +13,7 @@ Docker is a platform as a service (PaaS) tool that uses OS-level virtualization 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. +All [Scaleway GPU Instances](/gpu/reference-content/choosing-gpu-instance-type/) 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. diff --git a/pages/gpu/how-to/use-mig-with-kubernetes.mdx b/pages/gpu/how-to/use-mig-with-kubernetes.mdx index 696c9a1f99..eec6d316a4 100644 --- a/pages/gpu/how-to/use-mig-with-kubernetes.mdx +++ b/pages/gpu/how-to/use-mig-with-kubernetes.mdx @@ -24,7 +24,7 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete - 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 +- A [Kubernetes cluster](/kubernetes/quickstart/#how-to-create-a-kubernetes-cluster) with a [GPU Instance](/gpu/reference-content/choosing-gpu-instance-type/) as node MIG is fully supported on [Scaleway managed Kubernetes](/kubernetes/quickstart/) clusters (Kapsule and Kosmos). diff --git a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx index f21e31b600..95805345be 100644 --- a/pages/gpu/reference-content/choosing-gpu-instance-type.mdx +++ b/pages/gpu/reference-content/choosing-gpu-instance-type.mdx @@ -16,7 +16,7 @@ It empowers European AI startups, giving them the tools (without the need for a ## 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 SXM Instances](https://www.scaleway.com/en/gpu-instances/) 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. +Scaleway provides a range of GPU Instance offers, from [GPU RENDER Instances](https://www.scaleway.com/en/gpu-render-instances/) and [H100 SXM Instances](/gpu/reference-content/choosing-gpu-instance-type/) 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). @@ -28,7 +28,7 @@ Below, you will find a guide to help you make an informed decision: * **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. - * Or better, an HGX-based server setup with up to 8x NVlink GPUs with [H100-SXM Instances](https://www.scaleway.com/en/gpu-instances/) + * Or better, an HGX-based server setup with up to 8x NVlink GPUs with [H100-SXM Instances](/gpu/reference-content/choosing-gpu-instance-type/) * 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 or H100-SXM 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. @@ -108,6 +108,10 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | 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 | | | | | + + The service level objective (SLO) for all GPU Instance types (except H100-SXM) is 99.5% availability. [Read the SLA](https://www.scaleway.com/en/virtual-instances/sla/). + + ### 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) | |---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| diff --git a/pages/iam/concepts.mdx b/pages/iam/concepts.mdx index 4bea52d5ac..2a347b5672 100644 --- a/pages/iam/concepts.mdx +++ b/pages/iam/concepts.mdx @@ -19,12 +19,16 @@ The diagram above shows how different IAM concepts mentioned on this page intera A user account refers to a human who owns a Scaleway account. Your account bears your personal information and authentication methods required to access the [Scaleway console](https://console.scaleway.com/). When you create your Scaleway account, an [Organization](#organization) is automatically created with you as the designated Owner. You can also be added to an existing Organization as a Member and have an account that exists only within that Organization. +Refer to the [How to create an account](/account/how-to/create-an-account) documentation page for more information. + ## Application An application (also known as an IAM application) is a non-human user in an [Organization](#organization). IAM applications can be used when you want to create an API key that is not linked to a user, to give programmatic access to resources. Note that applications cannot, by definition, have access to the Scaleway console, as they have only an API key and no account themselves (they are not [accounts](#account)). +Refer to the [Users, groups and applications](/iam/reference-content/users-groups-and-applications) and [How to manage applications](/iam/how-to/manage-applications) documentation pages for more information. + ## API key An API key is a unique identifier, used to authenticate requests made to the [Scaleway API](https://www.scaleway.com/en/developers/api/). An API key consists of an access key and a secret key. The access key is like a unique ID or username, and is not a sensitive piece of information. The secret key is more sensitive as it is like a password to authenticate the access key. @@ -49,6 +53,8 @@ The grace period is the time an [IAM Member](#members) has to comply with the se A group (also known as an IAM group) is a grouping of [users](#user) and/or [applications](#application). Creating groups allows you to attach [policies](#policy) to multiple users and/or applications at the same time. +Refer to the [Users, groups and applications](/iam/reference-content/users-groups-and-applications) and [How to manage groups](/iam/how-to/manage-groups) documentation pages for more information. + ## IAM **I**dentity and **A**ccess **M**anagement allows you to share access to the management of your Scaleway [resources](#resource) in a controlled and secure manner. @@ -93,12 +99,17 @@ Permission set names contain descriptions that clearly explain their purpose. Fo Permissions sets (e.g.`InstanceReadAccess`) and their [scope](#scope) (e.g. "on Project A only") make up IAM rules, which define the access rights that a [principal](#principal) (user, group, or application) should have. + +Refer to the [Permission sets](/iam/reference-content/permission-sets) reference page for an extensive list of the available permission sets. + ## Policy -Policies control user rights by defining one or more [rules](#rule) to apply to the attached [principals](#principal) (users, groups, or applications). A policy rule has two parts: [permission set](#permission-set) and [scope](#scope). +Policies control user rights by defining one or more [rules](#rule) to apply to the attached [principals](#principal) (users, groups, or applications). A policy rule has two parts: [permission set](#permission-set), [scope](#scope) and [conditions](#conditions). For each policy rule, you specify one or more permission sets (e.g. "list all Instances") and their scope (e.g. "on Project A only"). This therefore defines the actions that the principles can carry out on resources within the scope. +Refer to the [Understanding IAM Policies](/iam/reference-content/policy) and the [How to manage a policy](/iam/how-to/manage-policies) documentation pages for more information. + ## Preferred Project You can carry out actions on Scaleway Object Storage resources either via the [Scaleway console](https://console.scaleway.com), or via a third-party API or CLI, such as [the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIOClient](/object-storage/api-cli/installing-minio-client/) or [Rclone](/object-storage/api-cli/installing-rclone/). While the Scaleway console gives you the option to specify the [Scaleway Project](/organizations-and-projects/concepts/#project) to carry out your Object Storage actions in, this option is not available via third-party API/CLI tools. These tools are based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services), which does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. See our page on [using API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) for more information. @@ -115,6 +126,8 @@ Projects are groupings of Scaleway [resources](#resource). Every Scaleway Organi For example, if IAM users within your [Organization](#organization) are working on building two different systems with Scaleway resources, you can group the resources for each system into different Projects. This then allows you to restrict [IAM users'](#user) access to only the Project they are working on. It also facilitates the separation of billing between Projects. +Refer to the [How to create a Project](/organizations-and-projects/how-to/create-a-project) documentation page for more information. + ## Resource A Scaleway resource is either a product or a feature in the Scaleway Ecosystem. Examples of resources include Instances, Private Networks, Kubernetes Kapsule and Flexible IPs, to name a few. @@ -152,4 +165,6 @@ A user (also known as an IAM user) is a human user in an Organization. They can - **Owner**: You are the Owner of the [Organization](#organization) that was created with your account. - **Member**: You are a Member when you are added to an Organization by an Owner or user with IAM Manager permissions. Members exist only within the specific Organizations in which they are created. -Within each Organization, different IAM users can have different rights (defined through [policies](#policy)) to perform actions on resources. \ No newline at end of file +Within each Organization, different IAM users can have different rights (defined through [policies](#policy)) to perform actions on resources. + +Refer to the [Users, groups and applications](/iam/reference-content/users-groups-and-applications) reference page for more information. \ No newline at end of file diff --git a/pages/iam/how-to/enforce-security-requirements-members.mdx b/pages/iam/how-to/enforce-security-requirements-members.mdx index 2396ec6a76..e24a43613a 100644 --- a/pages/iam/how-to/enforce-security-requirements-members.mdx +++ b/pages/iam/how-to/enforce-security-requirements-members.mdx @@ -2,7 +2,7 @@ title: How to enforce security requirements for IAM members in your Organization description: This page shows you how to edit the grace period IAM members have to comply with security requirements and enforce password renewal. dates: - validation: 2025-02-11 + validation: 2025-08-25 posted: 2025-02-11 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx index 416b7840c2..12b24aa00d 100644 --- a/pages/instances/api-cli/migrating-instances.mdx +++ b/pages/instances/api-cli/migrating-instances.mdx @@ -19,7 +19,7 @@ To do so, you need the Instance’s ID and a valid API key. - An [Instance](/instances/how-to/create-an-instance/), which must be stopped and not be in a placement group - Network interface names may vary across commercial families (e.g. ENT1 vs. POP2). Ensure that any hardcoded interface names in your configurations or scripts are updated to avoid migration issues. + Network interface names may vary across commercial families. Ensure that any hardcoded interface names in your configurations or scripts are updated to avoid migration issues. diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx index 67cbd3487b..09289ab86a 100644 --- a/pages/instances/concepts.mdx +++ b/pages/instances/concepts.mdx @@ -13,6 +13,10 @@ import Region from '@macros/concepts/region.mdx' import Volumes from '@macros/concepts/volumes.mdx' import StorageBootOnBlock from '@macros/storage/boot-on-block.mdx' +## ARM Instances + +[ARM Instances](/instances/reference-content/understanding-differences-x86-arm/) are cost-effective and energy-efficient Instances powered by Ampere Altra processors, optimized for AI innovation, real-time applications, and sustainable cloud computing. + ## Availability Zone @@ -30,13 +34,9 @@ import StorageBootOnBlock from '@macros/storage/boot-on-block.mdx' 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. +[Development Instances](/instances/reference-content/development/) are reliable and flexible Instances tuned to host your websites, applications, and development environments. ## Dynamic IP @@ -48,9 +48,13 @@ You can choose to give your Instance a dynamic IP address when creating or updat 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). +## General Purpose Instances + +[General Purpose Instances](/instances/reference-content/general-purpose/) are production-grade [Instances](#instance) designed for scalable infrastructures. Development Instances support the boot-on-block feature and allow you to launch high-performance services with high-end CPUs. + ## 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. +[GPU Instances](/gpu/reference-content/choosing-gpu-instance-type/) are powerful Instances equipped with dedicated high-end Nvidia graphics processing units. See our [dedicated GPU documentation](/gpu/) for more details. ## Image @@ -64,10 +68,6 @@ An Instance is a virtual computing unit that offers resources for running applic 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. -## 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 @@ -76,16 +76,6 @@ An InstantApp is an image with a preinstalled application. By choosing an Instan 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. @@ -159,3 +149,7 @@ Tags allow you to organize, sort, filter, and monitor your cloud resources using ## Volumes + +## x86 (Intel/AMD) Instances + +[x86 (Intel/AMD) Instances](/instances/reference-content/understanding-differences-x86-arm/) are reliable and high-performance Instances powered by AMD EPYC processors, tailored for development, testing, production workloads, and general-purpose applications. \ No newline at end of file diff --git a/pages/instances/faq.mdx b/pages/instances/faq.mdx index 095cadde45..bd42e5f0dd 100644 --- a/pages/instances/faq.mdx +++ b/pages/instances/faq.mdx @@ -59,16 +59,10 @@ You can change the storage type and flexible IP after the Instance creation, whi * PAR3 prices are shown separately. -**Learning Instances** | Range | Price for all regions* | Price for PAR3 | |-------------------|------------------------|-------------------| | STARDUST1-S | €0.0046/hour | Not available | - -**Cost-Optimized Instances** - -| Range | Price for all regions* | Price for PAR3 | -|-------------------|------------------------|-------------------| | COPARM1-2C-8G | €0.0426/hour | Not available | | COPARM1-4C-16G | €0.0857/hour | Not available | | COPARM1-8C-32G | €0.1724/hour | Not available | @@ -91,11 +85,6 @@ You can change the storage type and flexible IP after the Instance creation, whi | DEV1-M | €0.0256/hour | Not available | | DEV1-L | €0.0495/hour | Not available | | DEV1-XL | €0.0731/hour | Not available | - -**Production-Optimized Instances** - -| Range | Price for all regions* | Price for PAR3 | -|-------------------|------------------------|-------------------| | POP2-2C-8G | €0.0735/hour | €0.1103/hour | | POP2-4C-16G | €0.147/hour | €0.2205/hour | | POP2-8C-32G | €0.29/hour | €0.435/hour | @@ -103,15 +92,8 @@ You can change the storage type and flexible IP after the Instance creation, whi | POP2-32C-128G | €1.18/hour | €1.77/hour | | POP2-48C-192G | €1.77/hour | €2.655/hour | | POP2-64C-256G | €2.35/hour | €3.525/hour | -| ENT1-XXS | €0.0735/hour | €0.11/hour | -| ENT1-XS | €0.147/hour | €0.221/hour | -| ENT1-S | €0.29/hour | €0.44/hour | -| ENT1-M | €0.59/hour | €0.88/hour | -| ENT1-L | €1.18/hour | €1.76/hour | -| ENT1-XL | €2.35/hour | €3.53/hour | -| ENT1-2XL | €3.53/hour | €5.29/hour | -**Production-Optimized Instances with Windows Server operating system** +**General Purpose Instances with Windows Server operating system** | Range | Price for all regions* | Price for PAR3 | |-------------------|------------------------|-------------------| @@ -121,7 +103,7 @@ You can change the storage type and flexible IP after the Instance creation, whi | POP2-16C-64G-WIN | €1.4567/hour | Not available | | POP2-32C-128-WIN | €2.9133/hour | Not available | -**Workload-Optimized Instances** +**Specialized Instances** | Range | Price for all regions* | Price for PAR3 | |-------------------|------------------------|-------------------| @@ -267,25 +249,12 @@ You are free to bootstrap your own distribution. We provide a wide range of different Linux distributions and InstantApps for Instances. Refer to [Scaleway Instance OS images and InstantApps](/instances/reference-content/images-and-instantapps/) for a complete list of all available OSes and InstantApps. -### What are the differences between ENT1 and POP2 Instances? - -Both ENT1 and POP2 Instance types share the following features: -- Identical hardware specifications -- Dedicated vCPU allocation -- Same pricing structure -- Accelerated booting process - -POP2 Instances provide CPU- and memory-optimized variants tailored to suit your workload requirements more effectively. The primary distinction between ENT1 and POP2 lies in [AMD Secure Encrypted Virtualization (SEV)](https://www.amd.com/fr/developer/sev.html), which is disabled for POP2 Instances. -By choosing POP2 Instances, you gain access to the latest features, such as the potential for live migration of Instances in the future, ensuring that your infrastructure remains aligned with evolving demands and technological advancements. -We recommend choosing POP2 Instances for most general workloads unless your specific workload requires features unique to ENT1 Instances. - ### Where are my Instances located? Scaleway offers different Instance ranges in all regions: Paris (France), Amsterdam (Netherlands), and Warsaw (Poland). Check the [Instances availability guide](/account/reference-content/products-availability/) to discover where each Instance type is available. - ### What makes FR-PAR-2 a sustainable region? `FR-PAR-2` is our sustainable and environmentally efficient Availability Zone (AZ) in Paris. diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index c86808b82b..073f308ca1 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -67,7 +67,7 @@ Select a tab below for instructions on how to create an Instance via either our 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** Instance type from the **General Purpose** 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. diff --git a/pages/instances/how-to/migrate-instances.mdx b/pages/instances/how-to/migrate-instances.mdx index 59cea18f74..92481bdfc2 100644 --- a/pages/instances/how-to/migrate-instances.mdx +++ b/pages/instances/how-to/migrate-instances.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -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. +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. 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/). @@ -30,9 +30,9 @@ Follow the instructions to [create an image](/instances/how-to/create-a-backup/# 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. +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. + - You are free to choose your Instance type as long it uses the same CPU architecture (e.g. ARM to ARM or x86 to x86) - 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. @@ -42,13 +42,13 @@ Next, we will move the original DEV1-S Instance's [flexible IP address](/instanc 1. Click **CPU & GPU 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**. +3. Click next to the Instance's flexible IP. In the pop-up menu that then displays, click **Switch Instance**. +4. Select the new 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/). +Presuming that you no longer need the original Instance, you can [delete it](/instances/how-to/delete-instance/). diff --git a/pages/instances/reference-content/assets/windows.webp b/pages/instances/reference-content/assets/windows.webp new file mode 100644 index 0000000000..a348002bac Binary files /dev/null and b/pages/instances/reference-content/assets/windows.webp differ diff --git a/pages/instances/reference-content/choosing-instance-type.mdx b/pages/instances/reference-content/choosing-instance-type.mdx index 7627f5fc7a..14a162f70d 100644 --- a/pages/instances/reference-content/choosing-instance-type.mdx +++ b/pages/instances/reference-content/choosing-instance-type.mdx @@ -4,7 +4,7 @@ description: Find out how to select the ideal Scaleway Instance type for your sp dates: validation: 2025-05-15 posted: 2023-02-20 -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 +tags: instance comparison vcpu ram core --- Scaleway **CPU & GPU 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. @@ -13,7 +13,7 @@ Scaleway **CPU & GPU Instances** are virtual machines in the cloud. You can crea 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. +You may not need a super powerful Instance if you just want to play around and do some experiments for personal projects, so a **Development** 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 **General Purpose** Instance, precisely designed to reliably handle this type of demanding workload. ## Instance technical specifications @@ -47,35 +47,20 @@ The table below shows the different ranges of Instances at Scaleway and their sp 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](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Shared vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | -| **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 | +| **Instance range** | [Development](/instances/reference-content/development/) | [General Purpose](/instances/reference-content/general-purpose/) | [Compute Optimized](/instances/reference-content/specialized/) | [Memory Optimized](/instances/reference-content/specialized/) | +|-----------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| **Use cases** | 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 | Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases | +| **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage | Resilient Block Storage | Resilient Block Storage | +| **vCPU** | From 1 to 48 cores | From 1 to 64 cores | From 2 to 64 cores | From 2 to 64 cores | +| **Shared/Dedicated** | [Shared vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) | [Shared vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#shared-vcpu-instances) or [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | [Dedicated vCPU](/instances/reference-content/choosing-shared-vs-dedicated-cpus/#dedicated-vcpu-instances) | +| **RAM** | From 2 GiB to 256 GiB | From 2 GiB to 384 GiB | From 4 GiB to 512 GiB | From 4 GiB to 512 GiB | +| **Maximum Bandwidth** | From 200 Mbps to 10 Gbps | From 100 Mbps to 12.8 Gbps | From 400 Mbps to 12.8 Gbps | From 400 Mbps to 12.8 Gbps Refer to the tabs below to compare the different Instance ranges and learn more about their key use cases: - - Scaleway Learning Instances are virtual machines tailored for educational use, providing an ideal environment for discovering and experimenting with cloud computing. - Perfect for hosting small, self-contained applications like a LAMP website, code repository backups, or an internal wiki, these Instances eliminate the need to overpay for minimal personal projects. - - Key use cases include: - * Personal or low-traffic websites - * Blogs - * Development and test environments - * Microservice hosting - * Repository hosting - - Each Instance comes equipped with a single shared vCPU, 1 GB of RAM, and up to 100 Mbps of bandwidth. By adding an IPv4 address and 10 GB of storage, you can get started immediately. You can create up to one Instance per Availability Zone, currently available in FR-PAR-1, NL-AMS-1 and PL-WAW-2. - - Learn more about [Learning Instances](/instances/reference-content/learning/) - - - Scaleway Cost-Optimized Instances are highly reliable and affordably priced, making them an ideal choice for businesses looking to balance operational flexibility, cost-efficiency, and performance. + + Scaleway Development Instances are highly reliable and affordably priced, making them an ideal choice for businesses looking to balance operational flexibility, cost-efficiency, and performance. Designed for lightweight applications, development environments, and low-intensity workloads, these Instances offer a budget-friendly cloud solution. Key use cases include: @@ -85,13 +70,13 @@ Refer to the tabs below to compare the different Instance ranges and learn more * Hosting worker nodes in container ecosystems * CI/CD runners - Cost-Optimized Instances provide a cost-efficient yet powerful compute platform suitable for both development and light production use. Equipped with shared AMD EPYC™ vCPUs and ranging from 2 GiB to 128 GiB of RAM, they cater to a wide array of workloads with solid performance. + Development Instances provide a cost-efficient yet powerful compute platform suitable for both development and light production use. Equipped with shared AMD EPYC™ vCPUs and ranging from 2 GiB to 128 GiB of RAM, they cater to a wide array of workloads with solid performance. - Learn more about [Cost-Optimized Instances](/instances/reference-content/cost-optimized/) + Learn more about [Development Instances](/instances/reference-content/development/) - - Scaleway Production-Optimized Instances are reliable, high-performance Instances with dedicated vCPUs, designed for the most demanding workloads and mission-critical applications. Leveraging the state-of-the-art AMD EPYC™ 7003 series processors, they deliver exceptional performance and production-grade computing. + + Scaleway General Purpose Instances are reliable, high-performance Instances with shared or dedicated vCPUs, designed for the most demanding workloads and mission-critical applications. Leveraging the state-of-the-art AMD EPYC™ 7003 series processors, they deliver exceptional performance and production-grade computing. Designed for critical production environments and high-traffic applications, these Instances prioritize performance and reliability with an optimal mix of compute, memory, and network resources. Key use cases include: @@ -100,12 +85,12 @@ Refer to the tabs below to compare the different Instance ranges and learn more * Data analytics and business intelligence applications * Hosting of Software-as-a-Service (SaaS) platforms - Production-Optimized Instances provide high performance, security, and scalability, enabling organizations to efficiently manage high-traffic applications and build resilient architectures. Features like CPU pinning ensure optimized performance and reliability for your production workloads. + General Purpose Instances provide high performance, security, and scalability, enabling organizations to efficiently manage high-traffic applications and build resilient architectures. Features like CPU pinning ensure optimized performance and reliability for your production workloads. - Learn more about [Production-Optimized Instances](/instances/reference-content/production-optimized/) + Learn more about [General Purpose Instances](/instances/reference-content/general-purpose/) - - Scaleway Workload-Optimized Instances are designed to handle specific types of workloads efficiently, meeting the demands of applications that require high CPU or memory resources. These Instances are ideal for running compute-intensive or memory-intensive applications such as data analytics, high-performance databases, and machine learning inference. + + Scaleway Specialized Instances are designed to handle specific types of workloads efficiently, meeting the demands of applications that require high CPU or memory resources. These Instances are ideal for running compute-intensive or memory-intensive applications such as data analytics, high-performance databases, and machine learning inference. Tailored for businesses with fluctuating needs, these Instances allow for optimal use of resources and cost-effectiveness. Two variants are on offer: @@ -122,9 +107,9 @@ Refer to the tabs below to compare the different Instance ranges and learn more * Machine learning * Batch processing - Workload-Optimized Instances precisely tailor your computing resources to your application’s needs, ensuring you neither overspend nor underperform. Whether managing CPU-intensive data analytics or memory-hungry databases, these Instances adapt to your workloads, providing a balanced, cost-effective, and high-performing cloud computing solution ready to meet your specific business challenges. + Specialized Instances precisely tailor your computing resources to your application’s needs, ensuring you neither overspend nor underperform. Whether managing CPU-intensive data analytics or memory-hungry databases, these Instances adapt to your workloads, providing a balanced, cost-effective, and high-performing cloud computing solution ready to meet your specific business challenges. - Learn more about [Workload-Optimized Instances](/instances/reference-content/workload-optimized/) + Learn more about [Specialized Instances](/instances/reference-content/specialized/) diff --git a/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx b/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx index ccb12232db..a67fb9b673 100644 --- a/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx +++ b/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx @@ -29,7 +29,7 @@ Understanding the difference between these two techniques is key to making an in ## Shared vCPU Instances -Shared vCPU Instances, including [Learning](/instances/reference-content/learning/) and [Cost-Optimized](/instances/reference-content/cost-optimized/), are cost-effective virtual machines in which CPU resources are shared among multiple Instances. +Shared vCPU Instances, including [Development](/instances/reference-content/development/) and some [General Purpose](/instances/reference-content/general-purpose/) Instances, are cost-effective virtual machines in which CPU resources are shared among multiple Instances. This means that while each Instance gets its own vCPUs, these vCPUs are scheduled on physical cores that are shared across multiple Instances. @@ -56,7 +56,7 @@ While physical CPU threads are shared between Instances, vCPUs are dedicated to ## Dedicated vCPU Instances -Dedicated vCPU Instances, including [Production-Optimized](/instances/reference-content/production-optimized/) and [Workload-Optimized](/instances/reference-content/workload-optimized/), provide exclusive access to physical CPU cores. +Dedicated vCPU Instances, including selected [General Purpose](/instances/reference-content/general-purpose/), [Compute Optimized](/instances/reference-content/specialized/), and [Memory Optimized](/instances/reference-content/specialized/) Instances provide exclusive access to physical CPU cores. This ensures consistent and predictable performance at all times. Dedicated vCPU Instances are perfect for applications that require high CPU utilization and low latency. diff --git a/pages/instances/reference-content/cost-optimized.mdx b/pages/instances/reference-content/cost-optimized.mdx deleted file mode 100644 index d29bdfe3a6..0000000000 --- a/pages/instances/reference-content/cost-optimized.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -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. -dates: - validation: 2025-03-19 - posted: 2023-02-22 -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](/block-storage/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/development.mdx b/pages/instances/reference-content/development.mdx new file mode 100644 index 0000000000..f7b2fed2e3 --- /dev/null +++ b/pages/instances/reference-content/development.mdx @@ -0,0 +1,46 @@ +--- +title: The right Instance for development purposes +description: Discover Scaleway's development range of Instances, including options like the Stardust Instance, ideal for educational purposes. +dates: + validation: 2025-07-15 + posted: 2023-02-22 +tags: instance type stardust range development 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 Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/instances/concepts/#instantapp). + +## Development Instances + +Scaleway's **Development** range includes DEV1 and GP1 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: + +| Range | Development | +|:--------------------------------|:------------------------------------------------------------------------------| +| 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 48 vCPUs
From 2 to 256 GiB RAM | +| vCPU:RAM ratio | Various
(1:1, 1:2, 1:3) | + +## 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](/block-storage/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 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/) +- [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/enabling-dhcp-network-configuration-windows-server-2022.mdx b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx new file mode 100644 index 0000000000..15ba4cbfb0 --- /dev/null +++ b/pages/instances/reference-content/enabling-dhcp-network-configuration-windows-server-2022.mdx @@ -0,0 +1,180 @@ +--- +title: Enabling DHCP network configuration for Windows Server 2022 Instances +description: This page helps you to enable DHCP network configuration for Windows Server 2022 Instances +tags: windows instance dhcp console +dates: + validation: 2025-08-25 + posted: 2023-08-25 +--- +import Requirements from '@macros/iam/requirements.mdx' + + +The latest Windows Server 2022 and Windows Server 2022 Core images on Scaleway Instances now use DHCP for network configuration by default. This aligns with the standard mechanism used across all Scaleway Instance OS images. + +For existing running Instances, no changes to network configuration are necessary unless you plan to update the public IPv4 address. In such cases, the Instance may retain its static network configuration, continuing to use the previous public IPv4 address. +Follow the steps below to switch to DHCP, ensure the new address is applied correctly, and enable DHCP before assigning the new IP. + + + These steps involve modifying network settings, which carry a risk of losing network connectivity (e.g., SSH or RDP access). To avoid this, enable and configure Serial Console access on your Instance beforehand. This allows you to maintain access via the Scaleway console even if standard network connections fail. + + + + +- 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/) running on Windows Server 2022 + + +## Enabling Serial Console access + +Scaleway provides a Serial Console (TTY) for Instances, which is essential for troubleshooting network issues. +For Windows Server Instances, you must configure the OS to enable the Special Administration Console (SAC) for serial access. + +### Enabling SAC on Windows (OS configuration) + +Connect to your Windows Instance via RDP or another method and run the following commands in an elevated Command Prompt (Administrator) or PowerShell: + +1. Enable Emergency Management Services (EMS): + ``` + bcdedit /emssettings EMSPORT:1 + bcdedit /ems {current} on + ``` + +2. (Optional, but recommended) Enable the boot menu in the Serial Console: + ``` + bcdedit /set {bootmgr} displaybootmenu yes + bcdedit /set {bootmgr} timeout 10 + bcdedit /set {bootmgr} bootems yes + ``` + +3. Reboot the Instance to apply the changes: + ``` + shutdown /r /t 0 + ``` + +For more details, refer to [Microsoft's Azure Serial Console for Windows](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/serial-console-windows) documentation on enabling Serial Console for Windows VMs. + +### Accessing the Serial Console via Scaleway console + +1. Log in to the [Scaleway console](https://console.scaleway.com/). +2. Navigate to **Compute** > **CPU & GPU Instances**. +3. Click on the Instance you want to configure. +4. On the Instance **Overview** page, click **Console** to open the Serial Console in a pop-up window. +5. Once connected, you should see the SAC prompt. Use commands like `cmd` to start a command channel, then `ch -si 1` to switch to it. + +For more information on using the Scaleway Serial Console, see [How to use the Serial Console to connect to an Instance](/instances/how-to/use-serial-console/). + +## Steps to enable DHCP configuration + +Once Serial Console access is confirmed, configure DHCP using the Server Configuration tool (sconfig) on your Windows Instance. You can access sconfig via RDP, PowerShell, or the Serial Console. + + + The reboot of the Instance is required for full activation. + + +1. Open an elevated Command Prompt (Administrator) or PowerShell and run: + ``` + sconfig + ``` + +2. In the sconfig menu, select option **8** (Network settings). + +3. Select the network adapter index (usually **1** for the primary adapter). + +4. Select option **1** (Set network adapter address). + +5. Choose **D** for DHCP. + +6. The system will apply the changes and release any existing DHCP lease. + +7. Return to the main menu and select option **13** (Restart server) to reboot and activate the configuration. + +Below is an example interaction for reference: + +```sh +=============================================================================== + Welcome to Windows Server 2022 Datacenter +=============================================================================== + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + +Enter number to select an option: 8 +=============================================================================== + Network settings +=============================================================================== + +Available network adapters: + +Index # | IP address | Description +1 | 1.1.1.1 | Red Hat VirtIO Ethernet Adapter + +Select network adapter index # (Blank=Cancel): 1 +=============================================================================== + Network adapter settings +=============================================================================== + +NIC index: 1 +Description: Red Hat VirtIO Ethernet Adapter +IP address: 1.1.1.1, + fe80::dc00:ff:ff:ff:ff:ff +Subnet mask: 255.255.255.255 +DHCP enabled: False + +Default gateway: 62.210.0.1 +Preferred DNS server: +Alternate DNS server: + + 1) Set network adapter address + 2) Set DNS servers + 3) Clear DNS server settings + +Enter selection (Blank=Cancel): 1 +Select (D)HCP or (S)tatic IP address (Blank=Cancel): D +Setting NIC to use DHCP... +Successfully set gateway. +Successfully enabled DHCP. +Successfully released DHCP lease.. : 00-01-00-01-30-3E-73-36-DE-00-00-84-DB-2B +(Press ENTER to continue): +=============================================================================== + Welcome to Windows Server 2022 Datacenter +=============================================================================== + + 1) Domain/workgroup: Workgroup: WORKGROUP + 2) Computer name: WIN-010DQB68HIR + 3) Add local administrator + 4) Remote management: Enabled + + 5) Update setting: Download only + 6) Install updates + 7) Remote desktop: Enabled (all clients) + + 8) Network settings + 9) Date and time + 10) Telemetry setting: Required + 11) Windows activation + + 12) Log off user + 13) Restart server + 14) Shut down server + 15) Exit to command line (PowerShell) + +Enter number to select an option: 13 +Are you sure you want to restart? (Y)es or (N)o: Y +``` diff --git a/pages/instances/reference-content/general-purpose.mdx b/pages/instances/reference-content/general-purpose.mdx new file mode 100644 index 0000000000..b8cce0f849 --- /dev/null +++ b/pages/instances/reference-content/general-purpose.mdx @@ -0,0 +1,76 @@ +--- +title: The right Instance for production purposes +description: Find out more about Instances from Scaleway's General Purpose range. +dates: + validation: 2025-03-03 + posted: 2023-02-22 +tags: instance type production general purpose range POP +--- + +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). + +## POP2 Instances + +Scaleway's **General Purpose** 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 General Purpose Instances: + +| Range | General Purpose | +|:--------------------------------|:------------------------------------------------------------------------------| +| 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 | + +## PLAY2 Instances and PRO2 Instances + +In the same **General Purpose** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of General Purpose and General Purpose Instances. They offer 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 | General Purpose | +|:--------------------------------|:------------------------------------------------------------------------------| +| 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 + +COP-ARM Instances are an innovative option, 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 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 | General Purpose | +|:--------------------------------|:------------------------------------------------------------------------------| +| 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 General Purpose 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](/block-storage/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 General Purpose 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/historical-offers.mdx b/pages/instances/reference-content/historical-offers.mdx new file mode 100644 index 0000000000..aa02a7edb6 --- /dev/null +++ b/pages/instances/reference-content/historical-offers.mdx @@ -0,0 +1,32 @@ +--- +title: Historical Instances offering +description: Discover a list of historiacal Instance offers. These offers have reached their End of Life and are no longer available. +tags: instance +dates: + validation: 2025-08-28 + posted: 2025-08-28 +--- + +Below you find a list of historical Instance offers. These offers have reached their End of Life and are no longer available for new deployments. + +## ENT1 Instances + +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 | General Purpose | +|:--------------------------------|:------------------------------------------------------------------------------| +| 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 | + + diff --git a/pages/instances/reference-content/images-and-instantapps.mdx b/pages/instances/reference-content/images-and-instantapps.mdx index 65f0b195e2..0d2811247d 100644 --- a/pages/instances/reference-content/images-and-instantapps.mdx +++ b/pages/instances/reference-content/images-and-instantapps.mdx @@ -13,6 +13,7 @@ import centos from './assets/centos.webp' import fedora from './assets/fedora.webp' import rockylinux from './assets/rockylinux.webp' import almalinux from './assets/almalinux.webp' +import windows from './assets/windows.webp' import nextcloud from './assets/nextcloud.webp' import gitlab from './assets/gitlab.webp' import openvpn from './assets/openvpn.webp' @@ -34,7 +35,7 @@ Scaleway manages the deployment and maintenance of these OS images, ensuring the | | **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) | - +| | **Windows Server 2022** the latest long-term support (LTSC) version of Microsoft's enterprise-grade server operating system, offers enhanced security, performance, and hybrid cloud capabilities with ongoing updates through mainstream support until October 2026.
[Deploy Windows Server 2022](https://console.scaleway.com/instance/servers/create?imageKey=1b38cd96-9e7c-428e-8d2f-484058b284cd&zone=fr-par-1&offerName=POP2-2C-8G-WIN&tab=Production-Optimized&distribution=microsoft_windows_server) ## InstantApps An InstantApp allows you to deploy pre-configured applications quickly. diff --git a/pages/instances/reference-content/instances-datasheet.mdx b/pages/instances/reference-content/instances-datasheet.mdx index 02b59775f4..235834d293 100644 --- a/pages/instances/reference-content/instances-datasheet.mdx +++ b/pages/instances/reference-content/instances-datasheet.mdx @@ -28,13 +28,14 @@ This datasheet provides a concise overview of the performance, technical feature | Resources | Shared vCPUs | | Sizing | 1 vCPU, 1 GiB RAM | | vCPU:RAM ratio | 1:1 | -| SLA | None | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | None | -## Development and General Purpose Instances + +## Development Instances See below the technical specifications of Development and General Purpose Instances: -| Range | Cost-Optimized | +| Range | Development | |:--------------------------------|:-------------------------------------------------------------------------------------------| | Instance type | DEV1
GP1 | | Availability Zone | PAR1, PAR2, PAR3 (excl. DEV1), AMS1, AMS2, WAW1, WAW2 | @@ -45,12 +46,15 @@ See below the technical specifications of Development and General Purpose Instan | 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) | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | None | + -## PLAY2 and PRO2 Instances +## General Purpose Instances +### PLAY2 and PRO2 Instances See below the technical specifications of PLAY2 and PRO2 Instances: -| Range | Cost-Optimized | +| Range | General Purpose | |:--------------------------------|:------------------------------------------------------------------------------| | Instance type | PLAY2
PRO2 | | Availability Zone | PAR1, PAR2, PAR3 (excl PLAY2), AMS1, AMS2, AMS3, WAW1, WAW2, WAW3 | @@ -61,12 +65,14 @@ See below the technical specifications of PLAY2 and PRO2 Instances: | Resources | Shared vCPUs | | Sizing | From 1 to 32 vCPUs
From 2 to 128 GiB RAM | | vCPU:RAM ratio | Various
(1:2, 1:4) | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | None | + -## COP-ARM Instances +### COP-ARM Instances The table below displays the technical specifications of COP-ARM Instances: -| Range | Cost-Optimized | +| Range | General Purpose | |:--------------------------------|:------------------------------------------------------------------------------| | Instance type | COPARM1 | | Availability Zone | PAR2 | @@ -77,31 +83,14 @@ The table below displays the technical specifications of COP-ARM Instances: | Resources | Shared vCPUs | | Sizing | From 2 to 128 vCPUs
From 8 to 128 GiB RAM | | vCPU:RAM ratio | 1:4 | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | None | -## 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 +### POP2 Instances -See below the technical specifications of Production-Optimized Instances: +See below the technical specifications of POP2 Instances: -| Range | Production-Optimized | +| Range | General Purpose | |:--------------------------------|:------------------------------------------------------------------------------| | Instance type | POP2 | | Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, AMS3, WAW2, WAW3 | @@ -112,17 +101,19 @@ See below the technical specifications of Production-Optimized Instances: | Resources | Dedicated vCPUs* | | Sizing | From 2 to 96 vCPUs
From 8 GiB to 384 GiB RAM | | vCPU:RAM ratio | 1:4 | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | 99.5% availability | + \* 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 +## Specialized Instances -See below the technical specifications of Workload-Optimized Instances: +See below the technical specifications of Specialized 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 | +| Range | Specialized | |:--------------------------------|:------------------------------------------------------------------------------| | Instance type | POP2-HM, POP2-HC, POP2-HN | | Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW2, WAW3 | @@ -134,5 +125,7 @@ See below the technical specifications of Workload-Optimized Instances: | 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) | +| [SLO](https://www.scaleway.com/en/virtual-instances/sla/) | 99.5% availability | + \* 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 deleted file mode 100644 index 31123f13a1..0000000000 --- a/pages/instances/reference-content/learning.mdx +++ /dev/null @@ -1,46 +0,0 @@ ---- -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. -dates: - validation: 2025-07-15 - posted: 2023-02-22 -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](/block-storage/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 index 05cb32bb89..e1d02f8bd5 100644 --- a/pages/instances/reference-content/manual-configuration-private-ips.mdx +++ b/pages/instances/reference-content/manual-configuration-private-ips.mdx @@ -3,12 +3,12 @@ title: Configuring Instances manually on a Private Network description: Learn how to manually configure Scaleway Instances on a Private Network. tags: instance private-ip-address ip address private dhcp dates: - validation: 2025-02-17 + validation: 2025-08-28 --- - 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. + - If your Private Network was created before July 12, 2023, refer to our [migration documentation](/vpc/reference-content/vpc-migration/) to check if DHCP is automatically enabled. - 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.** diff --git a/pages/instances/reference-content/preventing-outgoing-ddos.mdx b/pages/instances/reference-content/preventing-outgoing-ddos.mdx index e48ca55b00..8d7a8b7f03 100644 --- a/pages/instances/reference-content/preventing-outgoing-ddos.mdx +++ b/pages/instances/reference-content/preventing-outgoing-ddos.mdx @@ -3,7 +3,7 @@ title: Preventing outgoing DDoS description: Learn how to prevent outgoing DDoS from happening on your Scaleway Instance tags: instance ddos outgoing attack prevention dates: - validation: 2025-02-17 + validation: 2025-08-27 --- diff --git a/pages/instances/reference-content/production-optimized.mdx b/pages/instances/reference-content/production-optimized.mdx deleted file mode 100644 index 53a52052c9..0000000000 --- a/pages/instances/reference-content/production-optimized.mdx +++ /dev/null @@ -1,69 +0,0 @@ ---- -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. -dates: - validation: 2025-03-03 - posted: 2023-02-22 -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](/block-storage/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/workload-optimized.mdx b/pages/instances/reference-content/specialized.mdx similarity index 77% rename from pages/instances/reference-content/workload-optimized.mdx rename to pages/instances/reference-content/specialized.mdx index bfc5ca900e..a161c0ddf5 100644 --- a/pages/instances/reference-content/workload-optimized.mdx +++ b/pages/instances/reference-content/specialized.mdx @@ -1,6 +1,6 @@ --- -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. +title: The right Instance for specialized purposes +description: Find out more about Instances from Scaleway's Specialized range, such as POP2-HC, POP2-HN, and POP2-HM. dates: validation: 2025-06-24 posted: 2023-05-11 @@ -9,17 +9,17 @@ 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 +## Specialized 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. +Scaleway's **Specialized** 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 the highest RAM to vCPU ratio. 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 the highest vCPU to RAM ratio. Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD. -See below the technical specifications of Workload-Optimized Instances: +See below the technical specifications of Specialized Instances: -| Range | Workload-Optimized | +| Range | Specialized | |:--------------------------------|:------------------------------------------------------------------------------| | Instance Type | POP2-HM, POP2-HC, POP2-HN | | Availability Zone | PAR1, PAR2, PAR3, AMS1, AMS2, WAW2, WAW3 | @@ -31,12 +31,12 @@ See below the technical specifications of Workload-Optimized Instances: | 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: +To help build and manage your applications, consider complementing your Specialized 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](/block-storage/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: +Try Scaleway Specialized 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/) diff --git a/pages/instances/reference-content/understanding-differences-x86-arm.mdx b/pages/instances/reference-content/understanding-differences-x86-arm.mdx index c100227807..71ccaaab89 100644 --- a/pages/instances/reference-content/understanding-differences-x86-arm.mdx +++ b/pages/instances/reference-content/understanding-differences-x86-arm.mdx @@ -3,7 +3,7 @@ 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. tags: instance x86 arm dates: - validation: 2025-02-17 + validation: 2025-08-17 --- In cloud computing and data centers, the dominance of x86 architecture has been unchallenged for decades. diff --git a/pages/instances/reference-content/understanding-instance-pricing.mdx b/pages/instances/reference-content/understanding-instance-pricing.mdx index e8b63f3443..d51463bbf9 100644 --- a/pages/instances/reference-content/understanding-instance-pricing.mdx +++ b/pages/instances/reference-content/understanding-instance-pricing.mdx @@ -45,9 +45,9 @@ For cost optimization, Scaleway offers [savings plans](/billing/additional-conte The **Compute savings plan** applies to the following Instance types across all regions: -- **Cost-optimized**: DEV1, GP1, PLAY2, PRO2 -- **Production-optimized**: ENT1, POP2 -- **Workload-optimized**: POP2 HC +- Development Instances +- General Purpose Instances +- Specialized Instances However, savings plans **do not apply** to the following Instance types: H100, RENDER, L40S, L4, COPARM1, START1, X64, and POP-WIN. diff --git a/pages/key-manager/faq.mdx b/pages/key-manager/faq.mdx index bd53741979..810e597ba8 100644 --- a/pages/key-manager/faq.mdx +++ b/pages/key-manager/faq.mdx @@ -2,7 +2,7 @@ title: Key Manager description: Explore Scaleway Key Manager with our comprehensive FAQ covering security, key types, and more. dates: - validation: 2025-07-24 + validation: 2025-08-28 productIcon: KmsProductIcon --- @@ -22,7 +22,7 @@ Read our [dedicated documentation](/key-manager/reference-content/understanding- ## Which cryptographic operations does Key Manager support? -Key Manager supports the three following cryptographic operations: +Key Manager supports the following cryptographic operations: - [Encryption](/key-manager/concepts/#encryption) - [Decryption](/key-manager/concepts/#decryption) @@ -50,3 +50,9 @@ When you delete a key, it is scheduled for deletion. This lets you mark a key an During this time, you can read your key version but cannot edit, access, or delete it. After the retention period, the key and its version are permanently deleted. Recovering keys [scheduled for deletion](/key-manager/concepts/#scheduled-deletion) is billed €0.01 per key. + +## How is Key Manager billed? + +- Symmeric and asymmetric key storage is billed €0.04 per key version monthly. +- Symmeric and asymmetric key operation is billed €0.03 per 10,000 requests. +- Restoring a key scheduled for deletion is billed €0.01 per key. \ No newline at end of file diff --git a/pages/key-manager/how-to/create-km-key.mdx b/pages/key-manager/how-to/create-km-key.mdx index be69819f6d..82d9bb432f 100644 --- a/pages/key-manager/how-to/create-km-key.mdx +++ b/pages/key-manager/how-to/create-km-key.mdx @@ -3,7 +3,7 @@ title: Create a Key Manager key description: Discover how to create a key from the Scaleway console to decrypt your data using Scaleway's Key Manager. tags: key-manager encryption data key dates: - validation: 2025-08-11 + validation: 2025-08-27 posted: 2025-02-06 --- import Requirements from '@macros/iam/requirements.mdx' @@ -18,7 +18,7 @@ Scaleway's Key Manager allows you to create key encryption keys from the [Scalew ## How to create a Key Manager key -1. Click **Key Manager** in the **Security and Identity section** of the [Scaleway console](https://console.scaleway.com) side menu. +1. Click **Key Manager** in the **Security & Identity** section of the [Scaleway console](https://console.scaleway.com) side menu. 2. Click **+ Create key**. 3. Choose the region in which you want to create your key. 4. Enter a name, a description, and optional tags for your key. @@ -30,4 +30,4 @@ Scaleway's Key Manager allows you to create key encryption keys from the [Scalew Key protection allows you to protect your key from accidental deletion. -7. Click **Create key**. Your key's **Overview** page displays. +7. Check the estimated cost, then click **Create key**. Your key's **Overview** page displays. diff --git a/pages/key-manager/how-to/create-manage-dek.mdx b/pages/key-manager/how-to/create-manage-dek.mdx index dcfb38240e..1988162d5b 100644 --- a/pages/key-manager/how-to/create-manage-dek.mdx +++ b/pages/key-manager/how-to/create-manage-dek.mdx @@ -3,7 +3,7 @@ title: Create and manage a Key Manager data encryption key description: Discover how to create a data encryption key from the Scaleway console to encrypt and decrypt your payloads using Scaleway's Key Manager. tags: key-manager data-encryption-key data key payload encryption dates: - validation: 2025-08-11 + validation: 2025-08-28 posted: 2025-02-06 --- import Requirements from '@macros/iam/requirements.mdx' @@ -26,7 +26,7 @@ You can then use your Key Manager key to encrypt your DEK. ## How to create and manage a data encryption key (DEK) -1. Click Key Manager in the **Security and Identity section** of the [Scaleway console](https://console.scaleway.com) side menu. Your keys display. +1. Click Key Manager in the **Security & Identity** section of the [Scaleway console](https://console.scaleway.com) side menu. Your keys display. 2. Click the key for which to create a data encryption key. 3. Scroll down to the **Create data encryption key** section. 4. Click **Create data encryption key**. A pop-up displays with the [ciphertext](/key-manager/concepts/#ciphertext) of your DEK. diff --git a/pages/key-manager/how-to/delete-km-keys.mdx b/pages/key-manager/how-to/delete-km-keys.mdx index 74f5db3534..3e28f38ba1 100644 --- a/pages/key-manager/how-to/delete-km-keys.mdx +++ b/pages/key-manager/how-to/delete-km-keys.mdx @@ -3,7 +3,7 @@ title: Schedule a Key Manager key deletion description: Discover how to delete a Key Manager key from the Scaleway console. tags: key-manager delete key dates: - validation: 2025-07-24 + validation: 2025-08-28 posted: 2025-02-06 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/key-manager/how-to/recover-deleted-keys.mdx b/pages/key-manager/how-to/recover-deleted-keys.mdx index e3d75f9b01..47d4df6509 100644 --- a/pages/key-manager/how-to/recover-deleted-keys.mdx +++ b/pages/key-manager/how-to/recover-deleted-keys.mdx @@ -3,7 +3,7 @@ title: How to recover keys scheduled for deletion description: Recover keys scheduled for deletion in the Scaleway console before they are permanently removed. tags: key encrypted-data scheduled-deletion recover-keys dates: - validation: 2025-07-24 + validation: 2025-08-27 posted: 2025-07-24 --- import Requirements from '@macros/iam/requirements.mdx' @@ -16,7 +16,7 @@ After this retention period, the key and its version are permanently deleted. - 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 [key](/key-manager/how-to/create-key/) +- Created a [key](/key-manager/how-to/create-km-key/) - Scheduled keys for deletion ## How to recover one key diff --git a/pages/key-manager/how-to/rotate-kem-keys.mdx b/pages/key-manager/how-to/rotate-kem-keys.mdx index 666a84306c..a1b34f8f95 100644 --- a/pages/key-manager/how-to/rotate-kem-keys.mdx +++ b/pages/key-manager/how-to/rotate-kem-keys.mdx @@ -3,7 +3,7 @@ title: Rotate keys using the Scaleway console description: Discover how to rotate a key from the Scaleway console to decrypt your data using Scaleway's Key Manager. tags: key-manager rotation key-version dates: - validation: 2025-08-11 + validation: 2025-08-28 posted: 2025-02-06 --- import Requirements from '@macros/iam/requirements.mdx' @@ -13,6 +13,8 @@ Key rotation is a critical security practice that ensures that encryption keys a This reduces the risk of exposure if a key is compromised, thus enhancing the overall security and resilience of your system. For symmetric encryption, it is generally recommended to rotate keys every 30 to 90 days. +Note that you **cannot rotate keys with a usage set to asymmetric encryption and/or signature**. + - A Scaleway account logged into the [console](https://console.scaleway.com) diff --git a/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx b/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx index 79c97757c7..fa6522be4c 100644 --- a/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx +++ b/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx @@ -166,7 +166,7 @@ Kubeconfig for cluster your-cluster-ID successfully written at /Users/youruserna A pool is a set of identical nodes. A pool has a name, a size (its current number of nodes), nodes number limits (min and max), and a Scaleway Instance type. - Instance type with insufficient memory are not eligible to become nodes (DEV1-S, PLAY2-PICO, STARDUST) + Instance type with insufficient (less than 4 GB) memory are not eligible to become nodes. Changing these limits increases/decreases the size of a pool. Thus, when autoscaling is enabled, the pool will grow or shrink inside those limits, depending on its load. diff --git a/pages/kubernetes/how-to/deploy-x86-arm-images.mdx b/pages/kubernetes/how-to/deploy-x86-arm-images.mdx index 1b245b56ac..a4c9ba2fa9 100644 --- a/pages/kubernetes/how-to/deploy-x86-arm-images.mdx +++ b/pages/kubernetes/how-to/deploy-x86-arm-images.mdx @@ -12,7 +12,7 @@ However, Kubernetes provides several mechanisms to manage architectural diversit ## What is ARM architecture, and why is it different from x86? - - ARM architecture is commonly used in devices like Raspberry Pi, IoT devices, and recent [Cost-Optimized Instances based on ARM](https://www.scaleway.com/en/cost-optimized-instances-based-on-arm/). + - ARM architecture is commonly used in devices like Raspberry Pi, IoT devices, and recent [General Purpose Instances based on ARM](https://www.scaleway.com/en/cost-optimized-instances-based-on-arm/). - Kubernetes clusters may consist of nodes with different architectures, including x86 and ARM. - Deploying applications across these diverse architectures requires special consideration. diff --git a/pages/kubernetes/how-to/manage-allowed-ips.mdx b/pages/kubernetes/how-to/manage-allowed-ips.mdx index 1f5c88539a..c433e5ecf9 100644 --- a/pages/kubernetes/how-to/manage-allowed-ips.mdx +++ b/pages/kubernetes/how-to/manage-allowed-ips.mdx @@ -22,10 +22,6 @@ The default entry `0.0.0.0/0` enables any host to establish a connection. Every cluster created after March 8th 2025 has this feature enabled by default. If you do not see the **Network** tab in your cluster's dashboard in the Scaleway console, then the feature is not enabled on your cluster. You can [open a support ticket](https://console.scaleway.com/support/tickets/create) to have it enabled manually. - - Allowed IP configuration is available for [fully isolated Kapsule clusters](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation), and Kosmos clusters. - - ## How to add an IP address 1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes dashboard** appears. diff --git a/pages/kubernetes/how-to/monitor-cluster.mdx b/pages/kubernetes/how-to/monitor-cluster.mdx index 8bd3346d11..616583948f 100644 --- a/pages/kubernetes/how-to/monitor-cluster.mdx +++ b/pages/kubernetes/how-to/monitor-cluster.mdx @@ -3,7 +3,7 @@ title: How to monitor your Kubernetes Kapsule cluster with Cockpit description: This page explains how to monitor your Scaleway Kubernetes Kapsule cluster with Cockpit tags: kubernetes kubernetes-kapsule kapsule cluster observability cockpit dates: - validation: 2025-02-17 + validation: 2025-08-28 posted: 2023-07-24 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx b/pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx index a0e03c3509..b5cce82806 100644 --- a/pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx +++ b/pages/kubernetes/how-to/use-nvidia-gpu-operator.mdx @@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx' Kubernetes Kapsule and Kosmos support NVIDIA's official Kubernetes operator for all GPU pools. -This operator is compatible with all Scaleway [GPU Instance](https://www.scaleway.com/en/gpu-instances/) offers. +This operator is compatible with all Scaleway [GPU Instance](/gpu/reference-content/choosing-gpu-instance-type/) offers. The GPU operator is set up for all GPU pools created in Kubernetes Kapsule and Kosmos, providing automated installation of all required software on GPU worker nodes, such as the device plugin, container toolkit, GPU drivers etc. For more information, refer to [the GPU operator overview](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/overview.html). diff --git a/pages/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber.mdx b/pages/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber.mdx index 74bfc55dea..c72c195d38 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber.mdx @@ -3,7 +3,7 @@ title: Setting up logical replication as a subscriber in PostgreSQL description: Learn how to set up and use logical replication as a subscriber in PostgreSQL to migrate your database with zero downtime tags: postgresql logical replication subscriber migration database dates: - validation: 2025-02-20 + validation: 2025-08-25 posted: 2025-02-20 --- @@ -31,7 +31,7 @@ To be able to create a subscription, you must have the privileges of the `pg_cre 1. Grant `pg_create_subscription` and CREATE privileges to your role of choice. In this example we use `my_replication_user`. Make sure you replace all variables with the information of your databases. - You must follow the step below as an admin. Only users with admin rights can grant `pg_create_subscription` to other users. + You must follow the step below as an admin. Only users with admin rights can grant `pg_create_subscription` to other users. ```sql @@ -74,7 +74,7 @@ To be able to create a subscription, you must have the privileges of the `pg_cre When creating a subscription from a Scaleway Database Instance to a public IP, the public interface of the Database Instance node is used to connect to the publisher. This might incur in the following consequences: -- If you only have a private endpoint, your Database Instance will still have a public management IP address. The ports are all closed, stopping all connections except the one with the publisher database. All outgoing data is securely encrypted. +- If you only have a private endpoint, your Database Instance will still have a public management IP address. The ports are all closed, stopping all connections except the one with the publisher database. All outgoing data is securely encrypted. - If your Database Instance set-up is composed of more than one node, your IP address is subject to change. In case of failover, for example, the IP address connecting to the publisher database will change. We cannot predict the new IP your nodes might take. However, you can use [Scaleway's Autonomous System](https://ipinfo.io/AS12876) to check the number (ASN) of your primary node's IP address, and look up the IP address allocation for the ASN. This can help you predict the IP address of your failover nodes. - There is a limit to the number of subscriptions that can be created per Database Instance offer. You can find the table of maximum number of subscriptions per node type below. diff --git a/pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx b/pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx index 6cfe0895fe..a4b72806df 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx @@ -7,7 +7,7 @@ dates: posted: 2024-12-19 --- -Encryption at rest allows you to permanently encrypt your database data. The data is encrypted at volume level using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup). The management of the encryption key is done by Scaleway. +[Encryption at rest](/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) allows you to permanently encrypt your database data. The data is encrypted at volume level using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup). The management of the encryption key is done by Scaleway. The feature can be activated upon Database Instance creation via the console and the API, or after creation exclusively through the API with the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance). diff --git a/pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx b/pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx index a0bcaf5b5a..519eb37c62 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx @@ -3,7 +3,7 @@ title: Setting up and using the pg_cron extension description: This page explains how to set up and use the pg_cron extension on Scaleway's Managed Databases for PostgreSQL. tags: managed-database postgresql pg_cron pg-extensions dates: - validation: 2025-02-18 + validation: 2025-08-25 posted: 2025-02-18 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx index cd1cf623cd..c3593befc7 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx @@ -40,6 +40,8 @@ A Database Instance is a managed database service created upon a custom base ima A [snapshot](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Their limitation is that, unlike backups, snapshots can only be stored in the same location as the original data. +Refer to the [How to manage snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) documentation page for more information. + ## Encryption at rest @@ -56,6 +58,7 @@ Encryption at rest can be activated after Database Instance creation via the [up Enabling encryption means your database data will be copied into a new, encrypted block volume. This takes approximately 1 hour per 100 GB of storage. When switching volumes, expect a few seconds of downtime towards the end of the copying process. +Refer to the [Encryption at rest performance benchmark](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) reference page to find a benchmark of the performance of Scaleway Managed Databases performing encryption at rest. ## Endpoint @@ -65,6 +68,9 @@ A point of connection to a database. The endpoint is associated with an IPv4 add A database engine is the software component that stores and retrieves your data from a database. Currently, PostgreSQL versions 9.6, 10, 11, 12, 13, 14, and 15 are available. MySQL is available in version 8. +Refer to the [PostgreSQL version updates](/managed-databases-for-postgresql-and-mysql/reference-content/pg-version-updates/) reference page for a list of PostreSQL version updates and the corresponding features that are supported at Scaleway. + + ## High availability Is a Database Instance configuration that allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime. @@ -99,6 +105,9 @@ Compared to traditional database management, which requires customers to provisi A Read Replica is a live copy of a Database Instance that behaves like an Instance, but that only allows read-only connections. The replica mirrors the data of the primary Database node and any changes made are synchronized and reflected in the replica. +Refer to the [How to manage Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/) documentation page for more information. + + ## Region and Availability Zone diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx index a08bdf33bd..ef04b41197 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx @@ -3,7 +3,7 @@ title: How to create a database description: Learn how to add a new database to your PostgreSQL and MySQL Database Instances. tags: managed-database database postgresql ferretdb database-instance mongodb dates: - validation: 2025-02-17 + validation: 2025-08-25 posted: 2023-08-01 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx index 1f2b106620..6c8bd7ea37 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx @@ -3,7 +3,7 @@ title: How to delete a database description: Guide to deleting databases in your PostgreSQL and MySQL Database Instances. tags: managed-database postgresql mysql dates: - validation: 2025-02-17 + validation: 2025-08-25 posted: 2023-08-01 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx index ad350c4ac0..1eac0231e8 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx @@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx' A Read Replica is a live copy of a Database Instance that behaves like an Instance, but that only allows read-only connections. The replica mirrors the data of the primary Database node and any changes made are replicated to the replica asynchronously. -Read Replicas allow you to scale your Database Instance for read-heavy database workloads. They can also be used for business intelligence workloads. +[Read Replicas](/managed-databases-for-postgresql-and-mysql/concepts/#read-replica) allow you to scale your Database Instance for read-heavy database workloads. They can also be used for business intelligence workloads. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx index 7c0fc2c860..ee2c5d4e55 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' import Autobackups from '@macros/databases/autobackups.mdx' -[Snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes. +[Snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes. When you set up [autobackups](/managed-databases-for-postgresql-and-mysql/how-to/manage-backups/) for Database Instances that use Block Storage, the automatic backups are created in snapshot format. diff --git a/pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx b/pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx index 4bc07100ca..f4d0e0c5a4 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx @@ -7,7 +7,7 @@ dates: posted: 2024-12-19 --- -In December 2024, the Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of encryption at rest on transactions, per second and latency. +In December 2024, the Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of [encryption at rest](/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) on transactions, per second and latency. For more information on pgbench transactions, refer to the "What is the 'Transaction' actually performed in pgbench?" section of the official [pgbench documentation](https://www.postgresql.org/docs/current/pgbench.html). diff --git a/pages/managed-databases-for-redis/concepts.mdx b/pages/managed-databases-for-redis/concepts.mdx index a7c6cb1ec8..4a237a001e 100644 --- a/pages/managed-databases-for-redis/concepts.mdx +++ b/pages/managed-databases-for-redis/concepts.mdx @@ -20,6 +20,8 @@ A Redis™* cluster consists of a set of primary and secondary nodes. Each Managed Database for Redis™ cluster consists of minimum three and maximum six compute Instances hosting each a primary Redis™ Instance and a secondary Instance for one of the other nodes. If one of the primary nodes fails, the remaining nodes hold a vote and elect one of the remaining secondary nodes as the new primary node. When the failing node rejoins the cluster, it automatically becomes a secondary node and begins to replicate the data of another primary node. +Learn more about the cluster mode on the [Managed Databases for Redis™ FAQ page](/managed-databases-for-redis/faq/#what-is-the-logic-behind-the-cluster-mode). + ## Endpoint An endpoint is a point of connection to a database. The endpoint is associated with one or more public IPv4 addresses and a port, or with a private IPv4 and a port (if you use [Private Networks](/vpc/concepts/#private-networks)). diff --git a/pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx b/pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx index 2eac7df645..d3fd128659 100644 --- a/pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx +++ b/pages/managed-databases-for-redis/troubleshooting/database-instance-unavailable.mdx @@ -3,7 +3,7 @@ title: Dealing with Database Instance unavailability description: Troubleshoot Database Instance unavailability for Managed Databases for Redis™. tags: unavailability databases dates: - validation: 2025-02-17 + validation: 2025-08-25 posted: 2025-02-17 --- diff --git a/pages/managed-inference/faq.mdx b/pages/managed-inference/faq.mdx index ca9ba611b3..e710f6a407 100644 --- a/pages/managed-inference/faq.mdx +++ b/pages/managed-inference/faq.mdx @@ -2,7 +2,7 @@ title: Managed Inference FAQ description: Get answers to the most frequently asked questions about Scaleway Managed Inference. dates: - validation: 2025-02-12 + validation: 2025-08-26 productIcon: InferenceProductIcon --- diff --git a/pages/managed-inference/reference-content/model-catalog.mdx b/pages/managed-inference/reference-content/model-catalog.mdx index 8d086516d9..68ac784629 100644 --- a/pages/managed-inference/reference-content/model-catalog.mdx +++ b/pages/managed-inference/reference-content/model-catalog.mdx @@ -34,8 +34,6 @@ A quick overview of available models in Scaleway's catalog and their core attrib | [`mixtral-8x7b-instruct-v0.1`](#mixtral-8x7b-instruct-v01) | Mistral | 32k | Text | H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) | | [`magistral-small-2506`](#magistral-small-2506) | Mistral | 32k | Text | L40S, H100, H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) | | [`devstral-small-2505`](#devstral-small-2505) | Mistral | 128k | Text | H100, H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) | -| [`moshiko-0.1-8b`](#moshiko-01-8b) | Kyutai | 4k | Audio to Audio | L4, H100 | [CC-BY-4.0](https://huggingface.co/datasets/choosealicense/licenses/blob/main/markdown/cc-by-4.0.md) | -| [`moshika-0.1-8b`](#moshika-01-8b) | Kyutai | 4k | Audio to Audio| L4, H100 | [CC-BY-4.0](https://huggingface.co/datasets/choosealicense/licenses/blob/main/markdown/cc-by-4.0.md) | | [`pixtral-12b-2409`](#pixtral-12b-2409) | Mistral | 128k | Text, Vision | L40S (50k), H100, H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) | | [`molmo-72b-0924`](#molmo-72b-0924) | Allen AI | 50k | Text, Vision | H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) and [Twonyi Qianwen license](https://huggingface.co/Qwen/Qwen2-72B/blob/main/LICENSE)| | [`qwen3-coder-30b-a3b-instruct`](#qwen3-coder-30b-a3b-instruct) | Qwen | 128k | Code | L40S, H100, H100-2 | [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) | @@ -66,8 +64,6 @@ A quick overview of available models in Scaleway's catalog and their core attrib | `mixtral-8x7b-instruct-v0.1` | Yes | No | English, French, German, Italian, Spanish | | `magistral-small-2506` | Yes | Yes | English, French, German, Spanish, Portuguese, Italian, Japanese, Korean, Russian, Chinese, Arabic, Persian, Indonesian, Malay, Nepali, Polish, Romanian, Serbian, Swedish, Turkish, Ukrainian, Vietnamese, Hindi, Bengali | | `devstral-small-2505` | Yes | Yes | English, French, German, Spanish, Portuguese, Italian, Japanese, Korean, Russian, Chinese, Arabic, Persian, Indonesian, Malay, Nepali, Polish, Romanian, Serbian, Swedish, Turkish, Ukrainian, Vietnamese, Hindi, Bengali | -| `moshiko-0.1-8b` | No | No | English | -| `moshika-0.1-8b` | No | No | English | | `pixtral-12b-2409` | Yes | Yes | English | | `molmo-72b-0924` | Yes | No | English | | `qwen3-coder-30b-a3b-instruct` | Yes | Yes | English, French, German, Chinese, Japanese, Korean and 113 additional languages and dialects | @@ -170,7 +166,7 @@ allenai/molmo-72b-0924:fp8 ## Text models -### Gpt-oss-120b +### Qwen3-235b-a22b-instruct-2507 Released July 23, 2025, Qwen 3 235B A22B is an open-weight model, competitive in multiple benchmarks (such as [LM Arena for text use cases](https://lmarena.ai/leaderboard)) compared to Gemini 2.5 Pro and GPT4.5. | Attribute | Value | @@ -345,30 +341,6 @@ mistral/devstral-small-2505:fp8 mistral/devstral-small-2505:bf16 ``` -### Moshiko-0.1-8b -Kyutai's Moshi is a speech-text foundation model for real-time dialogue. -Moshi is an experimental next-generation conversational model, designed to understand and respond fluidly and naturally to complex conversations, while providing unprecedented expressiveness and spontaneity. -While current systems for spoken dialogue rely on a pipeline of separate components, Moshi is the first real-time full-duplex spoken large language model. -Moshiko is the variant of Moshi with a male voice in English. - -#### Model names -``` -kyutai/moshiko-0.1-8b:bf16 -kyutai/moshiko-0.1-8b:fp8 -``` - -### Moshika-0.1-8b -Kyutai's Moshi is a speech-text foundation model for real-time dialogue. -Moshi is an experimental next-generation conversational model, designed to understand and respond fluidly and naturally to complex conversations, while providing unprecedented expressiveness and spontaneity. -While current systems for spoken dialogue rely on a pipeline of separate components, Moshi is the first real-time full-duplex spoken large language model. -Moshika is the variant of Moshi with a female voice in English. - -#### Model names -``` -kyutai/moshika-0.1-8b:bf16 -kyutai/moshika-0.1-8b:fp8 -``` - ## Code models ### Qwen3-coder-30b-a3b-instruct diff --git a/pages/managed-inference/reference-content/openai-compatibility.mdx b/pages/managed-inference/reference-content/openai-compatibility.mdx index 95a572c3a2..d2a8b3e7b1 100644 --- a/pages/managed-inference/reference-content/openai-compatibility.mdx +++ b/pages/managed-inference/reference-content/openai-compatibility.mdx @@ -7,12 +7,14 @@ dates: posted: 2024-05-06 --- +import ChatCompVsResponsesApi from '@macros/ai/chat-comp-vs-responses-api.mdx' + You can use any of the OpenAI [official libraries](https://platform.openai.com/docs/libraries/), for example, the [OpenAI Python client library](https://github.com/openai/openai-python) to interact with your Scaleway Managed Inference deployment. This feature is especially beneficial for those looking to seamlessly transition applications already utilizing OpenAI. -## Chat Completions API +### Chat Completions API or Responses API? -The Chat Completions API is designed for models fine-tuned for conversational tasks (such as X-chat and X-instruct variants). + ### CURL diff --git a/pages/managed-mongodb-databases/how-to/connect-database-private-network.mdx b/pages/managed-mongodb-databases/how-to/connect-database-private-network.mdx index a9ec18b188..4ede7bd208 100644 --- a/pages/managed-mongodb-databases/how-to/connect-database-private-network.mdx +++ b/pages/managed-mongodb-databases/how-to/connect-database-private-network.mdx @@ -3,7 +3,7 @@ title: How to connect an existing MongoDB® Database Instance to a Private Netwo description: Instructions for connecting your MongoDB® Database Instance over a Private Network. tags: managed-mongodb mongodb private-network database-instance dates: - validation: 2025-02-17 + validation: 2025-08-25 posted: 2025-02-17 --- import SshBastionMdb from '@macros/databases/ssh-bastion-mdb.mdx' diff --git a/pages/object-storage/api-cli/share-buckets-read-only.mdx b/pages/object-storage/api-cli/share-buckets-read-only.mdx index faae0ad743..50f5e83c60 100644 --- a/pages/object-storage/api-cli/share-buckets-read-only.mdx +++ b/pages/object-storage/api-cli/share-buckets-read-only.mdx @@ -1,6 +1,7 @@ --- title: Sharing Object Storage buckets in read-only mode description: Share Scaleway Object Storage buckets with read-only access using the AWS CLI. +noindex: true tags: object storage bucket read only read-only aws cli dates: validation: 2025-02-11 diff --git a/pages/opensearch/how-to/create-opensearch-deployment.mdx b/pages/opensearch/how-to/create-opensearch-deployment.mdx index c2f984ff93..c4677f6ba0 100644 --- a/pages/opensearch/how-to/create-opensearch-deployment.mdx +++ b/pages/opensearch/how-to/create-opensearch-deployment.mdx @@ -29,7 +29,7 @@ This page explains how to create an OpenSearch deployment using the Scaleway con 5. Select a deployment configuration. You can choose between: - **High Availability**: ensures fault tolerance in case of node failure, workload distribution across all nodes for improved performance, service continuity during rolling updates. - - **Standalone**: cost-optimized single-node deployment for testing environments and non-critical, small-scale applications, without redundancy. + - **Standalone**: General Purpose single-node deployment for testing environments and non-critical, small-scale applications, without redundancy. 6. Choose a node type for your deployment. Refer to the [dedicated documentation](/opensearch/reference-content/shared-vs-dedicated-resources/) for more information on shared and dedicated compute resources. diff --git a/pages/opensearch/quickstart.mdx b/pages/opensearch/quickstart.mdx index 7a4b9b327c..cb4123f5bc 100644 --- a/pages/opensearch/quickstart.mdx +++ b/pages/opensearch/quickstart.mdx @@ -26,7 +26,7 @@ This guide covers the basic steps to set up, log in to, and delete a Cloud Essen 2. Click **+ Create deployment**. A creation form displays. -3. Select the **Standalone** deployment configuration. Standalone deployments are cost-optimized single-node deployments for testing environments and non-critical, small-scale applications, without redundancy. +3. Select the **Standalone** deployment configuration. Standalone deployments are General Purpose single-node deployments for testing environments and non-critical, small-scale applications, without redundancy. 4. Select the **SEARCHDB-SHARED-2C-8G** node type. diff --git a/pages/organizations-and-projects/additional-content/organization-quotas.mdx b/pages/organizations-and-projects/additional-content/organization-quotas.mdx index 876161f776..86c26f95d3 100644 --- a/pages/organizations-and-projects/additional-content/organization-quotas.mdx +++ b/pages/organizations-and-projects/additional-content/organization-quotas.mdx @@ -113,13 +113,6 @@ At Scaleway, quotas are applicable per [Organization](/iam/concepts/#organizatio | PRO2 S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | | PRO2 M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | | PRO2 L | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | -| ENT1 XXS | 1 | 5 | -| ENT1 XS | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | -| ENT1 S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | -| ENT1 M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | -| ENT1 L | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | -| ENT1 XL | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | To use this product, you must [validate your identity](/account/how-to/verify-identity/).| -| ENT1 2XL | To use this product, you must [contact our Support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our Support team](https://console.scaleway.com/support/create)).| | POP2-2C-8G | 1 | 5 | | POP2-4C-16G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | | POP2-8C-32G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | diff --git a/pages/organizations-and-projects/concepts.mdx b/pages/organizations-and-projects/concepts.mdx index cd0d03b4a1..2e51e3da1f 100644 --- a/pages/organizations-and-projects/concepts.mdx +++ b/pages/organizations-and-projects/concepts.mdx @@ -28,6 +28,8 @@ The Organization ID identifies the [Organization](#organization) created with yo A Project is a grouping of Scaleway [resources](#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-region, meaning resources located in different [regions](/instances/concepts/#region) can be grouped in one single Project. When grouping resources into different Projects, you can use [IAM](/iam/concepts/#iam) to define custom access rights for each Project. +Refer to the [How to create a Project](/organizations-and-projects/how-to/create-a-project) documentation page for more information. + ## Project dashboard The Project dashboard can be viewed within the [console](https://console.scaleway.com/project). On this dashboard, you can see an overview of the Project's [resources](#resource), along with the Project's settings and credentials ([SSH keys](#ssh-key)). @@ -45,6 +47,11 @@ An SSH key (**S**ecure **Sh**ell key) allows passwordless connection to an [Inst The public key is kept in your Scaleway account and transferred to the Instance during the boot process, 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. +Refer to the [How to create an SSH key](/organizations-and-projects/how-to/create-ssh-key) documentation page for more information. + + ## 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/quotas) of the console and in the [Understanding quotas](/organizations-and-projects/additional-content/organization-quotas) documentation page. \ No newline at end of file +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/quotas) of the console. + +Refer to the [Understanding quotas](/organizations-and-projects/additional-content/organization-quotas) reference page for a list of the available quotas. diff --git a/pages/public-gateways/how-to/move-to-routed-ip.mdx b/pages/public-gateways/how-to/move-to-routed-ip.mdx index f9e15d5e07..17b26082df 100644 --- a/pages/public-gateways/how-to/move-to-routed-ip.mdx +++ b/pages/public-gateways/how-to/move-to-routed-ip.mdx @@ -1,6 +1,7 @@ --- title: How to move your Public Gateway to a routed IP description: Find out how to move your Public Gateway from a legacy NAT IP addressing solution, to a routed IP solution, compatible with Scaleway's IP mobility project and features. +noindex: true tags: public-gateway public gateway nat-ip routed-ip ip-mobility dates: validation: 2025-04-15 diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 9844aa8025..0ee7c68906 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -285,3 +285,7 @@ Unit used to measure the resource consumption of a container. It reflects the am ## Protocol Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended. + + +HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. + diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index 339bcaf1d2..2ec0a4c28e 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -235,6 +235,10 @@ Serverless Containers support **http1** and **http2**. **http1** is enabled by d You can [modify the protocol](/serverless-containers/how-to/manage-a-container/#manage-a-deployment-from-the-scaleway-container-registry) used by your container from the **Requests tab** of the **Advanced options**. + +HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information. + + ### Why does my gRPC container not respond? Containers use **http1** by default, yet the gRPC protocol requires `http2`. You can upgrade the protocol to `http2` (`h2c`). diff --git a/pages/serverless-containers/how-to/add-a-custom-domain-to-a-container.mdx b/pages/serverless-containers/how-to/add-a-custom-domain-to-a-container.mdx index 83175ce5eb..0babb42f2c 100644 --- a/pages/serverless-containers/how-to/add-a-custom-domain-to-a-container.mdx +++ b/pages/serverless-containers/how-to/add-a-custom-domain-to-a-container.mdx @@ -47,10 +47,6 @@ Each container comes with an automatically generated domain, on which it is avai 6. Connect to your container through that custom domain once the custom domain status is `ready`. - - **Custom Domains** do not currently support websockets. If you need to use websockets, you must configure them with the original container URL. - - ## Technical details and troubleshooting Read this section if you want more details about how custom domains are handled or if you are trying to troubleshoot an issue. diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index fa95fe9dbf..f20d8ccb60 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -82,6 +82,10 @@ Do not have your containers listen on these ports, as they are used by our servi **Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product. +### Protocols + +Serverless Containers support HTTP/1.1 and HTTP/2 connections. HTTP/1.0 is not supported. Refer to the [dedicated troubleshooting page](/serverless-containers/troubleshooting/http1-errors/) for more information on how to solve HTTP/1.0 issues. + ## Private Networks and Virtual Private Cloud (VPC) Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks/) on VPC and Serverless Containers integration for more information. diff --git a/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx new file mode 100644 index 0000000000..100e633fdd --- /dev/null +++ b/pages/serverless-containers/reference-content/migrate-to-serverless-containers.mdx @@ -0,0 +1,119 @@ +--- +title: How to migrate your workloads to Scaleway Serverless Containers +description: This page gives recommendations and steps to migrate your workloads from Kubernetes or conventional virtual machines to Scaleway Serverless Containers +tags: migration switch change adopt serverless containers go serverless try k8s vm +dates: + validation: 2025-08-27 + posted: 2025-08-27 +--- + +This guide is designed for developers and operators who are currently running workloads on Kubernetes or traditional virtual machines, and are considering a migration to [Serverless Containers](/serverless-containers/concepts/#serverless-containers). + +This guide covers the [core concepts](#why-migrate-to-serverless-containers) of Serverless Containers, the [operational benefits](#key-features) of this model, and a [practical path](#quick-deployment-guide) for migration. + +## Why migrate to Serverless Containers + +Moving to a Serverless Containers model involves a shift in operational responsibility from you to the cloud provider. This change brings several key advantages for development teams. + +**Reduced operational overhead** + +The primary benefit is the abstraction of the underlying infrastructure. You do not need to provision, manage, scale, or patch servers, operating systems, or container orchestration platforms like Kubernetes. This allows your team to focus on application logic rather than infrastructure management. + +**Container-based workflow** + +You can continue to use the standard container-based development workflow. Packaging your application and its dependencies into a container image ensures a consistent and reproducible environment, from local development to production. + +**Stateless architecture** + +Serverless Containers are designed for stateless services. This architectural pattern promotes building applications that are horizontally scalable and resilient, as any instance can handle any request without relying on local state. + +**Efficient resource consumption** + +The platform automatically scales the number of running container instances based on request volume, CPU consumption or RAM usage. This removes the need to manually configure and tune autoscaling rules, ensuring your application has the resources it needs to meet demand. For services with variable or infrequent traffic, this model is highly efficient, as resources can scale down to zero when there are no requests, eliminating the cost of idle capacity. + +Refer to our [dedicated overview page](/serverless-containers/reference-content/serverless-overview/) for general information on Scaleway's Serverless products. + +## Key features + +Serverless Containers come packed with features designed for modern application development. + +- **Private Networks compatibility**: Securely connect your services to other resources within your Virtual Private Cloud. + - Learn [how to use Private Networks with Serverless Containers](/serverless-containers/reference-content/containers-private-networks/). + +- **Custom domains**: Easily map your own domain names to your services. + - Discover [how to add custom domains to Serverless Containers](/serverless-containers/how-to/add-a-custom-domain-to-a-container/). + +- **Healthchecks**: Configure readiness and liveness probes to ensure your application instances are healthy and ready to serve traffic. + - Get [information about healtchecks](/serverless-containers/concepts/#health-check). + +- **Built-in monitoring**: Gain immediate insights on your application's performance with integrated logging and metrics, without needing to set up complex monitoring agents. + - Check [how to monitor your Serverless Container](/serverless-containers/how-to/monitor-container/). + +- **Enhanced security**: Because the platform is managed by Scaleway, it benefits from continuous security patching and best practices, reducing your operational security burden. + - Find out [how to secure a Serverless Container](/serverless-containers/how-to/secure-a-container/). + +To dive deeper into Serverless Containers, refer to the dedicated [concepts page](/serverless-containers/concepts/). + +## Quick deployment guide + +Deploying your first service to Serverless Containers is straightforward. Here’s a high-level overview of the steps. + +1. **Containerize your application**: If you haven't already, package your application into a container image using a Dockerfile. + +2. **Push your image to a registry**: Follow the [dedicated Quickstart documenation](/container-registry/quickstart/) to discover how to log in to the Scaleway Container Registry and store your images. + +3. **Deploy your container**: Read the [How to deploy a container](/serverless-containers/how-to/deploy-container/) page to create your container using the Scaleway console. + +4. **Click Deploy**: The Scaleway platform will pull your container image and run it. Within a few minutes, your Serverless Container will be publicly accessible via its HTTPS endpoint. + +## Best practices for migration + +Migrating existing applications from Kubernetes or Instances to Serverless Containers is an opportunity to modernize your architecture. + +### General best practices + +**Containerize everything** + +Your application must be packaged as a container image. This is the fundamental deployment unit for Serverless Containers. + +**Embrace statelessness** + +Since Serverless Containers are stateless, you cannot rely on the local filesystem for storing data that needs to persist between requests. + +**Use external storage** + +To store data, you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). + +**Externalize state** + +For application state, use a managed database, cache like [Redis](/managed-databases-for-redis/how-to/create-a-database-for-redis/) or [message queues](/queues/quickstart/). + +**Manage your infrastructure as code** + +While you can manage your services through the Scaleway console, we highly recommend using developer tools for a repeatable and version-controlled setup. + +**CLI** + +Use the [Scaleway command-line interface](/scaleway-cli/quickstart/) for easy resource management, scripting, and automation. + +**Terraform/IaC** + +Define your Serverless Containers services using tools like Terraform or OpenTofu via the [Scaleway Provider](/terraform/quickstart/) for a fully automated and declarative infrastructure. + +### Migration strategies + +**Progressive migration** + +You do not need to migrate your entire application at once. Serverless Containers are perfect for microservices. You can start by migrating a single, smaller service to get a feel of the platform. This approach minimizes risk and allows your teams to learn as they go. + +**API migration** + +When migrating an API, you can create a new version of your API on Serverless Containers. For example, you can create a new `/v2/` endpoint for your API that is served by Serverless Containers, while the existing `/v1/` remains on your current infrastructure. This allows for a gradual rollout to your users. + +### Start small with Serverless Jobs + +If you are looking for an even simpler way to start your Serverless journey, consider using Serverless Jobs. This is a companion product designed for running autonomous batch jobs, scripts, or automated tasks that run to completion. + +Instead of migrating a full web service, you can start by offloading a small automation task (like a nightly data processing script) to a Serverless Job. This is a low-risk way to familiarize your team with the Serverless Container ecosystem before committing to migrating larger, more critical services. + +Refer to the [Serverless Jobs quickstart guide](/serverless-jobs/quickstart/) to deploy your first job in a few minutes. diff --git a/pages/serverless-containers/troubleshooting/http1-errors.mdx b/pages/serverless-containers/troubleshooting/http1-errors.mdx new file mode 100644 index 0000000000..25eccd9226 --- /dev/null +++ b/pages/serverless-containers/troubleshooting/http1-errors.mdx @@ -0,0 +1,21 @@ +--- +title: Solving HTTP/1.0 issues +description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Containers +tags: issues error protocol http1.0 http0.9 backwards compatibiliy +dates: + validation: 2025-08-25 + posted: 2025-08-25 +--- + +## Problem + +I get an `HTTP 426 Upgrade Required` error while using Serverless Containers. + +## Cause + +Scaleway Serverless Containers only supports **HTTP/1.1** and **HTTP/2**. Other protocols are not compatible. + +## Solutions + +- Send **HTTP/1.1** requests if you have control over the protocol to use when calling a Serverless Container. +- Deploy a layer in front of your container to translate HTTP/1.0 into HTTP/1.1. \ No newline at end of file diff --git a/pages/serverless-containers/troubleshooting/index.mdx b/pages/serverless-containers/troubleshooting/index.mdx index 57d519660d..b9add516cf 100644 --- a/pages/serverless-containers/troubleshooting/index.mdx +++ b/pages/serverless-containers/troubleshooting/index.mdx @@ -68,4 +68,5 @@ productIcon: ContainersProductIcon - [I am experiencing clock drift with my Serverless Containers](/serverless-containers/troubleshooting/container-clock-drift) - [I am experiencing DNS issues with my container](/serverless-containers/troubleshooting/known-dns-containers-errors/) - [I cannot access my container](/serverless-containers/troubleshooting/cannot-access-container/) + - [I get errors when using HTTP/1.0](/serverless-containers/troubleshooting/http1-errors/) diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 15efbe299f..66f593adb0 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -126,6 +126,10 @@ Previously, Private Networks at Scaleway were zoned. Only resources from within While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information. +## Protocol + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ## Queue trigger A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/queues/concepts/#scaleway-queues), and invokes the function automatically whenever a message is added to the queue. diff --git a/pages/serverless-functions/faq.mdx b/pages/serverless-functions/faq.mdx index 894fb46dcf..fb8c21d223 100644 --- a/pages/serverless-functions/faq.mdx +++ b/pages/serverless-functions/faq.mdx @@ -253,6 +253,10 @@ You cannot use Serverless Functions with Edge Services because there are no nati By design, it is not possible to guarantee static IPs on Serverless Compute resources. +### Which protocols are supported by Serverless Functions? + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ### How can I attach Block Storage to a Serverless Function? Scaleway Serverless Functions do not currently support attaching Block Storage. These functions are designed to be diff --git a/pages/serverless-functions/how-to/add-a-custom-domain-name-to-a-function.mdx b/pages/serverless-functions/how-to/add-a-custom-domain-name-to-a-function.mdx index 7ddbc0361a..b5bc11a7dc 100644 --- a/pages/serverless-functions/how-to/add-a-custom-domain-name-to-a-function.mdx +++ b/pages/serverless-functions/how-to/add-a-custom-domain-name-to-a-function.mdx @@ -45,10 +45,6 @@ Each function comes with an automatically generated domain, on which it is avail 6. Connect to your function through that custom domain once the custom domain status is `ready`. - - **Custom Domains** do not currently support websockets. If you need to use websockets, you must configure them with the original function URL. - - ## Technical details and troubleshooting Read this section if you want more details about how custom domains are handled or if you are trying to troubleshoot an issue. diff --git a/pages/serverless-functions/reference-content/functions-limitations.mdx b/pages/serverless-functions/reference-content/functions-limitations.mdx index a6aa53ea91..5f02be24ee 100644 --- a/pages/serverless-functions/reference-content/functions-limitations.mdx +++ b/pages/serverless-functions/reference-content/functions-limitations.mdx @@ -64,6 +64,10 @@ Due to potential abuse (spam), no outbound traffic is allowed through following **Not available:** Serverless products are designed to abstract away infrastructure management, to be easily scalable, and to be cost-efficient and simple. So dedicated IPs are not supported for this product. +### Protocols + +Serverless Functions support **HTTP/1.1** and **HTTP/2**. Other protocols are not supported. Refer to the [dedicated troubleshooting page](/serverless-functions/troubleshooting/http1-errors/) for more information. + ## Private Networks and Virtual Private Cloud (VPC) Refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/) on VPC and Serverless Functions integration for more information. diff --git a/pages/serverless-functions/troubleshooting/http1-errors.mdx b/pages/serverless-functions/troubleshooting/http1-errors.mdx new file mode 100644 index 0000000000..3c21bde815 --- /dev/null +++ b/pages/serverless-functions/troubleshooting/http1-errors.mdx @@ -0,0 +1,21 @@ +--- +title: Solving HTTP/1.0 issues +description: This page provides solutions to issues encountered while using HTTP/1.0 with Scaleway Serverless Functions +tags: issues error protocol http1.0 http0.9 backwards compatibiliy +dates: + validation: 2025-08-25 + posted: 2025-08-25 +--- + +## Problem + +I get an `HTTP 426 Upgrade Required` error while using Serverless Functions. + +## Cause + +Scaleway Serverless Functions only supports **HTTP/1.1** and **HTTP/2**. Other protocols are not compatible. + +## Solutions + +- Send **HTTP/1.1** requests if you have control over the protocol to use when calling a Serverless Function. +- Deploy a layer in front of your function to translate HTTP/1.0 into HTTP/1.1. \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/index.mdx b/pages/serverless-functions/troubleshooting/index.mdx index 4147b590f7..3dc7d31c39 100644 --- a/pages/serverless-functions/troubleshooting/index.mdx +++ b/pages/serverless-functions/troubleshooting/index.mdx @@ -69,4 +69,5 @@ productIcon: FunctionsProductIcon - [I am experiencing timeout errors](/serverless-functions/troubleshooting/timeout-error) - [My function fails after trying too many times](/serverless-functions/troubleshooting/too-many-retries) - [I am experiencing clock drift with my Serverless Functions](/serverless-functions/troubleshooting/function-clock-drift) + - [I get errors when using HTTP/1.0](/serverless-functions/troubleshooting/http1-errors/) diff --git a/pages/transactional-email/concepts.mdx b/pages/transactional-email/concepts.mdx index f44a94e1f2..23d92cf3b7 100644 --- a/pages/transactional-email/concepts.mdx +++ b/pages/transactional-email/concepts.mdx @@ -18,6 +18,8 @@ An aggregate report (`rua`) is a periodic summary that provides data about a dom Blocklist is a feature that allows you to manage email addresses that generate errors, or “bounces”. Emails are automatically blocked when a mailbox does not exist, or is full, to prevent sending emails to a recipient address that is not reachable. +Refer to the [Manage blocklists](/transactional-email/how-to/manage-blocklists/) documentation page for more information. + ## Dedicated IPs @@ -28,6 +30,8 @@ Refer to the [Understanding managed dedicated IPs](/transactional-email/referenc Deliverability is the ability for an email to arrive in a recipient’s email inbox. +Refer to the [Understanding your reputation score with TEM](/transactional-email/reference-content/understanding-tem-reputation-score/#best-practices-for-domain-reputation-and-deliverability) for best practices on improving your domain reputation and deliverability. + ## DKIM record A Domain Keys Identified Mail (DKIM) record is an email security standard. It provides you with an encryption key and a digital signature that allows you to verify whether an email was altered. @@ -37,6 +41,10 @@ A Domain Keys Identified Mail (DKIM) record is an email security standard. It pr DMARC stands for **D**omain-bassed **M**essage **A**uthentication **R**eporting and **C**onformance. It is an email authentication protocol that helps prevent email spoofing and phishing attacks by verifying that the sender's domain is legitimate. DMARC builds upon other email authentication protocols: [SPF](#spf-record) and [DKIM](#dkim-record). It allows domain owners to publish policies in their Domain Name System (DNS) records specifying how emails sent from their domain should be handled if they fail authentication checks. + +Refer to the [Understanding DMARC configuration](/transactional-email/reference-content/dmarc-configuration/) documentation page for more information. + + ## DNS propagation DNS propagation is the time a DNS change takes to be updated across the internet. @@ -45,6 +53,8 @@ DNS propagation is the time a DNS change takes to be updated across the internet An email webhook is a mechanism that allows an application to send real-time notifications to another application when a specific email-related event occurs. When certain predefined events happen, a notification (webhook) is sent to a URL specified by the user. This allows the receiving application to immediately react to events such as email delivery, a bounce, or being marked as spam. +Refer to the [Understanding Webhook event payloads](/transactional-email/reference-content/webhook-events-payloads/) documentation page for more information. + ## Essential plan The Essential plan operates on a pay-as-you-go basis, making it ideal for users with occasional or low-volume email sending needs. @@ -55,6 +65,8 @@ The plan offers: - 300 free emails (with an additional cost of €0.25 for every 1000 additional emails) - An automatic blocklist with the option to unblock, but not manually add, email addresses. +Refer to the [How to manage TEM plans](/transactional-email/how-to/manage-tem-plans/) documentation page for more information. + ## Flags Scaleway uses flags to provide you with more information about your emails. Flags can let you know whether an email you have sent is considered a spam, for example. @@ -103,6 +115,8 @@ Some effective practices for warming up an IP address include: IP reputation measures the trustworthiness of an IP address and the amount of unwanted requests it sends. An IP address that sends authentic, spam-free emails, earns a good IP reputation. An IP address that sends high amounts of spam or viruses earns a bad IP reputation. IP reputation allows you to reject requests that are coming from an IP address with a bad reputation. +Refer to the [Understanding your reputation score with TEM](/transactional-email/reference-content/understanding-tem-reputation-score/) documentation page for best practices on improving your reputation score. + ## MX record A mail exchanger (MX) record is a DNS record that is required to deliver emails to your address. An MX record indicates which mail servers accept incoming emails for your domain and where emails sent to your domain should be routed to. @@ -146,6 +160,8 @@ The **closer to 100** your reputation score is, the more receiving email servers A domain's reputation score is determined by email providers and Internet Service Providers (ISPs), which means you have a different domain reputation for each email service provider. +Refer to the [Understanding your reputation score with TEM](/transactional-email/reference-content/understanding-tem-reputation-score/) documentation page for best practices on improving your reputation score. + ## Scale plan The Scale plan is a solution for sending transactional emails, designed for businesses and developers with high volume and advanced needs. It includes: @@ -156,6 +172,9 @@ The Scale plan is a solution for sending transactional emails, designed for busi - Detailed monitoring and reporting - A 99.9% SLA. +Refer to the [How to manage TEM plans](/transactional-email/how-to/manage-tem-plans/) documentation page for more information. + + ## Send API A send API is the main API that is used to send transactional emails to recipients. @@ -204,6 +223,8 @@ Two plans are available: - [Essential](#essential-plan) - [Scale](#scale-plan) +Refer to the [How to manage TEM plans](/transactional-email/how-to/manage-tem-plans/) documentation page for more information. + ## Webhook Event Type diff --git a/pages/use-cases/application-hosting/index.mdx b/pages/use-cases/application-hosting/index.mdx new file mode 100644 index 0000000000..13af583832 --- /dev/null +++ b/pages/use-cases/application-hosting/index.mdx @@ -0,0 +1,26 @@ +--- +title: Host an application +description: Seamlessly deploy and host your applications on Scaleway's scalable cloud infrastructure. +--- + +## Host an application at Scaleway +Seamlessly deploy and host your applications on Scaleway's scalable cloud infrastructure. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/back-up-data/index.mdx b/pages/use-cases/back-up-data/index.mdx new file mode 100644 index 0000000000..10a69fdc45 --- /dev/null +++ b/pages/use-cases/back-up-data/index.mdx @@ -0,0 +1,26 @@ +--- +title: Backup and archive data +description: Discover how to safeguard your data with different backup and archival solutions. +--- + +## Backup and archive your data +Safeguard your data with different backup and archival solutions. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/best-practices/index.mdx b/pages/use-cases/best-practices/index.mdx new file mode 100644 index 0000000000..d1497c8aef --- /dev/null +++ b/pages/use-cases/best-practices/index.mdx @@ -0,0 +1,26 @@ +--- +title: Best practices +description: Learn from Scaleway's expert guides and best practices to optimize your cloud strategy. +--- + +## Discover best practices +Learn from Scaleway's expert guides and best practices to optimize your cloud usage. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/build-and-run-ai/index.mdx b/pages/use-cases/build-and-run-ai/index.mdx new file mode 100644 index 0000000000..4a371d31ee --- /dev/null +++ b/pages/use-cases/build-and-run-ai/index.mdx @@ -0,0 +1,26 @@ +--- +title: Build and run AI +description: Discover how to leverage Scaleway's AI & Data services to develop, train, and deploy powerful AI models. +--- + +## Build and run AI at Scaleway +Leverage Scaleway's AI & Data services to develop, train, and deploy powerful AI models. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/deploy-external-software/index.mdx b/pages/use-cases/deploy-external-software/index.mdx new file mode 100644 index 0000000000..ccd136a8b1 --- /dev/null +++ b/pages/use-cases/deploy-external-software/index.mdx @@ -0,0 +1,26 @@ +--- +title: Deploy and manage external software +description: Discover how to deploy and manage external software with Scaleway's flexible and customizable cloud environment. +--- + +## Deploy and manage external software +Easily deploy and manage external software with Scaleway's flexible and customizable cloud environment. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/index.mdx b/pages/use-cases/index.mdx new file mode 100644 index 0000000000..d87c4e0032 --- /dev/null +++ b/pages/use-cases/index.mdx @@ -0,0 +1,89 @@ +--- +title: Use Cases +description: Discover the different ways you can use the Scaleway products to develop your projects. +--- + +## Use cases +Get started with our most popular use cases. + + +## What do you want to do? + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/pages/use-cases/iot/index.mdx b/pages/use-cases/iot/index.mdx new file mode 100644 index 0000000000..1218d4aa84 --- /dev/null +++ b/pages/use-cases/iot/index.mdx @@ -0,0 +1,26 @@ +--- +title: Connect IoT devices +description: Discover how to integrate and manage your IoT ecosystem using Scaleway's IoT Hub. +--- + +## Connect IoT devices with Scaleway +Integrate and manage your IoT ecosystem using Scaleway's IoT Hub. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/manage-share-and-store-data/index.mdx b/pages/use-cases/manage-share-and-store-data/index.mdx new file mode 100644 index 0000000000..d36dc56b8d --- /dev/null +++ b/pages/use-cases/manage-share-and-store-data/index.mdx @@ -0,0 +1,26 @@ +--- +title: Manage, share, store data +description: Discover the different ways you can use the Scaleway products to develop your projects. +--- + +## Manage, share, store data +Manage, share, and store your data with secure and scalable storage options. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/migration/index.mdx b/pages/use-cases/migration/index.mdx new file mode 100644 index 0000000000..c32a5780ee --- /dev/null +++ b/pages/use-cases/migration/index.mdx @@ -0,0 +1,44 @@ +--- +title: Migrate to Scaleway +description: Discover the different ways you can use the Scaleway products to develop your projects. +--- + +## Migrate to Scaleway +Discover how to seamlessly move your infrastructure to Scaleway. + + + + + + + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/monitoring/index.mdx b/pages/use-cases/monitoring/index.mdx new file mode 100644 index 0000000000..ebf90b3949 --- /dev/null +++ b/pages/use-cases/monitoring/index.mdx @@ -0,0 +1,26 @@ +--- +title: Monitor resources +description: Discover the different ways you can use the Scaleway products to develop your projects. +--- + +## Monitor your resources +Set up tools to keep your cloud environment running smoothly. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/resource-management/index.mdx b/pages/use-cases/resource-management/index.mdx new file mode 100644 index 0000000000..cc6d130191 --- /dev/null +++ b/pages/use-cases/resource-management/index.mdx @@ -0,0 +1,26 @@ +--- +title: Manage resources +description: Discover how to streamline your cloud operations with open-source resource management and orchestration tools. +--- + +## Manage your resources +Streamline your cloud operations with open-source resource management and orchestration tools. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/security/index.mdx b/pages/use-cases/security/index.mdx new file mode 100644 index 0000000000..211fbc1dc2 --- /dev/null +++ b/pages/use-cases/security/index.mdx @@ -0,0 +1,25 @@ +--- +title: Secure your resources +description: Discover how to protect your cloud infrastructure. +--- + +## Secure your resources +Protect your cloud infrastructure. + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/set-up-and-test/index.mdx b/pages/use-cases/set-up-and-test/index.mdx new file mode 100644 index 0000000000..2faff4294c --- /dev/null +++ b/pages/use-cases/set-up-and-test/index.mdx @@ -0,0 +1,25 @@ +--- +title: Set up and test +description: Discover how to set up your test infrastructures at Scaleway. +--- + +## Set up and test your projects +Quickly set up your test infrastructures at Scaleway. + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/use-cases/website-hosting/index.mdx b/pages/use-cases/website-hosting/index.mdx new file mode 100644 index 0000000000..a270ddeb44 --- /dev/null +++ b/pages/use-cases/website-hosting/index.mdx @@ -0,0 +1,26 @@ +--- +title: Host a website +description: Discover how to host your website on Scaleway's scalable cloud platform. +--- + +## Host a website at Scaleway +Host your website on Scaleway's scalable cloud platform. + + + + + + +## Related tutorials \ No newline at end of file diff --git a/pages/vpc/assets/scaleway-attach-resource.webp b/pages/vpc/assets/scaleway-attach-resource.webp index 014950e561..9929f57c84 100644 Binary files a/pages/vpc/assets/scaleway-attach-resource.webp and b/pages/vpc/assets/scaleway-attach-resource.webp differ diff --git a/pages/vpc/how-to/assets/scaleway-attach-resource.webp b/pages/vpc/how-to/assets/scaleway-attach-resource.webp index 9a72c35895..9929f57c84 100644 Binary files a/pages/vpc/how-to/assets/scaleway-attach-resource.webp and b/pages/vpc/how-to/assets/scaleway-attach-resource.webp differ diff --git a/pages/vpc/how-to/attach-resources-to-pn.mdx b/pages/vpc/how-to/attach-resources-to-pn.mdx index 4563c41712..7c58a2d2f6 100644 --- a/pages/vpc/how-to/attach-resources-to-pn.mdx +++ b/pages/vpc/how-to/attach-resources-to-pn.mdx @@ -3,16 +3,14 @@ title: How to attach resources to a Private Network description: This page explains how to attach resources to a Private Network in a Scaleway VPC tags: regional-private-network private-network vpc virtual-private-cloud attach detach resources regional dates: - validation: 2025-02-20 + validation: 2025-08-26 posted: 2023-03-21 --- import Requirements from '@macros/iam/requirements.mdx' -import image from './assets/scaleway-pn-overview.webp' -import image2 from './assets/scaleway-pn-attached-resources.webp' -import image3 from './assets/scaleway-attach-resource.webp' -import image4 from './assets/scaleway-attach-custom.webp' -import image5 from './assets/scaleway-attached-resources.webp' +import PNAttachedResources from './assets/scaleway-pn-attached-resources.webp' +import AttachResource from './assets/scaleway-attach-resource.webp' +import AttachCustomResource from './assets/scaleway-attach-custom.webp' VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create multiple **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet. @@ -56,28 +54,26 @@ The following resource types can be attached to a Private Network: 3. Click the Private Network to which you want to attach a resource. - The Private Network's dashboard displays. + The Private Network's **Attached Resources** tab displays. - + -4. Click the **Attached resources** tab. - - - -5. Use the toggle to select the type of resource you want to attach: + + You can use the toggle to view the different types of resources already attached to this Private Network: - **Managed** resources are created and managed via Scaleway, e.g. Instances, Elastic Metal servers, Load Balancers, Managed Databases, Kubernetes Kapsules, Public Gateways, Apple silicon etc. - **Custom** resources are created and managed by yourself, e.g. virtual machines you are hosting on a Proxmox cluster on an Elastic Metal server. + -6. Click **+ Attach resource**. A pop-up displays. +4. Click **+ Attach resource**. A pop-up displays. -7. Complete the required information about the resource to attach. This depends on whether you are attaching a managed or custom resource. +5. Complete the required information about the resource to attach. This depends on whether you are attaching a managed or custom resource. - + - From the first drop-down, select the **type** of managed resource (Instance, Elastic Metal server etc.) to attach. - From the second drop-down, select the **specific resource** of this type to attach. Only resources within the same region as the Private Network will be displayed. @@ -90,7 +86,7 @@ The following resource types can be attached to a Private Network: - + This method is intended for custom resources such as VMs hosted on Elastic Metal. Do **not** attempt to attach a managed resource, such as an Instance, via this method - use the **Managed resource** attachment instead. @@ -102,7 +98,7 @@ The following resource types can be attached to a Private Network: -8. Click **Attach to Private Network** to finish. +6. Click **Attach to Private Network** to finish. You are returned to the list of attached resources, where the newly-attached resource now displays. @@ -118,7 +114,7 @@ You can also attach a managed resource to a Private Network from the resource's - [Serverless Functions](/serverless-functions/how-to/use-private-networks/) - [Serverless Containers](/serverless-containers/how-to/use-private-networks/) -Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself. Serverless Functions and Containers can only be attached to Private Networks if they have been created in a namespace that supports VPC. +Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself. For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of managed resource. See the relevant documentation for [Elastic Metal](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) or [Apple silicon](/apple-silicon/how-to/use-private-networks/) for full instructions. @@ -129,9 +125,9 @@ When you attach a resource to a Private Network, it gets a private IPv4 address No matter whether it is auto-allocated or pre-reserved, the IP remains stable for as long as the resource is attached to the Private Network, and does not risk changing even across reboots and long poweroffs. An auto-allocated IP is lost only when you delete the resource or detach it from the Private Network. Reserved IPs remain reserved even after you delete the resource or detach it from the Private Network, until you [release the address](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address). -You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 5 above). +You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 3 above). - + It can also be viewed via the **Private Networks** tab of the resource's own dashboard. @@ -169,20 +165,16 @@ For full information on Scaleway internal DNS and hostname formats, including tr 3. Click the Private Network from which you want to detach a resource. -4. Click the **Attached resources** tab. - - The Private Network's dashboard displays. - -5. Click the **Attached resources** tab. + The Private Network's **Attached Resources** tab displays. -6. Use the toggle to select the type of resource you want to detach: +4. Use the toggle to select the type of resource you want to detach: - **Managed** resources are created and managed via Scaleway, e.g. Instances, Elastic Metal servers, Load Balancers, Managed Databases, Kubernetes Kapsules, Public Gateways, Apple silicon etc. - **Custom** resources are created and managed by yourself, e.g. virtual machines you are hosting on a Proxmox cluster on an Elastic Metal server. -7. Click the icon next to the resource you want to detach. +5. Click the icon next to the resource you want to detach. -8. Click **Detach resource** when prompted to confirm. +6. Click **Detach resource** when prompted to confirm. You can also detach a managed resource to a Private Network from the resource's own section of the console. diff --git a/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx b/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx index 04924f746b..afb38fd70e 100644 --- a/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx +++ b/pages/vpc/troubleshooting/cant-delete-vpc-pn.mdx @@ -3,7 +3,7 @@ title: I can't delete my VPC or Private Network description: Resolve issues deleting your Scaleway VPC or Private Network with this troubleshooting guide. Find solutions to common errors and get back to managing your infrastructure. tags: vpc private-network delete resources ipam error dates: - validation: 2025-02-21 + validation: 2025-08-26 posted: 2025-02-21 --- import image from './assets/scaleway-vpc-pns.webp' diff --git a/pages/vpc/troubleshooting/vpc-pn-routing-connectivity-issues.mdx b/pages/vpc/troubleshooting/vpc-pn-routing-connectivity-issues.mdx index 821fe101ab..a26de7448f 100644 --- a/pages/vpc/troubleshooting/vpc-pn-routing-connectivity-issues.mdx +++ b/pages/vpc/troubleshooting/vpc-pn-routing-connectivity-issues.mdx @@ -3,7 +3,7 @@ title: I am experiencing connectivity or routing issues with my VPC or Private N description: Troubleshoot access and connectivity issues with your Scaleway VPC or Private Network. Learn how to resolve common problems and get your network up and running smoothly. tags: vpc private-network access connectivity ssh ip dates: - validation: 2025-02-21 + validation: 2025-08-26 posted: 2025-02-21 --- diff --git a/pages/webhosting/how-to/order-dedicated-ip.mdx b/pages/webhosting/how-to/order-dedicated-ip.mdx index c7c0b49ac2..6a4238e6dc 100644 --- a/pages/webhosting/how-to/order-dedicated-ip.mdx +++ b/pages/webhosting/how-to/order-dedicated-ip.mdx @@ -3,7 +3,7 @@ title: How to order a dedicated IP address for a Web Hosting plan description: This page explains how to order a dedicated IP address for a Scaleway Web Hosting plan. tags: webhosting dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2023-12-20 --- import Requirements from '@macros/iam/requirements.mdx' @@ -27,33 +27,31 @@ Some potential advantages of having a dedicated IP address for Web Hosting are: - 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 - [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar -- A Web Hosting plan with a shared IP address +- [Ordered](/webhosting/how-to/order-webhosting/) a Web Hosting plan with a shared IP address -## Activate a dedicated IP address for a Web Hosting plan +## Order a dedicated IP address for a Web Hosting plan -1. Navigate to the **Domains & Web Hosting** section of the [console](https://console.scaleway.com/) side menu and click **Web Hosting**. This action will lead you to the **Web Hosting** overview page. -2. Click either or the domain name associated with the Web Hosting you want to configure. This will take you to the **Hosting Information** page. -3. Within the hosting options area of your Web Hosting, click on **Manage Options**. -4. Activate the **Dedicated IP** toggle to initiate the process of acquiring a dedicated IP address for your Web Hosting plan. -5. Complete the process by clicking **Update Web Hosting Plan**. - This action will not only update the configuration of your Web Hosting but also assign the newly acquired dedicated IP to it. +1. Navigate to the **Domains & Web Hosting** section of the [console](https://console.scaleway.com/) side menu and click **Web Hosting**. A list of your Web Hosting plans displays. +2. Click the domain associated with the Web Hosting you want to configure. The Web Hosting's **Overview** tab displays. +3. Scroll to the **Hosting options** section, then click **Manage options**. The **Manage hosting plan and options** page displays. +4. Scroll to the **Configure options** section and check the **Dedicated IP** check box to order a dedicated IP address for your Web Hosting plan. +5. Check the estimated cost, then click **Update Web Hosting**. This action will update the configuration of your Web Hosting but also assign the newly acquired dedicated IP to it. Alternatively, you can activate this option directly while configuring a new Web Hosting plan. -## Deactivate a dedicated IP address for a Web Hosting plan +## Remove a dedicated IP address from a Web Hosting plan -1. Navigate to the **Domains & Web Hosting** section of the [console](https://console.scaleway.com/) side menu and click **Web Hosting**. This action will lead you to the **Web Hosting** overview page. -2. Click either or the domain name associated with the Web Hosting you want to configure. This will take you to the **Hosting Information** page. -3. Within the hosting options area of your Web Hosting, click on **Manage Options**. -4. Deactivate the **Dedicated IP** toggle to initiate the process of removing the dedicated IP address of your Web Hosting plan. -5. Complete the process by clicking **Update Web Hosting Plan**. - This action will update the configuration of your Web Hosting plan by replacing the dedicated IP address with the shared IP address of the server. +1. Navigate to the **Domains & Web Hosting** section of the [console](https://console.scaleway.com/) side menu and click **Web Hosting**. A list of your Web Hosting plans displays. +2. Click the domain associated with the Web Hosting you want to configure. The Web Hosting's **Overview** tab displays. +3. Scroll to the **Hosting options** section, then click **Manage options**. The **Manage hosting plan and options** page displays. +4. Scroll to the **Configure options** section and uncheck the **Dedicated IP** check box to initiate the process of removing the dedicated IP address from your Web Hosting plan. +5. Check the estimated cost, then click **Update Web Hosting**. This action will update the configuration of your Web Hosting plan by replacing the dedicated IP address with the shared IP address of the server. When deactivating the dedicated IP address for your Web Hosting, automated checks will be conducted to ensure that the IP is not blacklisted. - If your IP address is found to be blacklisted, the option cannot be deactivated, and you should reach out to our [technical support](https://console.scaleway.com/support/tickets) for assistance. + If your IP address is found to be blocklisted, the option cannot be deactivated, and you should reach out to our [Support team](https://console.scaleway.com/support/tickets) for assistance. diff --git a/pages/webhosting/how-to/protect-webhosting.mdx b/pages/webhosting/how-to/protect-webhosting.mdx index 5186684548..a928523b78 100644 --- a/pages/webhosting/how-to/protect-webhosting.mdx +++ b/pages/webhosting/how-to/protect-webhosting.mdx @@ -3,29 +3,27 @@ title: How to use the protected hosting feature description: Learn how to effectively use the protected hosting feature to avoid accidental deletion of your Scaleway Web Hosting plan. tags: protected-hosting protected hosting dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2024-08-16 --- import Requirements from '@macros/iam/requirements.mdx' -The [protected hosting](/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancellations during routine maintenance or management activities. +The [protected hosting](/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancelations during routine maintenance or management activities. - 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 within the intended Organization -- An active [Web Hosting plan](/webhosting/how-to/order-webhosting/) +- [Ordered](/webhosting/how-to/order-webhosting/) a Web Hosting plan 1. Click **Web Hosting** in the **Domains & Web Hosting** section of the side menu. The [Web Hosting dashboard](https://console.scaleway.com/webhosting) displays. -2. Select the Web Hosting plan you want to protect. The **Overview** page for that plan displays. -3. Scroll down to the **Hosting Information** section and click **Enable** next to **Protection** to activate the protected hosting feature. +2. Select the Web Hosting plan you want to protect. The **Overview** page displays. +3. In the **Hosting information** section, click **Enable** next to **Protection** to activate the protected hosting feature. A pop-up displays, asking you to confirm the action. 4. Click **Enable protection** to activate the feature. - To disable protection for your hosting plan, repeat the steps above and toggle off the protection. - - -By following these steps, you ensure that your Web Hosting plan remains secure and protected against any unintended changes. \ No newline at end of file + To disable protection for your hosting plan, repeat the steps above, and click **Disable**, then **Disable protection** to confirm. + \ No newline at end of file diff --git a/pages/webhosting/reference-content/cpanel-reference-content.mdx b/pages/webhosting/reference-content/cpanel-reference-content.mdx index 426ab0c09d..0ca3a72664 100644 --- a/pages/webhosting/reference-content/cpanel-reference-content.mdx +++ b/pages/webhosting/reference-content/cpanel-reference-content.mdx @@ -3,7 +3,7 @@ title: cPanel Web Hosting - Additional content description: This page provides useful links and information for the management and configuration of your Scaleway cPanel Web Hosting plan. tags: webhosting cpanel jetbackup database mailing list mailing-list dates: - validation: 2025-02-17 + validation: 2025-08-27 posted: 2021-09-12 --- diff --git a/tutorials/ark-server/index.mdx b/tutorials/ark-server/index.mdx index e5531aa19f..944187dd44 100644 --- a/tutorials/ark-server/index.mdx +++ b/tutorials/ark-server/index.mdx @@ -49,10 +49,10 @@ In this tutorial, you will learn how to create an ARK server on a [Scaleway Inst - A copy of [ARK: Survival Evolved](https://store.steampowered.com/app/346110/ARK_Survival_Evolved/) for your local computer - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). -Creating an ARK server can be done in a few steps on a [Scaleway Instance](https://www.scaleway.com/en/cost-optimized-instances/). If you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). +Creating an ARK server can be done in a few steps on a [Scaleway Instance](/instances/reference-content/development/). If you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). The ARK: Survival Evolved game server application requires at least 6 GB of RAM to start. Memory requirements increase as the number of connected players increases, as well depending on the activated mods. We recommend that you use at minimum a **DEV1-L** Instance for smooth gameplay. diff --git a/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx b/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx index ce11984b7e..9f2ecc04a9 100644 --- a/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx +++ b/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx @@ -17,10 +17,10 @@ import Requirements from '@macros/iam/requirements.mdx' GitLab serves as an open-core Git repository manager, offering a broad suite of features such as a wiki, issue tracking, and CI/CD pipelines. In the open-core model, the fundamental software functionalities are available under an open-source license, complemented by optional modules. Numerous major technology companies rely on GitLab to oversee their software development life cycles. Originally crafted in Ruby, the platform now incorporates Go and Vue.js within its technology stack. -For those seeking a dependable and high-performance hosting solution, Scaleway Cost-Optimized Instances present an ideal choice for your GitLab infrastructure. They provide a robust infrastructure for hosting your GitLab Instance, coupled with a Managed Database for PostgreSQL. +For those seeking a dependable and high-performance hosting solution, Scaleway Development Instances present an ideal choice for your GitLab infrastructure. They provide a robust infrastructure for hosting your GitLab Instance, coupled with a Managed Database for PostgreSQL. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/create-models-django/index.mdx b/tutorials/create-models-django/index.mdx index 84b8994826..dd957310c5 100644 --- a/tutorials/create-models-django/index.mdx +++ b/tutorials/create-models-django/index.mdx @@ -24,7 +24,7 @@ import Requirements from '@macros/iam/requirements.mdx' To follow this tutorial, we assume that you completed the [first tutorial on Django installation and configuration](/tutorials/django-ubuntu-focal-fossa/). - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/deploy-awstats/index.mdx b/tutorials/deploy-awstats/index.mdx index 7dc046f90a..0de1c5ab14 100644 --- a/tutorials/deploy-awstats/index.mdx +++ b/tutorials/deploy-awstats/index.mdx @@ -29,7 +29,7 @@ AwStats leverages log file analysis to parse data from a wide range of web serve - `sudo` privileges or access to the root user - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). ## Installing Apache diff --git a/tutorials/deploy-chatwoot-self-care/index.mdx b/tutorials/deploy-chatwoot-self-care/index.mdx index 749b52edef..f5ca92719b 100644 --- a/tutorials/deploy-chatwoot-self-care/index.mdx +++ b/tutorials/deploy-chatwoot-self-care/index.mdx @@ -1,6 +1,6 @@ --- -title: Deploying Chatwoot on Scaleway Production-Optimized Instances -description: Learn how to deploy the Chatwoot CRM on Scaleway Production-Optimized Instances with this comprehensive guide. Follow our step-by-step instructions to set up and optimize Chatwoot for seamless customer relationship management on Scaleway. +title: Deploying Chatwoot on Scaleway General Purpose Instances +description: Learn how to deploy the Chatwoot CRM on Scaleway General Purpose Instances with this comprehensive guide. Follow our step-by-step instructions to set up and optimize Chatwoot for seamless customer relationship management on Scaleway. tags: chatwoot crm customer-service products: - instances @@ -27,7 +27,7 @@ Chatwoot is designed to enhance customer satisfaction and improve customer suppo - 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 [Production-Optimized Instance](/instances/how-to/create-an-instance/) with at least 8 GB RAM and 25 GB Block Storage, running on Ubuntu 20.04 LTS or later +- A [General Purpose Instance](/instances/how-to/create-an-instance/) with at least 8 GB RAM and 25 GB Block Storage, running on Ubuntu 20.04 LTS or later - Installed [Ruby 3.2.2](/tutorials/ruby-on-rails/) on your Instance - A (sub-)domain pointed to the Instance's IP address diff --git a/tutorials/deploy-instances-packer-terraform/index.mdx b/tutorials/deploy-instances-packer-terraform/index.mdx index dc899a5f85..ad0a94997e 100644 --- a/tutorials/deploy-instances-packer-terraform/index.mdx +++ b/tutorials/deploy-instances-packer-terraform/index.mdx @@ -27,7 +27,7 @@ Both applications are available for Linux, macOS, Windows, FreeBSD, and NetBSD. - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). ## Downloading and installing Packer @@ -69,7 +69,7 @@ The following are the **required** configuration parameters for a minimal config - `zone` (string) - The name of the zone to launch the server and where the snapshot will be available. -- `commercial_type` (string) - The name of the commercial type used to boot for example: RENDER-S, GP1-L, GP1-M, GP1-S, GP1-XS, ENT1-2XL, ENT1-XL, ENT1-L, ENT1-M, ENT1-S. +- `commercial_type` (string) - The name of the commercial type used to boot for example: RENDER-S, GP1-L, GP1-M, GP1-S, GP1-XS. A basic configuration should look like the following example: diff --git a/tutorials/django-ubuntu-focal-fossa/index.mdx b/tutorials/django-ubuntu-focal-fossa/index.mdx index a3417220bb..6a20e8e6c1 100644 --- a/tutorials/django-ubuntu-focal-fossa/index.mdx +++ b/tutorials/django-ubuntu-focal-fossa/index.mdx @@ -1,5 +1,5 @@ --- -title: Setting up a Django Web Framework on a Scaleway Production-Optimized Instance running Ubuntu 20.04 LTS (Focal Fossa) +title: Setting up a Django Web Framework on a Scaleway General Purpose Instance running Ubuntu 20.04 LTS (Focal Fossa) description: This page shows how to install Django web framework on Ubuntu 20.04 LTS (Focal Fossa) products: - instances @@ -28,7 +28,7 @@ There are many different ways to install Django on Ubuntu: In this tutorial, we install Django using `pip` in a virtual environment, as it is the most practical and most flexible way to install without affecting the larger system, along with other per-project customizations and packages. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/focalboard-project-management/index.mdx b/tutorials/focalboard-project-management/index.mdx index 0ed484350a..190e408b8c 100644 --- a/tutorials/focalboard-project-management/index.mdx +++ b/tutorials/focalboard-project-management/index.mdx @@ -1,6 +1,6 @@ --- title: Project management for technical teams with Focalboard on Ubuntu Instances -description: This page shows how to set up a Focalboard project-management tool on Cost-Optimized Scaleway Instances running Ubuntu Linux +description: This page shows how to set up a Focalboard project-management tool on General Purpose Scaleway Instances running Ubuntu Linux tags: focalboard ubuntu project-management nginx mariadb hero: products: @@ -22,7 +22,7 @@ Focalboard boasts a comprehensive array of functionalities as one of its standou In short, if you are seeking a robust and budget-friendly project management solution, Focalboard unquestionably merits exploration. Its impressive feature set coupled with a commitment to privacy positions it as a tool capable of fostering team organization and goal attainment. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/production-optimized/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/host-github-runner/index.mdx b/tutorials/host-github-runner/index.mdx index 11e090847c..d5a3b4bcd0 100644 --- a/tutorials/host-github-runner/index.mdx +++ b/tutorials/host-github-runner/index.mdx @@ -21,10 +21,10 @@ GitHub Actions stands as a versatile tool, simplifying the automation of all you GitHub offers a limited range of complementary resources for constructing applications through GitHub Actions; however, proficient developers can swiftly encounter these constraints. Teams engaged in professional-grade projects might also want full authority over their build environment. GitHub extends the option to use runners on self-managed instances. A runner function is an application executing tasks from a GitHub Actions workflow. -In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of Production-Optimized Instances provides dedicated resources for enhanced performance. +In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [General Purpose Instance with shared resources](/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of General Purpose Instances with dedicated resouces provides enhanced performance. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/load-testing-vegeta/index.mdx b/tutorials/load-testing-vegeta/index.mdx index dc8135ffcf..e64dc9d519 100644 --- a/tutorials/load-testing-vegeta/index.mdx +++ b/tutorials/load-testing-vegeta/index.mdx @@ -28,7 +28,7 @@ Before transitioning an application to a production environment, load testing he - Identification of performance constraints attributed to technical specifications of employed Instances - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx b/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx index bf1deb9fee..548659fe48 100644 --- a/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx +++ b/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx @@ -17,7 +17,7 @@ pgLoader is an open-source database migration tool developed to simplify the pro The tool supports migrations from several file types and database engines like [MySQL](https://www.mysql.com/), [MS SQL](https://www.microsoft.com/en-us/sql-server/sql-server-2019) and [SQLite](https://www.sqlite.org/index.html). -In this tutorial, you learn how to migrate an existing remote MySQL database to a [Database for PostgreSQL](https://www.scaleway.com/en/database/) using pgLoader and an intermediate [Development Instance](https://www.scaleway.com/en/cost-optimized-instances/) running Ubuntu Linux. +In this tutorial, you learn how to migrate an existing remote MySQL database to a [Database for PostgreSQL](https://www.scaleway.com/en/database/) using pgLoader and an intermediate [Development Instance](/instances/reference-content/development/) running Ubuntu Linux. diff --git a/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx b/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx index 7bd9cce0e5..ba9a8a2576 100644 --- a/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx +++ b/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx @@ -465,7 +465,7 @@ Conduct functional, performance, and end-to-end testing to verify the applicatio ### Leveraging Scaleway features -- **Elastic Metal nodes**: For workloads requiring dedicated resources, consider adding [Production-Optimized or Workload-Optimized nodes](/instances/reference-content/choosing-instance-type/) to your cluster. +- **Elastic Metal nodes**: For workloads requiring dedicated resources, consider adding [General Purpose or Specialized nodes](/instances/reference-content/choosing-instance-type/) to your cluster. - **Autoscaling**: Use cluster and [pod autoscaling](/kubernetes/concepts/#autoscale) to handle variable workloads efficiently. - **Private Networking**: Use [VPC and Private Networks](/vpc/quickstart/) for enhanced security. diff --git a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx index 4700ea35dc..943ece103d 100644 --- a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx +++ b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx @@ -25,13 +25,13 @@ import image11 from './assets/scaleway-rc_admin.webp' import Requirements from '@macros/iam/requirements.mdx' -In this tutorial, you will learn how the Private Network feature can help you to build a distributed [Rocket.Chat](/tutorials/run-messaging-platform-with-rocketchat/) application on [General Purpose](https://www.scaleway.com/en/cost-optimized-instances/) and [Development](https://www.scaleway.com/en/cost-optimized-instances/) Instances using a Private Network to communicate securely between them: +In this tutorial, you will learn how the Private Network feature can help you to build a distributed [Rocket.Chat](/tutorials/run-messaging-platform-with-rocketchat/) application on [General Purpose](/instances/reference-content/development/) and [Development](/instances/reference-content/development/) Instances using a Private Network to communicate securely between them: Private Networks are a LAN-like layer 2 Ethernet network. A new network interface with a unique MAC address is configured on each Instance in a Private Network. You can use this interface to communicate in a secure and isolated network, using private IP addresses of your choice. -To reach the goal of this tutorial, you will use four [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/) running **Ubuntu 24.04 Noble Numbat** or later: +To reach the goal of this tutorial, you will use four [General Purpose Instance](/instances/reference-content/general-purpose/) running **Ubuntu 24.04 Noble Numbat** or later: - 1 POP2-2C-8G Instance as NGINX Proxy frontend, that distributes the load on the Rocket.Chat applications - 1 POP2-8C-32G Instance as MongoDB® host @@ -39,7 +39,7 @@ To reach the goal of this tutorial, you will use four [Production-Optimized Inst - A [Private Network](/vpc/quickstart/) between these Instances - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/plausible-analytics-ubuntu/index.mdx b/tutorials/plausible-analytics-ubuntu/index.mdx index 01a40bcd84..702c4a157f 100644 --- a/tutorials/plausible-analytics-ubuntu/index.mdx +++ b/tutorials/plausible-analytics-ubuntu/index.mdx @@ -1,6 +1,6 @@ --- title: Running web analytics with Plausible on Ubuntu Linux -description: This page shows how to generate web analytics with Plausible on Cost-Optimized Instances running Ubuntu Linux +description: This page shows how to generate web analytics with Plausible on Development Instances running Ubuntu Linux tags: plausible ubuntu analytics hero: products: @@ -17,7 +17,7 @@ Plausible Analytics is an open-source web analytics initiative driven by the goa This tool significantly contributes to the enhancement of site performance, with its analytics script weighing in at less than 1 KB. This is 45 times smaller than the size tag of a typical commercial analytics solution. Plausible Analytics is intentionally designed for self-hosting through Docker, providing you with control over your analytics setup. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx b/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx index 64ca657d43..a93a54b8b3 100644 --- a/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx +++ b/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx @@ -28,7 +28,7 @@ In this tutorial, you will learn how to use a Prometheus Monitoring Instance wit - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). ## Preparing your environment diff --git a/tutorials/protect-server-fail2ban/index.mdx b/tutorials/protect-server-fail2ban/index.mdx index f363df519e..eb9fa3a94f 100644 --- a/tutorials/protect-server-fail2ban/index.mdx +++ b/tutorials/protect-server-fail2ban/index.mdx @@ -5,7 +5,7 @@ tags: security Fail2Ban brute-force products: - instances dates: - validation: 2025-04-08 + validation: 2025-08-25 posted: 2018-08-22 validation_frequency: 12 --- @@ -13,10 +13,8 @@ import image from './assets/scaleway-postfix-install.webp' import Requirements from '@macros/iam/requirements.mdx' - -Fail2Ban is a useful tool that analyses server log files for recurring patterns of failures. This allows blocking IPs trying to run brute force attacks against a server. - -In this tutorial, you will learn how to configure the service on an Ubuntu Bionic server to protect the SSH service. Fail2Ban can be used with all services generating log files. +Fail2Ban is a powerful tool that analyzes server log files for recurring patterns of failed login attempts, enabling the blocking of IPs attempting brute force attacks against a server. +In this tutorial, you will learn how to configure Fail2Ban on an Ubuntu 24.04 LTS (Noble Numbat) server to protect the SSH service. Fail2Ban can be used with any service that generates log files. @@ -28,79 +26,87 @@ In this tutorial, you will learn how to configure the service on an Ubuntu Bioni ## Installing Fail2Ban -1. The required packages are available in the repositories of Ubuntu and can be installed with `apt`: - ``` +1. Install Fail2Ban and Postfix (optional, for email notifications) using the package manager: + ```bash sudo apt-get install fail2ban postfix ``` -2. Choose `Internet Site` when asked for the configuration: +2. During Postfix installation, select **Internet Site** when prompted for configuration. -3. Once the installation has completed, open the file `/etc/aliases` and add the following line: + +3. After installation, edit `/etc/aliases` to configure email notifications: + ```bash + sudo nano /etc/aliases ``` + +4. Add the following line, replacing me@mydomain.tld with your email address: + ```bash root: me@mydomain.tld ``` - Make sure to replace `me@mydomain.tld` with your actual email address. - - - To receive notifications by email, it is required that the [email ports are unlocked](/instances/how-to/send-emails-from-your-instance/). - +5. Save the file, exit nano and run the following command: + ```bash + sudo newaliases + ``` + + - To receive email notifications, ensure outbound email ports (e.g., 25, 587) are open on your server. + - Postfix is optional. Alternatives like `ssmtp` or external SMTP services can be used for notifications. + ## Configuring Fail2Ban -1. Start by copying the configuration file: - ``` +1. Copy the default configuration file to create a custom configuration: + ```bash cd /etc/fail2ban && sudo cp jail.conf jail.local ``` + The jail.local file overrides jail.conf for custom settings, preserving the default configuration. - The file `jail.conf` contains the default parameters. If a file `jail.local` is available, it will have priority over `jail.conf` if parameters are modified. -2. Edit the file `/etc/fail2ban/jail.local` with your preferred editor. - - Following are the parameters which should be modified: - - `ignoreip = 127.0.0.1/8` - By default the IPs of localhost are ignored, self-banning would not be very useful. It is possible to exclude other IPs from being banned. - - `bantime = 600` - The duration of a ban. By default, it is set to 10 Minutes. The value has to be specified in seconds and it is recommended to set it at least to one hour, or one day. - - `findtime = 600` - The timespan which will be considered for maxretry. If you want for example to ban somebody who made more than 3 malicious attempts during the last hour or, as here, in the last 10 minutes. - - `maxretry = 3` - Amount of attempts before being banned. - - `destemail = root@localhost` - The recipient of the mail. As an alias for root has been set during the installation, this value can be left as it is. - - `sendername = Fail2Ban` - The name of the sender of the mail. - - `action = %(action_)s` - This defines the action to execute when a limit is reached. - By default, it will only block the user. - - To receive an email at each ban, set it to: - - - `action = %(action_mw)` - - To receive the logs with the mail, set it to: - - - `action = %(action_mwl)` - - Further down in the configuration file, it comes to the “Jails”. These are configurable blocks per service to filter logs and ban in cases where patterns are matched. - As a minimum, it is recommended to activate the jail ssh as follows: - ``` - [ssh] - - enabled = true - port = ssh - filter = sshd - logpath = /var/log/auth.log - ``` - - - If your SSH daemon is listening on multiple ports or a different port, you have to modify the line port with the correct parameters: - For example: - ``` - port = ssh,1234 - ``` - Fail2Ban analyses the logs and will ban the users who made several intrusion attempts on ports 22 (SSH by default) & 1234. - -3. Save the file once you have edited it. - - Fail2Ban uses filters, pre-made configuration files indicating what to parse in a log. - - They can be found in `/etc/fail2ban/filter.d`. - You can create your own filters in case you need to. -4. Restart the service to take the actions into effect: +2. Edit `/etc/fail2ban/jail.local` with your preferred editor (e.g., nano): + ```bash + sudo nano /etc/fail2ban/jail.local + ``` + Modify the following parameters: + ```bash + ignoreip = 127.0.0.1/8 - Ignores localhost IPs to prevent self-banning. Add other trusted IPs if needed (e.g., 127.0.0.1/8 192.168.1.0/24). + bantime = 3600 - Duration of a ban, set to 1 hour (3600 seconds) by default in newer versions. Consider increasing to 86400 (1 day) for stronger protection. + findtime = 3600 - Time window for counting failed attempts (1 hour). Adjust to 600 (10 minutes) for stricter monitoring if preferred. + maxretry = 5 - Number of failed attempts before a ban. The default in Ubuntu 24.04 is 5. + destemail = root@localhost - Email recipient for notifications. Leave as is if /etc/aliases is configured. + sendername = Fail2Ban - Sender name for notification emails. + banaction = nftables[multiport] - Default ban action using nftables, which is preferred in Ubuntu 24.04 over iptables. + action = %(action_mwl)s - Sends email with logs when banning. Use %(action_mw)s for email without logs, or %(action_)s for no email. ``` - sudo service fail2ban restart + +3. Enable the SSH jail by ensuring the following configuration is present: + ```bash + [sshd] + enabled = true + port = ssh + filter = sshd + logpath = /var/log/auth.log + ``` + If your SSH service uses a non-standard port, update the `port` line. For example, for ports 22 and 1234: + ``` + port = ssh,1234 + ``` + Fail2Ban will monitor the specified ports for intrusion attempts. + + For systems using `systemd` logging (e.g., Proxmox), use: + ``` + [sshd] + enabled = true + port = ssh + filter = sshd + logpath = %(sshd_log)s + backend = systemd + ``` + + +4. Save the file. + Fail2Ban uses filter files in `/etc/fail2ban/filter.d` to parse logs. The `sshd` filter is pre-configured for SSH. Custom [filters](https://fail2ban.readthedocs.io/en/latest/filters.html) can be created for other services. + +5. Restart Fail2Ban to apply changes: + ```bash + sudo systemctl restart fail2ban ``` -The service will now analyze the connections made to the SSH service. The logs of Fail2Ban are located in the file `var/log/fail2ban.log`. \ No newline at end of file +Fail2Ban will now monitor SSH connections. Check logs at `/var/log/fail2ban.log` for activity. diff --git a/tutorials/rtmp-self-hosted-streaming/index.mdx b/tutorials/rtmp-self-hosted-streaming/index.mdx index 397e1ca61a..25cf0faf30 100644 --- a/tutorials/rtmp-self-hosted-streaming/index.mdx +++ b/tutorials/rtmp-self-hosted-streaming/index.mdx @@ -26,7 +26,7 @@ For individuals craving absolute control over their content, open-source solutio Using the open-source [RTMP protocol](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol) on self-hosted streaming servers, users gain autonomy to manage their content free from external constraints and interruptions. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/sentry-error-tracking/index.mdx b/tutorials/sentry-error-tracking/index.mdx index 03e44c3a3c..e8bd928cfa 100644 --- a/tutorials/sentry-error-tracking/index.mdx +++ b/tutorials/sentry-error-tracking/index.mdx @@ -25,7 +25,7 @@ Crafted using Python, Sentry employs a client/server architecture that facilitat With Sentry as your ally, you can streamline your development workflow, enhance your applications, and provide your users with the seamless experience they desire. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/production-optimized/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). You can find all reports on a dashboard, which makes it easy to triage the problem, how often it occurs, its impact on the user experience, which part of your code causes the problem, and so on. diff --git a/tutorials/setup-minecraft/index.mdx b/tutorials/setup-minecraft/index.mdx index e4e299e251..2ecaf3aa2b 100644 --- a/tutorials/setup-minecraft/index.mdx +++ b/tutorials/setup-minecraft/index.mdx @@ -53,10 +53,10 @@ The Minecraft server is a Java application and runs perfectly on [Scaleway Insta - `sudo` privileges or access to the root user - A copy of the [Minecraft game client](https://www.minecraft.net/en-us/) for your local computer -Deploying your own Minecraft server can be done in a few easy steps on a [Scaleway Development Instance](https://www.scaleway.com/en/cost-optimized-instances/). In case you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). +Deploying your own Minecraft server can be done in a few easy steps on a [Scaleway Development Instance](/instances/reference-content/development/). In case you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/) with at least 8GB of RAM. + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/) with at least 8GB of RAM. 1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). diff --git a/tutorials/setup-mongodb-on-ubuntu/index.mdx b/tutorials/setup-mongodb-on-ubuntu/index.mdx index 5b60570ea9..2a8b5ff59d 100644 --- a/tutorials/setup-mongodb-on-ubuntu/index.mdx +++ b/tutorials/setup-mongodb-on-ubuntu/index.mdx @@ -16,10 +16,10 @@ import Requirements from '@macros/iam/requirements.mdx' Diverging from traditional relational databases, MongoDB® users no longer need an intricate predefined schema before adding data. This flexibility stems from its ability to modify schemas at any point in time. Embracing the NoSQL philosophy, it employs JSON-like documents for data storage, allowing the insertion of diverse and arbitrary data. -Powerful [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/) comes with the compute and storage capabilities you need to run your MongoDB® Instance smoothly. +Powerful [General Purpose Instance](/instances/reference-content/general-purpose/) comes with the compute and storage capabilities you need to run your MongoDB® Instance smoothly. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purposeance](/instances/reference-content/choosing-instance-type/). diff --git a/tutorials/setup-postfix-ubuntu-bionic/index.mdx b/tutorials/setup-postfix-ubuntu-bionic/index.mdx index a2be48bc0f..b308b9fb5e 100644 --- a/tutorials/setup-postfix-ubuntu-bionic/index.mdx +++ b/tutorials/setup-postfix-ubuntu-bionic/index.mdx @@ -16,7 +16,7 @@ In this tutorial you will learn how to configure a mail server that uses Postfi You learn also how to install a Roundcube webmail interface to be able to read your emails directly from your browser. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/wordpress-instantapp/index.mdx b/tutorials/wordpress-instantapp/index.mdx index d6ed8aa6ec..06268d0272 100644 --- a/tutorials/wordpress-instantapp/index.mdx +++ b/tutorials/wordpress-instantapp/index.mdx @@ -30,7 +30,7 @@ This guide demonstrates how to quickly deploy a WordPress application in seconds - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/cost-optimized/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx b/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx index e08df3042a..1c1789ffda 100644 --- a/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx +++ b/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx @@ -18,10 +18,10 @@ import Requirements from '@macros/iam/requirements.mdx' WordPress is a popular and freely accessible open-source tool that offers a seamless means to craft and manage content on your website. With its intuitive interface and user-friendly features, WordPress has garnered extensive adoption, making it an ideal solution for swiftly launching a website. The web front-end it provides ensures effortless administration, simplifying the process even for those lacking technical expertise. -If you are seeking to install WordPress on a newly established Ubuntu 22.04 LTS Instance, this tutorial is tailor-made for your needs. We will meticulously walk you through the installation steps, employing the LEMP stack (Linux + Nginx - pronounced "engine x" + MySQL + PHP). For the sake of this tutorial, we are choosing Nginx, a robust HTTP server that is efficient in resource usage, resulting in faster page delivery, especially for static content. By opting for a Cost-Optimized Instance configured with LEMP, you will gain access to a robust web server that elevates website performance, thus ensuring a seamless WordPress installation experience. +If you are seeking to install WordPress on a newly established Ubuntu 22.04 LTS Instance, this tutorial is tailor-made for your needs. We will meticulously walk you through the installation steps, employing the LEMP stack (Linux + Nginx - pronounced "engine x" + MySQL + PHP). For the sake of this tutorial, we are choosing Nginx, a robust HTTP server that is efficient in resource usage, resulting in faster page delivery, especially for static content. By opting for a General Purpose Instance configured with LEMP, you will gain access to a robust web server that elevates website performance, thus ensuring a seamless WordPress installation experience. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/zabbix-monitoring/index.mdx b/tutorials/zabbix-monitoring/index.mdx index ec79f31004..81aa075899 100644 --- a/tutorials/zabbix-monitoring/index.mdx +++ b/tutorials/zabbix-monitoring/index.mdx @@ -29,10 +29,10 @@ Zabbix is a powerful open-source software that offers real-time monitoring for s This monitoring tool enables users to determine the health status of their IT infrastructure and analyze data over time. The insights provided by Zabbix can be used to plan upgrades to the infrastructure when requirements grow. -In this tutorial, we will use two Scaleway [Production-Optimized](/instances/reference-content/choosing-instance-type/) Ubuntu Jammy Jellyfish (22.04 LTS) Instances. One Instance will be a server hosting the Zabbix application, while the other will be a client being monitored. Following this tutorial will teach you how to set up Zabbix and take control of your IT infrastructure. +In this tutorial, we will use two Scaleway [General Purpose](/instances/reference-content/choosing-instance-type/) Ubuntu Jammy Jellyfish (22.04 LTS) Instances. One Instance will be a server hosting the Zabbix application, while the other will be a client being monitored. Following this tutorial will teach you how to set up Zabbix and take control of your IT infrastructure. - We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). diff --git a/tutorials/zammad-ticketing/index.mdx b/tutorials/zammad-ticketing/index.mdx index 4aa8f7776e..ca74a80e65 100644 --- a/tutorials/zammad-ticketing/index.mdx +++ b/tutorials/zammad-ticketing/index.mdx @@ -26,7 +26,7 @@ Zammad is an open-source helpdesk system that allows you to oversee customer int This tutorial will guide you through the process of installing Zammad on a Scaleway Instance operating on **Ubuntu 20.04 LTS (Focal Fossa)**. Furthermore, you will receive a brief orientation of the application. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). If you are installing Zammad on Ubuntu 22.04 and up, avoid using an Instance with ARM architecure to follow this tutorial, as the package manager used upon installation is not compatible with the ARM architecture. + We recommend you follow this tutorial using a [General Purpose Instance](/instances/reference-content/general-purpose/). If you are installing Zammad on Ubuntu 22.04 and up, avoid using an Instance with ARM architecure to follow this tutorial, as the package manager used upon installation is not compatible with the ARM architecture.