diff --git a/changelog/april2025/2025-04-08-public-gateways-changed-new-public-gateway-api-v2.mdx b/changelog/april2025/2025-04-08-public-gateways-changed-new-public-gateway-api-v2.mdx index ea20358765..2ef9598f09 100644 --- a/changelog/april2025/2025-04-08-public-gateways-changed-new-public-gateway-api-v2.mdx +++ b/changelog/april2025/2025-04-08-public-gateways-changed-new-public-gateway-api-v2.mdx @@ -6,7 +6,7 @@ category: network product: public-gateways --- -We have released a new [Public Gateways API v2](https://www.scaleway.com/en/developers/api/public-gateway/), which comes with a new security feature for SSH bastion: [Allowed IPs](https://www.scaleway.com/en/docs/public-gateways/concepts/#allowed-ips). This version also removes some old DHCP features that are now managed by the IPAM and the built-in DHCP of the Private Networks. +We have released a new [Public Gateways API v2](https://www.scaleway.com/en/developers/api/public-gateways/), which comes with a new security feature for SSH bastion: [Allowed IPs](https://www.scaleway.com/en/docs/public-gateways/concepts/#allowed-ips). This version also removes some old DHCP features that are now managed by the IPAM and the built-in DHCP of the Private Networks. The API v1 is now deprecated and will be definitively removed by October 1, 2025. Public Gateways users are encouraged to migrate to the API v2. [Learn more in our detailed documentation.](/public-gateways/reference-content/understanding-v2/) diff --git a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-nats.mdx b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-nats.mdx index e86ad7eb5a..1a984ebb44 100644 --- a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-nats.mdx +++ b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-nats.mdx @@ -9,5 +9,5 @@ category: serverless product: nats --- -Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/), must now be used going forward. +Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/queues/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/nats/nats-api/), must now be used going forward. diff --git a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-queues.mdx b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-queues.mdx index cae9c4b4ce..0755349aac 100644 --- a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-queues.mdx +++ b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-queues.mdx @@ -9,5 +9,5 @@ category: serverless product: queues --- -Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/), must now be used going forward. +Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/queues/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/nats/nats-api/), must now be used going forward. diff --git a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-topics.mdx b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-topics.mdx index 33aba22349..03259b2bcc 100644 --- a/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-topics.mdx +++ b/changelog/december2023/2023-12-04-messaging-and-queuing-deprecated-api-v1alpha1-topics.mdx @@ -9,5 +9,5 @@ category: serverless product: topics-and-events --- -Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/), must now be used going forward. +Effective December 1st 2023, the Messaging and Queuing v1alpha1 API has been deprecated and its resources and endpoints are no longer available. The v1beta1 APIs, available for Messaging and Queuing [SQS](https://www.scaleway.com/en/developers/api/queues/sqs-api/), [SNS](https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/) and [NATS](https://www.scaleway.com/en/developers/api/nats/nats-api/), must now be used going forward. diff --git a/changelog/july2025/2025-07-11-mongodb-added-managed-mongodb-v1-api.mdx b/changelog/july2025/2025-07-11-mongodb-added-managed-mongodb-v1-api.mdx index 11e2b23a66..acde06ba32 100644 --- a/changelog/july2025/2025-07-11-mongodb-added-managed-mongodb-v1-api.mdx +++ b/changelog/july2025/2025-07-11-mongodb-added-managed-mongodb-v1-api.mdx @@ -6,4 +6,4 @@ category: databases product: mongodb --- -The Managed MongoDB API is now in `v1`. All new features from now on will not be available on `v1alpha1`. Check [the Managed MongoDB API documentation](https://www.scaleway.com/en/developers/api/managed-database-mongodb/) for more information. +The Managed MongoDB API is now in `v1`. All new features from now on will not be available on `v1alpha1`. Check [the Managed MongoDB API documentation](https://www.scaleway.com/en/developers/api/managed-mongodb-databases/) for more information. diff --git a/changelog/march2024/2024-03-19-block-storage-added-block-storage-new-user-journey-and-.mdx b/changelog/march2024/2024-03-19-block-storage-added-block-storage-new-user-journey-and-.mdx index e3d134638e..04b5641cb2 100644 --- a/changelog/march2024/2024-03-19-block-storage-added-block-storage-new-user-journey-and-.mdx +++ b/changelog/march2024/2024-03-19-block-storage-added-block-storage-new-user-journey-and-.mdx @@ -10,5 +10,5 @@ product: block-storage --- We are excited to introduce our new [Block Storage Low Latency](/block-storage/quickstart/) offers with 5K and 15K IOPS! -You can now create Block Storage Low Latency volumes through the [Scaleway console](https://console.scaleway.com/) and [API](https://www.scaleway.com/en/developers/api/block/). +You can now create Block Storage Low Latency volumes through the [Scaleway console](https://console.scaleway.com/) and [API](https://www.scaleway.com/en/developers/api/block-storage/). diff --git a/changelog/may2025/2025-05-14-instances-removed-block-storage-volume-creation-removed.mdx b/changelog/may2025/2025-05-14-instances-removed-block-storage-volume-creation-removed.mdx index c97747eb2c..ad55519024 100644 --- a/changelog/may2025/2025-05-14-instances-removed-block-storage-volume-creation-removed.mdx +++ b/changelog/may2025/2025-05-14-instances-removed-block-storage-volume-creation-removed.mdx @@ -6,5 +6,5 @@ category: compute product: instances --- -Since April 30th 2025, it has become impossible to **CREATE** new block volumes using the Instance API (or through associated developer tools). Customers can only list, mount, unmount or delete volumes through the Instance API. Block volume creation and management must go through the Block Storage API. Learn more about the advantages of migrating from the Instance API to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/) for [managing block volumes and snapshots](/block-storage/reference-content/advantages-migrating-to-sbs/). +Since April 30th 2025, it has become impossible to **CREATE** new block volumes using the Instance API (or through associated developer tools). Customers can only list, mount, unmount or delete volumes through the Instance API. Block volume creation and management must go through the Block Storage API. Learn more about the advantages of migrating from the Instance API to the [Block Storage API](https://www.scaleway.com/en/developers/api/block-storage/) for [managing block volumes and snapshots](/block-storage/reference-content/advantages-migrating-to-sbs/). diff --git a/changelog/september2024/2024-09-11-public-gateways-added-public-gateway-upgrade.mdx b/changelog/september2024/2024-09-11-public-gateways-added-public-gateway-upgrade.mdx index a665e6d5da..6de1c9b2d0 100644 --- a/changelog/september2024/2024-09-11-public-gateways-added-public-gateway-upgrade.mdx +++ b/changelog/september2024/2024-09-11-public-gateways-added-public-gateway-upgrade.mdx @@ -9,5 +9,5 @@ category: network product: public-gateways --- -Users can now upgrade their Public Gateway to a higher range from the [Scaleway console](https://console.scaleway.com/) or through the [Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateway/). +Users can now upgrade their Public Gateway to a higher range from the [Scaleway console](https://console.scaleway.com/) or through the [Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateways/). diff --git a/macros/compute/instances-block-bandwidth-overview.mdx b/macros/compute/instances-block-bandwidth-overview.mdx index 2c9c59fef1..3d9683e29e 100644 --- a/macros/compute/instances-block-bandwidth-overview.mdx +++ b/macros/compute/instances-block-bandwidth-overview.mdx @@ -12,7 +12,7 @@ Bandwidth impacts how your applications perform and interact with other systems. - **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. - Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. + Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. diff --git a/macros/storage/block-storage-migration.mdx b/macros/storage/block-storage-migration.mdx index 2fbb423497..75ae8972ef 100644 --- a/macros/storage/block-storage-migration.mdx +++ b/macros/storage/block-storage-migration.mdx @@ -4,7 +4,7 @@ macro: block-storage-migration

- - Scaleway is transitioning the management of all block volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instance/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block/). + - Scaleway is transitioning the management of all block volumes and snapshots from the [Instance API](https://www.scaleway.com/en/developers/api/instances/) to the [Block Storage API](https://www.scaleway.com/en/developers/api/block-storage/). - Find out about the [advantages of migrating the management of your volumes and snapshots](/block-storage/reference-content/advantages-migrating-to-sbs/) from the Instance API to the Block Storage API. - Find out how to [migrate your Block Storage volumes and snapshots](/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API. diff --git a/pages/block-storage/api-cli/increasing-volume-size.mdx b/pages/block-storage/api-cli/increasing-volume-size.mdx index 6e0261add2..d7de7f32a3 100644 --- a/pages/block-storage/api-cli/increasing-volume-size.mdx +++ b/pages/block-storage/api-cli/increasing-volume-size.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -The Block storage API allows you to interact with Block Storage volumes programmatically through API calls. Refer to the [Developers reference website](https://www.scaleway.com/en/developers/api/block/) for more information on how to use the Block Storage API. +The Block storage API allows you to interact with Block Storage volumes programmatically through API calls. Refer to the [Developers reference website](https://www.scaleway.com/en/developers/api/block-storage/) for more information on how to use the Block Storage API. diff --git a/pages/block-storage/faq.mdx b/pages/block-storage/faq.mdx index 3aaf9ae8cc..1daa065d11 100644 --- a/pages/block-storage/faq.mdx +++ b/pages/block-storage/faq.mdx @@ -77,7 +77,7 @@ Although there is no direct way to change the storage class of a volume while pr 1. [Create a snapshot of your Block Storage legacy volume](/block-storage/how-to/create-a-snapshot/). 2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). -3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). +3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block-storage/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). ## Can I manage my Block Storage volumes using the Scaleway Instances API? diff --git a/pages/block-storage/how-to/attach-a-volume.mdx b/pages/block-storage/how-to/attach-a-volume.mdx index cda2273f3b..d55c615322 100644 --- a/pages/block-storage/how-to/attach-a-volume.mdx +++ b/pages/block-storage/how-to/attach-a-volume.mdx @@ -41,7 +41,7 @@ You can also attach a Block storage to an Instance the following way: To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. - Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. + Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. diff --git a/pages/block-storage/how-to/create-a-volume.mdx b/pages/block-storage/how-to/create-a-volume.mdx index c099b1fe39..ff1101175f 100644 --- a/pages/block-storage/how-to/create-a-volume.mdx +++ b/pages/block-storage/how-to/create-a-volume.mdx @@ -25,7 +25,7 @@ import Requirements from '@macros/iam/requirements.mdx' To use **Block Storage Low Latency 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/block-storage/reference-content/block-instances-bandwidth-overview/) documentation. - Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. + Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. - Define a volume size of at least 5 GB. diff --git a/pages/block-storage/index.mdx b/pages/block-storage/index.mdx index 9f38da0d34..0104c48c7f 100644 --- a/pages/block-storage/index.mdx +++ b/pages/block-storage/index.mdx @@ -71,7 +71,7 @@ description: Explore Scaleway Block Storage Low Latency with quickstart guides, productLogo="cli" title="Block Storage API" description="Manage Block Storage using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/block/" + url="https://www.scaleway.com/en/developers/api/block-storage/" label="Go to Block Storage API" /> diff --git a/pages/block-storage/menu.ts b/pages/block-storage/menu.ts index 088087737c..12fa8d12c1 100644 --- a/pages/block-storage/menu.ts +++ b/pages/block-storage/menu.ts @@ -66,7 +66,7 @@ export const blockStorageMenu = { items: [ { label: 'Block Storage API Reference', - slug: 'https://www.scaleway.com/en/developers/api/block/', + slug: 'https://www.scaleway.com/en/developers/api/block-storage/', }, { label: 'Managing a volume', diff --git a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx index c4ec595bd5..d10b2eee98 100644 --- a/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx +++ b/pages/block-storage/reference-content/block-instances-bandwidth-overview.mdx @@ -23,7 +23,7 @@ Bandwidth impacts how your applications perform and interact with other systems. - **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. - Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. + Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. diff --git a/pages/container-registry/index.mdx b/pages/container-registry/index.mdx index a36c8e4a0c..de47533aa4 100644 --- a/pages/container-registry/index.mdx +++ b/pages/container-registry/index.mdx @@ -67,7 +67,7 @@ description: Dive into Scaleway Container Registry with our quickstart guides, h productLogo="cli" title="Container Registry API" description="Manage your Container Registry namespaces and images using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/registry/" + url="https://www.scaleway.com/en/developers/api/container-registry/" label="Go to Container Registry API" /> diff --git a/pages/container-registry/menu.ts b/pages/container-registry/menu.ts index 1ff003575a..d1d40ccd21 100644 --- a/pages/container-registry/menu.ts +++ b/pages/container-registry/menu.ts @@ -62,7 +62,7 @@ export const containerRegistryMenu = { items: [ { label: 'Container Registry API Reference', - slug: 'https://www.scaleway.com/en/developers/api/registry/', + slug: 'https://www.scaleway.com/en/developers/api/container-registry/', }, ], label: 'API/CLI', diff --git a/pages/container-registry/troubleshooting/index.mdx b/pages/container-registry/troubleshooting/index.mdx index 089a9c413b..76427b593f 100644 --- a/pages/container-registry/troubleshooting/index.mdx +++ b/pages/container-registry/troubleshooting/index.mdx @@ -30,7 +30,7 @@ productIcon: RegistryProductIcon diff --git a/pages/gpu/index.mdx b/pages/gpu/index.mdx index 6bb7bae909..f7f5c8b252 100644 --- a/pages/gpu/index.mdx +++ b/pages/gpu/index.mdx @@ -63,7 +63,7 @@ description: Dive into Scaleway GPU Instances with our quickstart guides, how-to productLogo="cli" title="Instances API" description="Learn how to create and manage your Scaleway GPU Instances through the API." - url="https://www.scaleway.com/en/developers/api/instance/" + url="https://www.scaleway.com/en/developers/api/instances/" label="Go to Instances API" /> diff --git a/pages/gpu/menu.ts b/pages/gpu/menu.ts index 80f2cb2c5e..81d0ff1dbe 100644 --- a/pages/gpu/menu.ts +++ b/pages/gpu/menu.ts @@ -50,7 +50,7 @@ export const gpuMenu = { items: [ { label: 'Instances API Reference', - slug: 'https://www.scaleway.com/en/developers/api/instance/', + slug: 'https://www.scaleway.com/en/developers/api/instances/', }, ], label: 'API/CLI', diff --git a/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx b/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx index 56a3fc39a4..88409c79dc 100644 --- a/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx +++ b/pages/gpu/reference-content/gpu-instances-bandwidth-overview.mdx @@ -17,7 +17,7 @@ GPU workloads often involve processing large datasets, requiring high-bandwidth - **Block bandwidth**: Impacts data access speeds for datasets stored in Block Storage, optimizing performance for AI pipelines, rendering workflows, and other data-intensive applications. - Bandwidth specifications listed here are for informational purposes only. To validate the exact bandwidth capacity of your GPU Instance, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve GPU Instance specifications. + Bandwidth specifications listed here are for informational purposes only. To validate the exact bandwidth capacity of your GPU Instance, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve GPU Instance specifications. diff --git a/pages/gpu/reference-content/understanding-nvidia-ngc.mdx b/pages/gpu/reference-content/understanding-nvidia-ngc.mdx index d04f52324b..ed175b3a1b 100644 --- a/pages/gpu/reference-content/understanding-nvidia-ngc.mdx +++ b/pages/gpu/reference-content/understanding-nvidia-ngc.mdx @@ -10,7 +10,7 @@ dates: NVIDIA provides access to NVIDIA GPU Cloud (NGC) through providers including Scaleway. NGC is a cloud-based platform that offers a comprehensive set of GPU-optimized software and tools for various deep learning, machine learning, and AI (Artificial Intelligence) tasks. It is designed to simplify deploying, managing, and utilizing AI and data science frameworks on NVIDIA GPUs. Unleash the power of your applications' deployment with Scaleway and NGC, where seamless deployment is as effortless as following these three simple steps: -1. Deploy your Scaleway GPU Instance from the [Scaleway console](https://console.scaleway.com/instance/servers/create?imageKey=7bdc1afb-231f-486a-9b85-1b0478bc0e4a&offerName=RENDER-S&zone=fr-par-2), the [CLI tools](https://github.com/scaleway/scaleway-cli), or the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/).1 +1. Deploy your Scaleway GPU Instance from the [Scaleway console](https://console.scaleway.com/instance/servers/create?imageKey=7bdc1afb-231f-486a-9b85-1b0478bc0e4a&offerName=RENDER-S&zone=fr-par-2), the [CLI tools](https://github.com/scaleway/scaleway-cli), or the [Scaleway API](https://www.scaleway.com/en/developers/api/instances/).1 1 You need [GPU Instance quotas](/organizations-and-projects/additional-content/organization-quotas/#gpu-instances) to be able to deploy GPU Instances. 2. Configure your Instance by pulling the required packages from NVIDIA NGC. 3. Run your application. diff --git a/pages/instances/api-cli/creating-backups.mdx b/pages/instances/api-cli/creating-backups.mdx index 2e3c2b823f..7e713547b7 100644 --- a/pages/instances/api-cli/creating-backups.mdx +++ b/pages/instances/api-cli/creating-backups.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -The Backup feature is used to back up your Instance data. It creates an image of a snapshot that contains all your volumes. You can create backups of your Instances using either the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). +The Backup feature is used to back up your Instance data. It creates an image of a snapshot that contains all your volumes. You can create backups of your Instances using either the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instances/). @@ -45,7 +45,7 @@ The Backup feature is used to back up your Instance data. It creates an image of - A backup is created using the [Instances API](https://www.scaleway.com/en/developers/api/instance/) with the following command: + A backup is created using the [Instances API](https://www.scaleway.com/en/developers/api/instances/) with the following command: ``` POST https://api.scaleway.com/instance/v1/zones//servers//action {"action":"backup"} diff --git a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx index 1a51ae3023..63c0cc9564 100644 --- a/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/pages/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -Scaleway Instances provide you with resources to develop, test code and deploy your applications in no time. Instances are designed for modern workflows. They are with you from prototyping to large-scale deployment. You can [create](/instances/how-to/create-an-instance/) and manage your Instances from the [console](https://account.scaleway.com/login), via the [API](https://www.scaleway.com/en/developers/api/instance/) or the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). +Scaleway Instances provide you with resources to develop, test code and deploy your applications in no time. Instances are designed for modern workflows. They are with you from prototyping to large-scale deployment. You can [create](/instances/how-to/create-an-instance/) and manage your Instances from the [console](https://account.scaleway.com/login), via the [API](https://www.scaleway.com/en/developers/api/instances/) or the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). ## Scaleway Command Line Interface (CLI) overview diff --git a/pages/instances/api-cli/migrating-instances.mdx b/pages/instances/api-cli/migrating-instances.mdx index a3f120ea72..f52a9a8d97 100644 --- a/pages/instances/api-cli/migrating-instances.mdx +++ b/pages/instances/api-cli/migrating-instances.mdx @@ -9,7 +9,7 @@ dates: import Requirements from '@macros/iam/requirements.mdx' -It is possible to change the commercial type of an Instance using the [Scaleway CLI](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). +It is possible to change the commercial type of an Instance using the [Scaleway CLI](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instances/). To do so, you need the Instance’s ID and a valid API key. @@ -141,6 +141,6 @@ To do so, you need the Instance’s ID and a valid API key. } ``` - For more information on using the API, refer to the complete [API documentation](https://www.scaleway.com/en/developers/api/instance/). + For more information on using the API, refer to the complete [API documentation](https://www.scaleway.com/en/developers/api/instances/). \ No newline at end of file diff --git a/pages/instances/api-cli/using-placement-groups.mdx b/pages/instances/api-cli/using-placement-groups.mdx index a38bac0285..53fcc82eb5 100644 --- a/pages/instances/api-cli/using-placement-groups.mdx +++ b/pages/instances/api-cli/using-placement-groups.mdx @@ -199,7 +199,7 @@ curl -q \ We hope that placement groups will help you build more performant and more reliable systems with Scaleway's products. -For more information and to see the full capabilities of placement groups, refer to the [full API documentation](https://www.scaleway.com/en/developers/api/instance/#path-placement-groups). +For more information and to see the full capabilities of placement groups, refer to the [full API documentation](https://www.scaleway.com/en/developers/api/instances/#path-placement-groups). Remember that a placement group will work only according to the following rules: - Instances must be in the same Availability Zone, diff --git a/pages/instances/concepts.mdx b/pages/instances/concepts.mdx index 29985f57e3..8cbdc6f696 100644 --- a/pages/instances/concepts.mdx +++ b/pages/instances/concepts.mdx @@ -43,7 +43,7 @@ Cloud-init is a multi-distribution package that [provides boot time customizatio A dynamic IP is an alternative type of public IP address for your Instance. This type of IP address is detached and released back into the general public pool of IP addresses whenever you stop your Instance. This means when you next power on your Instance, it may get a different dynamic IP address. In this respect, dynamic IPs are different from [flexible IPs](#flexible-ip), which remain associated with your Instance even when the Instance is stopped and are held in your account and can be moved between different Instances if you wish. -You can choose to give your Instance a dynamic IP address when creating or updating your Instance via the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/) only. Read our [billing FAQ](/billing/faq/#when-does-the-billing-of-an-instance-start-and-stop) for more information about the billing of dynamic and flexible IPs. +You can choose to give your Instance a dynamic IP address when creating or updating your Instance via the [Scaleway API](https://www.scaleway.com/en/developers/api/instances/) only. Read our [billing FAQ](/billing/faq/#when-does-the-billing-of-an-instance-start-and-stop) for more information about the billing of dynamic and flexible IPs. ## Flexible IP diff --git a/pages/instances/faq.mdx b/pages/instances/faq.mdx index d84b98e865..37a52e3d4e 100644 --- a/pages/instances/faq.mdx +++ b/pages/instances/faq.mdx @@ -27,7 +27,7 @@ A Marketplace is an online store that offers applications and services either bu Scaleway Marketplace provides information related to Instance images through variants named “local-images”. This information can include the Instance zone and identification, along with constraints regarding the applicable Instance types. -When you want to create an Instance using an image in the Instance [API](https://www.scaleway.com/en/developers/api/instance/), you need to specify the local-image UUID matching the zone and Instance type constraints you fetch from the marketplace API. +When you want to create an Instance using an image in the Instance [API](https://www.scaleway.com/en/developers/api/instances/), you need to specify the local-image UUID matching the zone and Instance type constraints you fetch from the marketplace API. Use the [Marketplace API](https://www.scaleway.com/en/developers/api/marketplace/) to find the UUID of the image you want to use. Alternatively, you can use this CLI command: diff --git a/pages/instances/how-to/create-an-instance.mdx b/pages/instances/how-to/create-an-instance.mdx index 20c245cd55..24fddcf58d 100644 --- a/pages/instances/how-to/create-an-instance.mdx +++ b/pages/instances/how-to/create-an-instance.mdx @@ -11,7 +11,7 @@ import Requirements from '@macros/iam/requirements.mdx' This page shows how to create your first Scaleway Instance. An [Instance](/instances/concepts/#instance) is a virtual machine in the cloud. Just like a physical machine, it has resources - virtualized CPU, RAM, storage etc. - which vary depending on the [Instance type](/instances/reference-content/choosing-instance-type/) you choose. After you have created your Instance you can [connect](/instances/how-to/connect-to-instance/) to it and use it for a wide range of computing use cases depending on the Instance type you chose, from running small-scale tests and personal projects to hosting applications and development environments to setting up a production environment. -Select a tab below for instructions on how to create an Instance via either our [console](https://console.scaleway.com), our [API](https://www.scaleway.com/en/developers/api/instance/), or our [CLI](https://github.com/scaleway/scaleway-cli). +Select a tab below for instructions on how to create an Instance via either our [console](https://console.scaleway.com), our [API](https://www.scaleway.com/en/developers/api/instances/), or our [CLI](https://github.com/scaleway/scaleway-cli). @@ -80,7 +80,7 @@ Select a tab below for instructions on how to create an Instance via either our To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. - Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. + Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. - **Configure network** of the Instance. @@ -174,10 +174,10 @@ Select a tab below for instructions on how to create an Instance via either our |-----------------|-----------------------------------------------------|----------------------------------------| | name | A name of your choice for the Instance (string) | Any string containing only alphanumeric characters, dots, spaces and dashes, e.g. `"my-new-instance"`. | | project | The Project in which the Instance should be created (string)| Any valid Scaleway Project ID (see above), e.g. `"b4bd99e0-b389-11ed-afa1-0242ac120002"` | - | commercial-type | The commercial Instance type to create (string) | Any valid ID of a Scaleway commercial Instance type, e.g. `"GP1-S"`, `"PRO2-M"`. Use the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint to get a list of all valid Instance types and their IDs. | + | commercial-type | The commercial Instance type to create (string) | Any valid ID of a Scaleway commercial Instance type, e.g. `"GP1-S"`, `"PRO2-M"`. Use the [List Instance Types](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) endpoint to get a list of all valid Instance types and their IDs. | | image | The image to install on the Instance, e.g. a particular OS (string) | Any valid Scaleway image label, e.g. `ubuntu_noble` which is the label for the Ubuntu 24.04 Noble Numbat image. | | enable_ipv6 | Whether to enable IPv6 on the Instance (boolean) | `true` or `false` | - | volumes | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`sbs_volume`), others also support Local Storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd` or `sbs_volume`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`). Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instance/#path-volumes). | + | volumes | An object that specifies the storage volumes to attach to the Instance. Must respect the volume constraints of the `commercial_type` (i.e. for each type of Instance, a minimum amount of storage is required, and there is also a maximum that cannot be exceeded. Some Instance types support only Block Storage (`sbs_volume`), others also support Local Storage (`l_ssd`) ). These constraints are available at the [List Instance Types](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types) endpoint, via the `volume_constraints` parameter for each type listed in the response | A (dictionary) object with a minimum of one key (`"0"`) whose value is another object containing the parameters `"name"` (a name for the volume), `"size"` (the size for the volume, in bytes), and `"volume_type"` (`"l_ssd` or `sbs_volume`). Additional keys for additional volumes should increment by 1 each time (the second volume would have a key of `1`). Further parameters are available, and it is possible to attach existing volumes rather than creating a new one, or create a volume from a snapshot. For full details see [here](https://www.scaleway.com/en/developers/api/instances/#path-volumes). | 4. Use the following curl command, replacing the payload with the one you specified in step 2, to create your Instance. @@ -195,10 +195,10 @@ Select a tab below for instructions on how to create an Instance via either our - When creating an Instance via the API, it is in a powered off state by default. To power it on, call the [Perform action](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action) endpoint, passing it the ID of your Instance (returned in the 201 response at step 3) and `poweron` as the `action` to perform. + When creating an Instance via the API, it is in a powered off state by default. To power it on, call the [Perform action](https://www.scaleway.com/en/developers/api/instances/#path-instances-perform-action) endpoint, passing it the ID of your Instance (returned in the 201 response at step 3) and `poweron` as the `action` to perform. - See the [Instance API documentation](https://www.scaleway.com/en/developers/api/instance/) for full details on the Instance API. In particular, see the [Create an Instance](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance) call for more details of configurable parameters when creating an Instance. + See the [Instance API documentation](https://www.scaleway.com/en/developers/api/instances/) for full details on the Instance API. In particular, see the [Create an Instance](https://www.scaleway.com/en/developers/api/instances/#path-instances-create-an-instance) call for more details of configurable parameters when creating an Instance. diff --git a/pages/instances/how-to/create-image-from-snapshot.mdx b/pages/instances/how-to/create-image-from-snapshot.mdx index 7e40d683f0..9818fd3419 100644 --- a/pages/instances/how-to/create-image-from-snapshot.mdx +++ b/pages/instances/how-to/create-image-from-snapshot.mdx @@ -67,7 +67,7 @@ scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id ## Creating an image via the Scaleway API -You can also create an image using the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/#path-images-create-an-instance-image). Use the following `curl` command: +You can also create an image using the [Scaleway API](https://www.scaleway.com/en/developers/api/instances/#path-images-create-an-instance-image). Use the following `curl` command: ```bash curl --location "https://api.scaleway.com/instance/v1/zones/$SCW_AVAILABILITY_ZONE/images" \ diff --git a/pages/instances/index.mdx b/pages/instances/index.mdx index 9cb79a6ea9..bec2990618 100644 --- a/pages/instances/index.mdx +++ b/pages/instances/index.mdx @@ -74,7 +74,7 @@ description: Dive into Scaleway Instances with our quickstart guides, how-tos, t productLogo="cli" title="Instance API" description="Learn how to create and manage your Scaleway Instances through the API." - url="https://www.scaleway.com/en/developers/api/instance/" + url="https://www.scaleway.com/en/developers/api/instances/" label="Go to Instances API" /> diff --git a/pages/instances/menu.ts b/pages/instances/menu.ts index d65b9ca013..070feedf5b 100644 --- a/pages/instances/menu.ts +++ b/pages/instances/menu.ts @@ -110,7 +110,7 @@ export const instanceMenu = { "items": [ { "label": "Instances API Reference", - "slug": "https://www.scaleway.com/en/developers/api/instance/" + "slug": "https://www.scaleway.com/en/developers/api/instances/" }, { "label": "Scaleway CLI Cheatsheet", diff --git a/pages/instances/reference-content/instances-bandwidth-overview.mdx b/pages/instances/reference-content/instances-bandwidth-overview.mdx index f2379a0a26..91b696fe5f 100644 --- a/pages/instances/reference-content/instances-bandwidth-overview.mdx +++ b/pages/instances/reference-content/instances-bandwidth-overview.mdx @@ -17,7 +17,7 @@ Bandwidth impacts how your applications perform and interact with other systems. - **Block bandwidth**: Determines the read/write speed to Block Storage, essential for storage-heavy workloads like databases and analytics. - Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. + Bandwidth specifications listed here are for informational purposes. To validate the exact bandwidth capacity of your Instance type, refer to the `block_bandwidth` field in the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instance-types-list-instance-types). Use the endpoint `/instance/v1/zones/{zone}/products/servers` to retrieve Instance type specifications. diff --git a/pages/instances/troubleshooting/bootscript-eol.mdx b/pages/instances/troubleshooting/bootscript-eol.mdx index dbd3df649a..ab17e2e231 100644 --- a/pages/instances/troubleshooting/bootscript-eol.mdx +++ b/pages/instances/troubleshooting/bootscript-eol.mdx @@ -16,7 +16,7 @@ If you are still using one of these Instance types with a bootscript, you have t You can find information about the Instances quotas allocated to your account in the [Understanding Organization quotas](/organizations-and-projects/additional-content/organization-quotas/) documentation page. - If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the [Scaleway CLI](/instances/api-cli/creating-managing-instances-with-cliv2/) as you normally would or through the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance), as long as you stay within your allocated quotas. [Check your Organization's quota usage in the Scaleway console](https://console.scaleway.com/organization/settings). + If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the [Scaleway CLI](/instances/api-cli/creating-managing-instances-with-cliv2/) as you normally would or through the [Instances API](https://www.scaleway.com/en/developers/api/instances/#path-instances-create-an-instance), as long as you stay within your allocated quotas. [Check your Organization's quota usage in the Scaleway console](https://console.scaleway.com/organization/settings). diff --git a/pages/instances/troubleshooting/change-rescue-mode.mdx b/pages/instances/troubleshooting/change-rescue-mode.mdx index 37ff6eb273..2a2db9f3f6 100644 --- a/pages/instances/troubleshooting/change-rescue-mode.mdx +++ b/pages/instances/troubleshooting/change-rescue-mode.mdx @@ -33,11 +33,11 @@ This is particularly useful when your Instance is not booting properly due to co ## Updating rescue mode using the Scaleway API -1. [List the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-list-all-instances) located in your Project(s). +1. [List the Instances](https://www.scaleway.com/en/developers/api/instances/#path-instances-list-all-instances) located in your Project(s). 2. Filter the returned Instances to keep only the ones with `boot_type: "rescue"`. -3. [Stop the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action). -4. [Update the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-update-an-instance) and set `boot_type: "local"`. +3. [Stop the Instances](https://www.scaleway.com/en/developers/api/instances/#path-instances-perform-action). +4. [Update the Instances](https://www.scaleway.com/en/developers/api/instances/#path-instances-update-an-instance) and set `boot_type: "local"`. If you still want to use rescue mode for your Instance(s), update these Instances again and switch back the `boot_type` to “rescue”. They will then use the updated rescue system. -5. [Start the Instances](https://www.scaleway.com/en/developers/api/instance/#path-instances-perform-action). \ No newline at end of file +5. [Start the Instances](https://www.scaleway.com/en/developers/api/instances/#path-instances-perform-action). \ No newline at end of file diff --git a/pages/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx b/pages/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx index 0a3d97828c..a099e488a0 100644 --- a/pages/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx +++ b/pages/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx @@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx' In this tutorial we will use the API through the well known utility [curl](https://curl.haxx.se/). This will show you how to create Hubs and Devices, as well as more advanced features of the Scaleway IoT Hub: Hub Events and Routes. -The API reference is here: [IoT API](https://www.scaleway.com/en/developers/api/iot/) +The API reference is here: [IoT API](https://www.scaleway.com/en/developers/api/iot-hub/) diff --git a/pages/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx b/pages/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx index bd7db5bca7..bcf134ef45 100644 --- a/pages/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx +++ b/pages/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx @@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx' In this tutorial we will use the API through the Scaleway command line interface [CLI](https://github.com/scaleway/scaleway-cli#Installation). This will show you how to create Hubs and Devices, as well as more advanced features of the Scaleway IoT Hub: Hub Events and Routes. -You can find the API reference documentation at the following link: [IoT API](https://www.scaleway.com/en/developers/api/iot/) +You can find the API reference documentation at the following link: [IoT API](https://www.scaleway.com/en/developers/api/iot-hub/) diff --git a/pages/iot-hub/faq.mdx b/pages/iot-hub/faq.mdx index 5eb597e722..44bfc2868f 100644 --- a/pages/iot-hub/faq.mdx +++ b/pages/iot-hub/faq.mdx @@ -35,7 +35,7 @@ The following plans are currently available: - **Dedicated Plan (stateful)**: The broker is provided with dedicated CPU and memory resources, and you can use them as you wish. There is no limitation in the usage of the broker, everything is dedicated to you. - **High Availability Plan (stateful)**: Two dedicated brokers, connected together, are provided to avoid service interruption if one of them fails. -Each IoT Hub can be fully configured both from the management console, and a powerful [REST-API](https://www.scaleway.com/en/developers/api/iot/). +Each IoT Hub can be fully configured both from the management console, and a powerful [REST-API](https://www.scaleway.com/en/developers/api/iot-hub/). ## How secure is Scaleway IoT? Scaleway IoT was designed with security in mind. Therefore, we implemented mutual authenticated TLS as the default authentication method. Each device needs its certificate+key pair to connect to the hub. diff --git a/pages/iot-hub/index.mdx b/pages/iot-hub/index.mdx index ac017a01a8..899f6d746b 100644 --- a/pages/iot-hub/index.mdx +++ b/pages/iot-hub/index.mdx @@ -48,7 +48,7 @@ description: Dive into Scaleway IoT Hub with our quickstart guides, how-tos, tut productLogo="cli" title="IoT Hub API" description="Learn how to create and manage your IoT Hub through the API." - url="https://www.scaleway.com/en/developers/api/iot/" + url="https://www.scaleway.com/en/developers/api/iot-hub/" label="Go to IoT Hub API" /> diff --git a/pages/iot-hub/menu.ts b/pages/iot-hub/menu.ts index ac14a4c0b8..b36e12863c 100644 --- a/pages/iot-hub/menu.ts +++ b/pages/iot-hub/menu.ts @@ -110,7 +110,7 @@ export const iotHubMenu = { items: [ { label: 'IoT Hub API Reference', - slug: 'https://www.scaleway.com/en/developers/api/iot/', + slug: 'https://www.scaleway.com/en/developers/api/iot-hub/', }, { label: 'Getting started with the IoT Hub CLI', diff --git a/pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx b/pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx index 6a4f343c86..aecfb0a1b6 100644 --- a/pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx +++ b/pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx @@ -105,7 +105,7 @@ curl --request POST \ - This action adds a new endpoint. If you want to use it in your environment, you need to update the endpoint in your configuration. -Refer to the [Managed Database for PostgreSQL and MySQL API documentation](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-endpoints-create-a-new-database-instance-endpoint) for further information. +Refer to the [Managed Database for PostgreSQL and MySQL API documentation](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/#path-endpoints-create-a-new-database-instance-endpoint) for further information. ### Are managed Load Balancers compatible with Kubernetes Kapsule Private Networks? diff --git a/pages/local-storage/index.mdx b/pages/local-storage/index.mdx index ee23109901..736e554f1b 100644 --- a/pages/local-storage/index.mdx +++ b/pages/local-storage/index.mdx @@ -41,6 +41,6 @@ description: Dive into Scaleway Local Storage with our quickstart guides, how-to productLogo="cli" title="Instance API" description="Learn how to create and manage your Scaleway Local Storage through the API." - url="https://www.scaleway.com/en/developers/api/instance/" + url="https://www.scaleway.com/en/developers/api/instances/" label="Go to Instances - Local Storage API" /> 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 a4b72806df..b653a95b7a 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 @@ -9,7 +9,7 @@ dates: [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). +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-databases-for-postgresql-and-mysql/#path-database-instances-upgrade-a-database-instance). - Once activated on a Database Instance, encryption at rest cannot be disabled. @@ -21,7 +21,7 @@ The feature can be activated upon Database Instance creation via the console and 1. Edit the POST request payload you will use to create your Database Instance. Make sure you include the `encryption` parameter and set the `enabled` attribute to `true`. - In all examples below the UUIDs, passwords and IP addresses displayed are not real. For more details about the parameters shown, refer to the [Managed Databases for PostgreSQL and MySQL API documentation](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) + In all examples below the UUIDs, passwords and IP addresses displayed are not real. For more details about the parameters shown, refer to the [Managed Databases for PostgreSQL and MySQL API documentation](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/) ```json diff --git a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx index 0e8990da23..a9eb352e6f 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/concepts.mdx @@ -30,7 +30,7 @@ Clone is a feature that allows you to create a full copy of your Database Instan ## Database backup -A database backup is a complete dated export of a logical database stored on a backup backend. You can use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-backups-create-a-database-backup) to define if the backup should be stored in a region different from the database. +A database backup is a complete dated export of a logical database stored on a backup backend. You can use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/#path-backups-create-a-database-backup) to define if the backup should be stored in a region different from the database. ## Database Instance @@ -53,7 +53,7 @@ Encryption at rest allows you to permanently encrypt your database data. The dat All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available. -Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance). +Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/#path-database-instances-upgrade-a-database-instance). 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. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx index f4f8e80407..074474121f 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx @@ -31,7 +31,7 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you -5. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-apply-database-instance-maintenance). +5. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/#path-database-instances-apply-database-instance-maintenance). Your Database Instance will be unavailable during the maintenance. This might take a few minutes. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx index b57a335058..570cb1016e 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx @@ -37,7 +37,7 @@ Compared to traditional database management, which requires customers to provide Keep in mind that: - Once activated on a Database Instance, encryption at rest cannot be disabled. All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available. - - Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance). + - Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/#path-database-instances-upgrade-a-database-instance). - 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. - Select a node type. 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 9125534be7..34b8bad608 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 @@ -40,7 +40,7 @@ A Read Replica is a live copy of a Database Instance that behaves like an Instan - If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) to do so via a command line or Terraform/OpenTofu. + If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/) to do so via a command line or Terraform/OpenTofu. 8. Click **Create Read Replica**. A list of your Read Replicas displays. diff --git a/pages/managed-databases-for-postgresql-and-mysql/index.mdx b/pages/managed-databases-for-postgresql-and-mysql/index.mdx index 3b3f64d363..1fac24c0d5 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/index.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/index.mdx @@ -70,7 +70,7 @@ description: Dive into Scaleway Managed Database for PostgreSQL and MySQL with o productLogo="cli" title="Managed Database for PostgreSQL and MySQL API" description="Manage your PostgreSQL and MySQL Database Instances using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/" + url="https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/" label="Go to Managed Database for PostgreSQL and MySQL API" /> diff --git a/pages/managed-databases-for-postgresql-and-mysql/menu.ts b/pages/managed-databases-for-postgresql-and-mysql/menu.ts index 6f00055665..80479f1842 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/menu.ts +++ b/pages/managed-databases-for-postgresql-and-mysql/menu.ts @@ -133,7 +133,7 @@ export const managedDatabasePostgresMySqlMenu = { { label: 'Managed Database for PostgreSQL and MySQL API Reference', - slug: 'https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/', + slug: 'https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/', }, { label: 'Setting up encryption at rest', diff --git a/pages/managed-databases-for-redis/api-cli/managing-username-and-password.mdx b/pages/managed-databases-for-redis/api-cli/managing-username-and-password.mdx index 55c3c89c88..fab8935d3b 100644 --- a/pages/managed-databases-for-redis/api-cli/managing-username-and-password.mdx +++ b/pages/managed-databases-for-redis/api-cli/managing-username-and-password.mdx @@ -22,7 +22,7 @@ You can specify a name for this user when you create a Database Instance. This a ## Specifying a name for a user -Follow the [create a Database Instance](https://www.scaleway.com/en/developers/api/managed-database-redis/#quickstart) procedure. +Follow the [create a Database Instance](https://www.scaleway.com/en/developers/api/managed-databases-for-redis/#quickstart) procedure. You can also define a username when you [create a Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) via the Scaleway console. diff --git a/pages/managed-databases-for-redis/index.mdx b/pages/managed-databases-for-redis/index.mdx index 9d5d2afc7f..573c27f6c8 100644 --- a/pages/managed-databases-for-redis/index.mdx +++ b/pages/managed-databases-for-redis/index.mdx @@ -59,7 +59,7 @@ description: Dive into Scaleway Managed Database for Redis™ with our quickstar productLogo="cli" title="Managed Database for Redis™ API" description="Manage your Redis™ Database Instances using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/managed-database-redis/" + url="https://www.scaleway.com/en/developers/api/managed-databases-for-redis/" label="Go to Managed Database for Redis™ API" /> diff --git a/pages/managed-databases-for-redis/menu.ts b/pages/managed-databases-for-redis/menu.ts index 18191c03b5..efe506939f 100644 --- a/pages/managed-databases-for-redis/menu.ts +++ b/pages/managed-databases-for-redis/menu.ts @@ -54,7 +54,7 @@ export const managedDatabaseRedisMenu = { items: [ { label: 'Managed Database for Redis™ API Reference', - slug: 'https://www.scaleway.com/en/developers/api/managed-database-redis/', + slug: 'https://www.scaleway.com/en/developers/api/managed-databases-for-redis/', }, { label: 'Managing username and password', diff --git a/pages/managed-inference/faq.mdx b/pages/managed-inference/faq.mdx index e710f6a407..360f6de4fc 100644 --- a/pages/managed-inference/faq.mdx +++ b/pages/managed-inference/faq.mdx @@ -40,7 +40,7 @@ You can deploy a variety of models, including: Managed Inference supports both open-source models and your own uploaded proprietary models. ### How do I deploy a model using Managed Inference? -Deployment is done through Scaleway's [console](https://console.scaleway.com/inference/deployments) or [API](https://www.scaleway.com/en/developers/api/inference/). You can choose a model from Scaleway’s selection or import your own directly from Hugging Face's repositories, configure [Instance types](/gpu/reference-content/choosing-gpu-instance-type/), set up networking options, and start inference with minimal setup. +Deployment is done through Scaleway's [console](https://console.scaleway.com/inference/deployments) or [API](https://www.scaleway.com/en/developers/api/managed-inference/). You can choose a model from Scaleway’s selection or import your own directly from Hugging Face's repositories, configure [Instance types](/gpu/reference-content/choosing-gpu-instance-type/), set up networking options, and start inference with minimal setup. ### Can I fine-tune or retrain my models within Managed Inference? Managed Inference is primarily designed for deploying and running inference workloads. If you need to fine-tune or retrain models, you may need to use a separate training environment, such as [Scaleway’s GPU Instances](/gpu/quickstart/), and then deploy the trained model in Managed Inference. @@ -82,4 +82,4 @@ Pricing details can be found on the [Scaleway pricing page](https://www.scaleway ### Can I pause Managed Inference billing when the Instance is not in use? When a Managed Inference deployment is running, corresponding resources are provisioned and thus billed. Resources can therefore not be paused. -However, you can still optimize your Managed Inference deployment to fit within specific time ranges (such as during working hours). To do so, you can automate deployment creation and deletion using the [Managed Inference API](https://www.scaleway.com/en/developers/api/inference/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/inference_deployment) or [Scaleway SDKs](https://www.scaleway.com/en/docs/scaleway-sdk/). These actions can be programmed using [Serverless Jobs](/serverless-jobs/) to be automatically carried out periodically. +However, you can still optimize your Managed Inference deployment to fit within specific time ranges (such as during working hours). To do so, you can automate deployment creation and deletion using the [Managed Inference API](https://www.scaleway.com/en/developers/api/managed-inference/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/inference_deployment) or [Scaleway SDKs](https://www.scaleway.com/en/docs/scaleway-sdk/). These actions can be programmed using [Serverless Jobs](/serverless-jobs/) to be automatically carried out periodically. diff --git a/pages/managed-inference/index.mdx b/pages/managed-inference/index.mdx index ab5aa6d4cc..5fa1485387 100644 --- a/pages/managed-inference/index.mdx +++ b/pages/managed-inference/index.mdx @@ -48,7 +48,7 @@ description: Dive into Scaleway Managed Inference with our quickstart guides, ho productLogo="cli" title="Managed Inference API" description="Learn how to create and manage your Scaleway Managed Inference endpoints through the API." - url="https://www.scaleway.com/en/developers/api/inference/" + url="https://www.scaleway.com/en/developers/api/managed-inference/" label="Go to Managed Inference API" /> diff --git a/pages/managed-inference/menu.ts b/pages/managed-inference/menu.ts index 6b2f2161a7..c94ddd3bf6 100644 --- a/pages/managed-inference/menu.ts +++ b/pages/managed-inference/menu.ts @@ -59,7 +59,7 @@ export const managedInferenceMenu = { items: [ { label: 'Managed Inference API Reference', - slug: 'https://www.scaleway.com/en/developers/api/inference/', + slug: 'https://www.scaleway.com/en/developers/api/managed-inference/', }, ], label: 'API/CLI', diff --git a/pages/managed-inference/reference-content/supported-models.mdx b/pages/managed-inference/reference-content/supported-models.mdx index 4cd80f16c8..68823470a5 100644 --- a/pages/managed-inference/reference-content/supported-models.mdx +++ b/pages/managed-inference/reference-content/supported-models.mdx @@ -9,7 +9,7 @@ dates: Scaleway Managed Inference allows you to deploy various AI models, either from: - * [Scaleway model catalog](#scaleway-model-catalog): A curated set of ready-to-deploy models available through the [Scaleway console](https://console.scaleway.com/inference/deployments/) or the [Managed Inference models API](https://www.scaleway.com/en/developers/api/inference/#path-models-list-models) + * [Scaleway model catalog](#scaleway-model-catalog): A curated set of ready-to-deploy models available through the [Scaleway console](https://console.scaleway.com/inference/deployments/) or the [Managed Inference models API](https://www.scaleway.com/en/developers/api/managed-inference/#path-models-list-models) * [Custom models](#custom-models): Models that you import, typically from sources like Hugging Face. ## Scaleway model catalog diff --git a/pages/managed-mongodb-databases/api-cli/managing-users-api.mdx b/pages/managed-mongodb-databases/api-cli/managing-users-api.mdx index 487266b2f1..1035409440 100644 --- a/pages/managed-mongodb-databases/api-cli/managing-users-api.mdx +++ b/pages/managed-mongodb-databases/api-cli/managing-users-api.mdx @@ -9,10 +9,10 @@ dates: When you create your MongoDB® Database Instance, a default user with administrative privileges is automatically created. -You can create more users and grant them pre-set roles via the [Scaleway Managed MongoDB® API](https://www.scaleway.com/en/developers/api/managed-database-mongodb/). +You can create more users and grant them pre-set roles via the [Scaleway Managed MongoDB® API](https://www.scaleway.com/en/developers/api/managed-mongodb-databases/). - All users you create initially have administrator roles, which can be modified after creation using the [Apply user roles](https://www.scaleway.com/en/developers/api/managed-database-mongodb/#path-users-apply-user-roles) API call. However, the default user's role cannot be changed. + All users you create initially have administrator roles, which can be modified after creation using the [Apply user roles](https://www.scaleway.com/en/developers/api/managed-mongodb-databases/#path-users-apply-user-roles) API call. However, the default user's role cannot be changed. ### How to create a user diff --git a/pages/managed-mongodb-databases/index.mdx b/pages/managed-mongodb-databases/index.mdx index 0ae6395120..5f329e223a 100644 --- a/pages/managed-mongodb-databases/index.mdx +++ b/pages/managed-mongodb-databases/index.mdx @@ -59,7 +59,7 @@ description: Dive into Scaleway Managed MongoDB® with our quickstart guides, ho productLogo="cli" title="Managed MongoDB® API" description="Manage your document Database Instances using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/managed-database-mongodb/" + url="https://www.scaleway.com/en/developers/api/managed-mongodb-databases/" label="Go to Managed MongoDB® API" /> diff --git a/pages/nats/index.mdx b/pages/nats/index.mdx index 33d2138653..0e2fa02004 100644 --- a/pages/nats/index.mdx +++ b/pages/nats/index.mdx @@ -60,7 +60,7 @@ description: Explore Scaleway NATS. Simplify your microservice workflows with sc productLogo="cli" title="NATS APIs" description="Manage NATS using the Scaleway APIs." - url="https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/" + url="https://www.scaleway.com/en/developers/api/nats/nats-api/" label="Go to Scaleway NATS API" /> diff --git a/pages/nats/menu.ts b/pages/nats/menu.ts index 88f67ac0f8..b4378ce627 100644 --- a/pages/nats/menu.ts +++ b/pages/nats/menu.ts @@ -46,7 +46,7 @@ export const natsMenu = { items: [ { label: 'NATS API Reference', - slug: 'https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/', + slug: 'https://www.scaleway.com/en/developers/api/nats/nats-api/', }, { label: 'Using the NATS CLI', diff --git a/pages/nats/reference-content/nats-overview.mdx b/pages/nats/reference-content/nats-overview.mdx index 6326d99e2f..f769785220 100644 --- a/pages/nats/reference-content/nats-overview.mdx +++ b/pages/nats/reference-content/nats-overview.mdx @@ -19,7 +19,7 @@ Scaleway NATS is a managed messaging service that enable seamless communication ## NATS accounts -You can easily create a NATS account from the [Scaleway console](https://console.scaleway.com/), via the [Scaleway API](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/) or via [Terraform/OpenTofu](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider). +You can easily create a NATS account from the [Scaleway console](https://console.scaleway.com/), via the [Scaleway API](https://www.scaleway.com/en/developers/api/nats/nats-api/) or via [Terraform/OpenTofu](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider). ## NATS credentials @@ -63,7 +63,7 @@ The following documents may help you get started using the above SDKs: - [Python: Using Jetstream](https://github.com/nats-io/nats.py#jetstream) - [Go: Using Jetstream](https://github.com/nats-io/nats.go#jetstream-basic-usage) -The main difference you will find between the standard NATS documentation and Scaleway NATS is that we require you to provide a specific NATS URL and credentials to access the service. Refer to our [developers documentation](https://www.scaleway.com/en/developers/api/messaging-and-queuing/nats-api/) for further information. +The main difference you will find between the standard NATS documentation and Scaleway NATS is that we require you to provide a specific NATS URL and credentials to access the service. Refer to our [developers documentation](https://www.scaleway.com/en/developers/api/nats/nats-api/) for further information. ## NATS resources diff --git a/pages/public-gateways/concepts.mdx b/pages/public-gateways/concepts.mdx index 3c8469b91b..c47960c7e3 100644 --- a/pages/public-gateways/concepts.mdx +++ b/pages/public-gateways/concepts.mdx @@ -61,9 +61,9 @@ Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. The mod **Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. Your gateway is a legacy gateway if: - You created it via the Scaleway console prior to 17 October 2023 -- You created it via the Scaleway API or developer tools prior to 17 October 2023, and you did not use the `ipam_config` object when creating the [GatewayNetwork](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateway-networks-attach-a-public-gateway-to-a-private-network) (attachment to a Private Network). +- You created it via the Scaleway API or developer tools prior to 17 October 2023, and you did not use the `ipam_config` object when creating the [GatewayNetwork](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateway-networks-attach-a-public-gateway-to-a-private-network) (attachment to a Private Network). -The auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-create-a-public-gateway) will have a value of `true`. +The auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateways-create-a-public-gateway) will have a value of `true`. Private Networks attached to legacy Public Gateways must stay in the gateway's auto-created VPC to ensure basic IPAM compatibility. @@ -71,7 +71,7 @@ Private Networks attached to legacy Public Gateways must stay in the gateway's a **IPAM** Public Gateways are fully and natively integrated with the Scaleway IPAM without any workaround. Your gateway is in IPAM mode if: - You created it via the Scaleway console on or after 17 October 2023 -- You created it via the Scaleway API or devtools using the `ipam_config` object, and the auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-create-a-public-gateway) has a value of `false`. +- You created it via the Scaleway API or devtools using the `ipam_config` object, and the auto-calculated `is_legacy` [Gateway parameter](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateways-create-a-public-gateway) has a value of `false`. - You moved it from legacy mode to IPAM mode using the dedicated button in the console, or the dedicated API call. diff --git a/pages/public-gateways/faq.mdx b/pages/public-gateways/faq.mdx index cf45395fc5..9b13bb4407 100644 --- a/pages/public-gateways/faq.mdx +++ b/pages/public-gateways/faq.mdx @@ -12,7 +12,7 @@ productIcon: PublicGatewayProductIcon Public Gateways sit at the border of Private Networks. They provide services to deal with traffic entering and exiting the network (NAT), and SSH bastion. A Public Gateway can be attached to up to 8 Private Networks, and up to 50 Public Gateways are supported per [Organization](/organizations-and-projects/concepts/#organization). -The Public Gateway can be configured through the console or the [API](https://www.scaleway.com/en/developers/api/public-gateway/). +The Public Gateway can be configured through the console or the [API](https://www.scaleway.com/en/developers/api/public-gateways/). ## Offering and availability @@ -42,7 +42,7 @@ The Public Gateways API v1 is now deprecated, and will be removed on 1 November - Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode: - - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). - **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above). @@ -77,4 +77,4 @@ In the meantime, if this is a concern, you could consider attaching several Publ ### I need more than 1 Gbps bandwidth for my Public Gateway, what can I do? -We have introduced a `VPC-GW-L` offer with 3 Gbps bandwidth, and a `VPC-GW-XL` offer with 10 Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/). \ No newline at end of file +We have introduced a `VPC-GW-L` offer with 3 Gbps bandwidth, and a `VPC-GW-XL` offer with 10 Gbps of bandwidth, to accommodate customers with this type of need. For pricing details, see our [dedicated page](https://www.scaleway.com/en/pricing/network/). You can upgrade your existing Public Gateway to one of these new offers via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateways-upgrade-a-public-gateway-to-the-latest-version-andor-to-a-different-commercial-offer-type) or the [Scaleway console](/public-gateways/how-to/upgrade-public-gateway/). \ No newline at end of file diff --git a/pages/public-gateways/how-to/use-ssh-bastion.mdx b/pages/public-gateways/how-to/use-ssh-bastion.mdx index 483b238b28..84a812230a 100644 --- a/pages/public-gateways/how-to/use-ssh-bastion.mdx +++ b/pages/public-gateways/how-to/use-ssh-bastion.mdx @@ -126,7 +126,7 @@ For [Legacy Private Networks](/public-gateways/concepts/#ipam) not in IPAM mode - **Via the Scaleway console**: The FQDN takes the form `resource-name.priv` - **Via Terraform**: The FQDN takes the form `resource-name.dns_local_name` where `dns_local_name` is [this](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/vpc_public_gateway_dhcp#dns_local_name) Terraform option. -- **Via the Scaleway CLI or API**: The FQDN takes the form `resource-name.dns_local_name` where `dns_local_name` follows the specification [here](https://www.scaleway.com/en/developers/api/public-gateway/#path-dhcp-create-a-dhcp-configuration), defaulting to `.priv`. +- **Via the Scaleway CLI or API**: The FQDN takes the form `resource-name.dns_local_name` where `dns_local_name` follows the specification [here](https://www.scaleway.com/en/developers/api/public-gateways/#path-dhcp-create-a-dhcp-configuration), defaulting to `.priv`. diff --git a/pages/public-gateways/index.mdx b/pages/public-gateways/index.mdx index f4160e66c8..47143d6269 100644 --- a/pages/public-gateways/index.mdx +++ b/pages/public-gateways/index.mdx @@ -70,7 +70,7 @@ description: Dive into Scaleway Public Gateways with our quickstart guides, how- productLogo="cli" title="Public Gateways API" description="Manage Public Gateways using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/public-gateway/" + url="https://www.scaleway.com/en/developers/api/public-gateways/" label="Go to Public Gateways API" /> diff --git a/pages/public-gateways/menu.ts b/pages/public-gateways/menu.ts index 6d0a886681..76acc7fe18 100644 --- a/pages/public-gateways/menu.ts +++ b/pages/public-gateways/menu.ts @@ -50,7 +50,7 @@ export const publicGatewaysMenu = { items: [ { label: 'Public Gateway API Reference', - slug: 'https://www.scaleway.com/en/developers/api/public-gateway/', + slug: 'https://www.scaleway.com/en/developers/api/public-gateways/', }, ], label: 'API/CLI', diff --git a/pages/public-gateways/reference-content/understanding-v2.mdx b/pages/public-gateways/reference-content/understanding-v2.mdx index f498823f98..6f842b9df6 100644 --- a/pages/public-gateways/reference-content/understanding-v2.mdx +++ b/pages/public-gateways/reference-content/understanding-v2.mdx @@ -15,7 +15,7 @@ This document explains what to expect and how to prepare for the upcoming change ## Summary (TL;DR) -All Scaleway Public Gateways until now have been created and managed with the version 1 of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/v1/), either explicitly via the API itself, or implicitly behind the scenes of the Scaleway console or other developer tools. +All Scaleway Public Gateways until now have been created and managed with the version 1 of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateways/v1/), either explicitly via the API itself, or implicitly behind the scenes of the Scaleway console or other developer tools. **We are now deprecating v1 of the API and transitioning to v2.** @@ -36,7 +36,7 @@ After a deprecation period ending on 1 Nov 2025, the Public Gateways API v1 and - Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM mode. You can do this in several ways: - Use the **Move to IPAM mode** button in the console - - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). + - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). - Use the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) - Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead, and do not refer to [removed functionalities](#introducing-public-gateways-api-v2). @@ -59,7 +59,7 @@ Whether you choose a custom or default CIDR block, automatic address assignment ## Introducing Public Gateways API v2 -Since the assignment and management of IP addresses on Private Networks is now managed by IPAM and the Private Networks themselves, we must complete the removal of the DHCP functionality from Public Gateways. This means releasing a new version (v2) of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/), which has until now retained a number of legacy DHCP functions. From this new version, you can observe: +Since the assignment and management of IP addresses on Private Networks is now managed by IPAM and the Private Networks themselves, we must complete the removal of the DHCP functionality from Public Gateways. This means releasing a new version (v2) of the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateways/), which has until now retained a number of legacy DHCP functions. From this new version, you can observe: - IPAM mode becomes default - Removal of the DHCP object @@ -74,7 +74,7 @@ Full details of each change are explained below. Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. You can see the mode of a given gateway by: - Checking its badge in the gateway listing page of the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) (see screenshot below). -- Checking the value of the `is_legacy` field via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateways-get-a-public-gateway). +- Checking the value of the `is_legacy` field via the [Public Gateways API](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateways-get-a-public-gateway). @@ -100,7 +100,7 @@ Remember that you can define a [custom CIDR block](/vpc/how-to/create-private-ne For some time now, this functionality has been available via the API and developer tools only (not the Scaleway console). -When attaching a Public Gateway to a Private Network (creating a [Gateway Network](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateway-networks-attach-a-public-gateway-to-a-private-network)) via the API, you could use the `address` field to define a single static IP address to assign to the Public Gateway on that Private Network. +When attaching a Public Gateway to a Private Network (creating a [Gateway Network](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateway-networks-attach-a-public-gateway-to-a-private-network)) via the API, you could use the `address` field to define a single static IP address to assign to the Public Gateway on that Private Network. **The `address` field does not exist in v2 of the API**. Instead, you can pass an `ipam_ip_id` to specify a reserved IP address to use for a Public Gateway on a Private Network, if you wish. On the Scaleway console, you can select a [reserved IP](/ipam/how-to/reserve-ip/) to use when attaching a Public Gateway to a Private Network. Otherwise, use the default behaviour where IPAM auto-assigns an IP address from the Private Network's CIDR block to the Public Gateway at the moment of attachment. @@ -110,7 +110,7 @@ When you [use a dedicated method](#how-do-i-move-my-legacy-public-gateway-to-ipa For some time now, this functionality has been available via the API and developer tools only (not the Scaleway console). -[DHCP entries](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-dhcp-entries-list-dhcp-entries) could be created, belonging to a specified `GatewayNetwork` (Public Gateway / Private Network attachment), holding dynamic DHCP leases or static, user-created DHCP reservations. They have effectively allowed the Public Gateway to assign certain IP addresses to certain resources on the Private Network. +[DHCP entries](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-dhcp-entries-list-dhcp-entries) could be created, belonging to a specified `GatewayNetwork` (Public Gateway / Private Network attachment), holding dynamic DHCP leases or static, user-created DHCP reservations. They have effectively allowed the Public Gateway to assign certain IP addresses to certain resources on the Private Network. **DHCP entries do not exist in v2 of the API**. Instead, you can rely on the default IPAM/DHCP functionality as described [above](#background-dhcp-and-ipam). The default behavior will auto-assign IP addresses to resources on the Private Network from the network's CIDR block, or you can use the IP reservation functionality to specify the IP address(es) to assign to each resource. @@ -134,7 +134,7 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also - **8 April 2025 - 1 Nov 2025: Migration period**: You have a six month migration period to complete the following actions - Ensure that your Public Gateway is in [IPAM mode](/public-gateways/concepts/#ipam). Only IPAM mode gateways are compatible with v2. - - Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + - Put any non-IPAM mode ([legacy](/public-gateways/concepts/#ipam)) Public Gateways in IPAM-mode, by using the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). - Ensure that [DHCP is activated](/vpc/how-to/activate-dhcp/) on all Private Networks attached to your IPAM-mode Public Gateways. - Update any code or scripts you have that call version 1 of the Public Gateways API, so that they call version 2 instead. This includes removing any use of the DHCP entries, DHCP objects or address fields as mentioned above. @@ -154,7 +154,7 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also - Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode: - - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). + - **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md). - **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above). @@ -163,7 +163,7 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also You can do this in several ways: - Use the **Move to IPAM mode** button in the console - - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). + - Use the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateways/v1/#path-gateways-put-a-public-gateway-in-ipam-mode). - Use the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) ### What happens when I move my legacy Public Gateway to IPAM mode? @@ -174,7 +174,7 @@ We will detach your Public Gateway from all attached Private Networks, and reatt If you only manage your gateway via the Scaleway console, you do not need to take any action once your gateway is in IPAM mode. -If you have any code or scripts that call v1 of the Scaleway Public Gateways API, you must update these to point towards [v2](https://www.scaleway.com/en/developers/api/public-gateway/) before 1 Nov 2025. +If you have any code or scripts that call v1 of the Scaleway Public Gateways API, you must update these to point towards [v2](https://www.scaleway.com/en/developers/api/public-gateways/) before 1 Nov 2025. ### What if I want to keep using my custom gateway DHCP configuration from v1 of the API? @@ -211,7 +211,7 @@ If you have any questions, get in touch with us on the `#public-gateway` channel The following documentation resources may be useful to you: -- [Public Gateway API Documentation](https://www.scaleway.com/en/developers/api/public-gateway/) +- [Public Gateway API Documentation](https://www.scaleway.com/en/developers/api/public-gateways/) - [Public Gateway Main Documentation](https://www.scaleway.com/en/docs/public-gateways/) - [IPAM API Documentation](https://www.scaleway.com/en/developers/api/ipam/) - [IPAM Main Documentation](https://www.scaleway.com/en/docs/ipam/) diff --git a/pages/public-gateways/troubleshooting/gateway-services-not-working.mdx b/pages/public-gateways/troubleshooting/gateway-services-not-working.mdx index 2509cc3eca..a55e1b1337 100644 --- a/pages/public-gateways/troubleshooting/gateway-services-not-working.mdx +++ b/pages/public-gateways/troubleshooting/gateway-services-not-working.mdx @@ -18,7 +18,7 @@ First, check whether the gateway is properly plugged into the Private Network. W 1. Identify the Private Network's network interface on your Instance (which is attached to a Public Gateway). We will use `priv0` as an example. 2. Set it as `UP` to be able to use it: `ip link set priv0 up` -3. Identify the MAC address of the gateway in your Private Network using either the [Scaleway console](https://console.scaleway.com/) or the [API](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateway-networks) (`mac_address` field of the GatewayNetwork). We'll use `02:00:b1:ac:ca:fe` as an example. +3. Identify the MAC address of the gateway in your Private Network using either the [Scaleway console](https://console.scaleway.com/) or the [API](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateway-networks) (`mac_address` field of the GatewayNetwork). We'll use `02:00:b1:ac:ca:fe` as an example. 4. Go [here](https://ben.akrin.com/?p=1347), and paste the MAC address to get the IPv6 Link-Local Address of your gateway. In our example, using priv0, it is `fe80::000:b1ff:feac:cafe` 5. From your Instance, ping the gateway on its IPv6 link-local address, taking care to specify the Private Network interface. In our example, using `priv0`, the command is `ping fe80::000:b1ff:feac:cafe%priv0`. diff --git a/pages/queues/index.mdx b/pages/queues/index.mdx index b576c29eb0..5aad3e1516 100644 --- a/pages/queues/index.mdx +++ b/pages/queues/index.mdx @@ -60,7 +60,7 @@ description: Explore Scaleway Queues. Simplify your microservice workflows with productLogo="cli" title="Queues API" description="Manage Queues using the Scaleway APIs." - url="https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/" + url="https://www.scaleway.com/en/developers/api/queues/sqs-api/" label="Go to Scaleway Queues API" /> diff --git a/pages/queues/menu.ts b/pages/queues/menu.ts index f038096ca7..bd0103c24e 100644 --- a/pages/queues/menu.ts +++ b/pages/queues/menu.ts @@ -42,7 +42,7 @@ export const queuesMenu = { items: [ { label: 'Queues API Reference', - slug: 'https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/', + slug: 'https://www.scaleway.com/en/developers/api/queues/sqs-api/', }, { label: 'Connecting Queues to the AWS-CLI', diff --git a/pages/serverless-sql-databases/index.mdx b/pages/serverless-sql-databases/index.mdx index d903aa35bd..c84e643d8a 100644 --- a/pages/serverless-sql-databases/index.mdx +++ b/pages/serverless-sql-databases/index.mdx @@ -48,7 +48,7 @@ description: Introduction to Scaleway's serverless SQL database solutions, featu productLogo="cli" title="Serverless SQL Databases API" description="Manage Serverless SQL Databases using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/serverless-databases/" + url="https://www.scaleway.com/en/developers/api/serverless-sql-databases/" label="Go to Serverless SQL Databases API" /> diff --git a/pages/serverless-sql-databases/menu.ts b/pages/serverless-sql-databases/menu.ts index 33ec2d1a66..0c07ab9d56 100644 --- a/pages/serverless-sql-databases/menu.ts +++ b/pages/serverless-sql-databases/menu.ts @@ -59,7 +59,7 @@ export const serverlessSqlDatabasesMenu = { items: [ { label: 'Serverless SQL Database API Reference', - slug: 'https://www.scaleway.com/en/developers/api/serverless-databases/', + slug: 'https://www.scaleway.com/en/developers/api/serverless-sql-databases/', }, { label: 'Importing data into Serverless SQL Databases', diff --git a/pages/site-to-site-vpn/index.mdx b/pages/site-to-site-vpn/index.mdx index 3ad03f6a22..1347f915eb 100644 --- a/pages/site-to-site-vpn/index.mdx +++ b/pages/site-to-site-vpn/index.mdx @@ -51,7 +51,7 @@ noindex: true productLogo="cli" title="Site-to-Site VPN APIs" description="Manage Site-to-Site VPN using the Scaleway API." - url="https://www.scaleway.com/en/developers/api/s2s-vpn/" + url="https://www.scaleway.com/en/developers/api/site-to-site-vpn/" label="Go to Scaleway Site-to-Site VPN API" /> diff --git a/pages/topics-and-events/index.mdx b/pages/topics-and-events/index.mdx index b04cfbfecc..7c3660f2b9 100644 --- a/pages/topics-and-events/index.mdx +++ b/pages/topics-and-events/index.mdx @@ -60,7 +60,7 @@ description: Explore Scaleway Topics and Events. Simplify your microservice work productLogo="cli" title="Topics and Events APIs" description="Manage Topics and Events using the Scaleway APIs." - url="https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/" + url="https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/" label="Go to Scaleway Topics and Events API" /> diff --git a/pages/topics-and-events/menu.ts b/pages/topics-and-events/menu.ts index 475865cc2c..568e319beb 100644 --- a/pages/topics-and-events/menu.ts +++ b/pages/topics-and-events/menu.ts @@ -46,7 +46,7 @@ export const topicsAndEventsMenu = { items: [ { label: 'Topics and Events API Reference', - slug: 'https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/', + slug: 'https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/', }, { label: 'Connecting Topics and Events to the AWS-CLI', diff --git a/pages/topics-and-events/reference-content/topics-and-events-overview.mdx b/pages/topics-and-events/reference-content/topics-and-events-overview.mdx index 927578a6da..d2ff5eab43 100644 --- a/pages/topics-and-events/reference-content/topics-and-events-overview.mdx +++ b/pages/topics-and-events/reference-content/topics-and-events-overview.mdx @@ -27,7 +27,7 @@ Scaleway Topics and Events makes it easy to migrate your existing SNS-connected - [Serverless Functions](https://www.scaleway.com/en/serverless-functions/) - Scaleway queues in the same [Project](/organizations-and-projects/concepts/#project) - Refer to the [developers documentation](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sns-api/) for more information. + Refer to the [developers documentation](https://www.scaleway.com/en/developers/api/topics-and-events/sns-api/) for more information. ## Topics and Events credentials diff --git a/pages/vpc/reference-content/dns.mdx b/pages/vpc/reference-content/dns.mdx index 646ff58340..46f597d9e4 100644 --- a/pages/vpc/reference-content/dns.mdx +++ b/pages/vpc/reference-content/dns.mdx @@ -54,9 +54,9 @@ The DNS service resolves the following formats: The `resource_uuid` does not generally correspond to the ID of the principal resource (e.g. Instance, Elastic Metal server, Public Gateway), but rather to the ID of the sub-resource that facilitates the attachment to the Private Network. For example: -- Instances: `resource_uuid` corresponds to the [Private NIC](https://www.scaleway.com/en/developers/api/instance/#path-private-nics-list-all-private-nics) ID +- Instances: `resource_uuid` corresponds to the [Private NIC](https://www.scaleway.com/en/developers/api/instances/#path-private-nics-list-all-private-nics) ID - Elastic Metal: `resource_uuid` corresponds to the ID of the [Server-to-Private Network mapping](https://www.scaleway.com/en/developers/api/elastic-metal/private-network-api/#path-private-networks-add-a-server-to-a-private-network) -- Public Gateways: `resource_uuid` corresponds to the [GatewayNetwork](https://www.scaleway.com/en/developers/api/public-gateway/#path-gateway-networks-list-public-gateway-connections-to-private-networks) ID. +- Public Gateways: `resource_uuid` corresponds to the [GatewayNetwork](https://www.scaleway.com/en/developers/api/public-gateways/#path-gateway-networks-list-public-gateway-connections-to-private-networks) ID. DNS cannot resolve or forward queries between different VPCs. It can only resolve hostnames for resources within the same VPC, though they may be on different Private Networks within that VPC. diff --git a/pages/vpc/reference-content/vpc-migration.mdx b/pages/vpc/reference-content/vpc-migration.mdx index c4ebf9ceb1..3bb91e2cf7 100644 --- a/pages/vpc/reference-content/vpc-migration.mdx +++ b/pages/vpc/reference-content/vpc-migration.mdx @@ -85,7 +85,7 @@ If you fall into one of the cases where DHCP is not automatically activated for See the dedicated documentation on [activating DHCP](/vpc/how-to/activate-dhcp/) -Any static DHCP reservations (static leases) configured via a Public Gateway have been transparently migrated. Going forward, [DHCP reservations via the Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateway/) and other developer tools are deprecated but still available via the API, to avoid breaking changes. They are no longer available via the console. We strongly recommend that you use our IPAM product to [reserve](/ipam/how-to/reserve-ip/) and manage your IP addresses. +Any static DHCP reservations (static leases) configured via a Public Gateway have been transparently migrated. Going forward, [DHCP reservations via the Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateways/) and other developer tools are deprecated but still available via the API, to avoid breaking changes. They are no longer available via the console. We strongly recommend that you use our IPAM product to [reserve](/ipam/how-to/reserve-ip/) and manage your IP addresses. ## Aspect 3: DNS on Private Networks @@ -131,7 +131,7 @@ The general availability of VPC brings the following changes to our developer to **API** - The VPC v1 zoned API (which actually only concerns Private Networks and not VPC as it is now understood) will keep working, but is deprecated and has been moved to read only. The VPC v2 API, covering both VPCs and Private Networks with regional scope and DHCP, is the new default API. Note that in the [VPC API documentation](https://www.scaleway.com/en/developers/api/vpc/), you can select v1 or v2 from the drop-down menu at the top to navigate between the two versions. -- [DHCP reservations via the Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateway/) are deprecated but still available, to avoid breaking changes. IP reservations are also available through [the IPAM API](https://www.scaleway.com/en/developers/api/ipam/). +- [DHCP reservations via the Public Gateway API](https://www.scaleway.com/en/developers/api/public-gateways/) are deprecated but still available, to avoid breaking changes. IP reservations are also available through [the IPAM API](https://www.scaleway.com/en/developers/api/ipam/). **CLI** - As the CLI does not support multiple versions of an API, new and future versions will drop the VPC v1 API in favor of v2. diff --git a/tutorials/create-serverless-scraping/index.mdx b/tutorials/create-serverless-scraping/index.mdx index d853f6f255..f34aae688a 100644 --- a/tutorials/create-serverless-scraping/index.mdx +++ b/tutorials/create-serverless-scraping/index.mdx @@ -146,8 +146,8 @@ For the purposes of this tutorial, we show how to provision all resources via Te If you do not want to use Terraform/OpenTofu, you can also create the required resources via the [console](https://console.scaleway.com/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), or any other [developer tool](https://www.scaleway.com/en/developers/). Remember that if you do so, you will need to set up environment variables for functions as previously specified. The following documentation may help create the required resources: -- **Scaleway Queues resources**: [console documentation](/queues/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/) -- **Managed Database for PostgreSQL**: [console documentation](/managed-databases-for-postgresql-and-mysql/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) +- **Scaleway Queues resources**: [console documentation](/queues/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/queues/sqs-api/) +- **Managed Database for PostgreSQL**: [console documentation](/managed-databases-for-postgresql-and-mysql/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/) - **Serverless Functions**: [console documentation](/serverless-functions/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/serverless-functions/) - **Serverless Functions triggers**: [console documentation](/serverless-functions/how-to/add-trigger-to-a-function/) | [API documentation](https://www.scaleway.com/en/developers/api/serverless-functions/#path-triggers-list-all-triggers) diff --git a/tutorials/deploy-meilisearch-instance/index.mdx b/tutorials/deploy-meilisearch-instance/index.mdx index 0b0a84ca52..3929dbbecb 100644 --- a/tutorials/deploy-meilisearch-instance/index.mdx +++ b/tutorials/deploy-meilisearch-instance/index.mdx @@ -166,7 +166,7 @@ If you have created your Instance within a **Private Network** or if you are usi - Move your Instance inside a [Private Network](/instances/how-to/use-private-networks/) if you do not want it to be exposed publicly on the internet - Configure regular data backups using [Meilisearch Snapshots](https://www.meilisearch.com/docs/learn/advanced/snapshots/) or [Instances snapshots](/block-storage/how-to/create-a-snapshot/) -- **Fine-tune deployment configuration** such as [Instance type or disk size](/instances/reference-content/choosing-instance-type/), from the [Scaleway console](https://console.scaleway.com/instance/servers/), [the Scaleway API](https://www.scaleway.com/en/developers/api/instance/), [CLI](/instances/api-cli/cli-cheatsheet/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/instance_server/), or [OpenTofu](https://search.opentofu.org/provider/opentofu/scaleway/latest). +- **Fine-tune deployment configuration** such as [Instance type or disk size](/instances/reference-content/choosing-instance-type/), from the [Scaleway console](https://console.scaleway.com/instance/servers/), [the Scaleway API](https://www.scaleway.com/en/developers/api/instances/), [CLI](/instances/api-cli/cli-cheatsheet/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/instance_server/), or [OpenTofu](https://search.opentofu.org/provider/opentofu/scaleway/latest). ## Troubleshooting diff --git a/tutorials/manage-instances-with-terraform-and-functions/index.mdx b/tutorials/manage-instances-with-terraform-and-functions/index.mdx index 5c4959c30c..ae2a7667d3 100644 --- a/tutorials/manage-instances-with-terraform-and-functions/index.mdx +++ b/tutorials/manage-instances-with-terraform-and-functions/index.mdx @@ -133,7 +133,7 @@ This tutorial will simulate a project with a production environment running all For this example we will use the native python library `urllib`, which allows us to keep the package slim. - All information about the Instance API can be found in the [developers documentation](https://www.scaleway.com/en/developers/api/instance/#path-instances). + All information about the Instance API can be found in the [developers documentation](https://www.scaleway.com/en/developers/api/instances/#path-instances). diff --git a/tutorials/postman-api/index.mdx b/tutorials/postman-api/index.mdx index 78ed166ca5..763ebe59d1 100644 --- a/tutorials/postman-api/index.mdx +++ b/tutorials/postman-api/index.mdx @@ -50,7 +50,7 @@ In this tutorial, you will learn how to import Scaleway APIs into Postman, confi 2. Enter a name and description and select a visibility setting for your workspace. Your workspace displays. 3. Go to the Scaleway [developers website](https://www.scaleway.com/en/developers/) and select a product API to download. - In this tutorial, we use the [Scaleway Instances API](https://www.scaleway.com/en/developers/api/instance/). + In this tutorial, we use the [Scaleway Instances API](https://www.scaleway.com/en/developers/api/instances/). 4. Click **Download OpenAPI**. 5. Click **Collections** > **Import** in the side menu of the Postman interface. @@ -113,7 +113,7 @@ In this tutorial, we will create an Instance through an API request operated wit 5. Edit the parameters in the request with your preferences following the example below. In this tutorial, we will create a GP1-M Instance with the default local volume. - - For more information on how to fill out the parameters, refer to the [Scaleway Developers website](https://www.scaleway.com/en/developers/api/instance/#path-instances-create-an-instance). + - For more information on how to fill out the parameters, refer to the [Scaleway Developers website](https://www.scaleway.com/en/developers/api/instances/#path-instances-create-an-instance). - To find the image UUID, [follow this procedure](/instances/faq/#what-is-a-marketplace-image). diff --git a/tutorials/upgrade-managed-postgresql-database/index.mdx b/tutorials/upgrade-managed-postgresql-database/index.mdx index 8409536c06..d60f60c86c 100644 --- a/tutorials/upgrade-managed-postgresql-database/index.mdx +++ b/tutorials/upgrade-managed-postgresql-database/index.mdx @@ -403,4 +403,4 @@ This solution enables you to migrate your database(s) automatically, with a bash The script will guide you through the migration process, asking you to complete the necessary information for your migration as required. -You now have successfully migrated your managed PostgreSQL database(s) to version 13 of the database engine. For more information about all new features and improvements in this version refer to the [PostgreSQL release notes](https://www.postgresql.org/docs/release/) and the [official documentation](https://www.postgresql.org/docs/). To learn more about Scaleway's powerful REST-API, refer to our [developers' documentation](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/). \ No newline at end of file +You now have successfully migrated your managed PostgreSQL database(s) to version 13 of the database engine. For more information about all new features and improvements in this version refer to the [PostgreSQL release notes](https://www.postgresql.org/docs/release/) and the [official documentation](https://www.postgresql.org/docs/). To learn more about Scaleway's powerful REST-API, refer to our [developers' documentation](https://www.scaleway.com/en/developers/api/managed-databases-for-postgresql-and-mysql/). \ No newline at end of file